lol they ask you to a lot of trouble like: outcome from mediainfo.
And a few posts later: did you ever try the candidate version r4824 firmware

Billie how do you want people to fix things, if they dont know what you put into the mashine, Handbrake can be used in many ways.

I get that, but let's try the latest software first....

While this may fix the problem of files encoded with Handbrake 0.9.5, I would still consider that Handbrake 0.9.5 is still "broken". Files encoded with 0.9.4 need not have to have the frame-rate specified, and leaving it at "same as source" had no problems.

This brings up another question - let's say I have no idea what the framerate from the source is, whether 23.97, 25, 30 or whatever. If I do not know and I specify, say, "30", will it cause the encoded file to have some slight "stutter", if the rate is different?

I will try this "fix" and see if it works on my POHD and Handbrake 0.9.5.

Yes i see your point that the 095 is broken, but still if people wants to use it, i had no problems with the program in forced mode.

If you convert a file you dont know the fps of, you could use mediainfo to show fps

But if it is from bourgt or borrowed sources like dvd or blurays it should be the framerate statet on the cover

It worked for me, i just tryed to help

Apparently the variable frame rate feature in Handbrake 0.9.5 is not a bug but rather an option of h264.
We should not expect any "correction" in HB.
Realtek-based players do not seem to be compatible ....


https://forum.handbrake.fr/viewtopic.php?f=11&t=19466


Could a new firmware solve this ?

I went to Handbrake website to see if I can find out anything more useful. I believe I have found a thread here:

https://forum.handbrake.fr/viewtopic.php?f=11&t=19466

It described the same problems we seem to be having on our POHDs, and it also says that 0.9.4 was the one that was "broken" as it didn't correctly mark the MKV files as "Frame Rate: Variable". 0.9.5 fixed this "problem", and if players do not play the new fixed MKV files then they are considered "broken players".

In any case, it seems to verify that fixing a frame rate for encoding will solve our problems here.

Will any ACRyan rep comment on this?

That would mean that AC Ryan should believe us saying there is an error, they still havent accepted the fact that the player cant play 23.976 files
But hey, the sun may shine again.

Handbrake does h.264 inside of a mkv container marginally well. Why not use a proven mkv wrapper - they are free? I am sorry if you can not use a CL interface but those are the brakes.

But the real question here is not CL or GUI, but rather : does POHD/realtek support variable frame rate ? Maybe you could test this with your software ? If you could produce a vfr-file that POHD plays then we could start looking for the probem elsewhere.