Rendering fails on 2013 Mac Pro with Dual AMD FirePro D500

[latenitefilms]

Discussed in #14

^{Originally posted by tangierc January 1, 2023}
Hello Chris. One of the things I was particularly hopeful for is just bringing in Braw video that I can use in a proxy/original workflow and allow FCP or Sync-N-Link to do my syncing using XML. A large part of this equation is being able to relink clips as needed, but BRAW Toolbox imports are don't allow me access to FCP's native reveal in browser, reveal, in finder, and relinking capabilities.

My proxies were already made using Premiere Pro and migrating the project to FCP, I wanted to link those proxies to their original counterpart using BRAW Toolbox and in the end send to Resolve for color. Would these capabilities be possible in a future update? I know this is a beta. As it stands I am unable to use BRAW Toolbox imports both due to playback and scrubbing performance issues (on an Intel Mac) and no access to FCP's native clip management features.

Thank you for all of your hard work.

[latenitefilms]

This will HOPEFULLY be fixed in the next public beta @tangierc.

[latenitefilms]

@tangierc has a 2013 Mac Pro with Dual AMD FirePro D500 and reports:

Plugin Not Responding. On a 2013 Mac Pro with Dual AMD FirePro 500 GPUs, the BRAW clip plays fine inside the workflow extension window, but once it's in the FCP library the clip displays solid green and blue frames along with bits of the video footage when scrubbing or attempting playback. Then the clip goes offline with a plugin not responding notice. This is using FCP 10.6.5.

Jamie Lejeune has a 2019 Mac Pro with 2x W5700X GPU and reports:

Dang, the new beta is actually a lot worse than the last version on my machine. Attempts at playback result in flashing green in the viewer. And then pretty quickly, sometimes within seconds, sometimes a minute or two, it locks up my entire system — not just FCP, but the whole OS. I have to do a hard restart holding down the power button to regain control. And, on that reboot, if I’m not fast enough to force quit FCP, it locks up the system all over again. I can’t even get far enough to check the implementation of the HDR.

The last beta that I was testing didn’t have any of these issues. The only hiccups was occasionally the viewer image would turn blue, but that was usually because I kept changing the parameters or toggling the effect.

[tangierc]

My FCCP prefs were trashed before this test as I am also working on a GUI responsiveness issue for large projects. The previous beta, though still having the flashing blue and green frames at times, did respond better than the current beta. I forgot to mention that I am using macOS Monterey 12.6.2 and not Ventura.

…

On Jan 14, 2023, at 12:20:03 PM, Chris Hocking ***@***.***> wrote: @tangierc <https://github.com/tangierc> has a 2013 Mac Pro with Dual AMD FirePro D500 and reports: Plugin Not Responding. On a 2013 Mac Pro with Dual AMD FirePro 500 GPUs, the BRAW clip plays fine inside the workflow extension window, but once it's in the FCP library the clip displays solid green and blue frames along with bits of the video footage when scrubbing or attempting playback. Then the clip goes offline with a plugin not responding notice. This is using FCP 10.6.5. Jamie Lejeune has a 2019 Mac Pro with 2x W5700X GPU and reports: Dang, the new beta is actually a lot worse than the last version on my machine. Attempts at playback result in flashing green in the viewer. And then pretty quickly, sometimes within seconds, sometimes a minute or two, it locks up my entire system — not just FCP, but the whole OS. I have to do a hard restart holding down the power button to regain control. And, on that reboot, if I’m not fast enough to force quit FCP, it locks up the system all over again. I can’t even get far enough to check the implementation of the HDR. The last beta that I was testing didn’t have any of these issues. The only hiccups was occasionally the viewer image would turn blue, but that was usually because I kept changing the parameters or toggling the effect. — Reply to this email directly, view it on GitHub <#25 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACJCKTWUAAZT3STFL7MKKIDWSMC7HANCNFSM6AAAAAATU5AJO4>. You are receiving this because you were mentioned.

[latenitefilms]

@tangierc - It would still be really handy to have a look at your logs and crash logs.

You can find the log files here:

/Users/YOUR-USER-NAME/Library/Group Containers/A5HDJTY9X5.com.latenitefilms.BRAWToolbox/Library/Application Support/

You can find any crash reports here (basically anything with a BRAW in the file name):

/Users/YOUR-USER-NAME/Library/Logs/DiagnosticReports

You can upload here:

https://latenitefilms.digitalpigeon.com

Are you also able to share a screenshot of the options in the Render/Share GPU dropdown in FCPX Preferences?

In the meantime, I'll have another look and try some different things - it's just tricky because I only currently have access to single GPU machines.

[tangierc]

Sure thing. I’ll prepare those things for you now.I’ve been using EtreCheck Pro also to see if I can isolate any problematic files just in case, but my system is otherwise performing well overall. Tangier

…

On Jan 14, 2023, at 1:12:12 PM, Chris Hocking ***@***.***> wrote: @tangierc <https://github.com/tangierc> - It would still be really handy to have a look at your logs and crash logs. You can find the log files here: /Users/YOUR-USER-NAME/Library/Group Containers/A5HDJTY9X5.com.latenitefilms.BRAWToolbox/Library/Application Support/ You can find any crash reports here (basically anything with a BRAW in the file name): /Users/YOUR-USER-NAME/Library/Logs/DiagnosticReports You can upload here: https://latenitefilms.digitalpigeon.com <https://latenitefilms.digitalpigeon.com/> Are you also able to share a screenshot of the options in the Render/Share GPU dropdown in FCPX Preferences? <https://user-images.githubusercontent.com/22286696/212496705-5c8c8791-09ce-4f33-acfb-46a6dffb7d7c.png> In the meantime, I'll have another look and try some different things - it's just tricky because I only currently have access to single GPU machines. — Reply to this email directly, view it on GitHub <#25 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACJCKTRG65L3I47IOJAI2BTWSMJCZANCNFSM6AAAAAATU5AJO4>. You are receiving this because you were mentioned.

[latenitefilms]

I'm uploading a new build to TestFlight now. Let me know if there's any improvement.

[latenitefilms]

Interestingly, @tangierc's GPUs just appear as one in the Final Cut Pro interface:

[tangierc]

Chris I just sent you a screen recording. Could it be that it only shows as one because in the 2013 Mac Pro one GPU is used for GPU processing and the other for driving the monitors? I used to think that both GPUs were fully accessible to any app, but it seems that not the case by design? I read about this not too long ago. Tangier

…

On Jan 14, 2023, at 2:51:05 PM, Chris Hocking ***@***.***> wrote: Interestingly, @tangierc <https://github.com/tangierc>'s GPUs just appear as one in the Final Cut Pro interface: <https://user-images.githubusercontent.com/22286696/212500504-fa5528b4-b0b5-4d08-9116-24df5a6ca256.png> — Reply to this email directly, view it on GitHub <#25 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACJCKTU2S4QYQSTAJKMVDCTWSMUVTANCNFSM6AAAAAATU5AJO4>. You are receiving this because you were mentioned.

[latenitefilms]

@tangierc - I believe the GPUs in the Trashcan 2013 Mac Pro work a bit differently to older and newer Cheese-grater Mac Pro models, and Mac with eGPUs.

I just saw your screen recording. As soon as FCPX marks a plugin as "not responding", it won't work again until you restart Final Cut Pro.

Let me know if the latest beta - 1.0.0 (21) - Public Beta 8 - offers any improvement?

[tangierc]

This version has flickering blue frames using browser and timeline playback, but the plugin error did not happen this time. Thanks, Tangier

…

On Jan 14, 2023, at 3:06:19 PM, Chris Hocking ***@***.***> wrote: @tangierc <https://github.com/tangierc> - I believe the GPUs in the Trashcan 2013 Mac Pro work a bit differently to older and newer Cheese-grater Mac Pro models, and Mac with eGPUs. I just saw your screen recording. As soon as FCPX marks a plugin as "not responding", it won't work again until you restart Final Cut Pro. Let me know if the latest beta - 1.0.0 (21) - Public Beta 8 - offers any improvement? — Reply to this email directly, view it on GitHub <#25 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACJCKTWN43MHLZ7ZVFPJ5FTWSMWOXANCNFSM6AAAAAATU5AJO4>. You are receiving this because you were mentioned.

[latenitefilms]

Can you send a screenshot of Activity Monitor on the Memory panel and with the GPU History open during playback?

[tangierc]

Here you go. Both of these taken while the BRAW clip was playing. GPU ranged from 15% to 19% in slot 1.

On Jan 14, 2023, at 3:16:38 PM, Chris Hocking ***@***.***> wrote: Can you send a screenshot

  of Activity Monitor on the Memory panel and with the GPU History open during playback?

