problem parsing mediainfo (2 Viewers)

[TheNavvie]

I've got the same issue, again with files created using Handbrake. The MediaInfo GUI does not pick up the bitrate for the video stream in the MKV container.

This issue crept in when Handbrake offered a "same as source" option on the frame rate, which I believe marks the files as having a variable frame rate? Or maybe when I started using vbv-bufsize and maxrate.

I've tried re-muxing these files through mkvmerge etc with no luck.

Edit/added info.
Mediainfo GUI is not able to determine the run time for the files that handbrake produces. I need to do more testing to get to the bottom of this.

 

[TheNavvie]

Solved this...

The problem is mediainfo is not very good at handling files that are variable framerate that Handbrake produces. You can try this out yourself, pick an source and encode just 10 seconds of it. In the "video" tab leave the default as "variable framerate", check it with mediainfo and it won't be able to determine the length of the file. Now change the output to be "constant framerate", check again in mediainfo and it can correctly determine the frame rate.

As far as I am concerned I do not need to know the exact length of the title down to the millisecond. Mediainfo should be able to "guess" what the correct constant framerate is for a variable frame rate file... if the frame rate varies from 23.978 to 23.974... chances are the framerate *should be* 23.976.

Problem is mediainfo will blame the handbrake devs and they will blame mediainfo.

 

[RoChess]

Solved this...

The problem is mediainfo is not very good at handling files that are variable framerate that Handbrake produces. You can try this out yourself, pick an source and encode just 10 seconds of it. In the "video" tab leave the default as "variable framerate", check it with mediainfo and it won't be able to determine the length of the file. Now change the output to be "constant framerate", check again in mediainfo and it can correctly determine the frame rate.

As far as I am concerned I do not need to know the exact length of the title down to the millisecond. Mediainfo should be able to "guess" what the correct constant framerate is for a variable frame rate file... if the frame rate varies from 23.978 to 23.974... chances are the framerate *should be* 23.976.

Problem is mediainfo will blame the handbrake devs and they will blame mediainfo.

My experience with the MediaInfo developers listning to suggestions has been excellent, so don't be discouraged to start a ticket at their SourceForge project site. In the end they still need to report the correct runtime, which should be available as-is in the header actually, so that might be a very bad Handbrake bug then, but perhaps MediaInfo is still willing to apply a rough estimate calculation based on your suggestion of the average framerate.

 

[borgster]

My experience is that Media info is reading the data. If I right click the file I get the data. If I use any of a number of media programs that read the data they all read it correctly, including Myfilms, Tiny Media Manager, and others. It only seems to be MP-TV series that has the issues, Even Moving Pictures is reading the file correctly, at least as far as runtime and that. In other words, it works for me in all the other programs, just not MP-TVseries.

 

[RoChess]

My experience is that Media info is reading the data. If I right click the file I get the data. If I use any of a number of media programs that read the data they all read it correctly, including Myfilms, Tiny Media Manager, and others. It only seems to be MP-TV series that has the issues, Even Moving Pictures is reading the file correctly, at least as far as runtime and that. In other words, it works for me in all the other programs, just not MP-TVseries.

Are you able to create a small 1-3MB avi/mp4/mkv/etc sample from that large movie that contains the same problem? Seems you can generate them yourself with handbrake, so the smallest sample you can make that shows the problem (really small resolution with high compression, etc) would then allow you to add it as an attachment and then @ltfearme can then use that to properly fix things.

Without ability for developer to repeat the problem, it is usually a daunting task they ignore and focus on their large list of other things to work on. So the quicker you can provide a small sample file that showcases the 'bug', the quicker it will be fixed in the next release of MP-TVSeries.

Enjoy.

 

[wonkyd]

I did report this to the mediainfo revs but they said it was handbrakes fault. https://forum.team-mediaportal.com/...ash-rate-correctly.114972/page-2#post-1037487

If you drop back to 0.7.58 it'll all work again.

 

[JiRo]

I did report this to the mediainfo revs but they said it was handbrakes fault. https://forum.team-mediaportal.com/...ash-rate-correctly.114972/page-2#post-1037487

If you drop back to 0.7.58 it'll all work again.

I add... 7.58 or 7.68. Bewteen these versions is a "black hole"!

Same problem by using MovingPicture and/or MP-TV Series configuration and MediPortal 1.6 with MediaInfo.dll 7.61. Both plugins configuration crashed by parsing some mkv files. The same files I tried open by the same MediaInfo GUI version (7.58, 7.61 and 7.68) and it behave identically! 7.61 crashed, 7.53 and 7.68 performed well.

Now I copied MediaInfo.dll 7.68 into MediaPortal 1.6 program directory and everything are working well!