I know there were a couple of topics on the MC16 board a few months back about this. I don't know if this entry on the list of changes for beta 46
6. NEW: Rewritten video import -- gets compression and frame rate for almost all videos and runs around 40% faster.
was supposed to help, but I'm still having problems with the FPS field. I did a 'refresh library from tags' for all the target files, after installing beta 46. The resulting FPS contains every 'normal' (or not) FPS value a number of times. 12 entries for '25', 28 for '29.97' and so on.
If I build a smartlist and aim for list all videos with FPS = 25 I get a number that does not much the number of videos shown if I select in Standard view all the '25' in the FPS field.
It's unmanageable if I wanna make a decision based on framerate (say create folders with PAL content, as a random example).
What's going on, that FPS value is detected with a various number of decimals, rounded up for display purposes to 2 decimals, but internally MC thinks they have that just a bit different FPS, hence showing an entry for each? For all the files that MC puts in multiple 25 or 29.97 entries, MediaInfo detects the same, consistent value, either 25.000 for all '25', or 29.970 for all '29.70'. So why multiple entries in MC? Are these values returned from the header of files or after being sent through a DirectShow chain?
