User manual

User Manual : Troubleshooting
User Manual
329
• On non-Intel motherboards using the Intel 84x chipsets (in particular the Intel 845 series supporting
the Pentium 4 processors). The reason for this is that the 84x series gives absolute priority to PCI
writes over PCI reads.
• On some Dual Xeon motherboards, using multiple PCI controllers with PCI-X slots.
PCI performance can be affected by a combination of different parameters and add-on cards such as
specific combinations of Raid adapters, Graphics adapters, Dual processors and PCI-X slots.
Upgrading a component's BIOS/driver/firmware or even the operating system will often fix some early
limitations or conflicts with a particular PC component. As an example switching from Windows 2000 to
Windows XP Pro totally fixed the PCI latency problems on a Dell Inspiron 8000 and installing a “Signed”
graphic card driver did the same for an Asus Dual PIII workstation.
Audio Engine Drops Warning
This message informs users about possible CPU delays leading to potential audio errors in record or
playback.
Mykerinos sends or requests audio data to or from the CPU in “frames” of 26ms. If one of these frames
is not given to, or taken from, the Mykerinos driver in time, this will result in a loss of audio data, and the
Audio Engine Drops Warning will be shown.
Playback Stalls Warning
Playback Stall messages are triggered by access delays impacting either the VS3, resulting in audio
drops while preserving the synchronization of the tracks or the Mykerinos driver. In the latter case the
stall may also endanger the integrity of the synchronization between tracks being recorded.
Multi-channel Audio Files
Wave, Broadcast Wave, AIFF or SDII multi-channel files are seen as mono files by the Pyramix Media
Manager unless their file names conform to Pyramix requirements.
Audio File Formats
Some audio file formats (like Pyramix native format, PMF and OMF) embed the track/channel num-
ber(s) in the file itself. In this case, Pyramix recognizes the track as mono, stereo or multi-channel with-
out problem even if the different audio tracks/channels of these files are actually stored in separate files.
Some other formats (like Wave, Broadcast Wave Format, AIFF or MacIntosh SDII) do not keep this
information in the file itself but in the filename. Unless the correct naming convention is followed, Pyra-
mix will see files in these formats as individual mono, regardless of whether they are part of a stereo
pair or multi-channel recording.
Broadcast WAV Files
BWF-P means polyphonic. I.e. multitracks within the same file
BWF-M means monophonic. I.e. one file per track
Pyramix Requirements
In order for Pyramix to recognize that separate audio files in these formats are actually part of a stereo
or multi-channel recording, Pyramix requires the following naming convention:
The filename of the different tracks/channels must be the same except for one section containing the
tracks/channels number as 3 digits surrounded by _## and ##_. For example: