Forum Replies Created

Page 49 of 2910
  • Jeremy Garchow

    January 17, 2019 at 7:41 pm in reply to: FCPX 10.4.5 update

    I hope this does actually improve performance on those clips. This has been a problem for a very long time.

    In a separate note, the update notes from Slack were funny today.
    In a separate note, the update notes from Slack were funny today. (fixed)

  • Jeremy Garchow

    January 15, 2019 at 7:54 pm in reply to: Big Project Render / Share Issue Won’t Go Away!

    – Try exporting in 5 minute chunks. See if you get any errors.

    – Snapshot the timeline and try breaking apart your compound clips, see if that will export.

    – Try exporting to a different drive, if you have the space.

    Jeremy

  • Jeremy Garchow

    January 10, 2019 at 5:58 pm in reply to: 4K and Mac HDMI

    Sorry, for the Pr screen grab, the 4k out to the Sony monitor is the “Adobe Monitor 2” option even though the T-Tap is selected.

  • Jeremy Garchow

    January 10, 2019 at 4:48 pm in reply to: 4K and Mac HDMI

    You can get UHD (or 4k) 24, 25, or 30p to a consumer set, yes. iMac Pro may get you higher frame rates. You can see I can choose between AJA and the HDMI here:

    FCPX:

    Adobe:

    There are Sony OLED consumer sets around here, and even 2013 rMBP can send 4k them out of the built-in HDMI

  • Jeremy Garchow

    December 14, 2018 at 3:14 am in reply to: Blurry image using effect with Shape Mask

    Can you show a picture of the mask in the FCPX viewer?

  • Jeremy Garchow

    December 13, 2018 at 5:56 pm in reply to: Apple and LumaForge

    I saw the Lumaforge offerings on Apple.com yesterday, but didn’t know about Bayes. This is really cool!

  • What version of Ae?

    V16 has a bug that alphas weren’t rendered. An update was released a day or two ago.

    Other than that, try changing the alpha type as Jeff suggests.

  • Jeremy Garchow

    December 12, 2018 at 6:51 pm in reply to: Davinci FCPX timeline corruption on roundtripping.

    Some of the things do translate, some don’t. It’s really a case by case basis, and you certainly have to spend a little time “prepping” the timeline in DaVinci. I typically try and keep things as simple as possible when sending to DaVinci, which means I have to spend some time getting things back together in FCPX.

  • Jeremy Garchow

    December 12, 2018 at 1:25 pm in reply to: Attack of the Phantom Sound Effect

    Try deleting the render files for that Project.

  • Jeremy Garchow

    December 12, 2018 at 1:24 pm in reply to: Davinci FCPX timeline corruption on roundtripping.

    I typically break everything down before going to Resolve. I then reassemble all the effects back in fcpx.

    It would be hard to help you as I can’t see exactly what’s happening, but I find it best to simplify the timeline before sending to Resolve.

    Secondary storylines come over as nests in Resolve. You can “Decompose in place” in Resolve to get access to the clips.

Page 49 of 2910

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy