Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add frame rate to mezzanine text annotation & QR code #21

Closed
nicholas-fr opened this issue Jan 4, 2021 · 8 comments
Closed

Add frame rate to mezzanine text annotation & QR code #21

nicholas-fr opened this issue Jan 4, 2021 · 8 comments
Assignees
Labels
agreed-needs-implementation Agreed, just needs to be completed

Comments

@nicholas-fr
Copy link
Collaborator

nicholas-fr commented Jan 4, 2021

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.

@jpiesing
Copy link

jpiesing commented Jan 4, 2021

@yanj-github Does this proposal look OK to you?

@yanj-github
Copy link

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).

@nicholas-fr
Copy link
Collaborator Author

nicholas-fr commented Jan 5, 2021

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.

@jpiesing jpiesing assigned jpiesing and nicholas-fr and unassigned jpiesing Jan 5, 2021
@jpiesing
Copy link

jpiesing commented Jan 5, 2021

Jan 5th meeting
Next steps
TP Vision to re-generate the mezzanine content.

@yanj-github
Copy link

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?

@nicholas-fr
Copy link
Collaborator Author

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:
vlcsnap-2021-01-20-15h38m29s889

Example for 30000/1001:
vlcsnap-2021-01-20-15h33m55s935

@yanj-github
Copy link

Thanks @nicholas-fr, they both look good to me and can be decoded correctly. Thank you very much!

@nicholas-fr nicholas-fr added the agreed-needs-implementation Agreed, just needs to be completed label Jan 25, 2021
@nicholas-fr
Copy link
Collaborator Author

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
agreed-needs-implementation Agreed, just needs to be completed
Projects
None yet
Development

No branches or pull requests

3 participants