Forum Replies Created

  • Hey Glenn,
    Thanks for getting back to me, it’s a bit of a weird one actually.
    The workflow for the most part is standard, the DIT transcoded to DnxHD36 on set in resolve and has supplied us, into the avid like normal, but we’re working with directors who like to do their own effects in AE.
    So the edits in avid, then we have a lot of temp comp work done in AE, but we need to send a proper EDL of the edit to where its being finished, but as say the edit has a comp in it called ‘lemons_2.mov’ from AE, I need to get the assets from AE into that EDL.
    So AE- send to Premiere, from Premiere make an AAF, import that AAF into Avid (without Avid playing up) and then replace the comp with the rushes used.
    Bit long but the directors are fussy so it has to be done this way,

    Out of about 14 comps I have to replace it’s worked maybe once,
    I haven’t fixed the problem yet but still looking into it,
    But I need to fix it soon so will let you know how I get on,

    Assistant Editor @whitehousepost LDN
    Avid – FCP7 – FCPX – Premier Pro CC – Resolve 12

  • Hey Kevin,
    Did restranscoding in resolve fix this issue?
    I’ve had exactly the same thing happen,

    I imported an AAF from premire into Avid (long story short there were some comps built in AE but I need to supply proper EDLs to the post houses), the AAF was made of 5 clips or so, 3 wont link now as they’re being recognised as DV 25P 420 (PAL),
    My media creation is all set to DNxHD36, I’ve trashed the database, reimported.

    And it’s definitely the AAF that has done this, I opened a backup project without the ISIS media mounted so everything was offline and it all read as should, DNxHD36.

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