Acid can do this. I'm not sure if it can open it, because I've never seen a file format composed off 11 seperate audio tracks unless it was a Vegas project. I would try opening it in Acid and then do a render as .wav and there is a check box to render each track as seperate .wav files. Of course if you could open a vegas project in acid or an acid project in Vegas or an EDL in Acid, then your problem would be solved.
The other thing you could do is "open copy in sound forge" and save each through Sound Forge.
I'm not aware of anything with a GUI that can handle these multi-channel WAVs.
But there is a nice set of free command-line tools at http://www.cs.bath.ac.uk/~rwd/mctools.html which allow you to do all sorts of things with multi-channel WAVs. In particular, the CHANNELX utility will allow you to extract each of the channels to a separate mono WAV.
It may not be legal. Im trying to stick the BFD samples into drumagog. I've been emailing fxspansion to see if they couldnt make their BFD go trigger style instead of just midi. The samples are pretty nice. I tired to use it and drumagog together in ACID but ACID cant do multiple outs so i have to render every trigger five times in order to get the whole set when Im triggering drums. Big PITA. Hopefully some year fxspansion will get back about triggering
The answer was, the BFD samples. It shows as a wav, vegas sees it as an 11 channel wave in porperties. There are in fact 11 parts you can adjust in each sample, thru the BFD interface.
If this could be combined with drumagog in a really efficient way, the possibilities are enormous! Of course I dont put it past the Sonic Foundry team to make an even better triggering system, with a gate as useable as the Ultrafunk one ( except that to be complete be all and end all the Ultrafunk one would need to include a hysteresis control).
As for not answering the qustion, let me tell you, we just got a benchmark DAC-1 and it is without a doubt a REALLY worthwhile upgrade to the whole vegas monitoring system
I love it when people use acronyms. I give people at work sh*t about this all the time. They use these acronyms, like EVERYONE in the world has the same experience as them and should know exactly what they're talking about. BFD samples? BFD interfaces? DAC-1?
You know what BFD means thru my experience? "BIG F**King Deal". So when I read through your post I see you using yout Big f**king deal interface, and then I wonder, what's the big f**king deal anyways? DAC, is digital to analog converter in my world, but I have no idea what a DAC-1 is
BFD is the latest addition of what brough me to the PC in the first place, drum triggers. The problem is this one is midi, its still QUITE worth a look/ listen
The DAC-1 is a CHEAP digital to analog converter from Benchmark and kicks serious ass, without the goofball clocking issues of some other lower priced converters
It's funny because at work when I first started, I'ld have people saying stuff to me like.
"We need you to go to TTC, because the QE of TMMK, issued a CAR on the D6 for the 592N and we need to get an RDDP from VE2 and then we need to inform TMS of the TCI and get approval from TMMNA QA......ASAP.
I know, sounds like a foreign language, but this actually makes total sense to me now.
Although this thread has gone a bit astray TQFIMHO ;) I really WOULD like it if the Sony products would read/write multichannel wave or interleaved RAW pcm files. I use them quite a lot for storing 5.1 material in a single file and have to use command line tools to tear these apart and make into mono wave files to manipulate in the Sony tools.
B.