I actually did tests on premiere (cc2014 on 10.9.5) to protools (11.x.x on 10.10.x) today. Not a fully test though.
My issue was that both the aaf and the omf dropped the time code on import to protools. And instead of using the clips original time code it started the clips time code at 00:00:00:00.
As far as my tests went I could conclude that exporting both aaf and omf was unreliable.
Test subject
A random videoclip chopped up in a sequence (1080p25)
Export aaf with both wave/aiff embedded or separate clips gave the wrong time code in protools.
However the funky thing is importing the aaf back to premiere showed a drift in the audio time code.
So something is weird with the aaf.
I also tried the "go to audition" and exported omf from it - no luck , it still dropped the time code.
Just for the fun of it, when I troubleshoot I tried going through good old fcp7 via xml and then aaf via automatics duck .. And guess what no drop or drift in time code.
Unfortunately I didn't had the time to go more into this today..but to be continued.
But I do wonder how do other export to protools - when the sound designer actually has to link back to his original sound files.
Tina Hedegaard | Teknisk koordinator • Trainee supervisor
Mob: (+45) 31412150 | tina@postyr.dk
PostyrPost PostyrPostproduktion
On 06/09/2015, at 18.26, Pat Horridge pat@horridge.org.uk [Avid-L2] <Avid-L2@yahoogroups.com> wrote:
But isn't the Adobe "suite" idea that you do it all in Adobe cloud land? Good interop with the outside world sort of breaks that ethos.
Pat from his mobile.
__._,_.___
Posted by: Tina Hedegaard <hedegaardforum@me.com>
| Reply via web post | • | Reply to sender | • | Reply to group | • | Start a New Topic | • | Messages in this topic (8) |
this is the Avid-L2
.
__,_._,___
No comments:
Post a Comment