My FCPX Braw Workflow

Поделиться
HTML-код
  • Опубликовано: 15 июл 2024
  • LUT i use: payhip.com/b/S5vw1
    Video Retainer Contract Template: podcast.adobe.com/enhance
    Learn the EASIEST and FASTEST way to get BRAW files into FCPX and SAVE ON HARD DRIVE SPACE.
    Instagram: / joshrchappell
    Intro 0:00
    BRAW Files 1:10
    Import Into Resolve 2:00
    Apply Color Grade Resolve 2:50
    Resolve Export Settings 4:35
    Compare Sizes 6:16
    Bring Into Final Cut 6:35
    Archiving 8:35
  • КиноКино

Комментарии • 19

  • @MaxLib
    @MaxLib 2 года назад

    This is the best tutorial on this on RUclips and I’m serious.. Thank you:

  • @seanholloran
    @seanholloran 2 года назад +2

    thanks for this. have been searching around for a tutorial where I just got 6k pro and am used to using final cut.

  • @asphaltandtacos
    @asphaltandtacos Год назад

    You could group all of the clips and apply a grade or use the Color Management tool to get a nice looking image. With the second option you can return to Resolve after the edit is complete for color grading and finishing. There are tools in Resolve to speed up the color correction process.

  • @uncleanAlibertine1
    @uncleanAlibertine1 2 года назад +3

    nice ! But another option is to do basic lut and exposure with WB, and then do pro res proxies in davinchi and use other video work, as this isn/t to hard on computer! great video!

  • @_Mach3
    @_Mach3 2 года назад +4

    This is cool and all but is it good to color before you edit? What if you edit and you wanna change the feel?

  • @eiga0114
    @eiga0114 2 года назад +6

    So, you basically delete all your native footage ? Who wants to do that ? I mean, there's no point to shoot in 6K if you eventually just create proxies in H265 and then delete the natives.
    Simplest workflow is to create proxies in Resolve, edit in Final Cut Pro, then export to sound edit via AAF (using X2Pro or Logic Pro AAF export), and then export a XML to Resolve and relink to natives for color grading. Then, sync everything for final delivery.
    Before creating proxies in Resolve, make sure to check "Assist reel names from the source clip file name" in the general options, so that every metadatas will remain in case you decide to rename your clips in FCP X.

    • @clarksvisions
      @clarksvisions 2 года назад +1

      this is the one right here!!

    • @flickharrison2770
      @flickharrison2770 Год назад

      That sounds good - But I'd want to be very sure all my fx, retiming, transitions and so on translate into a DaVinci XML. I've had misery a few times around such issues going from FCPX to ProTools.

    • @eiga0114
      @eiga0114 Год назад

      @@flickharrison2770 XML usually import just fine on Resolve by my side - in fact, I prefer using them over AAFs export, so I do XMLs even from Premiere. The transition from FCP X to Pro Tools, however, is the most problematic since Avid will only allow you to use AAFs. The two methods described should work fine, but it’s definitely better to try the workflow prior to the editing step.

  • @obscuriatv9977
    @obscuriatv9977 2 года назад

    Seems like you would wait until your edit is locked on FCP before going to Davinici for the grade. After the grade is done, are there any downfalls to exporting the master from Davinici, or does it need to go back to FCP?

  • @coreycook7447
    @coreycook7447 2 года назад

    Great video! I started to do this with a project I have and about 10 min worth of shooting in braw turned into a 17 hour render to H.265. Is this right? I stopped the render and wasn't sure if it would really take this long? I have a very fast MacBook Pro with 64G of ram and all of the files live on the internal Mac hard drive so it's not a bandwidth issue with a slow external.

    • @coryoung1
      @coryoung1 2 года назад

      I think yoir problem is, by having all files ON your computer HD, is going to 100% slow down your computer, because you’re taking up all its memory space. Along with your internal HD is an HDD. You need an external SSD.

    • @coreycook7447
      @coreycook7447 2 года назад

      @@coryoung1 My internal hard drive is way faster than an external drive. I think it's because H.265 is a more compressed file size so that might be why it's taking longer. I tried converting the Braw files to Apple Prores HQ and 45 min of footage only takes about 5-7 min. to convert to prores! so this is what I've been doing now.

  • @DavinciHD_
    @DavinciHD_ 2 года назад

    I’m getting black bars all around my footage doing this method. Is there a reason for that? I followed all instructions

  • @1001Hobbies
    @1001Hobbies Год назад +1

    For me, the question becomes....if the files are no longer going to be raw files of any kind, would a person be further ahead to just shoot in the highest quality of Pro Res instead? Is there any image quality gained by doing it this way over ProRes?

    • @JoshChappell
      @JoshChappell  Год назад

      If you want to color grade, than shooting braw would still be the best option. If you don’t want to color grade, than yes shooting prores could work too

  • @coryoung1
    @coryoung1 2 года назад

    Do you know why, that going from DR, that it shrunk the video? I followed the same steps as you. It still claims 6k, but it doesnt seem right. Your video fills the whole window, while mine is half the size looking….? 😅

  • @mikeseager8768
    @mikeseager8768 2 года назад

    What iMac are you using to be able to edit the BRAW footage so well? In the market for a new machine and debating on getting a 2 -3 yearold iMac Pro, or going with one of the new M1's

    • @JoshChappell
      @JoshChappell  2 года назад +1

      I like the M1s for portability. The older iMac Pro is a beast too.