2009-06-18, 02:17
ronie Wrote:Since you're stepping in for fekker lately, do you perhaps have any idea how MIP is detecting progressive or interlaced ?
You know, I remember "watching" fekker talk to himself as to how he was figuring out whether it was interlaced or progressive, but I cannot for the life of me remember what was said. It's possible that this discussion is in one of the two MIP/MMP threads...
Gamester17 Wrote:Progressive or interlaced should still be possible to set and import via NFO files right?
You should be able to enter 480i, 480p, 576i, 576p, 720i, 720p, 1080i, or 1080p in an NFO file, (either manually or via a standalone media manager that handles), and XBMC should pick it up when scraping, right?
Or...until the long-awaited return of Fekker, maybe check out the code behind MIP and see how he's writing the info to the Studio tag? Again, I remember seeing him explain how he was calculating what dimensions should be considered as what resolution, but the exact specifics are beyond me.
CapnBry Wrote:Argh. I forgot to fix the importer to pull the codec tag rather than codec, but that codec field is wrong too. It should say mpeg4. codecid probably should probably be named codectag too, gah I don't know. I need a beer.
AspectRatio is supposed to be in aspectratio too, not aspectdisplayratio. This one is probably acceptable to be fixed in xbmc though.
EDIT: But scan type I don't pull because StreamDetails doesn't have a field for that. Why? I only store information the probe can probe currently.
Here brother...have a drink on me.
I would think that aspectdisplayratio would be allright to use on the XBMC side of things.
And scantype...I understand what you're saying about not storing the stuff the probe can't do, but would it hurt to assume that the video is one or the other unless specified by the user or a .nfo file?