Closed nicholas-fr closed 3 years ago
@yanj-github Does this proposal look OK to you?
Thanks, we suggest to have "rounding to a maximum of 3 decimal places", if there will be an intention to have frame rates such as 24000/1001 fps, which is usually rounded to 23.976 (3 decimal places).
Thanks, I agree that makes sense. And in that case we would still get "29.97" and "59.94" for the 30 and 60 fps fractional rates respectively.
Jan 5th meeting Next steps TP Vision to re-generate the mezzanine content.
Thanks @nicholas-fr, I cannot check fractional rates yet, but I have checked frame rate 30, which looks fine to me. I guess we wont be able to check 3 decimal spaces for quite a bit of time, but can you kinldy confirm if it will support 3 decimal spaces please?
Thanks for the confirmation. Here are some screencaps for the fractional rates (up to 3 decimal places). Please let me know if these are also OK. If so, I'll re-encode all the streams we need for AVC and clean up the mezzanine FTP. Once that's done I'll send out an email to the group.
Example for 24000/1001:
Example for 30000/1001:
Thanks @nicholas-fr, they both look good to me and can be decoded correctly. Thank you very much!
This issue was resolved by pull request #22 as confirmed by Eurofins above.
A new batch of 15/30/60fps content (including fractional frame rates) was generated and uploaded here: WAVE mezzanine content.
This contains all the mezzanine streams required to generate the test content as described in Test Content Generation issue 13.
Old mezzanine streams were moved to the old
subfolder, with the intention of deleting them following group confirmation at the next DPCFT call.
As requested by Eurofins here I propose to extend the annotation text we have with as little extra text as possible:
HH:MM:SS.MMM;<frame #>;<framerate>
For example:
00:00:37.167;0001115;30
Rounding fractional rates to 2 decimal places, for example:
00:00:37.204;0001115;29.97
Please share any comments or preferred alternatives.