I know the wrong fps param of xml.
Look at help from BDSup2Sub 5.1.2:
https://github.com/mjuhasz/BDSup2Sub/wiki
Supported formats.
The culprit is the
Sony BDN XML format that only knows
integer fps.
Mjuhasz wrote:
Quote:
|
Note: although the BDN XML looks pretty straight forward and clean, the timing information in this format is a little weird for unknown reasons. Indeed the timings are always based on an integer frame rate.
|
The parameter
--convert-fps 24p,24p is set in v0.56 and 24p symbol means 23.976 fps. The BDN xml is always converted to real 24 fps! (x 1.001)
In v0.61 is no parameter --convert-fps and BDSup2Sub thinks it is 25 fps standard. So the time stamps are
untouched 23.976 fps.
Using this with .3dp results in asynchronous depth values.