M-Audio Audiophile 24/96

[kiyardo]

I'm recording with an Audiophile 24/96 on Cool Edit pro v1.0. Whenever I record on the second, third, fourth, etc tracks, the previous tracks record with it (dumping) I've tried isolating the recording source in the driver, but no luck. Also, the susequent tracks are delayed as the signal is recorded in time. The delay increaes over time between tracks. Can anyone help?

[kiyardo]

I guess no one ever comes to these forums

[Clay Stahlka]

While it has been slow in this forum lately, I can perhaps help you a bit. Usually, the card's driver doesn't affect the way multiple tracks record. That is a function of the application software only. I would have you take a look at the setting in CoolEditPro and make sure you only record-arm the track(s) you want to record on. The unarmed tracks cannot record if they are unarmed. If this is not the case, you have a problem in your application installation and I would re-install it and/or contact technical support. If it records at all on any tracks, then the card's drivers are working properly.

As for the delay you are incurring, this is called latency, and it occurs due to the delay on processing the signals in the CPU. The best way to reduce this latency is to adjust the buffer size downward when tracking and use no plug-ins. When mixing your recorded tracks, raise the buffer size, which will allow the use of more tracks and plug-ins, because at mixdown, latency is a non-issue.

I hope this helps you. -cs

[kiyardo]

Clay,

Thanks for the reply. I've checked Cool Edit and the arming of the tracks. Tech Support called me back and I think I have an IRQ conflict (I'm not by the machine to check for sure)but, if that's the case, would you concur that this could cause latency? Because i've set the buffer back all the way to "good". I'm going to reinstall the card on another PCI slot and see if Windows 2000 corrects the IRQ conflict.

Thanks again for your reply

[kiyardo]

Let me qualify my original statement. The recording happens like this (as if dumping):

Track two records the signal sent to track two PLUS track one.

Track three records Track two, etc.

I also found out that the application software has nothing to do with inout routing. This is all done within the Sound Card's driver software. I've toggled the radio buttons in the 2496 driver and it still records the wav file recorded in track one unto track two. I don't understand why it does this.

[Clay Stahlka]

I disagree with the notion that the application does not have anything to do with I/O routing. While I am not a software engineer, I do know that all the driver does is make individual ins and outs available to Windows, or whatever OS you use, so that the application can access the hardware. That being said, if the driver in question does not let the OS pickup individual ins and/or outs then that is a problem. But, assuming that the driver is operating correctly and is making the individual ins and outs available, it is the application's responsibility to go out and grab one or more of those available ins and/or outs and assign them to track record and playback routing. Whoever told you that routing is the driver's responsibility is most probably trying to shift blame to the hardware. -cs

[kiyardo]

Originally posted by Clay Stahlka
While I am not a software engineer, I do know that all the driver does is make individual ins and outs available to Windows, or whatever OS you use, so that the application can access the hardware.

You've defined routing. And, this is done through the driver alone as you stated. I found out that M-Audio made a crucial mistake in sending Sweetwater Sound the wrong drivers for the 2496. It does not allow multi-track recording. I had to uninstall the driver, and load a BETA driver in place of the old driver. This driver allowed the Application to select the proper inputs routed by the driver. Problem solved, through hours on the phone with M-Audio at my expense.