Latest post Sun, Feb 17 2019 9:38 PM by Alayne Holmes. 4 replies.
Page 1 of 1 (5 items)
Sort Posts: Previous Next
  • Fri, Feb 15 2019 9:19 PM

    • Leo Baker
    • Top 500 Contributor
    • Joined on Wed, Oct 5 2011
    • London
    • Posts 314
    • Points 3,865

    AAF from 2018.12.1 Crashes Resolve

    I have two AAF's one from Media Composer 6 works.aaf and Media Composer 2018.12.1 fails.aaf

    Davinci Resolve 15.2.4 and prior v15 releases.

    1. I go to the edit tab, choose FIle, Import Timeline choose my AAF. And The Media offline referances are imported no source files as a test fil;e. Then it crashes resolves with the 2018.12.1. Version 8 imports no crash?

    I created a simple AAF in 2018.12.1 and it won't import into Resolve without a crash.as it shuts down the software. 

     

    Here are the links to the two AAF's

    https://drive.google.com/drive/folders/1FfdGa7uCoLEMKtHDpn8TryxvlJZI077Y?usp=sharing

     

    Avid Media Composer 2018.12 Pro Tools 12.7 OSX Sierra 10.12.6 Computer: HP Z800 DUAL QUAD XEON X5667 3.07GHZ 96GB 2TB Caldigit HDONE Media 1TB SSD Graphics... [view my complete system specs]
  • Sat, Feb 16 2019 1:38 AM In reply to

    • Andrew
    • Not Ranked
    • Joined on Wed, Apr 6 2011
    • Costa Mesa, Orange County, California
    • Posts 105
    • Points 1,245

    Re: AAF from 2018.12.1 Crashes Resolve

    I couldn't open the file that says "works."  I didn't try the other one.

    Avid MC v2018.12.2, macOS Mojave 10.14.3, iMac 21.5-inch, late 2015 (purchased new on Jan. 2017), , Processor: 2.8 GHz Intel Core i5, Memory: 16 GB 1867... [view my complete system specs]
  • Sat, Feb 16 2019 7:33 AM In reply to

    Re: AAF from 2018.12.1 Crashes Resolve

    Using a PC with W10 Resolve 15.2.3. MC 2018.12.1

    Your file that says it works  worked here.  The other one failed crashing Resolve with error message about unknown effects.

    I then tested a 90 minute 1080 50i edit I had just finished here by exporting it from MC 2018.12.1 as an AAF with linked media. There were no effects in the timeline apart from two Rendered Dissolve in and out of title media. Avid MediaFiles\MXF\1 folder. The AAF crashed Resolve the first time. For some reason Resolve did not like the folder I had saved the AAF too. (strange as Resolve had been using media from that folder earlier in the day.) 

    After changing the folder the AAF was in and Resolve was mostly happy. The rendered MC title failed to be recognised (created in the old Title tool). The title only showed during the dissolves. A mixdown of the title and dissolves to and from an imported black movie, not filler, and edited this back to the Resolve timeline fixed the problem.

    If it is of any interest Resolve is exporting to high quality H264 file in real time from the AAF as against 5 hours it took Sorenson Squeeze 11 for  the same file yesterday.

    Alayne

  • Sat, Feb 16 2019 4:44 PM In reply to

    • Leo Baker
    • Top 500 Contributor
    • Joined on Wed, Oct 5 2011
    • London
    • Posts 314
    • Points 3,865

    Re: AAF from 2018.12.1 Crashes Resolve

    Hello Alayne,

    Thanks for testing, that's interesting about the AAF that you exported from your project which crashed Resolve on the first try. But on the second import into Resolve that AAF did not crash based on moving it's folder location?

    Kind regards,

    Leo

    Avid Media Composer 2018.12 Pro Tools 12.7 OSX Sierra 10.12.6 Computer: HP Z800 DUAL QUAD XEON X5667 3.07GHZ 96GB 2TB Caldigit HDONE Media 1TB SSD Graphics... [view my complete system specs]
  • Sun, Feb 17 2019 9:38 PM In reply to

    Re: AAF from 2018.12.1 Crashes Resolve

    Leo Baker:
    But on the second import into Resolve that AAF did not crash based on moving it's folder location?
    Hi Leo, 

    I just moved the AAF to a different folder on the same drive. Both folders are at the base level of the drive. F:\xxx. The why one worked and the other did not makes no sense at all to me. Both have simple short alpha numeric names names and their properties and user permissions are identical.  

    As it had worked the second time the why became secondary. I spent 15 hours with this project yesterday completeing it without issues.   

    Resolve then went up in my appreciation as I discovered it's NVIDIA codec for H264 for the delivery render. 86 minutes of HD encoded to H264 with all settings at highest took just over 19 minutes.   I believe H265 would have been faster with a smaller resultant file but the customer wanted greatest compatability. The file delivered perfectly from a USB3 stick plugged into a USB 2 connection on his BluRay player. 

    Alayne.

Page 1 of 1 (5 items)

© Copyright 2011 Avid Technology, Inc.  Terms of Use |  Privacy Policy |  Site Map |  Find a Reseller