x264 incompatible with LG BluRay player

[Bart Z Lederman]

Well, I already tried 59.99 to try to get as close as possible to the value you
gave, and it works.  The setting panel for Resample FPS only goes to two
digits.

It's true that a lot of old material is at 29.97 fps to match NTSC Color,
and twice that would be 59.94: which could be a good setting. But
Digital TV seems to have gotten away from that.  The various devices
I have with video output like DVR boxes and the digital cable box I
used to have appear to run at an actual 60 FPS, according to what
VirtualDub measures and reports.  I see conflicting information at
the various reference sites I've checked, but the ATSC standard
allows for various scan rates up to an exact 60 FPS.  And since the
resulting video is being processed by a computer program, the exact
frame rate doesn't matter much.  I also got one of the 'standards'
from the ATSC.org web site, and it says anything up to 60 FPS is
O.K., but not to exceed that value.  That could explain why LG doesn't
work past 60, the standard for TV says "don't do that".  Another
article lists this for ATSC and DVB:

    23.976 Hz (film-looking frame rate compatible with NTSC clock speed standards)
    24 Hz (international film and ATSC high-definition material)
    25 Hz (PAL film, DVB standard-definition and high-definition material)
    29.97 Hz (NTSC film and standard-definition material)
    30 Hz (NTSC film, ATSC high-definition material)
    50 Hz (DVB high-definition material)
    59.94 Hz (ATSC high-definition material)
    60 Hz (ATSC high-definition material)


Anyway, the MediaInfo reports the video I encoded as 59.99
as "Constant 60".  This works on the LG and Roku and everything
else I tested, so I'm satisfied: though I will probably use 59.94
in the future.

I don't think "Change FPS" would be necessary.  I can try that, and
I have used it in the past, but I don't think duration needs to be
changed.  When I play back videos at 60 FPS the motion of objects
appears correct, the pitch of the sounds is correct, and the duration
of the overall video appears correct: though I doubt if anyone would
see a significant difference between 60.00 and 59.99 or 59.94 .

If the video was going to be re-broadcast over a commercial TV station,
I would be more concerned about the exact timing.  For watching it at
home, this will be fine.  I'm satisfied that just dropping the frame rate
a tiny amount is a good solution to the problem.

Thanks for all your effort on this matter.

Now, I just wonder why nobody else has reported a problem editing
videos created by VirtualDub.  It's a fairly popular program.

[eumagga0x2a]

I hope that

[coreMuxer,coreUtils,coreVideoEncoder] Try to avoid accumulation of rounding errors in time increment to frame rate conversion for standard fps values, add 60 and 59.94 fps to known standard frame rates [...]

and

[muxerGate] Use existing function for time increment to frame rate conversion to avoid rounding errors with standard fps values

together will make videos resampled to 60 fps with Avidemux really 60 fps and thus fully compatible with that LG device. Please try a future nightly.

[Bart Z Lederman]

Thanks for the update, and all of your effort.

I'll try a nightly in a day or so.

[Bart Z Lederman]

I just tried the July 5 build, and everything looks good.

The output is marked as constant 60 FPS, and the LG player
handles it with no problems.

Thanks again for all of your work.