ACID Default to ASIO Sound Card on Opening? -ACID Product Family

Subject:ACID Default to ASIO Sound Card on Opening? Posted by: spinweb Date:1/15/2007 8:29:09 AM ACID rarely defaults to the sound card I want upon loading. Why? Is there a way to tell it to only use my ASIO driver? It's tiring on every boot, telling it to take the ASIO driver! Sometimes I need to turn my 002 Rack off and back on to get it to show up in my audio device list in ACID. Anyone else have this problem? Thanks, Rick
Subject:RE: ACID Default to ASIO Sound Card on Openin Reply by: JohnnyRoy Date:1/15/2007 8:37:22 AM I haven't seen this problem since I got rid of my SoundBlaster Audigy card. ;-) I have all of my windows desktop sounds coming through the motherboard chipset and ACID is set to use my M-Audio FW-410 and it never gets it wrong. Is it possible that the ASIO device that you are using is not always available or visible? (it sounds like it might be) This is the problem I had with the SoundBlaster. The Creative ASIO driver was so flaky it kept failing and then ACID would default to the next audio device it could find. So this may be a device driver problem. Make sure you have the latest from the manufacturer ~jr
Subject:RE: ACID Default to ASIO Sound Card on Openin Reply by: spinweb Date:1/17/2007 1:09:39 PM I'm not sure what you mean by having all your "windows desktop sounds coming through the motherboard chipset". How would I even know if I did? I have selected the ASIO driver in ACID. That should be the end of it, right? Once and fini? Well, I occasionally forget to turn on the 002 rack before booting the machine. Then I can understand ACID not finding it. But it also seems to happen when I have the 002 on, then boot up. I'll try to find an updated driver. Will have to search for one. Thanks for the response. -Rick
Subject:RE: ACID Default to ASIO Sound Card on Openin Reply by: JohnnyRoy Date:1/18/2007 3:58:38 AM > I'm not sure what you mean by having all your "windows desktop sounds coming through the motherboard chipset". How would I even know if I did? In Windows, if you go to Start > All Programs > Sounds and Audio Devices > Audio tab you get to select which audio device Windows uses to make it's beeps and other sounds. Initially I was told to disable the motherboard sound chip and only use the M-Audio FW410. But what I found was that Windows uses 16/44K for its waves so if I switched away from ACID for a moment, the FW410 would switch from the 24/48 in ACID to 16/44 and it didn't always switch back correctly. Sometimes it would get confused. Now I keep the motherboard chipset active and have Windows use sit so that my FW410 is only used by ACID and and stays at 24/48 regardless of what other application I switch to. > I occasionally forget to turn on the 002 rack before booting the machine. Then I can understand ACID not finding it. But it also seems to happen when I have the 002 on, then boot up. Once you forget that's it! ACID resets and forever more uses the next audio device it finds and does not switch back even if you turn the 002 on the next time. So if you boot with the 002 and set ACID to use it. Then boot without the 002 and load ACID it will use the next available audio device. Then boot with the 002 on and ACID will still use the next audio device until you change it back to the 002. This is the normal behavior. Perhaps this is what you are seeing,. ~jr

Subject:ACID Default to ASIO Sound Card on Opening?

Posted by: spinweb

Date:1/15/2007 8:29:09 AM

ACID rarely defaults to the sound card I want upon loading. Why? Is there a way to tell it to only use my ASIO driver? It's tiring on every boot, telling it to take the ASIO driver!

Sometimes I need to turn my 002 Rack off and back on to get it to show up in my audio device list in ACID.

Anyone else have this problem?

Thanks,
Rick

Subject:RE: ACID Default to ASIO Sound Card on Openin

Reply by: JohnnyRoy

Date:1/15/2007 8:37:22 AM

I haven't seen this problem since I got rid of my SoundBlaster Audigy card. ;-) I have all of my windows desktop sounds coming through the motherboard chipset and ACID is set to use my M-Audio FW-410 and it never gets it wrong. Is it possible that the ASIO device that you are using is not always available or visible? (it sounds like it might be) This is the problem I had with the SoundBlaster. The Creative ASIO driver was so flaky it kept failing and then ACID would default to the next audio device it could find. So this may be a device driver problem. Make sure you have the latest from the manufacturer

~jr

Subject:RE: ACID Default to ASIO Sound Card on Openin

Reply by: spinweb

Date:1/17/2007 1:09:39 PM

I'm not sure what you mean by having all your "windows desktop sounds coming through the motherboard chipset". How would I even know if I did?

I have selected the ASIO driver in ACID. That should be the end of it, right? Once and fini? Well, I occasionally forget to turn on the 002 rack before booting the machine. Then I can understand ACID not finding it. But it also seems to happen when I have the 002 on, then boot up.

I'll try to find an updated driver. Will have to search for one.

Thanks for the response.

-Rick

Subject:RE: ACID Default to ASIO Sound Card on Openin

Reply by: JohnnyRoy

Date:1/18/2007 3:58:38 AM

> I'm not sure what you mean by having all your "windows desktop sounds coming through the motherboard chipset". How would I even know if I did?

In Windows, if you go to Start > All Programs > Sounds and Audio Devices > Audio tab you get to select which audio device Windows uses to make it's beeps and other sounds. Initially I was told to disable the motherboard sound chip and only use the M-Audio FW410. But what I found was that Windows uses 16/44K for its waves so if I switched away from ACID for a moment, the FW410 would switch from the 24/48 in ACID to 16/44 and it didn't always switch back correctly. Sometimes it would get confused. Now I keep the motherboard chipset active and have Windows use sit so that my FW410 is only used by ACID and and stays at 24/48 regardless of what other application I switch to.

> I occasionally forget to turn on the 002 rack before booting the machine. Then I can understand ACID not finding it. But it also seems to happen when I have the 002 on, then boot up.

Once you forget that's it! ACID resets and forever more uses the next audio device it finds and does not switch back even if you turn the 002 on the next time. So if you boot with the 002 and set ACID to use it. Then boot without the 002 and load ACID it will use the next available audio device. Then boot with the 002 on and ACID will still use the next audio device until you change it back to the 002. This is the normal behavior. Perhaps this is what you are seeing,.

~jr