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.

Sign up for GitHub

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

Jump to bottom

Better Handling of Clips with Different Frame Rates Than Project/Timeline Frame Rate #17

Closed
latenitefilms opened this issue Jan 3, 2024 · 1 comment
Closed

Better Handling of Clips with Different Frame Rates Than Project/Timeline Frame Rate #17

latenitefilms opened this issue Jan 3, 2024 · 1 comment
Assignees
@latenitefilms
Labels
bug Something isn't working priority

Comments

@latenitefilms
Copy link
Owner

Currently I've basically just been assuming the clip frame rates are same as the project frame rate. Will need to go back and fix up the code to make sure we do the maths correctly.
@latenitefilms latenitefilms added the bug Something isn't working label Jan 3, 2024
@latenitefilms latenitefilms self-assigned this Jan 3, 2024
@latenitefilms latenitefilms added this to the v1.0.0 milestone Jan 7, 2024
@latenitefilms latenitefilms removed this from the v1.0.0 milestone Jan 16, 2024
@latenitefilms latenitefilms changed the title Better Handling of Clips with Different Frame Rates Than Project Frame Rate Better Handling of Clips with Different Frame Rates Than Project/Timeline Frame Rate Jan 17, 2024
@latenitefilms
Copy link
Owner Author

This has been fixed in FCPXMLReport.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@latenitefilms latenitefilms

Labels
bug Something isn't working priority
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@latenitefilms