You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
We requently edit blackmagic raw files and some time arri raw files. We have M1 Ultra and fast Nas that can do online Edit easily so we don't need to wait for generating proxies.
We currently use Davinci Resolve to edit those files as they just work inside Reosolve, but we really missed editing on FCP.
Describe the solution you'd like
A simple support for native arri raw and blackmagic raw files.
The text was updated successfully, but these errors were encountered:
latenitefilms
changed the title
Support for native arri raw and blackmagic raw files.
Support for native ARRIRAW and Blackmagic RAW files
Dec 11, 2024
Apple announced at the 2024 FCP Creative Summit that Blackmagic will be releasing a Media Extension for Blackmagic RAW at some point - although they didn't specify a timeframe.
Now that Media Extensions are supported in macOS and Final Cut Pro 11, anyone can (in theory) write their own codec support.
So whilst it doesn't look like Apple themselves will be building a BRAW or ARRIRAW plugin anytime soon - it's entirely possible that ARRI and Blackmagic themselves might do it, or even a third party.
In the meantime, if you want BRAW in Final Cut Pro, there's always my BRAW Toolbox on the Mac App Store.
Apple Feedback Assistant ID: MISSING!
Is your feature request related to a problem? Please describe.
We requently edit blackmagic raw files and some time arri raw files. We have M1 Ultra and fast Nas that can do online Edit easily so we don't need to wait for generating proxies.
We currently use Davinci Resolve to edit those files as they just work inside Reosolve, but we really missed editing on FCP.
Describe the solution you'd like
A simple support for native arri raw and blackmagic raw files.
The text was updated successfully, but these errors were encountered: