|
|
|
|
|
|
Q:
"Could not complete the 'Open Session..' command because: an unexpected error happened while trying to open the file" when attempting to open or import an AAF in Pro Tools 6.4 or previous.
A:
This is a known issue that can occur when importing an AAF generated from Pro Tools version 6.5 or higher (or Avid Composer Adrenaline 1.5, News Cutter Adrenaline or Xpress 5.5, or Xpress Pro/Xpress DV 4.5 or higher) into Pro Tools 6.4 or previous (or Composer Adrenaline 1.4, News Cutter Adrenaline and Xpress 5.4, or Xpress Pro/Xpress DV 4.4 or earlier).
A change was made to the AAF specification which breaks backwards compatibility with older versions of software supporting the AAF toolkit. The result of this change is that AAF files produced by the newer application versions mentioned above, will not be readable in Pro Tools 6.4 or previous (or the older Avid versions mentioned above). Forwards compatibility with older AAF's will not be broken by this change. The workaround is to export an OMF rather than AAF when interchanging between the effected software versions.
Other Popular Articles:
when bouncing to disk I receive this error: Could Not Complete Bounce To Disk...command because: Assertion in "\code\azores_Handel\AlturaPorts\NewFileLibs\FF\Audio\FF_Audio Property.cpp", line 33 If Command|8 is not recognized by Windows XP after installing its software from the Pro Tools Installer CD-ROM, it may indicate that the maximum number of MIDI driver entries in your registry (10) has been exceeded. Using Command|8 with the USB Mini-2 extender from Gefen over a 25m distance results in frequent 'lost communication with Command|8' messages in Pro Tools. I'm getting "bad disk" and "you don't have permission..." messages when I try to install Virtual Guitarist into Mac OSX from the install disk. How do I get rid of these demo plug-ins in Pro Tools? |