…

— Reply to this email directly, view it on GitHub <#25 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACJCKTXT7UE4NGT6KEFUE5LWSMXVNANCNFSM6AAAAAATU5AJO4>. You are receiving this because you were mentioned.

[latenitefilms]

@tangierc - Thanks for the new screen recording! Very helpful! To be honest, I have absolutely no idea why this is happening. It's not an issue with the BRAW SDK, as it's obviously playing fine in the Workflow Extension, and it's rendering frames normally in FCPX most of the time. Something in FxPlug4 is failing. I'll reach out to Apple and see if they have any words of wisdom.

I'm also waiting to hear back from Jamie Lejeune who has a 2019 Mac Pro with 2 x W5700X GPU (16GB VRAM).

It could just be a VRAM issue as the Dual AMD FirePro D500 only has 3GB VRAM, as 1.0.0 (21) - Public Beta 8 is doing a single frame on the one GPU.

[tangierc]

Understood. I’ve been configuring a Mac Studio online. I wasn’t quite ready, but maybe I’ll make the jump soon. This machine has been working great for almost every project (except a few large ones). The obvious choice would be just to use my M1 Pro MBP, but that’s not practical for me the way I have my workstation set up and how I use the MBP from place to place. Here’s a p [MediaInfo.pdf](https://github.com/latenitefilms/BRAWToolbox/files/10419127/MediaInfo.pdf) df of the full specs on that braw file. I don’t know if it’s useful at all, but sending anything I can to provide insight. This is using the MediaInfo app.

…

On Jan 14, 2023, at 3:28:03 PM, Chris Hocking ***@***.***> wrote: @tangierc <https://github.com/tangierc> - Thanks for the new screen recording! Very helpful! To be honest, I have absolutely no idea why this is happening. It's not an issue with the BRAW SDK, as it's obviously playing fine in the Workflow Extension, and it's rendering frames normally in FCPX most of the time. Something in FxPlug4 is failing. I'll reach out to Apple and see if they have any words of wisdom. I'm also waiting to hear back from Jamie Lejeune who has a 2019 Mac Pro with 2 x W5700X GPU (16GB VRAM). It could just be a VRAM issue as the Dual AMD FirePro D500 only has 3GB VRAM, as 1.0.0 (21) - Public Beta 8 is doing a single frame on the one GPU. — Reply to this email directly, view it on GitHub <#25 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACJCKTRWGVDO5GUEYUDLN43WSMZAHANCNFSM6AAAAAATU5AJO4>. You are receiving this because you were mentioned.

[tangierc]

I made sure to test other braw clips that I have as well just in case there was a problem with the first clip file. They all have LTC embedded. I don’t think that’d cause an issue, but want to be sure I mention that again to be transparent about all variables. Tangier

…

On Jan 14, 2023, at 3:16:38 PM, Chris Hocking ***@***.***> wrote: Can you send a screenshot of Activity Monitor on the Memory panel and with the GPU History open during playback? — Reply to this email directly, view it on GitHub <#25 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACJCKTXT7UE4NGT6KEFUE5LWSMXVNANCNFSM6AAAAAATU5AJO4>. You are receiving this because you were mentioned.

[latenitefilms]

@tangierc - Each time you get a blue render frame does it write something like ERROR - Failed to get processedImage. in ~/Library/Group Containers/A5HDJTY9X5.com.latenitefilms.BRAWToolbox/Library/Application Support/FxPlug.log?

[latenitefilms]

(FYI: I don't think your attachments come through when you reply via email)

[tangierc]

Ahhh, thanks for that. I updated those last posts here on Github with the files. Tangier

…

On Jan 14, 2023, at 3:49:35 PM, Chris Hocking ***@***.***> wrote: (FYI: I don't think your attachments come through when you reply via email) — Reply to this email directly, view it on GitHub <#25 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACJCKTSGLFF7HPMZWXCT2SDWSM3Q7ANCNFSM6AAAAAATU5AJO4>. You are receiving this because you were mentioned.

[tangierc]

Chris, I think it does. Initially I tried to count them and I could, but then the blue flashes happened too fast and I couldn’t count them. I went into the FxPlug log and sure enough it seems that they’re happening that fast when I look at the time stamps. I check the clock before I started paying attention and pressing play so your thought is spot on. Tangier

…

On Jan 14, 2023, at 3:48:00 PM, Chris Hocking ***@***.***> wrote: @tangierc <https://github.com/tangierc> - Each time you get a blue render frame does it write something like ERROR - Failed to get processedImage. in ~/Library/Group Containers/A5HDJTY9X5.com.latenitefilms.BRAWToolbox/Library/Application Support/FxPlug.log? — Reply to this email directly, view it on GitHub <#25 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACJCKTTSTUEBQPVA4DNZQODWSM3LBANCNFSM6AAAAAATU5AJO4>. You are receiving this because you were mentioned.

[latenitefilms]

@tangierc - Interestingly, all the crash reports you sent all seem to crash in similar code, in the AMD Metal Driver.

Thread 531 Crashed::  Dispatch queue: com.apple.root.user-interactive-qos
0   AMDMTLBronzeDriver            	    0x7ffa3347f029 amdBronzeMtlTextureStdWriteTile256ByteChunkedDisp3(void*, void*, unsigned int, unsigned int) + 52
1   AMDMTLBronzeDriver            	    0x7ffa3347c963 BronzeGenerateMicroTileAddresses2D(BronzeCpuTexInterfaceRec const*, ATIMipmapBufferHeader const*, unsigned int, unsigned int, unsigned int, unsigned int, unsigned int, unsigned int, unsigned int, void (*)(unsigned long long, unsigned int, unsigned int, unsigned int, void*), void*) + 1245
2   AMDMTLBronzeDriver            	    0x7ffa3347d356 amdMtlBronzeTextureStdReplaceTiles(BronzeCpuTexInterfaceRec const*, ATIMipmapBufferHeader const*, ati_si_format_info const*, unsigned long, unsigned int, unsigned long, unsigned long, unsigned int, unsigned int, unsigned int, unsigned int, unsigned int) + 268
3   AMDMTLBronzeDriver            	    0x7ffa3347ce4a amdMtlBronzeTextureStdAccessRegion(BronzeCpuTexInterfaceRec const*, void (*)(BronzeCpuTexInterfaceRec const*, ATIMipmapBufferHeader const*, ati_si_format_info const*, unsigned long, unsigned int, unsigned long, unsigned long, unsigned int, unsigned int, unsigned int, unsigned int, unsigned int), void (*)(BronzeCpuTexInterfaceRec const*, ATIMipmapBufferHeader const*, ati_si_format_info const*, unsigned long, unsigned int, unsigned long, unsigned long, unsigned int, unsigned int, unsigned int, unsigned int, unsigned int), ATIMipmapBufferHeader const*, ati_si_format_info const*, unsigned long, unsigned int, unsigned long, unsigned long, unsigned int, unsigned int, unsigned int, unsigned int, unsigned int) + 573
4   AMDMTLBronzeDriver            	    0x7ffa3347d1df amdMtlBronzeTextureStdReplaceRegion(BronzeCpuTexInterfaceRec const*, ATIMipmapBufferHeader const*, ati_si_format_info const*, void*, unsigned int, unsigned long, unsigned long, unsigned int, unsigned int, unsigned int, unsigned int, unsigned int) + 294
5   AMDMTLBronzeDriver            	    0x7ffa335004f1 -[BronzeMtlTexture replaceRegion:mipmapLevel:withBytes:bytesPerRow:] + 564
6   BRAW Toolbox Renderer         	       0x10e25cd7e 0x10e250000 + 52606
7   FxPlug                        	       0x10e601d6d __123-[FxRemotePluginCoordinator tileablePlugin:renderWithState:withImageInputs:withOutput:rendererRegistryID:atTime:withReply:]_block_invoke + 254
8   libdispatch.dylib             	    0x7ff816ce60cc _dispatch_call_block_and_release + 12
9   libdispatch.dylib             	    0x7ff816ce7317 _dispatch_client_callout + 8
10  libdispatch.dylib             	    0x7ff816cf6c0c _dispatch_root_queue_drain + 673
11  libdispatch.dylib             	    0x7ff816cf725c _dispatch_worker_thread2 + 160
12  libsystem_pthread.dylib       	    0x7ff816e9af8a _pthread_wqthread + 256
13  libsystem_pthread.dylib       	    0x7ff816e99f57 start_wqthread + 15

Thread 69 Crashed::  Dispatch queue: com.apple.root.user-interactive-qos
0   libsystem_kernel.dylib        	    0x7ff8018e700e __pthread_kill + 10
1   libsystem_pthread.dylib       	    0x7ff80191d1ff pthread_kill + 263
2   libsystem_c.dylib             	    0x7ff801868d24 abort + 123
3   libsystem_c.dylib             	    0x7ff8018680cb __assert_rtn + 314
4   AMDMTLBronzeDriver            	    0x7ffa1e071a8a amdMtlBronzeCmdBufUpdateRsrc(BronzeCmdBufInfoRec*, MTLIOAccelResource*, unsigned int, unsigned int) (.cold.1) + 35
5   AMDMTLBronzeDriver            	    0x7ffa1df573bd amdMtlBronzeCmdBufUpdateRsrc(BronzeCmdBufInfoRec*, MTLIOAccelResource*, unsigned int, unsigned int) + 173
6   AMDMTLBronzeDriver            	    0x7ffa1dfef496 amdMtlBronzeHandleLoadActions(BronzeDeviceMembersRec*, BronzeSurfSyncMgrRec*, BronzeCmdBufInfoRec*, AMDBitVectorRec*, MTLRenderPassDescriptor const*, BronzeLoadStoreInfo*, ATI_BOOL) + 2128
7   AMDMTLBronzeDriver            	    0x7ffa1df764da -[BronzeMtlRenderCmdEncoder initWithCommandBuffer:descriptor:] + 1454
8   AMDMTLBronzeDriver            	    0x7ffa1df59a81 -[BronzeMtlCmdBuffer renderCommandEncoderWithDescriptor:] + 52
9   BRAW Toolbox Renderer         	       0x107a445d3 0x107a38000 + 50643
10  FxPlug                        	       0x107de9d6d __123-[FxRemotePluginCoordinator tileablePlugin:renderWithState:withImageInputs:withOutput:rendererRegistryID:atTime:withReply:]_block_invoke + 254
11  libdispatch.dylib             	    0x7ff8017650cc _dispatch_call_block_and_release + 12
12  libdispatch.dylib             	    0x7ff801766317 _dispatch_client_callout + 8
13  libdispatch.dylib             	    0x7ff801775c0c _dispatch_root_queue_drain + 673
14  libdispatch.dylib             	    0x7ff80177625c _dispatch_worker_thread2 + 160
15  libsystem_pthread.dylib       	    0x7ff801919f8a _pthread_wqthread + 256
16  libsystem_pthread.dylib       	    0x7ff801918f57 start_wqthread + 15

Thread 1 Crashed::  Dispatch queue: com.apple.root.user-interactive-qos
0   libsystem_kernel.dylib        	    0x7ff8018e700e __pthread_kill + 10
1   libsystem_pthread.dylib       	    0x7ff80191d1ff pthread_kill + 263
2   libsystem_c.dylib             	    0x7ff801868d24 abort + 123
3   libsystem_c.dylib             	    0x7ff8018680cb __assert_rtn + 314
4   AMDMTLBronzeDriver            	    0x7ffa1e071a8a amdMtlBronzeCmdBufUpdateRsrc(BronzeCmdBufInfoRec*, MTLIOAccelResource*, unsigned int, unsigned int) (.cold.1) + 35
5   AMDMTLBronzeDriver            	    0x7ffa1df573bd amdMtlBronzeCmdBufUpdateRsrc(BronzeCmdBufInfoRec*, MTLIOAccelResource*, unsigned int, unsigned int) + 173
6   AMDMTLBronzeDriver            	    0x7ffa1dfef496 amdMtlBronzeHandleLoadActions(BronzeDeviceMembersRec*, BronzeSurfSyncMgrRec*, BronzeCmdBufInfoRec*, AMDBitVectorRec*, MTLRenderPassDescriptor const*, BronzeLoadStoreInfo*, ATI_BOOL) + 2128
7   AMDMTLBronzeDriver            	    0x7ffa1df764da -[BronzeMtlRenderCmdEncoder initWithCommandBuffer:descriptor:] + 1454
8   AMDMTLBronzeDriver            	    0x7ffa1df59a81 -[BronzeMtlCmdBuffer renderCommandEncoderWithDescriptor:] + 52
9   BRAW Toolbox Renderer         	       0x10dc775d3 0x10dc6b000 + 50643
10  FxPlug                        	       0x10e01cd6d __123-[FxRemotePluginCoordinator tileablePlugin:renderWithState:withImageInputs:withOutput:rendererRegistryID:atTime:withReply:]_block_invoke + 254
11  libdispatch.dylib             	    0x7ff8017650cc _dispatch_call_block_and_release + 12
12  libdispatch.dylib             	    0x7ff801766317 _dispatch_client_callout + 8
13  libdispatch.dylib             	    0x7ff801775c0c _dispatch_root_queue_drain + 673
14  libdispatch.dylib             	    0x7ff80177625c _dispatch_worker_thread2 + 160
15  libsystem_pthread.dylib       	    0x7ff801919f8a _pthread_wqthread + 256
16  libsystem_pthread.dylib       	    0x7ff801918f57 start_wqthread + 15

Thread 53 Crashed::  Dispatch queue: com.apple.root.user-interactive-qos
0   libsystem_kernel.dylib        	    0x7ff8018e700e __pthread_kill + 10
1   libsystem_pthread.dylib       	    0x7ff80191d1ff pthread_kill + 263
2   libsystem_c.dylib             	    0x7ff801868d24 abort + 123
3   libsystem_c.dylib             	    0x7ff8018680cb __assert_rtn + 314
4   AMDMTLBronzeDriver            	    0x7ffa1e071a8a amdMtlBronzeCmdBufUpdateRsrc(BronzeCmdBufInfoRec*, MTLIOAccelResource*, unsigned int, unsigned int) (.cold.1) + 35
5   AMDMTLBronzeDriver            	    0x7ffa1df573bd amdMtlBronzeCmdBufUpdateRsrc(BronzeCmdBufInfoRec*, MTLIOAccelResource*, unsigned int, unsigned int) + 173
6   AMDMTLBronzeDriver            	    0x7ffa1dfef496 amdMtlBronzeHandleLoadActions(BronzeDeviceMembersRec*, BronzeSurfSyncMgrRec*, BronzeCmdBufInfoRec*, AMDBitVectorRec*, MTLRenderPassDescriptor const*, BronzeLoadStoreInfo*, ATI_BOOL) + 2128
7   AMDMTLBronzeDriver            	    0x7ffa1df764da -[BronzeMtlRenderCmdEncoder initWithCommandBuffer:descriptor:] + 1454
8   AMDMTLBronzeDriver            	    0x7ffa1df59a81 -[BronzeMtlCmdBuffer renderCommandEncoderWithDescriptor:] + 52
9   BRAW Toolbox Renderer         	       0x108b105d3 0x108b04000 + 50643
10  FxPlug                        	       0x108eb5d6d __123-[FxRemotePluginCoordinator tileablePlugin:renderWithState:withImageInputs:withOutput:rendererRegistryID:atTime:withReply:]_block_invoke + 254
11  libdispatch.dylib             	    0x7ff8017650cc _dispatch_call_block_and_release + 12
12  libdispatch.dylib             	    0x7ff801766317 _dispatch_client_callout + 8
13  libdispatch.dylib             	    0x7ff801775c0c _dispatch_root_queue_drain + 673
14  libdispatch.dylib             	    0x7ff80177625c _dispatch_worker_thread2 + 160
15  libsystem_pthread.dylib       	    0x7ff801919f8a _pthread_wqthread + 256
16  libsystem_pthread.dylib       	    0x7ff801918f57 start_wqthread + 15

Thread 53 Crashed::  Dispatch queue: com.apple.root.user-interactive-qos
0   libsystem_kernel.dylib        	    0x7ff8018e700e __pthread_kill + 10
1   libsystem_pthread.dylib       	    0x7ff80191d1ff pthread_kill + 263
2   libsystem_c.dylib             	    0x7ff801868d24 abort + 123
3   libsystem_c.dylib             	    0x7ff8018680cb __assert_rtn + 314
4   AMDMTLBronzeDriver            	    0x7ffa1e071a8a amdMtlBronzeCmdBufUpdateRsrc(BronzeCmdBufInfoRec*, MTLIOAccelResource*, unsigned int, unsigned int) (.cold.1) + 35
5   AMDMTLBronzeDriver            	    0x7ffa1df573bd amdMtlBronzeCmdBufUpdateRsrc(BronzeCmdBufInfoRec*, MTLIOAccelResource*, unsigned int, unsigned int) + 173
6   AMDMTLBronzeDriver            	    0x7ffa1dfef496 amdMtlBronzeHandleLoadActions(BronzeDeviceMembersRec*, BronzeSurfSyncMgrRec*, BronzeCmdBufInfoRec*, AMDBitVectorRec*, MTLRenderPassDescriptor const*, BronzeLoadStoreInfo*, ATI_BOOL) + 2128
7   AMDMTLBronzeDriver            	    0x7ffa1df764da -[BronzeMtlRenderCmdEncoder initWithCommandBuffer:descriptor:] + 1454
8   AMDMTLBronzeDriver            	    0x7ffa1df59a81 -[BronzeMtlCmdBuffer renderCommandEncoderWithDescriptor:] + 52
9   BRAW Toolbox Renderer         	       0x10f6b45d3 0x10f6a8000 + 50643
10  FxPlug                        	       0x1108cbd6d __123-[FxRemotePluginCoordinator tileablePlugin:renderWithState:withImageInputs:withOutput:rendererRegistryID:atTime:withReply:]_block_invoke + 254
11  libdispatch.dylib             	    0x7ff8017650cc _dispatch_call_block_and_release + 12
12  libdispatch.dylib             	    0x7ff801766317 _dispatch_client_callout + 8
13  libdispatch.dylib             	    0x7ff801775c0c _dispatch_root_queue_drain + 673
14  libdispatch.dylib             	    0x7ff80177625c _dispatch_worker_thread2 + 160
15  libsystem_pthread.dylib       	    0x7ff801919f8a _pthread_wqthread + 256
16  libsystem_pthread.dylib       	    0x7ff801918f57 start_wqthread + 15

Thread 98 Crashed::  Dispatch queue: com.apple.root.user-interactive-qos
0   libsystem_kernel.dylib        	    0x7ff81125b00e __pthread_kill + 10
1   libsystem_pthread.dylib       	    0x7ff8112911ff pthread_kill + 263
2   libsystem_c.dylib             	    0x7ff8111dcd24 abort + 123
3   libsystem_c.dylib             	    0x7ff8111dc0cb __assert_rtn + 314
4   AMDMTLBronzeDriver            	    0x7ffa2d9e5a8a amdMtlBronzeCmdBufUpdateRsrc(BronzeCmdBufInfoRec*, MTLIOAccelResource*, unsigned int, unsigned int) (.cold.1) + 35
5   AMDMTLBronzeDriver            	    0x7ffa2d8cb3bd amdMtlBronzeCmdBufUpdateRsrc(BronzeCmdBufInfoRec*, MTLIOAccelResource*, unsigned int, unsigned int) + 173
6   AMDMTLBronzeDriver            	    0x7ffa2d963496 amdMtlBronzeHandleLoadActions(BronzeDeviceMembersRec*, BronzeSurfSyncMgrRec*, BronzeCmdBufInfoRec*, AMDBitVectorRec*, MTLRenderPassDescriptor const*, BronzeLoadStoreInfo*, ATI_BOOL) + 2128
7   AMDMTLBronzeDriver            	    0x7ffa2d8ea4da -[BronzeMtlRenderCmdEncoder initWithCommandBuffer:descriptor:] + 1454
8   AMDMTLBronzeDriver            	    0x7ffa2d8cda81 -[BronzeMtlCmdBuffer renderCommandEncoderWithDescriptor:] + 52
9   BRAW Toolbox Renderer         	       0x10340a5d3 0x1033fe000 + 50643
10  FxPlug                        	       0x1037afd6d __123-[FxRemotePluginCoordinator tileablePlugin:renderWithState:withImageInputs:withOutput:rendererRegistryID:atTime:withReply:]_block_invoke + 254
11  libdispatch.dylib             	    0x7ff8110d90cc _dispatch_call_block_and_release + 12
12  libdispatch.dylib             	    0x7ff8110da317 _dispatch_client_callout + 8
13  libdispatch.dylib             	    0x7ff8110e9c0c _dispatch_root_queue_drain + 673
14  libdispatch.dylib             	    0x7ff8110ea25c _dispatch_worker_thread2 + 160
15  libsystem_pthread.dylib       	    0x7ff81128df8a _pthread_wqthread + 256
16  libsystem_pthread.dylib       	    0x7ff81128cf57 start_wqthread + 15

Thread 2 Crashed::  Dispatch queue: com.apple.root.user-interactive-qos
0   libsystem_kernel.dylib        	    0x7ff81125b00e __pthread_kill + 10
1   libsystem_pthread.dylib       	    0x7ff8112911ff pthread_kill + 263
2   libsystem_c.dylib             	    0x7ff8111dcd24 abort + 123
3   libsystem_c.dylib             	    0x7ff8111dc0cb __assert_rtn + 314
4   AMDMTLBronzeDriver            	    0x7ffa2d9e5a8a amdMtlBronzeCmdBufUpdateRsrc(BronzeCmdBufInfoRec*, MTLIOAccelResource*, unsigned int, unsigned int) (.cold.1) + 35
5   AMDMTLBronzeDriver            	    0x7ffa2d8cb3bd amdMtlBronzeCmdBufUpdateRsrc(BronzeCmdBufInfoRec*, MTLIOAccelResource*, unsigned int, unsigned int) + 173
6   AMDMTLBronzeDriver            	    0x7ffa2d963496 amdMtlBronzeHandleLoadActions(BronzeDeviceMembersRec*, BronzeSurfSyncMgrRec*, BronzeCmdBufInfoRec*, AMDBitVectorRec*, MTLRenderPassDescriptor const*, BronzeLoadStoreInfo*, ATI_BOOL) + 2128
7   AMDMTLBronzeDriver            	    0x7ffa2d8ea4da -[BronzeMtlRenderCmdEncoder initWithCommandBuffer:descriptor:] + 1454
8   AMDMTLBronzeDriver            	    0x7ffa2d8cda81 -[BronzeMtlCmdBuffer renderCommandEncoderWithDescriptor:] + 52
9   BRAW Toolbox Renderer         	       0x1011ff5d3 0x1011f3000 + 50643
10  FxPlug                        	       0x1015a4d6d __123-[FxRemotePluginCoordinator tileablePlugin:renderWithState:withImageInputs:withOutput:rendererRegistryID:atTime:withReply:]_block_invoke + 254
11  libdispatch.dylib             	    0x7ff8110d90cc _dispatch_call_block_and_release + 12
12  libdispatch.dylib             	    0x7ff8110da317 _dispatch_client_callout + 8
13  libdispatch.dylib             	    0x7ff8110e9c0c _dispatch_root_queue_drain + 673
14  libdispatch.dylib             	    0x7ff8110ea25c _dispatch_worker_thread2 + 160
15  libsystem_pthread.dylib       	    0x7ff81128df8a _pthread_wqthread + 256
16  libsystem_pthread.dylib       	    0x7ff81128cf57 start_wqthread + 15

Thread 1 Crashed::  Dispatch queue: com.apple.root.user-interactive-qos
0   libsystem_kernel.dylib        	    0x7ff81125b00e __pthread_kill + 10
1   libsystem_pthread.dylib       	    0x7ff8112911ff pthread_kill + 263
2   libsystem_c.dylib             	    0x7ff8111dcd24 abort + 123
3   libsystem_c.dylib             	    0x7ff8111dc0cb __assert_rtn + 314
4   AMDMTLBronzeDriver            	    0x7ffa2d9e5a8a amdMtlBronzeCmdBufUpdateRsrc(BronzeCmdBufInfoRec*, MTLIOAccelResource*, unsigned int, unsigned int) (.cold.1) + 35
5   AMDMTLBronzeDriver            	    0x7ffa2d8cb3bd amdMtlBronzeCmdBufUpdateRsrc(BronzeCmdBufInfoRec*, MTLIOAccelResource*, unsigned int, unsigned int) + 173
6   AMDMTLBronzeDriver            	    0x7ffa2d963496 amdMtlBronzeHandleLoadActions(BronzeDeviceMembersRec*, BronzeSurfSyncMgrRec*, BronzeCmdBufInfoRec*, AMDBitVectorRec*, MTLRenderPassDescriptor const*, BronzeLoadStoreInfo*, ATI_BOOL) + 2128
7   AMDMTLBronzeDriver            	    0x7ffa2d8ea4da -[BronzeMtlRenderCmdEncoder initWithCommandBuffer:descriptor:] + 1454
8   AMDMTLBronzeDriver            	    0x7ffa2d8cda81 -[BronzeMtlCmdBuffer renderCommandEncoderWithDescriptor:] + 52
9   BRAW Toolbox Renderer         	       0x10a9d75d3 0x10a9cb000 + 50643
10  FxPlug                        	       0x10ad7cd6d __123-[FxRemotePluginCoordinator tileablePlugin:renderWithState:withImageInputs:withOutput:rendererRegistryID:atTime:withReply:]_block_invoke + 254
11  libdispatch.dylib             	    0x7ff8110d90cc _dispatch_call_block_and_release + 12
12  libdispatch.dylib             	    0x7ff8110da317 _dispatch_client_callout + 8
13  libdispatch.dylib             	    0x7ff8110e9c0c _dispatch_root_queue_drain + 673
14  libdispatch.dylib             	    0x7ff8110ea25c _dispatch_worker_thread2 + 160
15  libsystem_pthread.dylib       	    0x7ff81128df8a _pthread_wqthread + 256
16  libsystem_pthread.dylib       	    0x7ff81128cf57 start_wqthread + 15

Thread 168 Crashed::  Dispatch queue: com.apple.root.user-interactive-qos
0   libsystem_kernel.dylib        	    0x7ff81125b00e __pthread_kill + 10
1   libsystem_pthread.dylib       	    0x7ff8112911ff pthread_kill + 263
2   libsystem_c.dylib             	    0x7ff8111dcd24 abort + 123
3   libsystem_c.dylib             	    0x7ff8111dc0cb __assert_rtn + 314
4   AMDMTLBronzeDriver            	    0x7ffa2d9e5a8a amdMtlBronzeCmdBufUpdateRsrc(BronzeCmdBufInfoRec*, MTLIOAccelResource*, unsigned int, unsigned int) (.cold.1) + 35
5   AMDMTLBronzeDriver            	    0x7ffa2d8cb3bd amdMtlBronzeCmdBufUpdateRsrc(BronzeCmdBufInfoRec*, MTLIOAccelResource*, unsigned int, unsigned int) + 173
6   AMDMTLBronzeDriver            	    0x7ffa2d963496 amdMtlBronzeHandleLoadActions(BronzeDeviceMembersRec*, BronzeSurfSyncMgrRec*, BronzeCmdBufInfoRec*, AMDBitVectorRec*, MTLRenderPassDescriptor const*, BronzeLoadStoreInfo*, ATI_BOOL) + 2128
7   AMDMTLBronzeDriver            	    0x7ffa2d8ea4da -[BronzeMtlRenderCmdEncoder initWithCommandBuffer:descriptor:] + 1454
8   AMDMTLBronzeDriver            	    0x7ffa2d8cda81 -[BronzeMtlCmdBuffer renderCommandEncoderWithDescriptor:] + 52
9   BRAW Toolbox Renderer         	       0x10abec5d3 0x10abe0000 + 50643
10  FxPlug                        	       0x10af91d6d __123-[FxRemotePluginCoordinator tileablePlugin:renderWithState:withImageInputs:withOutput:rendererRegistryID:atTime:withReply:]_block_invoke + 254
11  libdispatch.dylib             	    0x7ff8110d90cc _dispatch_call_block_and_release + 12
12  libdispatch.dylib             	    0x7ff8110da317 _dispatch_client_callout + 8
13  libdispatch.dylib             	    0x7ff8110e9c0c _dispatch_root_queue_drain + 673
14  libdispatch.dylib             	    0x7ff8110ea25c _dispatch_worker_thread2 + 160
15  libsystem_pthread.dylib       	    0x7ff81128df8a _pthread_wqthread + 256
16  libsystem_pthread.dylib       	    0x7ff81128cf57 start_wqthread + 15

Thread 98 Crashed::  Dispatch queue: com.apple.root.user-interactive-qos
0   libsystem_kernel.dylib        	    0x7ff81125b00e __pthread_kill + 10
1   libsystem_pthread.dylib       	    0x7ff8112911ff pthread_kill + 263
2   libsystem_c.dylib             	    0x7ff8111dcd24 abort + 123
3   libsystem_c.dylib             	    0x7ff8111dc0cb __assert_rtn + 314
4   AMDMTLBronzeDriver            	    0x7ffa2d9e5a8a amdMtlBronzeCmdBufUpdateRsrc(BronzeCmdBufInfoRec*, MTLIOAccelResource*, unsigned int, unsigned int) (.cold.1) + 35
5   AMDMTLBronzeDriver            	    0x7ffa2d8cb3bd amdMtlBronzeCmdBufUpdateRsrc(BronzeCmdBufInfoRec*, MTLIOAccelResource*, unsigned int, unsigned int) + 173
6   AMDMTLBronzeDriver            	    0x7ffa2d963496 amdMtlBronzeHandleLoadActions(BronzeDeviceMembersRec*, BronzeSurfSyncMgrRec*, BronzeCmdBufInfoRec*, AMDBitVectorRec*, MTLRenderPassDescriptor const*, BronzeLoadStoreInfo*, ATI_BOOL) + 2128
7   AMDMTLBronzeDriver            	    0x7ffa2d8ea4da -[BronzeMtlRenderCmdEncoder initWithCommandBuffer:descriptor:] + 1454
8   AMDMTLBronzeDriver            	    0x7ffa2d8cda81 -[BronzeMtlCmdBuffer renderCommandEncoderWithDescriptor:] + 52
9   BRAW Toolbox Renderer         	       0x10a8ce5d3 0x10a8c2000 + 50643
10  FxPlug                        	       0x10ac73d6d __123-[FxRemotePluginCoordinator tileablePlugin:renderWithState:withImageInputs:withOutput:rendererRegistryID:atTime:withReply:]_block_invoke + 254
11  libdispatch.dylib             	    0x7ff8110d90cc _dispatch_call_block_and_release + 12
12  libdispatch.dylib             	    0x7ff8110da317 _dispatch_client_callout + 8
13  libdispatch.dylib             	    0x7ff8110e9c0c _dispatch_root_queue_drain + 673
14  libdispatch.dylib             	    0x7ff8110ea25c _dispatch_worker_thread2 + 160
15  libsystem_pthread.dylib       	    0x7ff81128df8a _pthread_wqthread + 256
16  libsystem_pthread.dylib       	    0x7ff81128cf57 start_wqthread + 15

[latenitefilms]

@tangierc - I'm uploading a new build shortly with some very minor changes. I'm not sure it'll have any impact, but I guess we'll wait and see.

[tangierc]

Sound good. I’ll give a go. Tangier

…

On Jan 14, 2023, at 5:10:19 PM, Chris Hocking ***@***.***> wrote: @tangierc <https://github.com/tangierc> - I'm uploading a new build shortly with some very minor changes. I'm not sure it'll have any impact, but I guess we'll wait and see. — Reply to this email directly, view it on GitHub <#25 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACJCKTWMF7XK2A6I5ALHXGTWSNE7XANCNFSM6AAAAAATU5AJO4>. You are receiving this because you were mentioned.

[latenitefilms]

1.0.0 (22) - Public Beta 9 should now be up.

[tangierc]

Thanks for the follow up. I guess it’s either just my machine or the clip itself. I’ve swapped out the ports being used for the displays and drives. The footage doesn’t have the green frames when rendered, but the stutter/jitter is more pronounced. Tested on a new account. Same results. Downloaded BRAW clips from BM site (first two clips on this page https://www.blackmagicdesign.com/products/blackmagicpocketcinemacamera/gallery <https://www.blackmagicdesign.com/products/blackmagicpocketcinemacamera/gallery>). They don’t have any of these issues. Sending clips now - ETA 30 min upload. One screen recording, one for testing. Tangier

…

On Jan 18, 2023, at 12:58:07 PM, Chris Hocking ***@***.***> wrote: I just heard back from someone on a 2013 Mac Pro with Dual AMD FirePro D700 and it's working fine on their system. No green frames. Playback performance isn't as good as on Apple Silicon or newer Intel's, however, if you render the footage in the timeline, it all works fine - so the effect is working. It seems maybe the CPU is just a bit too slow on these older Mac Pros. One thing I never asked, if you render footage on your Mac Pro, does it render in the green frames and stuttering? Given your screenshots show that you're not pushing the D500 much at all - I don't think increasing from D500 to D700 would make any difference, so I can only assume that it's actually your specific machine that has some kind of issue. Have you tried another User account or booting into a fresh macOS install on an external drive or seperate partition? — Reply to this email directly, view it on GitHub <#25 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACJCKTSYXFYHYVHMOIQK543WTBKN7ANCNFSM6AAAAAATU5AJO4>. You are receiving this because you were mentioned.

[tangierc]

Hey Chris I just cancelled the test clip uploading. It was a large file. I realized we already know that it works in Resolve and on an M1 and no issues on my Intel MBP, so it must not be the clip.

…

On Jan 18, 2023, at 10:20:46 PM, Tangier Clarke ***@***.***> wrote: Thanks for the follow up. I guess it’s either just my machine or the clip itself. I’ve swapped out the ports being used for the displays and drives. The footage doesn’t have the green frames when rendered, but the stutter/jitter is more pronounced. Tested on a new account. Same results. Downloaded BRAW clips from BM site (first two clips on this page https://www.blackmagicdesign.com/products/blackmagicpocketcinemacamera/gallery <https://www.blackmagicdesign.com/products/blackmagicpocketcinemacamera/gallery>). They don’t have any of these issues. Sending clips now - ETA 30 min upload. One screen recording, one for testing. Tangier > On Jan 18, 2023, at 12:58:07 PM, Chris Hocking ***@***.*** ***@***.***>> wrote: > > > I just heard back from someone on a 2013 Mac Pro with Dual AMD FirePro D700 and it's working fine on their system. No green frames. Playback performance isn't as good as on Apple Silicon or newer Intel's, however, if you render the footage in the timeline, it all works fine - so the effect is working. It seems maybe the CPU is just a bit too slow on these older Mac Pros. > > One thing I never asked, if you render footage on your Mac Pro, does it render in the green frames and stuttering? > > Given your screenshots show that you're not pushing the D500 much at all - I don't think increasing from D500 to D700 would make any difference, so I can only assume that it's actually your specific machine that has some kind of issue. > > Have you tried another User account or booting into a fresh macOS install on an external drive or seperate partition? > > — > Reply to this email directly, view it on GitHub <#25 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACJCKTSYXFYHYVHMOIQK543WTBKN7ANCNFSM6AAAAAATU5AJO4>. > You are receiving this because you were mentioned. >

[latenitefilms]

What was the difference between the BRAW files? Are the original clips higher quality?

It could just be a matter of your GPUs not being able to easily handle the resolution of 12K files or something?

Rather than using the Workflow Extension, you could try manually applying the BRAW Toolbox effect on a black generator in a HD timeline with the original clips and see if that works?

[latenitefilms]

Looking at the PDF you posted earlier, you're working with 6176x3472 BRAW files @ 23.976fps. The Workflow Extension will create a Sync Clip with the same resolution (regardless of Decode Quality), so again, maybe try making it UltraHD instead and see if that has any impact?

[tangierc]

I think at the end of the day it’s just the machine or machine config - eating two monitors. The same footage has no problems on my 2016 15” MBP with Touch Bar; single display and integrated graphics as mentioned before (and less video memory than any of my D500s in my Mac Pro. So it has to be the computer. There’s something fundamentally wrong with that machine (the Mac Pro) managing the results of BRAW Toolbox. My hardware test checked out fine. The same issues showed up in a new user account. Seems like one of those situations where the actual reason just won’t be discovered. It’s still a good machine and useful for a lot of things to me, but time to replace it. Thanks Chris.

…

On Jan 19, 2023, at 1:10 PM, Chris Hocking ***@***.***> wrote: Looking at the PDF you posted earlier, you're working with 6176x3472 BRAW files @ 23.976fps. The Workflow Extension will create a Sync Clip with the same resolution (regardless of Decode Quality), so again, maybe try making it UltraHD instead and see if that has any impact? — Reply to this email directly, view it on GitHub <#25 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACJCKTWKUY2LDSFH4HRVZT3WTGUTFANCNFSM6AAAAAATU5AJO4>. You are receiving this because you were mentioned.

[latenitefilms]

I'm going to guess that the MacBook Pro will still work if you connect the same external monitors to it?

What results do you get if you run the Blackmagic BRAW Speed Test on both machines?

[tangierc]

Here's the results. The First is the 2013 3.5 GHz 6-core / Dual AMD D500s Mac Pro, the second is the 2016 Intel 15" MBP w/Touchbar

[latenitefilms]

So strange. Well, unfortunately I'm totally out of ideas.

I haven't heard anything back from Apple. I also haven't had any other feedback from other users reporting similar issues.

Given this, I'm going to close this issue for now, as I can only ASSUME it's something funky on that particular machine.

If I learn anything else, I'll definitely update this issue.

[latenitefilms]

@tangierc - If you have time, are you able to download the v1.0.1 TestFlight release and see if that has any impact on your MacPro?

https://testflight.apple.com/join/GC92jL9o

[tangierc]

Chris, just to be sure - I have the purchased version installed already. I’ll be replacing that with the test version. Tangier

…

On Feb 7, 2023, at 3:52:35 PM, Chris Hocking ***@***.***> wrote: @tangierc <https://github.com/tangierc> - If you have time, are you able to download the v1.0.1 TestFlight release and see if that has any impact on your MacPro? https://testflight.apple.com/join/GC92jL9o <https://testflight.apple.com/join/GC92jL9o> — Reply to this email directly, view it on GitHub <#25 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACJCKTT3Y5IT3IK6UPF7RNTWWLN4HANCNFSM6AAAAAATU5AJO4>. You are receiving this because you were mentioned.

[latenitefilms]

Yes, correct. Please close Final Cut Pro, send the /Applications/BRAW Toolbox.app from the Mac App Store to trash, then download the v1.0.1 beta from TestFlight and give that a go.

I have no idea if it'll have an impact or not - but hey, it's worth a shot!

[tangierc]

Hey Chris. I am doing everything I did before to duplicate the green and blue frames. They’re not there! First I tested the new beta on old libraries that I used for testing BRAW Toolbox. These libraries had the issues show up. This time they’re not there. Next I created a new library and used BRAW Toolbox 1.01 beta to import the exact same clips. Still no green or blue frames. I usually can invoke the frames by starting and stopping the playhead at random frames. All of the above was playback in the browser. I tested in the timeline and the performance is the same - no strange flashing frames. Whatever you did, looks to be successful and I am curious if you can share any insight. Thanks, Tangier P.S. I did try moving my Mac Pro a little to the left as you suggested a little while ago, hoping that would fix the issue, but it didn’t…or did it? ;)

…

On Feb 7, 2023, at 7:46:29 PM, Chris Hocking ***@***.***> wrote: Yes, correct. Please close Final Cut Pro, send the /Applications/BRAW Toolbox.app from the Mac App Store to trash, then download the v1.0.1 beta from TestFlight and give that a go. I have no idea if it'll have an impact or not - but hey, it's worth a shot! — Reply to this email directly, view it on GitHub <#25 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACJCKTWMLCNVJFZ3BCKLSTDWWMJJLANCNFSM6AAAAAATU5AJO4>. You are receiving this because you were mentioned.

[latenitefilms]

Woohoo! Great news!

The main change I made, which I THINK is what is fixing your issue is that if a BRAW frame fails to render for whatever reason, we now retry five times before giving up. I'm not really sure WHY it fails in some cases - but at least now it tries five times first before outputting an error message.

There's still one remaining thing that I want to try solve in v1.0.1 before I push out publicly - the BRAW Toolbox Renderer seems to be using a LOT of threads, which most likely means I'm not releasing something properly somewhere in the BRAW code. I'm currently working with Apple and Blackmagic to try and resolve this - but aside from that, it seems very stable and reliable on all the machines I tested it on.

[latenitefilms]

v1.0.1 (34) will hit TestFlight shortly. Are you able to check that it still works on your machine. Assuming all is good, this will be the version we release publicly. Thanks!

[tangierc]

Yes. I’ll check.Tangier On Feb 8, 2023, at 5:40 AM, Chris Hocking ***@***.***> wrote: v1.0.1 (34) will hit TestFlight shortly. Are you able to check that it still works on your machine. Assuming all is good, this will be the version we release publicly. Thanks! —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: ***@***.***>

[tangierc]

Hey Chris. It all still works well! Tangier

…

On Feb 8, 2023, at 6:02:54 AM, TC Gmail ***@***.***> wrote: Yes. I’ll check. Tangier > On Feb 8, 2023, at 5:40 AM, Chris Hocking ***@***.***> wrote: > >  > > v1.0.1 (34) will hit TestFlight shortly. Are you able to check that it still works on your machine. Assuming all is good, this will be the version we release publicly. Thanks! > > — > Reply to this email directly, view it on GitHub <#25 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACJCKTXFGZ2LKVEEW4KCRETWWOO6XANCNFSM6AAAAAATU5AJO4>. > You are receiving this because you were mentioned. >

[tangierc]

Chris, can you think of a clever way to relink to braw originals using BRAW Toolbox clips? I have an edit that already points to proxies (.mov files) made from braw clips. This was given to me. I am trying to figure out a way to point the original back to the braw counterpart, but BRAW Toolbox nor FCP can see the files that way. Just curious if you can think of a workaround. Thanks, Tangier

…

On Feb 8, 2023, at 6:59:56 AM, Tangier Clarke ***@***.***> wrote: Hey Chris. It all still works well! Tangier > On Feb 8, 2023, at 6:02:54 AM, TC Gmail ***@***.*** ***@***.***>> wrote: > > Yes. I’ll check. > > Tangier > >> On Feb 8, 2023, at 5:40 AM, Chris Hocking ***@***.*** ***@***.***>> wrote: >> >>  >> >> v1.0.1 (34) will hit TestFlight shortly. Are you able to check that it still works on your machine. Assuming all is good, this will be the version we release publicly. Thanks! >> >> — >> Reply to this email directly, view it on GitHub <#25 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACJCKTXFGZ2LKVEEW4KCRETWWOO6XANCNFSM6AAAAAATU5AJO4>. >> You are receiving this because you were mentioned. >>

[tangierc]

To clarify, the proxies made from the braw files are ProRes Proxies; seemingly made in Premiere Pro perhaps. Tangier

…

On Feb 13, 2023, at 9:58:53 AM, Tangier Clarke ***@***.***> wrote: Chris, can you think of a clever way to relink to braw originals using BRAW Toolbox clips? I have an edit that already points to proxies (.mov files) made from braw clips. This was given to me. I am trying to figure out a way to point the original back to the braw counterpart, but BRAW Toolbox nor FCP can see the files that way. Just curious if you can think of a workaround. Thanks, Tangier > On Feb 8, 2023, at 6:59:56 AM, Tangier Clarke ***@***.*** ***@***.***>> wrote: > > Hey Chris. It all still works well! > > Tangier > >> On Feb 8, 2023, at 6:02:54 AM, TC Gmail ***@***.*** ***@***.***>> wrote: >> >> Yes. I’ll check. >> >> Tangier >> >>> On Feb 8, 2023, at 5:40 AM, Chris Hocking ***@***.*** ***@***.***>> wrote: >>> >>>  >>> >>> v1.0.1 (34) will hit TestFlight shortly. Are you able to check that it still works on your machine. Assuming all is good, this will be the version we release publicly. Thanks! >>> >>> — >>> Reply to this email directly, view it on GitHub <#25 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACJCKTXFGZ2LKVEEW4KCRETWWOO6XANCNFSM6AAAAAATU5AJO4>. >>> You are receiving this because you were mentioned. >>> >

[latenitefilms]

You could try this:

https://brawtoolbox.io/toolbox/#add-braw-toolbox-to-proxy-clips-within-an-event

If it doesn't work in this use case, send me a FCPXML via email and I'll have a think/play.

[tangierc]

Thanks Chris. I am trying to wrap my head around this after reading the instructions. My timeline already has ProRes Proxies made from the braw files by someone else, but the original .braw files were never used in an edit even before it was handed to me; only the .mov proxies. So there’s no current relationship between original .braw files and the proxies if I were to switch those playback options in FCP? Since I used an XML (via Send to X) to bring over the project from Premiere Pro You’re saying that by taking events with the proxies, there will be a way for me to associate these proxies with the originals created by BRAW Toolbox so that toggling back and the playback in FCP will keep track of that in the same fashion we’re used to with other media? I realize this isn’t ideal. The ideal situation is to just use the braw clips and change the decode settings so I don’t have to use the proxies. In FCP, replacing each proxy from the braw with a clip made by BRAW Toolbox would be a tedious and manual effort since I can’t tell FCP to point to the BRAW Toolbox created clips as the originals. The only other option I can think of, (and it’s a long shot) is send the project out to Resolve using XML. Resolve has a replace feature, but I don’t know if it can batch replace clips. Even still, it would be pointing to the actual .braw files and not BRAW Toolbox clips. I hope this makes sense. Thanks again. Tangier

…

On Feb 13, 2023, at 11:28:32 AM, Chris Hocking ***@***.***> wrote: You could try this: https://brawtoolbox.io/toolbox/#add-braw-toolbox-to-proxy-clips-within-an-event <https://brawtoolbox.io/toolbox/#add-braw-toolbox-to-proxy-clips-within-an-event> If it doesn't work in this use case, send me a FCPXML via email and I'll have a think/play. — Reply to this email directly, view it on GitHub <#25 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACJCKTWZWFQEZ3MCONVUMHTWXKDOBANCNFSM6AAAAAATU5AJO4>. You are receiving this because you were mentioned.

[latenitefilms]

The Add BRAW Toolbox to Proxy Clips within an EVENT Toolbox basically does what it says - it adds the BRAW Toolbox effect to any of the .mov proxy files that exist in that Final Cut Pro event. The proxy file needs to be in the same folder as the BRAW file. So basically, "inside" each of your proxy clips, if you Open Clip, the BRAW Toolbox effect will be applied so you can modify the metadata there.

If it doesn't work, what you MIGHT have to do is Open Clip, apply any other effect (i.e. just apply a colour grade effect that doesn't do anything), and then try again - it really depends on what the FCPXML looks like coming back from SendToX.

Does that make sense?

[tangierc]

Got it. It does thank you. Would you mind explaining the extra characters in the name braw name of the Wav files created. I may need to explain this as I am using EDL-X to create an EDL. At first EDL didn’t take the name of the BRAW Toolbox-created clips. They came back null in the EDL. When I used EDL-X’s feature of adding an EDL-X share item in FCP and sent my timeline over that way, the EDL captured the name. Thanks Chris. Tangier

…

On Feb 13, 2023, at 5:22:31 PM, Chris Hocking ***@***.***> wrote: The Add BRAW Toolbox to Proxy Clips within an EVENT Toolbox basically does what it says - it adds the BRAW Toolbox effect to any of the .mov proxy files that exist in that Final Cut Pro event. The proxy file needs to be in the same folder as the BRAW file. So basically, "inside" each of your proxy clips, if you Open Clip, the BRAW Toolbox effect will be applied so you can modify the metadata there. If it doesn't work, what you MIGHT have to do is Open Clip, apply any other effect (i.e. just apply a colour grade effect that doesn't do anything), and then try again - it really depends on what the FCPXML looks like coming back from SendToX. Does that make sense? — Reply to this email directly, view it on GitHub <#25 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACJCKTV4LU2C5TDDUBUTHMLWXLM5PANCNFSM6AAAAAATU5AJO4>. You are receiving this because you were mentioned.

[latenitefilms]

The extra characters at the end are just random characters. We add them because it's possible that a user might import several BRAW files that all have the same name, and the audio all lives in the one folder.

[tangierc]

That makes sense. I use EditReady to create a custom nomenclature so there can’t be duplicates for clips.

…

On Feb 13, 2023, at 5:40:38 PM, Chris Hocking ***@***.***> wrote: The extra characters at the end are just random characters. We add them because it's possible that a user might import several BRAW files that all have the same name, and the audio all lives in the one folder. — Reply to this email directly, view it on GitHub <#25 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACJCKTQTWHRR3SOIXCI7BGLWXLPBNANCNFSM6AAAAAATU5AJO4>. You are receiving this because you were mentioned.

[tangierc]

Chris, have you tried BRAW Toolbox clips with EDL-X? The team who I’ll be working with for color who will be using Resolve want the clips to nut be “null” for the clip name. I’ll keep playing with the settings of EDL-X, but wanted to know if you’ve tried this out. Here’s a copy of a segment of my EDL for reference: * FROM CLIP NAME: A003_A003_0223KZ_001.R3D * ROLES: DIALOGUE DIALOGUE.CAMERA * AUDIO SOURCE CHANNELS: 1 * COM.APPLE.PROAPPS.STUDIO.REEL: A003_A003_0223KZ * COM.APPLE.PROAPPS.STUDIO.REEL: A003_A003_0223KZ- 220429 * COM.APPLE.PROAPPS.STUDIO.SCENE: 175B * COM.APPLE.PROAPPS.STUDIO.SHOT: 001 * COM.APPLE.PROAPPS.MIO.CAMERANAME: A * COM.APPLE.PROAPPS.STUDIO.RAWTOLOGCONVERSION: 0 * COM.APPLE.PROAPPS.SPOTLIGHT.KMDITEMPROFILENAME: HD (1-1-1) * COM.APPLE.PROAPPS.STUDIO.CAMERAISO: 0 * COM.APPLE.PROAPPS.STUDIO.CAMERACOLORTEMPERATURE: 0 * COM.APPLE.PROAPPS.SPOTLIGHT.KMDITEMCODECS: LINEAR PCM LQ * COM.APPLE.PROAPPS.MIO.SHOOTINGRATE: 23.976 * COM.APPLE.PROAPPS.MIO.MANUFACTURER: RED * COM.APPLE.PROAPPS.MIO.MODELNAME: V-RAPTOR 8K VV * COM.APPLE.PROAPPS.MIO.CAMERAID: A * COM.APPLE.PROAPPS.MIO.CLIPFILENAME: A003_A003_0223KZ_001.R3D * COM.APPLE.PROAPPS.MIO.INGESTDATE: 2022-12-04 20:31:12 -0800 008 106 V C 00:00:42:19 00:01:12:18 00:01:01:00 00:01:30:23 * FROM CLIP NAME: (NULL) * ROLE: VIDEO * COM.APPLE.PROAPPS.STUDIO.REEL: 5 * COM.APPLE.PROAPPS.STUDIO.SCENE: 1 * COM.APPLE.PROAPPS.STUDIO.SHOT: 99 * COM.APPLE.PROAPPS.STUDIO.ANGLE: B * COM.APPLE.PROAPPS.MIO.CAMERANAME: BLACKMAGIC POCKET CINEMA CAMERA 6K PRO * COM.APPLE.PROAPPS.MIO.INGESTDATE: 2022-02-17 13:52:00 -0800 * EFFECTS: BRAW TOOLBOX: FILE PATH BOOKMARK DATA DECODE QUALITY ISO EXPOSURE COLOR TEMP TINT COLOR SCIENCE VERSION COLOR SPACE/GAMUT GAMMA HIGHLIGHT RECOVERY GAMUT COMPRESSION LUT SOURCE SATURATION CONTRAST MIDPOINT HIGHLIGHT ROLLOFF SHADOW ROLLOFF BLACK LEVEL WHITE LEVEL USE VIDEO BLACK LEVEL 009 104 A1 C 00:00:42:19 00:01:12:18 00:01:01:00 00:01:30:23 * FROM CLIP NAME: B005_02171452_C034-7644F8E3-BB46-4AC2-B53F-56BB3E032804.WAV * ROLES: DIALOGUE DIALOGUE.DIALOGUE-1 * AUDIO SOURCE CHANNELS: 1 2 * COM.APPLE.PROAPPS.STUDIO.REEL: 5 * COM.APPLE.PROAPPS.STUDIO.SCENE: 1 * COM.APPLE.PROAPPS.STUDIO.SHOT: 99 * COM.APPLE.PROAPPS.STUDIO.ANGLE: B * COM.APPLE.PROAPPS.MIO.CAMERANAME: BLACKMAGIC POCKET CINEMA CAMERA 6K PRO * COM.APPLE.PROAPPS.MIO.INGESTDATE: 2022-02-17 13:52:00 -0800 * COM.APPLE.PROAPPS.MIO.INGESTDATE: 2022-02-17 13:52:00 -0800 010 106 V C 00:00:16:04 00:00:46:05 00:01:30:23 00:02:01:00 * FROM CLIP NAME: (NULL) * ROLE: VIDEO * COM.APPLE.PROAPPS.STUDIO.REEL: 5 * COM.APPLE.PROAPPS.STUDIO.SCENE: 1 * COM.APPLE.PROAPPS.STUDIO.SHOT: 99 * COM.APPLE.PROAPPS.STUDIO.ANGLE: B * COM.APPLE.PROAPPS.MIO.CAMERANAME: BLACKMAGIC POCKET CINEMA CAMERA 6K PRO * COM.APPLE.PROAPPS.MIO.INGESTDATE: 2022-02-17 12:57:53 -0800 * EFFECTS: BRAW TOOLBOX: FILE PATH BOOKMARK DATA SHOW PARAMETERS RESET METADATA DECODE QUALITY ISO EXPOSURE COLOR TEMP TINT COLOR SCIENCE VERSION COLOR SPACE/GAMUT GAMMA HIGHLIGHT RECOVERY GAMUT COMPRESSION LUT SOURCE SATURATION CONTRAST MIDPOINT HIGHLIGHT ROLLOFF SHADOW ROLLOFF BLACK LEVEL WHITE LEVEL USE VIDEO BLACK LEVEL 011 005 A1 C 00:00:16:04 00:00:46:05 00:01:30:23 00:02:01:00 * FROM CLIP NAME: B005_02171357_C028-922CD26E-1FD3-4E28-AC8D-C3FB137D6C35.WAV * ROLES: DIALOGUE DIALOGUE.DIALOGUE-1 * AUDIO SOURCE CHANNELS: 1 2 * COM.APPLE.PROAPPS.STUDIO.REEL: 5 * COM.APPLE.PROAPPS.STUDIO.SCENE: 1 * COM.APPLE.PROAPPS.STUDIO.SHOT: 99 * COM.APPLE.PROAPPS.STUDIO.ANGLE: B * COM.APPLE.PROAPPS.MIO.CAMERANAME: BLACKMAGIC POCKET CINEMA CAMERA 6K PRO * COM.APPLE.PROAPPS.MIO.INGESTDATE: 2022-02-17 12:57:53 -0800 * COM.APPLE.PROAPPS.MIO.INGESTDATE: 2022-02-17 12:57:53 -0800 012 015 V C 12:48:50:06 12:49:20:06 00:02:01:00 00:02:31:00 Tangier

…

On Feb 13, 2023, at 5:52:36 PM, Tangier Clarke ***@***.***> wrote: That makes sense. I use EditReady to create a custom nomenclature so there can’t be duplicates for clips. > On Feb 13, 2023, at 5:40:38 PM, Chris Hocking ***@***.*** ***@***.***>> wrote: > > > The extra characters at the end are just random characters. We add them because it's possible that a user might import several BRAW files that all have the same name, and the audio all lives in the one folder. > > — > Reply to this email directly, view it on GitHub <#25 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACJCKTQTWHRR3SOIXCI7BGLWXLPBNANCNFSM6AAAAAATU5AJO4>. > You are receiving this because you were mentioned. >

[latenitefilms]

Try using "Top-Level Clip Names":

Although, I am curious why you're using a EDL for Resolve and not a FCPXML?

[tangierc]

Thanks. I can’t answer that question and have been curious about that as well. I rarely use EDLs, but on occasion the sound or color teams I work with will ask for it. I’ll have to ask specifically how it helps them in Resolve. Tangier

…

On Feb 15, 2023, at 12:17 AM, Chris Hocking ***@***.***> wrote: Try using "Top-Level Clip Names": <https://user-images.githubusercontent.com/22286696/218970926-bbcf4e1e-83e8-4837-b112-9c5474728363.png> <https://user-images.githubusercontent.com/22286696/218971018-3687f969-dab0-4f65-bc8a-2c8ffcccf005.png> Although, I am curious why you're using a EDL for Resolve and not a FCPXML? — Reply to this email directly, view it on GitHub <#25 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACJCKTRPF23ABH7CSTSBK2DWXSGIZANCNFSM6AAAAAATU5AJO4>. You are receiving this because you were mentioned.

[tangierc]

Hey Chris. I need help trying to understand something. Is it possible to have copies of BRAW clips on two separate drives and relink as needed without having to got inside each clip to select BRAW file? I do this because at home I have my Red R3D original files that I can have FCP switch to original playback with the BRAW clips. My mobile drive can’t accommodate that much space so I use prores proxies of the RED files paired and want to pair that with copies of the BRAW clips. It’s a matter of storage. I did a test this morning where I created a library on Drive 1 where I keep libraries exclusively (no media) with three BRAW clips that are on Drive 2 (my home drive). I have a copy of those same BRAW clips on my mobile drive - Drive 3. I opened the same library but want to redirect the library to look at Drive 3 Of course, they’re offline with the missing file, security-scoped bookmark issue. I open one clip to grant sandbox access to the folder with the clips, but none of the clips update and link. I realize that one option is just use the mobile drive as the originals for everything, but I need to be able to switch to Drive 2 if I am handing the project over. Could you assist please? Sincerely, Tangier

…

On Feb 13, 2023, at 5:22 PM, Chris Hocking ***@***.***> wrote: The Add BRAW Toolbox to Proxy Clips within an EVENT Toolbox basically does what it says - it adds the BRAW Toolbox effect to any of the .mov proxy files that exist in that Final Cut Pro event. The proxy file needs to be in the same folder as the BRAW file. So basically, "inside" each of your proxy clips, if you Open Clip, the BRAW Toolbox effect will be applied so you can modify the metadata there. If it doesn't work, what you MIGHT have to do is Open Clip, apply any other effect (i.e. just apply a colour grade effect that doesn't do anything), and then try again - it really depends on what the FCPXML looks like coming back from SendToX. Does that make sense? — Reply to this email directly, view it on GitHub <#25 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACJCKTV4LU2C5TDDUBUTHMLWXLM5PANCNFSM6AAAAAATU5AJO4>. You are receiving this because you were mentioned.