File and Project Interchange : Dolby
18 - 475
MXF
The Pyramix MXF implementation can read and decode MXF files following specifications AS WELL as files coming
from Avid / Digidesign workstations.
Pyramix MXF can generate valid MXF files complying with MXF specifications and have passed the validations
tests provided by Snell&Wilcox.
As of today, supported MXF formats are OP1A and OPAtom, as well as potentially OP1B, OP1C, OP2A.
MXF Essences supported today are AES3 & Broadcast Wave audio files (conforming to SMPTE 382M).
For the latest MXF interchange information please see:
http://forum.merging.com/viewtopic.php?f=23&t=2094
Dolby
Dolby AC3 encoding and Dolby E encoding and decoding can be accomodated via optional Minnetonka Sur-
Code plug-ins. These require the relevant iLok authorizations from Minnetonka. Please contact your Merging
Technologies sales partner for more information.
Note: The Dolby plug-ins require a separate installer.
Simple File Conversion
To convert to or from PMF audio files use the Project > Render ><None> function.
Place the file you wish to convert on a Track or Tracks in the Timeline and select the resultant Clip by clicking on it.
Make appropriate settings in the Render dialog, click on the Render button and voila!
File & Project Interchange with Apple Macintosh
Currently, the recommended Interchange Format when working with Pro Tools 7 is AAF / OMF, with BWF media
files. Please see: AAF on page 481 and OMF on page 495 for further information and also refer to the Pyramix
Interchange Forum in the Support Section (for registered users) for regularly updated information, as well as Inter-
change tips & tricks :
http://forum.merging.com/viewforum.php?f=23
History
SD2 & Pro Tools 5 Sessions and Legacy Apple File Formats
Old Macintosh files such as SD2 and PT4.x and PT5.x projects files have a Mac-binary, or double-fork structure that
the PC cannot handle directly. As opposed to interchange files, PC files or new Mac files (that do carry a simple sin-
gle file structure), SD2 and PT5 projects files are based on a Data fork (the one you see in every computer file) and
a Resource fork (a hidden, second file storing all the file info). While this binary structure was actually quite a clever
and convenient move, the fact that half of the file is hidden by design makes it a very fragile cross-platform media.
A sure sign that the resource fork has been lost is when the file appears with a generic icon and is present but
unreadable. A broken binary file cannot be rebuilt.
Note: SD2 is only supported on 32-bit systems.
Note: For more info about the specific handling of "old" Apple files, please read the following
entry in the Forum's Support Section (for registered users):
http://forum.merging.com/viewtopic.php?f=23&t=1414
To Next Page
Loading...