After installing 5.2 the 002 option no longer appears in the Send To sub menu 9just the MBox options...any idea why?

Secondly, when I export using the default 002 option and attempt to open the AAF session file in Protools I get the following message:

"Could not create new document because an unexpected error happened while trying to determine the file's timecode format"

This is occuring on all sequences exported no matter 25p or 25i (yes I am in a PAL territory). All sequences tried from different projects start at timecode 00:00:30:00. I have restored the 002 export setting to its default in settings but no joy.

Help please!

 

bump

 

This is amazing...not one idea out there as to how to fix this problem? Avid?

Anyways, another clue might be that if I attempt to import session data (instead of creating a Protools session by opening the aaf file on startup) I get a slightly different message, it says:

"Could not complete the 'Import Session Data...' command because an unexpected error happened while reading the file's main composition sequences"

Helpful eh!...not

I have now re-installed the entire system and it still DOES NOT WORK so I think it must be project related. Is there anyway the timecode can become corrupted in a project or clip that would cause this, if so is there a way round it? (I have tried duplicating the sequence but this does not fix the problem). Is it a bug that Avid might tell us about if they get found out? (Like the playback buffers problem for example)

I have tried exporting to Protools (without the 'send to' route), consolidating and just about everything I can think of but with no luck.

I can open some older aaf sessions that were created under the SD version of the Studio suite but nothing since the HD upgrade. This combined with the Protools 002 'Send to' option missing from the 'send to' sub menu makes me wonder.

Please, someone must have a clue...surely!

you could try this...(scroll down to bottom). Also try contacting David Thompson.

Hello,

When you tried the AAF export, did you make sure the audio and video was "linked" as opposed to "embedded"?

Pro Tools should tell you that it doesn't deal with embedded AAF's on the import but it's possible that it gave the error messages you described.

Also, you may want to try an OMF export as opposed to AAF and see if that works instead.

Jon Connolly
Digidesign Product Specialist

Hi Jon, thanks for the response.

Yes I am exporting as aaf linked to original media. I actually have a sneaking suspicion this is related to the 25p project. I ran a test on a new test 25i project with the new 5.2.1 HD update installed and it impoted into Protools without a problem. Any progressive project I try produces the same errors.

I will try as OMF and see what happens and report back.

OK, Jon's suggestion of using OMF instead of the default AAF format worked! Not sure why AAF is not working but the problem is fixed for this job. Many thanks.

 

mmm... I just downloaded the new protools version and installed it. I get the same error messages when I try aaf. Anyone else who has this problem?

I get the same error message when I try to create pro tools session from aaf file linked to audio and video. With omf file I do not get this error, however, I can't view video in client monitor when using a pro tools session created with omf audio from avid studio hd.

Does this mean that the new Pro Tools v. 6.5.3r2 is not really a fix?

After reformatting my SCSI drives to Dynamic 4 way striped I no longer receive the error "Could not create new document because an unexpected error happened while trying to determine the file's timecode format." I am able to import aaf session data from Avid into Pro Tools. However, on playback I now get the error which version 6.5.3r2 is supposed to fix, namely, "video playback stopped due to hardware buffer underrun". Changing the buffer settings has not solved the issue.

Is there something I'm failing to do here? Please help.

I have the same problem importing AAFs linked. I can bring them in with audio and video individually. Still happening with 5.2.2

I have exactly the same problem.

Sometimes an AAF will import OK but most of the time I get the error messages.  I cant seem to pin down what the problem is.

If anyone finds a solution, please let me know and I will keep trying.

 

Strange.  I have had not issues with ProTools for 2 months or so, but all of a sudden, when sending linked audio & video files (AAF) to PT, I am getting the same error.

I have done it a couple of dozen times before and nothing has changed in the setup.

Did anyone get to the bottom of this (other than going OMF)?

I too am having this issue, although I cannot even export an OMF.  Every time I try to export in any format for Pro Tools LE I get an error that reads "DAE Connection Does Not Exist."  If I bypass that error, it will continue to export, but when I try to open the file in Pro Tools I get the timecode error that everyone else has received.  Has anyone else had this problem with the DAE Connection?

 I am getting that same error ...

"Could not create ... unexpected error ... timecode format."

I followed the tutorial for exporting to Avid P.T. (mbox_Ref) and opening session with the  Adv. Authoring Format file.

Anyone figure out what the problem is?