Quote:
Originally Posted by r0lZ
(Note that I don't need the fix to use BDSup2Sub with BD3D2MK3D. I have added the "convert from 23.976 fps to 23.976 fps" arguments to the command line used by BD3D2MK3D, and it's sufficient to obtain the correct output. But is it really normal to have to do it? And do you really want to have to explain to all users that have encountered the bug that they have to force a theoretically useless frame rate conversion to obtain the correct output?)
|
I use the same line. This has been known for quite sometime and its not to bad when using it from command line. It just gets confusing to users when they open the GUI and expect it to work when FPS is deselected.