"Add BRAW Toolbox to Proxy Clips within an EVENT" Toolbox produces invalid FCPXML #104
Comments
|
My sincerest apologies for the delayed reply - for some reason GitHub decided to stop sending me email notifications for this repo. Sorry! If Final Cut Pro is not accepting the dropped file, it means there must be something wrong with the FCPXML. You should be able to find that FCPXML in this folder:
If you try manually dragging that file into Final Cut Pro, it should hopefully give you an error message with clues to what's going on. |
|
I think I posted the file to the direct contact. Let me know if I need to resend. |
|
I don't believe I ever got the |
|
No problem. I just sent it.
Thanks
… On Apr 20, 2023, at 12:41 AM, Chris Hocking ***@***.***> wrote:
I don't believe I ever got the Last MOV to BRAW.fcpxml from you, so if you can re-send that would be great. Thanks!
—
Reply to this email directly, view it on GitHub <#104 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACJCKTXTEQMDPDM5KL4F42LXCDSCTANCNFSM6AAAAAAWLIQP3I>.
You are receiving this because you authored the thread.
|
latenitefilms
added
bug
|
This is the error I get when trying to import that FCPXML. Will need to do some further digging.
|
latenitefilms
changed the title
|
Can you try create a new event, with a single Before dragging this event to the Toolbox, select the |
|
Chris, I just sent you a Quicktime screen recording (ignore the first one, just view the second one) showing what happens when I attempt to do this. There’s no success. I started to wonder if the issue (in this test case) is if FCP sees the proxy as an original file and not a proxy and that’s complicating BRAW Toolbox. In other words, I only brought in the MOV clip, but FCP assigns that as an original file. FCP won’t allow the same clip to be used as a proxy. However the codecs are shown in my quicktime, the playback is set to proxy, and the clip is still viewable / playable when set to proxy only.
I created a test folder with the same proxy clip in an original folder and a proxy folder so I could separate the two and put the braw original file with the proxy file in the proxy folder since BRAW Toolbox requires that. It still didn’t work.
Thanks,
Tangier
… On Apr 29, 2023, at 2:35 PM, Chris Hocking ***@***.***> wrote:
Reopened #104 <#104>.
—
Reply to this email directly, view it on GitHub <#104 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACJCKTSBKESP26KQXRQUDCLXDWCT5ANCNFSM6AAAAAAWLIQP3I>.
You are receiving this because you authored the thread.
|
|
As the instructions say, the BRAW file needs to be in the SAME folder as the MOV:
Have a look at this post, and see if that makes more sense: |
|
Hi Chris. My braw file that I imported is in the same folder as the proxy version. It’s a proxy as identified by FCP as a proxy video file other than the original, not proxy in the literal sense as any video file that isn’t the original and lower quality than the original due to codec. It shows this in the video I sent at 1:16. The braw and proxy files are in the same folder.
Here’s a screenshot of the quicktime video I sent with the braw and proxy file. in the same folder, with the file names being the same.

