MComposer Automation Not Translating to PT

[Polaris]

We are seeing errors and omission in the automation from the picture editor's avid being translated to a PT10 session. We have tried all the combinations in the AAF import window but none seem to be correct. There are clips that should be playing that do not and vice versa.

As a test, I went back and tried in PT9 and was able to successfully import the correct automation.

Anyone else seeing this behavior?

Cheers

MacPro
PT10.0HD
TDM HD1

[Craig F]

what version(s) of MC?
is it making it to Clip Gain?

[Polaris]

it is MC v5.0.4. and yes, I seem to be able to get clip gain or auto moves but not both.

From my testing, it seems PT9 does more of a "coalesce" of the two types of automation rather than what PT10 does which appears to be a "convert" in PT parlance. The picture editor is using both clip gain and rubber band gain. He'll gain down an alternate using clip gain, then at a later date gain it back up using rubber band gain. Not ideal but its what we got.

There just does not seem to be a way to achieve an AAF conversion in PT10 similar to how it was handled in PT9 which is odd given that PT10 adds these new clip gain features.

Are you seeing similar results by chance? I've made some snapshots as examples. Some of this is subtle but other areas are extreme. Bottom track is a guide. (note the huge gain difference around 520').

Here's what it should look like as created by PT9 (convert clip gain to auto):

https://picasaweb.google.com/lh/phot...eat=directlink

Here's what PT10 is producing (Import clip gain & auto):

https://picasaweb.google.com/lh/phot...eat=directlink

(Import Clip gain NOT checked)

https://picasaweb.google.com/lh/phot...eat=directlink

Its a head scratcher...

[C]

Achieving the same result in 9 and 10 is a two stage process.

First import as clip gain then "coalesce clip gain to volume automation" from Edit > Automation menu. Results in the "coalesce" that you've previously known.

Ceri

[Polaris]

Thanks C.

I had tried that as well and it does not work either. Here's is a typical problem: AAF has a region volume graph = -∞dB but clip gain = 0dB. In PT9, that region comes in at 0dB but in PT10 at -∞dB; no matter what combination of import settings.

Perhaps this is a larger problem of PT10 just not converting automation correctly but its happening a lot on our AAFs.

At any rate, the PT9 session matches the guide track, the PT10 session does not. Just wondering if we are the only ones seeing this.

Cheers,

[C]

AAF has a region volume graph = -∞dB but clip gain = 0dB. In PT9, that region comes in at 0dB but in PT10 at -∞dB; no matter what combination of import settings.

Yes I have seen this before. Does it occur on more than one file for you? I had it happen once a little while ago and couldn't reproduce with another AAF.

[jglasgow]

It turns out this is a known issue. We expect to have a fix very soon.

Best,

[Polaris]

Ah, thank you for the confirmation. I was beginning to worry it was just us.

Glad there is a fix in the works.

@ Ceri - yes, we are seeing it in large and small differences in several AAF's.