Audiobox USB96 Problem ??

  • Thread starter Thread starter BriamJH
  • Start date Start date
B

BriamJH

Active member
Hi: I have an Audiobox USB 96 with Reaper. Even though everything seems to be working just fine, I regularly get the message below, screenshot A. I show also screenshot B which is how my Audiobox setup looks. Why do I keep getting theses messages. Many thanks, Brian
 

Attachments

  • Screenshot A.webp
    Screenshot A.webp
    23 KB · Views: 75
  • Screenshot B.webp
    Screenshot B.webp
    42.9 KB · Views: 59
No experience with that interface myself. Go through basic steps first.

Try to see if there is a driver update for your device and system.


I have heard a few times about USB ports settings can go to sleep. I have never experienced it with my PC's, but worth looking into.

And the obvious is to replace the USB cable and make sure it isn't the fault.

Best to ya!
 
Thank you very much. I will now look at the driver situation. Brian
 
Don't know if this will help any, my situation didn't involve MIDI, just lack of audio. Your's could be totally different.

Under the Actions tab (Show actions list) you can add a ReaScript to reset your Audio Device. I had a similar situation with my previous Tascam interface. When I opened Reaper and got the pop-up window about Audio Device not detected, I just went to the Actions tab and clicked the new reset action. This worked well for several months then stopped for some reason. My only other solution was to do a Restart on my PC - big PITA, but worked every time.

The code for this action is :

reaper.Audio_Quit()
reaper.Audio_Init()

Here are the directions I got from the Reaper Forum :

  1. Action List -> ReaScript: Edit new ReaScript (EEL2 or lua)...
  2. Save the file in your "script" folder, Call it "Reset Audio Hardware.lua"
  3. Copy Paste those two lines as is in the resulting window
  4. Hit Save and you now have a "Reset Audio Hardware" Action in your action list
_______________

Much thanks to @lexaproductions over at Reaper Forums.
 
Last edited:
Many thanks for your reply. This looks very interesting. After I received the reply from Jimmys1969 (above) I have gone to the Presonus website he showed and downloaded updated drivers. Since then (i.e. just a few days, so far) the message has not recurred. Maybe the problem was related to drivers. In any case, I am really greatful for your response. Brian
 
Many thanks for your reply. This looks very interesting. After I received the reply from Jimmys1969 (above) I have gone to the Presonus website he showed and downloaded updated drivers. Since then (i.e. just a few days, so far) the message has not recurred. Maybe the problem was related to drivers. In any case, I am really greatful for your response. Brian
Glad you got it sorted Brian! ?
 
Back
Top