Tangier
… On May 2, 2023, at 3:51 PM, Chris Hocking ***@***.***> wrote:
As the instructions say, the BRAW file needs to be in the SAME folder as the MOV:
<https://user-images.githubusercontent.com/22286696/235800852-5a0c447f-8db4-4992-9740-15faad765c58.png>
Have a look at this post, and see if that makes more sense:
#124 (comment) <#124 (comment)>
—
Reply to this email directly, view it on GitHub <#104 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACJCKTVEBIPZSV232GZTOG3XEGFXXANCNFSM6AAAAAAWLIQP3I>.
You are receiving this because you authored the thread.
|
|
I don't think your screenshot came through, but I can see it in your screen recording:
The BRAW file needs to be in the same folder as the Original source file. This is probably where the confusion lies... When we say "proxy", we don't actually mean Final Cut Pro proxies - we just mean a MOV as opposed to a BRAW file. The Optimised/Original, Proxy Preferred and Proxy Only are irrelevant in terms of BRAW Toolbox. |
|
Yes, that’s it. I know the folders may seem backwards. It’s because I already brought in the MOV and FCP would inherently think that’s the original. So I just put the braw and a copy of the original in a proxy folder since FCP won’t allow the original and proxy to reference the same file.
Tangier
… On May 2, 2023, at 6:07 PM, Chris Hocking ***@***.***> wrote:
I don't think your screenshot came through, but I can see it in your screen recording:
<https://user-images.githubusercontent.com/22286696/235815943-643e9920-dfc0-4c1e-9d04-b4529831dc24.png>
The BRAW file needs to be in the same folder as the Original source file.
This is probably where the confusion lies... When we say "proxy", we don't actually mean Final Cut Pro proxies - we just mean a MOV as opposed to a BRAW file.
The Optimised/Original, Proxy Preferred and Proxy Only are irrelevant in terms of BRAW Toolbox.
—
Reply to this email directly, view it on GitHub <#104 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACJCKTSJB2IH2KSDGB4QCBTXEGVU5ANCNFSM6AAAAAAWLIQP3I>.
You are receiving this because you authored the thread.
|
|
So to clarify, you've actually imported the MOV in the ...and if you follow these steps, it doesn't work on your machine? |
|
The mov file in the proxy folder is linked as an actual proxy file in FCP. A duplicate of that file is in the “original” folder. This was the only one imported directly.
I could delete that original folder and solely focus on the proxy folder and relink that mov currently there as the original mov file. It seems ultimately what matters is that the braw and proxy file are in the same folder no matter what the folder name is.
Technically both mov files are “proxy” clips made from the braw before they were delivered to me; perhaps with a third party tool. They’re duplicates of each other. Though when I read "Add BRAW Toolbox to Proxy Clips within an event”, I read that to mean, FCP must see that proxy clip in the event as an FCP database designated proxy clip, not a proxy by codec. Therefore I had to have an original clip (the mov file as an original) and I made a duplicate of it in a separate folder so that FCP would designate it as a qualified proxy before I could use this BRAW Toolbox feature.
Since I can’t import the BRAW Toolbox-generated clip can’t reference a Finder clip I can’t use it as an original clip against a proxy clip (file in the Finder). I needed to have an original clip and a proxy clip qualified by FCP before I could use this feature. Not sure if this makes sense.
Tangier
… On May 2, 2023, at 7:17 PM, Chris Hocking ***@***.***> wrote:
So to clarify, you've actually imported the MOV in the proxy folder into Final Cut Pro?
...and if you follow these steps, it doesn't work on your machine?
#124 (comment) <#124 (comment)>
—
Reply to this email directly, view it on GitHub <#104 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACJCKTXEXCKWFSPRPOFT34TXEG52FANCNFSM6AAAAAAWLIQP3I>.
You are receiving this because you authored the thread.
|
|
Basically the Toolbox should probably be renamed to Add BRAW Toolbox to Video Clips within an Event. Yes, the only thing that's really important is that the BRAW file must be in the same path as the MOV file. |
|
Yeah. I don’t know why it doesn’t work for me. I have the files in the right place.
Tangier
… On May 2, 2023, at 7:36 PM, Chris Hocking ***@***.***> wrote:
Basically the Toolbox should probably be renamed to Add BRAW Toolbox to Video Clips within an Event.
Yes, the only thing that's really important is that the BRAW file must be in the same path as the MOV file.
—
Reply to this email directly, view it on GitHub <#104 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACJCKTQ63FXIKT43TOOQTGLXEHAD7ANCNFSM6AAAAAAWLIQP3I>.
You are receiving this because you authored the thread.
|
|
Can you try on a new library, and basically just follow the exact same steps here and see if it works? |
|
This is actually my third attempt even though it’s called test 2. It finally worked. Though like before I couldn’t drag the event which I think led to me sending the XML.
I’ll send the screen recording so you can see my entire process.
Thanks,
Tangier
… On May 2, 2023, at 7:40 PM, Chris Hocking ***@***.***> wrote:
Can you try on a new library, and basically just follow the exact same steps here and see if it works?
#124 (comment) <#124 (comment)>
—
Reply to this email directly, view it on GitHub <#104 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACJCKTX42YLPV6QGKEXSVQTXEHAQBANCNFSM6AAAAAAWLIQP3I>.
You are receiving this because you authored the thread.
|
|
I think MAYBE the issue you're having is that you have a BRAW Toolbox clip already in your event. I THINK it's only expecting to have MOV files in there. Will investigate. |
|
I'm going to close this issue in favour of #124. |
Using v1.0.6 (44) on Mac Book Pro / M2 Max / macOS 13.2.1 / FCP 10.6.5
I am attempting to use the Add BRAW Toolbox to Proxy Clips within an EVENT feature. Once I get the success message from BRAW Toolbox and drag the green event into my library, the event snaps back into place int he BRAW Toolbox window no matter what I do or how many times I try.
I have the proxies in the same folder as the braw clips. If I didn't I wouldn't have gotten a success message. I granted access to the top level folder for all assets.
The text was updated successfully, but these errors were encountered: