Disappearing asio driver?

Randy Brown wrote on 10/12/2010, 8:25 AM
Just wondering why my Delta 1010 asio driver doesn't show up under audio device type.
If I select "Windows Classic wave driver" I can at least select line 1 and 2 to be able to use my Event 2020s but just curios why I don't have the Delta drivers in the drop down.

Here's a snippet

Comments

Dan Sherman wrote on 10/12/2010, 9:39 AM
Same issue here.
Randy Brown wrote on 10/12/2010, 9:48 AM
Geez, it's worse than I thought...it also broke VP8c AND Sonar!
KSmith wrote on 10/12/2010, 10:35 AM
I don't know if this might be related:
I had left Finale running, using my Firepod driver.
Started Vegas10, everything looks fine but the transport controls were not working.
Took a minute before I realized Vegas was calling for the Asio4all driver.
Switched Finale to use Asio4All. That got Vegas unstuck.

Finale (closed and restarted) complains that maybe the card is not multi-client.

This is not something I've had trouble with before and thus, not something I've had to be careful about, I'll be keeping an eye on it.

Any chance you guys have another app in the background that's accessing your 1010's?

Keith
pwppch wrote on 10/12/2010, 12:00 PM
It sounds like another app is using the driver. Check you task manager to see if another instance of Vegas is running or failed to close properly.

Peter
KSmith wrote on 10/12/2010, 1:01 PM
Thanks, Peter.
Is this something new or perhaps something needs to be set differently?

I'm pretty sure I've had Finale, Vegas9, and either Cubase SX or Reaper all up together (all 32bit on Win764) without problems, before --definitely any two of them .

I can't swear that the driver choices were always consistent from app to app or not, since I've never had this issue. What with experimenting, I'd be pretty sure it's worked in both conditions.

Keith
Randy Brown wrote on 10/12/2010, 1:33 PM
It sounds like another app is using the driver. Check you task manager to see if another instance of Vegas is running or failed to close properly.

Yes the first instance of VP 10 was the only thing showing the Delta driver. How do I get VP 10 to share the driver (I've had several instances of VP8c open with no problems...and even Sonar at the same time).
It seems there used to be a "share drivers" or something but I can't seem to be able to find it.

Thanks Peter,
Randy
KSmith wrote on 10/12/2010, 2:19 PM
Prefs|General|Close Audio & Midi Ports when not the active application. (?)

Mine is checked.

I did get it to play nice with Reaper provided I used a different driver to access the same sound card (Asio4All in Reaper, Presonus Firepod in V10).
Hmm, counter-intuitive to say the least. [Ed. given the way it worked with Finale in the first place]
k
Rob Franks wrote on 10/12/2010, 2:25 PM
"How do I get VP 10 to share the driver (I've had several instances of VP8c open with no problems."

I have no issues using ASIO with multiple apps at the same time (creative asio2) so I doubt that would be an issue.... or shouldn't be anyway.
Randy Brown wrote on 10/12/2010, 2:27 PM
Hmmm...yessir mine is checked too. Man I sure hope this will be fixed!
KSmith wrote on 10/12/2010, 2:56 PM
Rob's post has me fearing the worst. Creative is right in bed with MS and very tightly integrated with Windows.

Both the 1010 and the Firepod are getting a bit old. Presonus came up with a Win7 driver for the Firepod, only after some rather strenuous bitching from recent purchasers of the FP10. If I remember correctly, they said (at first) it was a problem with limitations of some of the chips, and the product was nearing end of life anyway.

It makes me wonder if there's something in the new code that breaks some kind of band-aid in the drivers. The 1010 may be in the same boat.
Randy Brown wrote on 10/12/2010, 3:56 PM
These are supposed to be Win 7 drivers...maybe a reinstall (Delta) is in order?
KSmith wrote on 10/12/2010, 4:16 PM
Doesn't sound like it could hurt.
Let us know how it goes!

Keith
Randy Brown wrote on 10/13/2010, 6:56 AM
I did a successful "repair" and it looked like it was going to work. I opened a second instance and under audio device type the Delta is listed...yay!!!...however when I select it it jumps back to MS Sound Mapper.