Media Composer, Poly Channel Files + AMA = Lots of troubles??

[rantanplan]

Hi there,

I know that this has been discussed already many times. But we still couldn't find the solution in our case...

I have to admit that I'm still using PT 10 HD. But I think that the issue is on the Media Composer's side.

When I import the AAF into Pro Tools it always complains about Poly channel files and that it can only refer to the first track.

On top of this there's also an issue with the sample rate. In Media Composer we forced the audio to be converted into mono 48/24 WAVs, but the import window in PT still tells me that the AAF is mixed sample rates - Which is wrong, because all the consolidated WAVs are indeed 48/24 mono.

The video editing guy "spread" all the poly tracks on to several editing tracks, hoping that they will be exported and referred as single mono files. But the AAF still seem to contain information about poly files, no matter what exporting options we choose.

Apparently it's no possible to not consolidate audio data, because they're AMA...

Is there any hope? I don't need these poly files in my PT session, I'm fine with several mono tracks instead. Actually I prefer this. It's for a short film and there aren't many tracks in total.

Is there a way to make Media Composer really forget about Poly Files and treat each track from such a file as an independent mono file? Transcode and consolidate didn't do the trick.

Cheers
Till

[Frank Kruse]

I'm not sure if PT10 was able to play 32bit, maybe it was, it's too long ago, sorry...
Maybe that' part of the problem?

Linking to poly files should not be a problem in general.

You can check if there are still 96k files in the finder or the workspace. Sounds like there still are 96k files in that sequence. If all else fails, try an embedded AAF.

[rantanplan]

Originally Posted by Frank Kruse

I'm not sure if PT10 was able to play 32bit, maybe it was, it's too long ago, sorry...
Maybe that' part of the problem?

Linking to poly files should not be a problem in general.

You can check if there are still 96k files in the finder or the workspace. Sounds like there still are 96k files in that sequence. If all else fails, try an embedded AAF.

Thanks for your reply.

32bit is supported in PT10, this shouldn't be the problem.

All files in the OMFI export folder are mono / 48k/24.

I managed at least to solve the problem with the sample rates: I simply have to use 48kHz as session sample rate and then disable SR conversion in the import dialogue... And chose "link to original files where possible".

But the problem with the poly channel WAVs remains. I will ask the film editor to send me the original field recorder files. I hope that I can still relink the poly files in some way, even when the AAF export session from Media Composer has been consolidated...

Cheers
Till

[rantanplan]

Ok, I think we finally found the issue.

The majority of the field record poly files were recorded with SR 48 kHz, but some are in 96.

Apparently, Media Composer only puts a reference of those files into the AFF instead of rendering the corresponding mono files for each channel. Hence the original field record file can't be matched because it has a different sample rate...

For some reason, transcode in Media Composer does not solve this. So we have to sample rate convert each original file by hand. And then, hopefully, I can link them with the field recorder work flow.

Or we replace all AWA references with conventional audio import.

Cheers
Till

[smurfyou]

AMA can cause trouble on export. But I've only had an issue with random files the edit uses not field recorder files. So it was a quick fix.

For a short film I'd rather try to solve the problem on the Avid side and have them import and convert the files. In a duplicate sequence / project in case it proves difficult. If it works, on your AAF you won't have to worry about matching or linking. They'll be there on the timeline for you.

[rantanplan]

Originally Posted by smurfyou

AMA can cause trouble on export. But I've only had an issue with random files the edit uses not field recorder files. So it was a quick fix.

For a short film I'd rather try to solve the problem on the Avid side and have them import and convert the files. In a duplicate sequence / project in case it proves difficult. If it works, on your AAF you won't have to worry about matching or linking. They'll be there on the timeline for you.

Hi Will, thanks for your reply.

This turns more and more into a nightmare... The SR was not the issue because we have the same problem with some 48kHz files.

Relinking the segments with the field recorder workflow fails because the timestamps are different. I guess that in some part of the processing, AVID lost or changed the time codes. Maybe one consolidating and / or transcoding too many...

I wonder if we can force Media Composer to reference the complete files in the AAF export. Some of WAVs in the OMFI folder differ in length from the original field recorder files.

Cheers
Till

[rantanplan]

I really wonder what is the right way to export AAF from Media Composer when AMA is involved:



results in

[smurfyou]

Have you tried an embedded AAF?

[rantanplan]

Originally Posted by smurfyou

Have you tried an embedded AAF?

We're trying that right now. But there's the 2GB limitation, so we have to split the film...

[its2loud]

You should be able to export a larger AAF file by checking the “AAF Edit Protocol” box.

https://avid.secure.force.com/pkb/ar...ow_to/en389451