Virtual audio device like ReaRoute, but not limited to ASIO
So, I'm the tech guy for a radio station.
Reaper is the ultimate audio processing/routing system and can easily handle any processing/routing tasks we have here. Absolutely brilliant. Can replace 10's of thousands of dollars worth of digital mixing/processing gear.
BUT!... Isn't there always a but.
But this all falls apart if the audio streams come from or go to another piece of software on the same computer.
For example, we have a computer in the broadcast stack that receives the audio from the studios over balanced analog. Three streams go out of this system. Unmodified for logging, lightly compressed for internet streaming, and more complicated stuff for the FM transmitter.
The only way to get the audio from reaper to the other programs is to go out through an audio device, and back in through another audio device. So, one output for the FM transmitter, and output and an input for the logging software, and another output and input for the internet stream.
We also have a radio automation program running on the broadcast computer (for when the studio is unmanned) that has to go out of the computer and back into another input to get into reaper, and then back out to the various end points.
So, either multiple audio devices or a multichannel audio device with multiple virtual audio devices and internal routing (or just a bunch of patch cables) is required just to get audio from place to place on a single computer.
ReaRoute would be the ultimate solution to such issues if all windows software supported ASIO, but they don't. Also for example, our streaming is done using edcast which sends a stream to an icecast server. Edcast has an ASIO version which works fine with a real audio device, but crashes and burns when connected to ReaRoute. Our logging system works brilliantly, but has no ASIO support. Neither does our automation software.
If anyone mentions VAC (Virtual Audio Cable), I'll chain them to a chair in front of the computer and not let them go until they make it work, which means they'll die of starvation.
Apart from this specific example there are many other situations where a virtual sound card would be useful.
Back when I had an Audigy 2 sound card in my main computer, I ran the KX Project drivers. I had a crossover running on the DSP controlling my main speaker rig, and a secondary output with a full range signal for headphones. All windows audio ran through the DSP.
I could replicate this setup, without the DSP limitations of an Audigy, on any computer, with any sound card, if there was a way to get the audio into reaper in the first place. Reaper would essentially become the DSP system, more powerful than any DSP powered audio interface at any price.
So, that's my rant. What do ya'll think? I just think it is crazy with all the CPU power I have today, that I can't achieve something that can be done with a soundblaster live. Why should a multichannel DSP powered audio interface be necessary to move audio between programs running on the same CPU? Why do I need a DSP powered audio interface to run a basic crossover that would use bugger all CPU power?
Last edited by drumphil; 08-15-2013 at 04:52 AM.
|