AAF if anyone can test?

[trevora]

Hi

I'm an editor trying out Resolve v15 beta and have done a simple AAF export test to see what the limitations are (partly in response to the DaVinci Resolve AAF Test thread). If anyone does have some time to try it out and report any problems (I don't have access to PT at the mo). Thanks & apologies for double post - be good if any responses went in the other thread.

https://we.tl/s1tF5YHGQG

4 x mono tracks with a mixture of mono and stereo sources:
A1 mono - mono dialogue source
A2 mono - mono fx
A3 mono - stereo fx
A4 mono - stereo music

Then duplicated the clips and put them in A5-A8 stereo tracks.

Exported using default settings (other than setting 50f handles and changing video to DNX36)

Also exported a stereo mixdown to check sync.

No frame rate changes, no fades / levels / eq / gain etc applied.

ID sources are the whole source clip, others are from within a bigger clip so should be a reasonable guide to see if sync is maintained compared to mixdown.


PS The mono source in stereo timeline track & vice versa are gotchas for why you might get weird sources from editors. In Media Composer it's not possible to mix up tracks like this, but PP and Resolve do let you.

[lucienpalmer]

Seems to work okay. Is this the version that was just released? I had an export from Resolve two weeks ago that was a nightmare. (actually they all have had problems)

When I first imported yours, I thought it was empty, but then zoomed in and found the picture and audio hiding at 09:59:55:00. Did you intend to start it there?

[trevora]

Thanks for checking.

That’s the template start time - usually 4” slate, 1” prevision.

Good to know that PT always starts at 0 though!

Thanks

[mfranken]

Thanks for sharing the AAF. I had a look as well as I wanted to check the stereo tracks. Tested with PTHD 2018.1 - all opened okay with 50fr handles. However when I played the AAF tracks with the mix tracks you supplied I noticed some AAF clips were 1 frame late and some were 1 frame early. See clip groups on new tracks:




Regards,

Mark

[lucienpalmer]

I mixed a theatrical feature that came from Resolve about two months ago. That version had certain scenes 2 frames off, and some were correct.

Sounds like maybe a bug in their export.

[trevora]

Originally Posted by mfranken

Thanks for sharing the AAF. I had a look as well as I wanted to check the stereo tracks. Tested with PTHD 2018.1 - all opened okay with 50fr handles. However when I played the AAF tracks with the mix tracks you supplied I noticed some AAF clips were 1 frame late and some were 1 frame early. See clip groups on new tracks:




Regards,

Mark

Interesting.

Upon further inspection of Resolve timeline I can see that Resolve's edit index has the timeline ins incorrectly. (i.e. I jump forward to next edit and sometimes the playhead is 1 frame earlier than the actual edit).

Also there is a discrepancy in the source timecodes in Resolve compared to those imported from the AAF (in Media Composer).

(Some of my sources were 44.1, so maybe there is an error introduced by the SRC too.)

Here's the Resolve timeline lined up, with the same clip sources coloured the same, not sure it's any help in diagnosis!

https://www.dropbox.com/s/8mmyq4y1zt...F_180502_2.png

[TVPostSound]

Originally Posted by lucienpalmer

I mixed a theatrical feature that came from Resolve about two months ago. That version had certain scenes 2 frames off, and some were correct.

Sounds like maybe a bug in their export.

Ive received AAFs from MC that had parts 2 frames off too!!

[polyh3dron]

Originally Posted by TVPostSound

Ive received AAFs from MC that had parts 2 frames off too!!

Yep, same here with FCP7 (OMFs though)