Media Management & Libraries : Mounting Rules
4 - 87
Treat all files as 48kHz/16bit for ‘exotic’ DAR originated Wave files
As it says. Please see DAR WAV file Import on page 87
Group files with name ending with a surround label (like .L,. C, .R, .Ls, .Rs, .Lf or _L, _C, _R, _Ls, _Rs,
_LFE) as a single multichannel media
As it says. Useful when working with files generated by certain other DAWs.
Special rules for Wave files containing BWF or iXML chunks:
Always use Filename as Media Name instead of BWF Description or iXML Family Name
This will allow files recorded in Steinberg’s Nuendo to be mounted and can also help with (re)conforming files
from Aaton Cantar or other location recorders where the filename matches information in the EDL.
Ignore BWF chunk and mount files as standard Wave
This effectively treats Broadcast Wave files as ordinary Wave files and can help with (re)conforming as above.
Ignore iXML chunk and mount files as standard BWF or Wave
This treats iXML files as pure Wave or BWF with the same aims as above.
Special rules for Wave/BWF and AIFF files containing OMF information:
Never mount Wave/BWF files as OMF
Never mount AIFF files as OMF
Show ProTools Wave/BWF files with ‘Enforced Avid Compatibility’ as OMF
Special rules for cache file decompression
When compressed audio files are mounted Pyramix creates an uncompressed WAV version of the file(s) in a cache.
The location of these cache files is determined by this dialog.
Locally (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 Pyra-
mix in 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. When
this option is selected the
Browse... button is available to open a file browser window to set the user defined path.
Enable enables the rule.
Allow cache files mounting when ticked, cache files can be mounted directly, otherwise they remain invisible, i.e.
filtered out of Media Manager views.
Options
Also apply this rule to all sub-folders
Refresh immediately
DAR WAV file Import
It seems that DAR systems were strange in that they always played audio at 48khz. Even if 44.1khz audio
was imported into a DAR, it would be converted to 48khz. The sample rate and bit-depth information in
the WAV files was ignored as everything was assumed to be 16-bit/48khz. We've seen WAV files from
DAR systems where the WAV files were identified as containing 128-bit audio or having a 10hz sample
rate. So it would seem there must have been a bug in the DAR software that caused incorrect data to be
stored in the WAV header. There is already code in the Pyramix WAV handler to try to catch these com-
pletely invalid parameters but, unfortunately, the WAV files from DAR don't include any manufacturer
identifier so it isn't simply a case of identifying that they are from a DAR and automatically forcing them
to 48khz in Pyramix.
To Next Page
Loading...
