Editing issue in FCP

[Guthrie64]

Making an edit in FCP, with a converted BRAW file (from a BMPCC 6k), doesn't remove the portion of the clip that I want removed. Instead the clip in question is shortened by the duration I wanted removed but the clip begins at the same place it was originally, prior to the edit. The duration does change to reflect the edit but the in point remains the same. I've tired it a number of times and the issue persists. Do you have a suggestion? Thanks

[Guthrie64]

Conversely, if I trim from the tail of the same clip the edit is as it would be expected. It's only at the beginning of the clip where the issue is noted. I also note that the audio, when trimmed from the beginning is off by a corresponding amount of time so that it is no longer sync'd.

[Guthrie64]

I also note that when attempting to add a dissolve at the head of the clip it leaves a thin re

d line where the rendering would normally be seen and the resulting dissolve is staccato at best.

[Guthrie64]

Like the previously mentioned edit issue, the dissolve at the end of the clip is perfect and not exhibiting the issue I mentioned above.

[latenitefilms]

I assume you're running BRAW Toolbox v1.0.2 on Final Cut Pro v10.6.5?

Are the BRAW clips the same frame-rate as the project/timeline? I believe those "red lines", although totally undocumented in any of the Final Cut Pro manuals, only happen if you have, for example, 25fps footage in a 24.0fps project. They seem to only appear if you have clips on the primary storyline (i.e. if you move them to a secondary timeline they'll disappear), and I don't think they have any impact on the video - they're just used internally by Apple for debugging. I've asked the Final Cut Pro team about an official response about them, but they haven't been able to give me a proper answer yet.

Making an edit in FCP, with a converted BRAW file (from a BMPCC 6k), doesn't remove the portion of the clip that I want removed. Instead the clip in question is shortened by the duration I wanted removed but the clip begins at the same place it was originally, prior to the edit. The duration does change to reflect the edit but the in point remains the same. I've tired it a number of times and the issue persists. Do you have a suggestion?

Just to confirm, you're importing these clips into a timeline, correct? For clarity, you should never edit the "insides" of the Synchronised Clips or Multicam Clips.

If you are importing into a timeline, are these the same clips that have the red lines? Curious... does converting the clip into a compound clip in the timeline fix the issue? If so, can you try creating Multicam Clips rather than Synchronised Clips when importing from BRAW Toolbox?

See: https://brawtoolbox.io/faq/#i-dont-like-synchronised-clips-can-i-import-a-multicam-clips-instead

[Guthrie64]

Hi Chris:

I'm away from my office attempting to rectify some streaming issues at our church and am away from my system.

The clips are all the same frame rate (30fps) and aspect ratio (6144x3456) as shot (BRAW) in my BMPCC 6k.

I'll be in touch. I really like what you've done with your plugin and do hope I won't have to return to shooting ProRes clips as opposed to BRAW. As has happened in the past, I seem to be the only soul with these issues...

Thanks!

On Sat, Feb 11, 2023 at 3:55 PM Chris Hocking @.***> wrote:

I assume you're running BRAW Toolbox v1.0.2 on Final Cut Pro v10.6.5?

Are the BRAW clips the same frame-rate as the project/timeline? I believe those "red lines", although totally undocumented in any of the Final Cut Pro manuals, only happen if you have, for example, 25fps footage in a 24.0fps project. They seem to only appear if you have clips on the primary storyline (i.e. if you move them to a secondary timeline they'll disappear), and I don't think they have any impact on the video - they're just used internally by Apple for debugging. I've asked the Final Cut Pro team about an official response about them, but they haven't been able to give me a proper answer yet.

Making an edit in FCP, with a converted BRAW file (from a BMPCC 6k), doesn't remove the portion of the clip that I want removed. Instead the clip in question is shortened by the duration I wanted removed but the clip begins at the same place it was originally, prior to the edit. The duration does change to reflect the edit but the in point remains the same. I've tired it a number of times and the issue persists. Do you have a suggestion?

Just to confirm, you're importing these clips into a timeline, correct? For clarity, you should never edit the "insides" of the Synchronised Clips or Multicam Clips.

If you are importing into a timeline, are these the same clips that have the red lines? Curious... does converting the clip into a compound clip in the timeline fix the issue? If so, can you try creating Multicam Clips rather than Synchronised Clips when importing from BRAW Toolbox?

See: https://brawtoolbox.io/faq/#i-dont-like-synchronised-clips-can-i-import-a-multicam-clips-instead

— Reply to this email directly, view it on GitHub https://github.com/latenitefilms/BRAWToolbox/issues/81#issuecomment-1426874900, or unsubscribe https://github.com/notifications/unsubscribe-auth/A52Z4ZESRXRDUTC4KSN24OLWW74F7ANCNFSM6AAAAAAUYZ6VHE . You are receiving this because you authored the thread.Message ID: @.***>

-- Nick Nicholson Principal

404-316-5842 @.*** www.skysight.aero

[Guthrie64]

Chris:

Running BRAW Toolbox v1.0.2 (36) FCP v 10.6.5 Ventura 13.2 BRAW frame rates identical as purposefully shot by me yesterday.

When I queried a senior advisor at Apple he had never encountered them (red lines) previously and suggested that I upgrade to: [image: Screenshot 2023-02-11 at 7.59.58 PM.png] I was currently on Blackmagic RAW 2.7. Alas, this made no difference whatsoever.

I am importing the selected clips into a bin and then into a timeline in FCP.

I will now try importing Multicam clips as opposed to Synchronized clips, and see if that remedies the issue.

Thanks.

On Sat, Feb 11, 2023 at 3:55 PM Chris Hocking @.***> wrote:

I assume you're running BRAW Toolbox v1.0.2 on Final Cut Pro v10.6.5?

Are the BRAW clips the same frame-rate as the project/timeline? I believe those "red lines", although totally undocumented in any of the Final Cut Pro manuals, only happen if you have, for example, 25fps footage in a 24.0fps project. They seem to only appear if you have clips on the primary storyline (i.e. if you move them to a secondary timeline they'll disappear), and I don't think they have any impact on the video - they're just used internally by Apple for debugging. I've asked the Final Cut Pro team about an official response about them, but they haven't been able to give me a proper answer yet.

Making an edit in FCP, with a converted BRAW file (from a BMPCC 6k), doesn't remove the portion of the clip that I want removed. Instead the clip in question is shortened by the duration I wanted removed but the clip begins at the same place it was originally, prior to the edit. The duration does change to reflect the edit but the in point remains the same. I've tired it a number of times and the issue persists. Do you have a suggestion?

Just to confirm, you're importing these clips into a timeline, correct? For clarity, you should never edit the "insides" of the Synchronised Clips or Multicam Clips.

If you are importing into a timeline, are these the same clips that have the red lines? Curious... does converting the clip into a compound clip in the timeline fix the issue? If so, can you try creating Multicam Clips rather than Synchronised Clips when importing from BRAW Toolbox?

See: https://brawtoolbox.io/faq/#i-dont-like-synchronised-clips-can-i-import-a-multicam-clips-instead

— Reply to this email directly, view it on GitHub https://github.com/latenitefilms/BRAWToolbox/issues/81#issuecomment-1426874900, or unsubscribe https://github.com/notifications/unsubscribe-auth/A52Z4ZESRXRDUTC4KSN24OLWW74F7ANCNFSM6AAAAAAUYZ6VHE . You are receiving this because you authored the thread.Message ID: @.***>

-- Nick Nicholson Principal

404-316-5842 @.*** www.skysight.aero

[latenitefilms]

Yeah, the red frame thing is a bit of a mystery - I have an open Radar/Feedback Assistant enquiry with Apple, but the FCPX team haven't given me any useful answers yet. Either way, the red frames aren't specifically a BRAW Toolbox issue, as they are still there even if you delete the BRAW Toolbox effect - it's something to do with Generators inside Sync/Multicam Clips, possibly some kind of duration bug. I'll update the documentation if Apple ever comes back with some definitive information.

Keep me posted on how you go with Multicam Clips.

[latenitefilms]

Oh, and I also can't see the "Screenshot 2023-02-11 at 7.59.58 PM.png" image?

[Guthrie64]

I'm uploading a 1 minute clip to Frame.io and will invite you to view it if you're curious.

On Sat, Feb 11, 2023 at 8:31 PM Chris Hocking @.***> wrote:

Oh, and I also can't see the "Screenshot 2023-02-11 at 7.59.58 PM.png" image?

— Reply to this email directly, view it on GitHub https://github.com/latenitefilms/BRAWToolbox/issues/81#issuecomment-1426916157, or unsubscribe https://github.com/notifications/unsubscribe-auth/A52Z4ZB7RJQRQPROVHX2ZOLWXA4PHANCNFSM6AAAAAAUYZ6VHE . You are receiving this because you authored the thread.Message ID: @.***>

-- Nick Nicholson Principal

404-316-5842 @.*** www.skysight.aero -- Nick Nicholson Principal

404-316-5842 @.*** www.skysight.aero

[latenitefilms]

What's the 1 minute clip of?

Feel free to post a link here or send to:

https://brawtoolbox.io/support/

[Guthrie64]

Please disregard my prior email re the 1 minute clip. I think I have your program figured out after more experimentation today. Well done.

On Sun, Feb 12, 2023 at 2:07 PM Chris Hocking @.***> wrote:

What's the 1 minute clip of?

Feel free to post a link here or send to:

https://brawtoolbox.io/support/

— Reply to this email directly, view it on GitHub https://github.com/latenitefilms/BRAWToolbox/issues/81#issuecomment-1427108961, or unsubscribe https://github.com/notifications/unsubscribe-auth/A52Z4ZEPLO3YW3TADUEM4BLWXEYHLANCNFSM6AAAAAAUYZ6VHE . You are receiving this because you authored the thread.Message ID: @.***>

-- Nick Nicholson Principal

404-316-5842 @.*** www.skysight.aero

[latenitefilms]

Great news! I'll close this issue for now, but feel free to yell out if you run into any problems or have any issues.

[Guthrie64]

Thank you, Chris.

On Sun, Feb 12, 2023 at 5:10 PM Chris Hocking @.***> wrote:

Great news! I'll close this issue for now, but feel free to yell out if you run into any problems or have any issues.

— Reply to this email directly, view it on GitHub https://github.com/latenitefilms/BRAWToolbox/issues/81#issuecomment-1427145562, or unsubscribe https://github.com/notifications/unsubscribe-auth/A52Z4ZEX2HUIEZPO3CXCNP3WXFNVVANCNFSM6AAAAAAUYZ6VHE . You are receiving this because you authored the thread.Message ID: @.***>

-- Nick Nicholson Principal

404-316-5842 @.*** www.skysight.aero

[Guthrie64]

Chris:

I do have another quick question for you regarding rendering clips once they've been dropped onto a timeline. If the timeline is 6144x3456 and the clip is 6144x3456 both at 30fps, why must the clips be rendered if no efx, grades etc. have been applied. Thanks for bringing BRAW into FCP. It was sorely missed and is a welcomed addition! Here's my system at a glance: [image: Screenshot 2023-02-13 at 10.54.56 AM.png]

On Sun, Feb 12, 2023 at 5:10 PM Chris Hocking @.***> wrote:

Great news! I'll close this issue for now, but feel free to yell out if you run into any problems or have any issues.

— Reply to this email directly, view it on GitHub https://github.com/latenitefilms/BRAWToolbox/issues/81#issuecomment-1427145562, or unsubscribe https://github.com/notifications/unsubscribe-auth/A52Z4ZEX2HUIEZPO3CXCNP3WXFNVVANCNFSM6AAAAAAUYZ6VHE . You are receiving this because you authored the thread.Message ID: @.***>

-- Nick Nicholson Principal

404-316-5842 @.*** www.skysight.aero

[Guthrie64]

I'm going to guess that Ventura is probably the culprit in this equation.

On Mon, Feb 13, 2023 at 10:55 AM Nick Nicholson @.***> wrote:

Chris:

I do have another quick question for you regarding rendering clips once they've been dropped onto a timeline. If the timeline is 6144x3456 and the clip is 6144x3456 both at 30fps, why must the clips be rendered if no efx, grades etc. have been applied. Thanks for bringing BRAW into FCP. It was sorely missed and is a welcomed addition! Here's my system at a glance: [image: Screenshot 2023-02-13 at 10.54.56 AM.png]

On Sun, Feb 12, 2023 at 5:10 PM Chris Hocking @.***> wrote:

Great news! I'll close this issue for now, but feel free to yell out if you run into any problems or have any issues.

— Reply to this email directly, view it on GitHub https://github.com/latenitefilms/BRAWToolbox/issues/81#issuecomment-1427145562, or unsubscribe https://github.com/notifications/unsubscribe-auth/A52Z4ZEX2HUIEZPO3CXCNP3WXFNVVANCNFSM6AAAAAAUYZ6VHE . You are receiving this because you authored the thread.Message ID: @.***>

-- Nick Nicholson Principal

404-316-5842 @.*** www.skysight.aero

-- Nick Nicholson Principal

404-316-5842 @.*** www.skysight.aero

[latenitefilms]

They don't HAVE to be rendered. BRAW Toolbox is just an effect, so you'll always see render lines above the BRAW clips - but if your system is fast enough to play them back, there's no need to actually render them.

[Guthrie64]

Understood. Indeed, once rendered on the timeline, I no longer have to re-render after simple edits.

On Mon, Feb 13, 2023 at 2:16 PM Chris Hocking @.***> wrote:

They don't HAVE to be rendered. BRAW Toolbox is just an effect, so you'll always see render lines above the BRAW clips - but if your system is fast enough to play them back, there's no need to actually render them.

— Reply to this email directly, view it on GitHub https://github.com/latenitefilms/BRAWToolbox/issues/81#issuecomment-1428514256, or unsubscribe https://github.com/notifications/unsubscribe-auth/A52Z4ZG6FATO553ESJGO2ELWXKB7JANCNFSM6AAAAAAUYZ6VHE . You are receiving this because you authored the thread.Message ID: @.***>

-- Nick Nicholson Principal

404-316-5842 @.*** www.skysight.aero