1.0 and Media Composer 10.0

[EasternSky]

When will we see an upgrade to include compatability with Media Composer 10.0 an a Meridian board set?

Can Digi coordinate the development of these two applications so we don't have a leap frog effect?

David Brown

[Paul Greyson]

Sorry, I don't understand your question?
Is this a question about Digi Translator?

------------------
Paul Greyson
Digidesign Engineering

[EasternSky]

Originally posted by Paul Greyson:
Sorry, I don't understand your question?
Is this a question about Digi Translator?

Yes.

[Paul Greyson]

OK. I still don't understand you're question.

What's the compatability issue?

------------------
Paul Greyson
Digidesign Engineering

[EasternSky]

I recently finished a project that I received from an Avid Media Composer 10.0. All translated well from Avid to Pro Tools via Digi Translator. I completed a mix, translated to Avid from Pro Tools in Digi Translator. When the Avid editor tried to open the program, he received a prompt saying the file was of the wrong type. Even trying to import the .aif files of the mix received the same prompt. The work around was to load it on his mac, convert the .aif files to .aif (no changed parameters, just go through the motions), network over to the Avid, import and re-sync via start and end frames. I called Digi to find out what the problem was, and the tech said Digi Translator was incompatable with Avid v 10.0. He told me the work around (which we came up with on our own). So, when will this be resolved and will it continue to leap frog as each application grows and changes? Will the new version of Digi Translator address this? When will it be ready?

David Brown

[Paul Greyson]

Which Pro Tools version are you using?

Also, exactly what was the error message the Avid editor received? I don't recognize what you describe.

------------------
Paul Greyson
Digidesign Engineering

[EasternSky]

Exception: File Edit Rate not equal to Project Edit Rate

[Paul Greyson]

Hmm. How is the target MC project setup? 29.97? It's necessary to set the DT options to match the target project.

There error message you describe occurs when they don't match.

Another possibility is that "Quantize Edits To Frame Boundaries" was unchecked. This option is required for interacting with Avid systems.

None of this is particular to MC 10

------------------
Paul Greyson
Digidesign Engineering

[doug sjostrom]

This is a known bug! Avid broke Composer. 10.1 fixes this. It's not a DT problem, but an Avid Problem. It covers Composer v 8 thru 10.

[Paul Greyson]

Doug, I don't think this is the bug that was fixed in 10.1. That was a problem with calculating the number of samples in a given number of frames. This problem sounds like incorrect settings in DT.

------------------
Paul Greyson
Digidesign Engineering