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

Final Cut Pro grinds to a halt when using Metaburner on complex projects #27

Closed
latenitefilms opened this issue Jan 5, 2024 · 2 comments
Assignees
Labels
bug Something isn't working

Comments

@latenitefilms
Copy link
Owner

For example, I applied Metaburner to a nearly 2 hour timeline of BRAW clips (using BRAW Toolbox), and Metaburner takes a good 30sec to actually render a frame. I THINK this is because we're storing the entire FCPXML internally - and FCPX is taking a long time to read the FCPXML data (and probably processed data), each frame. Will have to investigate if we can do some caching or something.

@latenitefilms latenitefilms added the bug Something isn't working label Jan 5, 2024
@latenitefilms latenitefilms self-assigned this Jan 5, 2024
@latenitefilms
Copy link
Owner Author

@randomeizer - Any recommendations on good Swift profiling frameworks?

@latenitefilms
Copy link
Owner Author

This should be fixed in next beta by using caching.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant