Please ensure Javascript is enabled for purposes of website accessibility Jump to content

Reaper Says "no Asio Drivers Found!"


Recommended Posts

So I've been using Reaper forever with various versions and up until today, I've had no problems. Now I load a project I was working on yesterday and when I try to select the POD HD500 driver in the dropdown it says "No ASIO Drivers Found!" and shows no I/O selection options.

 

I already uninstalled/removed from registry/reinstalled Line 6 Drivers via Monkey and direct download

 

I have uninstalled all other ASIO device drivers (TASCAM US-1800, AudioBox 2x2)

 

Tried installing ASIO4All---still doesn't show up

 

Uninstalled/reinstalled Reaper (tried with old versions and the newest)

 

Still get the "No ASIO Drivers Found!" message

 

Anyone have any other ideas? I'm not really looking forward to reinstalling my whole OS and all my plugins to get Reaper to work. I can use Cubase LE, WaveLab, or Studio One Artist with the drivers no problem (including ASIO4ALL).

Link to comment
Share on other sites

In no particular order and some of which you may of done aldready

check usb drivers might be corrupted on the record.

Also, unhinge it from the audio player if possible.

open pc "sounds" utility in  control panel and select it in there.

Reinstall asio4all.

  • Upvote 1
Link to comment
Share on other sites

In no particular order and some of which you may of done aldready

check usb drivers might be corrupted on the record.

Also, unhinge it from the audio player if possible.

open pc "sounds" utility in  control panel and select it in there.

Reinstall asio4all.

I redid my USB drivers for the computer, removed old from registry, but this seems unneeded as it works in every other audio program like Cubase LE, Wavelab, etc....reset Foobar2000 drivers to WDM when it started, and I've done two un/installs of ASIO4All in the last 24 hours....thanks, though!

 

Just for clarification, if you run Monkey you have green ticks for everything?

 

If you create a new project in Reaper do you get the same symptom?

Yes, and Yes. I even went as far as deleting all my user preferences and initiliazation files for Reaper, opening a project with factory defaults restored, ...still no "seeing" my drivers.

 

Thanks for trying guys!

Link to comment
Share on other sites

Do you have a specific need for ASIO4ALL?

 

I personally would completely remove ASIO4ALL until you resolve the situation.

 

Also try manually disabling any other audio devices and selecting the POD HD 500 as your default device.

 

BTW, can POD HD 500 Edit communicate with your POD HD 500?

Link to comment
Share on other sites

Yep, Edit works fine, the problem is isolated to Reaper, and I did remove ASIO4All as soon as I saw it wasn't working....I'm not a fan of the driver, but its been useful when similar issues have come up without the time to properly repair things cause it ALWAYS seems to work, which it did in Cubase...

 

I can set the HD500 to be my main soundcard if I want, but it still doesn't show up in Reaper...getting a little pissed at my g*&d(*&n f$%$ing computer....

Link to comment
Share on other sites

So it seems to be a reaper only issue, including any previous version. weird alright.

google this; Foobar2000 drivers

There are a tone of asio issues which might resolve it

Also WDM isn't asio and so it won't show. Can you select asio instead?

Does the tascam show up?

Link to comment
Share on other sites

So Reaper support forums are giving me nothing, the problem still persists...I've rolled drivers back (like a year and half back!), went all the way back to Reaper 3.2.....still not working. And, everything still works just wonderful in every other program on my PC that can use ASIO drivers in any of the versions/configurations I've installed....WTF! Guess I'll spend some more money and buy the Pro version of Studio One...

Link to comment
Share on other sites

So, the guys at Cockos think I need to DE-select "Microsoft Wavetable GS Synth" in the midi devices panel...haven't tested, but that was the "official" suggestion

 

This had no effect on anything....I've uninstalled/deleted from registry/reinstalled drivers, done the same with Reaper (tried different locations, portable install to HDD, portable install to thumb drive, installation on a different partition) and the problem persists, but again, only in Reaper. Got my Studio One License on Saturday and have been working on bouncing out all of Reaper projects and moving them over (reaper still works with Windows native drivers for some reason!?!?! just not any of my interfaces or ASIO4ALL) If you guys think of something else, please let me know, as I'm not fully ready to give up on Reaper just yet, but thanks for all of the suggestions so far.

Link to comment
Share on other sites

  • 8 years later...

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

 Share

×
×
  • Create New...