AAF import issue

[Chooch]

Anyone experienced the error "Can not import session because data basic_string::at" when importing an AAF from the editor using Avid?

From what I gather its a problem on the editor's side, and that there is some sort of corrupt clip or invalid fade on their end. What should I tell the editor to do to fix it?

Im using PT 9 on a MBP on 10.7.5

Thanks!

[Craig F]

Tell him to make a new AAF and give him the error you are getting

you could try importing only one track at a time to narrow down the culprit for him

[Chooch]

Thanks Craig

Strange thing is that he did the ol' reboot and re-export several times, even went to different machines to source out the issue, and I got the same error on my end.
We ended up settling on an 8 channel .wav file with no renderings, which was really tough due to the lack of handles.

As long as I know its not a PT issue, Im fine with it because there are several options, its just always frightening to get a mysterious PT error when you see the clock ticking down to your deadline!

[Chooch]

In the mix now, got the same problem. We decided to check the edit session track by track, and out of the 12 channels, the first 2 had the corrupt audio. All fades were deleted and his fx turned off, but for some reason they still had issues. I just had him send me expanded clips (like it had handles) as aiffs locked to the timeline. It worked, and the spot is due to air tomorrow, soooooo, there we go...

They said they are going to dig in to it on their end to see what the problem is...I will keep posted with the progress

[Craig F]

are these imbedded or linked AAFs
I prefer linked

[Chooch]

ah, these are embedded

[paranerd]

Originally Posted by Chooch

ah, these are embedded

I always go for the folder option. No size limit and maximum handles.

Once in a while a corrupt clip will just screw the whole thing up for whatever reason. It usually happens on projects where there's a whole bunch of different video sources in all kinds of formats. I try to transcode the audio for the whole sequence first then export from that transcoded sequence. It usually fixes things, but it's kind of equivalent to rebooting when you don't know what's causing the issue.

[Chooch]

Great, thanks so much for the advice!

[Chooch]

Well, looks like we have narrowed down the problem this week. The bites are coming in at 2 different time codes: 23.98 and 59.94.

Tried setting up the session with 23.98 as time code 1 and 59.94 as time code 2 in the Session menu, but no dice.

Any advice in consolidating time code?

[Craig F]

if this is 23.9 project the 59.94 needs to be converted on the Media Composer side to 23.9
or do 2 exports splitting the 2 time codes, make separate Pro Tools sessions fro the different time codes, then import one of the Pro Tools sessions into the other might work