V6 User Manual 1.00.book - Studio General

Mounting RulesIn addition to the general settings, Mounting Rules can be created to override the Default decompression cachesettings for a specific Mounting location:Special rules for cache file decompressionLocally (by the original) File(s) will be created in the same location as the original file.Sub-locally (by the original, in a \MTDXCache sub folder). File(s) will be created in a sub folder created by Pyramixin the same location as the original file.Custom (files are generated to the specified location). File(s) will be created in a user specified location. Whenthis option is selected the Browse... button is available to open a file browser window to set the user defined path.Enable enables the rule.Mounting Rules dialog decompression rules sectionAllow cache files mounting when ticked cache files can be mounted directly, otherwise they remain invisible.MXFThe Pyramix MXF implementation can read and decode MXF files following specifications AS WELL as files comingfrom Avid / Digidesign workstations.Pyramix MXF can generate valid MXF files complying with MXF specifications and have passed the validationstests provided by Snell&Wilcox.As of today, supported MXF formats are OP1A and OPAtom, as well as potentially OP1B, OP1C, OP2A, but theseremain to be fully validated.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=2094File & Project Interchange with Apple MacintoshCurrently, the recommended Interchange Format when working with ProTools 7 is AAF / OMF, with BWF mediafiles. Please see: AAF on page 314 and OMF on page 324 for further information and also refer to the PyramixInterchange Forum in the Support Section (for registered users) for regularly updated information, as well as Interchangetips & tricks :http://forum.merging.com/viewforum.php?f=23HistorySD2 & ProTools 5 Sessions and Legacy Apple File FormatsOld Macintosh files such as SD2 and PT4.x and PT5.x projects files have a Mac-binary, or double-fork structure thatthe PC cannot handle directly. As opposed to interchange files, PC files or new Mac files (that do carry a simple singlefile structure), SD2 and PT5 projects files are based on a Data fork (the one you see in every computer file) anda Resource fork (a hidden, second file storing all the file info). While this binary structure was actually quite a cleverand convenient move, the fact that half of the file is hidden by design makes it a very fragile cross-platform media.File and Project Interchange : File & Project Interchange with Apple Macintosh 17 - 308