Yes, I mean that problem.
It's been discovered that it's caused by a mismatch in reported fps to output Hz. The hardware is perfectly capable, it's just being fed wrong information. So cause is known. HiMedia just have to fix it.
Many MKV movies report 24P when they really should report 24P/1001 instead. Have seen this numerous times as this problem has been around for many years already. You may expect players to play crummy content correctly by adjusting itself to this condition but calling it a bug is not really honest. Yes it is a real bug but within the program used to create the container with.
Why do many (older) other brand players not have this problem then? This is fairly easy to answer as most of current players just support 24P/1001 and call it 24P support, this regardless if 24P or 24P/1001 is reported. There are only very few real 24P movies circulating so very few people ever notice.
Now that Q10 Pro moved to the next level supporting all frame-rates correctly including distinguishing 24P from 24P/1001 it is observed as a degradation instead of an improvement. Very understandable but not technically correct.
Mapping 24P back to 24P/1001 is a quick workaround which will bring one back to what other players are doing. In almost all cases it will have the desired effect as I repeat only few real 24P material exists. It can easily be done with a configurable auto frame-rate switch APP.
To deal correctly with this the frame-rate can be derived from the transport stream itself as a workaround. Doing so may in fact increase startup times for all movies checking for incorrect header information. If implemented that way then I hope this will be done for MKV only or made an option if performance is influenced noticeably.
You can on the other hand solve it yourself easily by correcting the container which remedies the root cause. I am clearly in favor of solving it that way. It also will make these videos play correctly with any other media player straight away.
Honestly I would prefer Himedia to provide a simple (integrated) APP which adjusts/validates the header with the correct frame-rate information. This way the problem is eradicated instead of being spread. Together with the configurable auto frame-rate switch it provides an excellent and simple solution.
Always make BD ISO's myself from MKV movies again which re-inserts correct header and picture timing information. These files never give this error. Yes I know the file grows slightly bigger as the consequence and you may loose some by BD unsupported audio and subtitle streams. Recommend using the
excellent freeware program tsMuxeR for this job. It is simple to use and is blazing fast as it never re-encodes.
By the way the whole 24P/1001, 30P/1001 and 60P/1001 confusion and standards is a leftover from the good old analog TV world with NTSC (Never The Same Color) as the US standard. Needing different carriers for the video and color signals it was implemented that way. Europe had PAL and SECAM not needing this.
