One of my hobbies is running live sound and recording such concerts. Over the last four years I’ve built up my sound system into quite a nice system.
I’ve also learned a lot about what is and isn’t compatible amongst systems that should just plug and play. Earlier this year I got a new recording rig, specifically for multitrack recording in a portable studio type configuration. In such a setting I would not have my full sound system (which at the time was a Mackie Onyx 1640 with the Firewire option providing 18 x 2 channels). So I got a system based on the Mackie Onyx Blackbird which provides 8 channels of input including Mackie’s nice preamps, and 8 channels of ADAT. The Firewire interface on the system is a 16 x 18 channel system.
The Firewire implementation is the Dice II system–used in a lot of the high-channel systems on the market–which (I found out after I got it) pretty much requires the Texas Instruments Firewire chipset on the computer. The computer I’d been using for all of my prior recording with the Mackie 1640 would not sync with the Blackbird.
After much research and trying to connect to many systems at the local computer store, I finally bought a laptop from ADK Pro Audio configured and tweaked specifically for use as a DAW (Digital Audio Workstation). I had planned on this being a computer for general laptop use (including software development) and proceeded to load lots of development tools and such as well as the DAW software (Mackie Tracktion 3).
Even with this system I was having problems. I finally reset the configuration as shipped from ADK and found that it worked much better.
One of the critical measures for such a system is the Deferred Procedure Call (DPC) Latency. This can be measured with a tool called DPCLat . With all of the stuff I had loaded the average latencies were in the 700-800 µs with excursions greater than 2000 µs (2 ms). This was causing loss of sync, dropouts, etc.
After resetting it to factory fresh, and installing just the minimal drivers, the average DPC latency is now in the 80-200 µs range.
I’m going to be providing sound and recording for the Filk track at Renovation, the 69th World Science Fiction Convention. For this I’ll be using my new sound system, an Allen & Heath iLive system. This uses yet a different audio transport for recording: Audinate’s Dante system, transporting up to 64 x 64 channels via Gigabit Ethernet. The ADK laptop is working nicely with this system, and I’ve upgraded to using Reaper for recording.
However, the concert for the Filk Guest of Honor, Tricky Pixie will be in a different (larger) room than the one my system will be set up in, and that system is not set up for recording. So I’ll be bringing the Mackie Blackbird (and a Behringer 8×8 ADAT converter) and an analog mic splitter and record the concert with that system.
Just to be certain that the laptop is fully operational for recording from the Blackbird (since I haven’t used it since flattening the system), I’m running a bit of a stress test. The laptop is currently performing a recording test by sending 16 channels of pre-recorded tracks of via ethernet and simultaneously recording these tracks coming in over firewire.
The signal chain is as follows:
- Mackie Tracktion playing 16 pre-recorded tracks (recorded at 44.1K/16, transcoded and output at 48K/24) via
- ASIO driver to Audinate’s Dante Virtual Sound Card via
- Ethernet to the iLive Mixrack (Mixrack being controlled via WiFi from a Windows tablet running the iLive Editor)
- Mixrack routes the Dante channels 1-16 to analog outputs 1-16
- Two 8-channel cable snakes connect the iLive outputs to the Blackbird and Behringer inputs where they are digitized
- The Behringer system encodes its 8 channels (48K/24) and sends them via ADAT lightpipe to the Blackbird.
- Blackbird encodes its analog inputs at 48K/24 and sends these and the 8 ADAT inputs via Firewire to
- ASIO Blackbird firewire driver to
- Reaper which is recording the 16 channels.
I’ll be running this stress test for the rest of the night, to be sure everything stays in sync and properly playing and recording. In actual operation, I’ll only be doing the recording, so it will be running far less than I’m running right now.