FCPX 11.0 on Mac Studio M2 Ultra - exports grinding down to a halt when using BRAWToolbox

[localproductions-au]

Hi there

Got a new mac studio and when applying BRAWToolBox to BRAW clips the CPU activity is crippled during exports. It eventually exports but the grinding time makes it unusable.

90sec clip takes +20mins to render/export.

Do we need to update anything?

Thanks

[latenitefilms]

Unfortunately I can't see your screenshot.

What version of Final Cut Pro? What version of macOS? What version of BRAW Toolbox? What decode quality?

There have been some reports of performance issues with Final Cut Pro 11 - see:

https://fcp.cafe/update-guide/#final-cut-pro-11

...however, you're the first person to report anything with BRAW Toolbox.

There shouldn't be much being done on the CPU to be honest - BRAW Toolbox's BRAW support is mostly done on the GPU.

Do you have any effects applied to the BRAW Toolbox clips? For example, I've heard some reports of ColorFinale having issues on Final Cut Pro 11, but nothing confirmed yet...

[localproductions-au]

Hi Chris 🙂 FCPX 11.0 Decode Automatic (UltraHD) Thanks heaps for any suggestions [Screenshot 2024-11-21 at 3.44.04 pm.png] [Screenshot 2024-11-21 at 3.24.12 pm.png] [Screenshot 2024-11-20 at 10.37.17 pm.png] On 21 Nov 2024, at 3:39 pm, Chris Hocking ***@***.***> wrote: Unfortunately I can't see your screenshot. What version of Final Cut Pro? What version of macOS? What version of BRAW Toolbox? What decode quality? There have been some reports of performance issues with Final Cut Pro 11 - see: https://fcp.cafe/update-guide/#final-cut-pro-11 ...however, you're the first person to report anything with BRAW Toolbox. There shouldn't be much being done on the CPU to be honest - BRAW Toolbox's BRAW support is mostly done on the GPU. Do you have any effects applied to the BRAW Toolbox clips? For example, I've heard some reports of ColorFinale having issues on Final Cut Pro 11, but nothing confirmed yet... — Reply to this email directly, view it on GitHub<#195 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BNDOA6TZFEUUOIKZRA4X52T2BVPXZAVCNFSM6AAAAABSGB5LZOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOJQGA3DGNJRGA>. You are receiving this because you authored the thread.Message ID: ***@***.***> - - - Alexander Harkness Local Productions Design | Deliver | Inspire localproductions.com.au [LP-Logo-Green-25x25px-sRGB.gif]

[latenitefilms]

Unfortunately I still can't see your screenshots. You might have to upload them via the GitHub website, as opposed to via email.

Visit: #195

[localproductions-au]

Here are the pix Chris - yes I have 'fresh face' applied to some of the clips

I thought I'd uninstall and reinstall and got this additional message

Thanks in advance for any suggestions

[latenitefilms]

Uninstalling will trash the security-scope bookmarks, so you'll need to make sure you grant sandbox access to the drive(s) that contain your BRAW clips after running uninstall, if you're working with old projects.

See: https://brawtoolbox.io/relinking/

macOS Sequoia now has increased security, so you'll need to give the Uninstall tool Full Disk Access to uninstall these files.

[localproductions-au]

I was thinking if I uninstall/reinstall BRTB would update to the latest version If the latest version is already 1.40 (70) then there’s no need to uninstall right? GPU/CPU I’m totally in the dark on, but does that CPU activity screenshot from Activity Monitor look normal to you? Seems like a lot of % being absorbed by BRTB - wasn’t sure if that’s normal? Thanks Alex On 22 Nov 2024, at 12:55 pm, Chris Hocking ***@***.***> wrote: Uninstalling will trash the security-scope bookmarks, so you'll need to make sure you grant sandbox access to the drive(s) that contain your BRAW clips after running uninstall, if you're working with old projects. See: https://brawtoolbox.io/relinking/ macOS Sequoia now has increased security, so you'll need to give the Uninstall tool Full Disk Access to uninstall these files. — Reply to this email directly, view it on GitHub<#195 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BNDOA6XDCXWBTDSTZ3GCW332B2FJNAVCNFSM6AAAAABSGB5LZOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOJSG4YTEMJZGI>. You are receiving this because you authored the thread.Message ID: ***@***.***> - - - Alexander Harkness Local Productions Design | Deliver | Inspire localproductions.com.au [LP-Logo-Green-25x25px-sRGB.gif]

[latenitefilms]

The latest version of BRAW Toolbox on the Mac App Store is v1.4.1 (71). You can update through the Mac App Store application.

The Blackmagic RAW SDK will try and make full use of your system's resources - so whilst most of the work is done on the GPU, on a Mac Studio with lots of CPU cores, it'll also utilise whatever it can get its hands on - so I THINK what you're seeing is probably normal. I'd be more curious to see what the GPU History shows in Activity Monitor - hopefully it's also heavily utilising the GPU.

Really though, looking at your screenshot, your Mac Studio is really using up very little CPU resources - it's only a few CPU cores that are showing heavy use:

[localproductions-au]

Yes - I saw overall system utilisation was low in the screenshot It’s the extraordinary processing time that I was concerned about vs pure prores or hevc clips Your suggestion that additional FX were contributing makes sense as there were a few in play Sometime I’ll reduce them one by one and recheck render times Know any good tutorials on creating a Compressor Render Farm (eg: macbook pro 2021, macmini2021, mac studio?) I can never seem to input an IP for daisy chained devices that Compressor sees 🙄 Many thanks Alex On 22 Nov 2024, at 5:00 pm, Chris Hocking ***@***.***> wrote: The latest version of BRAW Toolbox on the Mac App Store is v1.4.1 (71). You can update through the Mac App Store application. The Blackmagic RAW SDK will try and make full use of your system's resources - so whilst most of the work is done on the GPU, on a Mac Studio with lots of CPU cores, it'll also utilise whatever it can get its hands on - so I THINK what you're seeing is probably normal. I'd be more curious to see what the GPU History shows in Activity Monitor - hopefully it's also heavily utilising the GPU. Really though, looking at your screenshot, your Mac Studio is really using up very little CPU resources - it's only a few CPU cores that are showing heavy use: image.png (view on web)<https://github.com/user-attachments/assets/da183d02-cb2d-4411-825b-cb2ada3ad349> — Reply to this email directly, view it on GitHub<#195 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BNDOA6QIG45TCAIAGTHECGD2B3B7XAVCNFSM6AAAAABSGB5LZOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOJSHEZTGMBTGE>. You are receiving this because you authored the thread.Message ID: ***@***.***> - - - Alexander Harkness Local Productions Design | Deliver | Inspire localproductions.com.au [LP-Logo-Green-25x25px-sRGB.gif]