Reaper ошибка инициализации буферов asio

I did some additional testing with the x86 version of REAPER (no difference), and with ASIOSigGen. ASIOSigGen also fails w/SAR and works with my interface. Its debug log has some info:

ASIOSigGen version 4.32 Copyright (C) 2017 George W. Taylor
All rights reserved!
http://www.TropicalCoder.com
"E:DownloadsASIOSigGenASIOSigGen.exe" 

Enumerating ASIO Drivers...

numDev: 0
ASIO Fireface USB
C:WINDOWSsystem32fireface_usb_asio.dll

numDev: 1
ASIO4ALL v2
C:Program Files (x86)ASIO4ALL v2asio4all.dll

numDev: 2
Synchronous Audio Router
C:Program FilesSynchronous Audio RouterSarAsio.dll

Total num devices found: 3
Found ASIO Configuration file!
nRequestedDrvNum: 2, Num devices: 3
asioOpenDriver success!
Diver selected...
Synchronous Audio Router
C:Program FilesSynchronous Audio RouterSarAsio.dll

Synchronous Audio Router
Driver Vers: 1
numInputChannels: 18, numOutputChannels: 12
inputLatency: 567, outputLatency: 575
minSize: 512, maxSize: 512
preferredSize: 512, granularity: 0
sampleRate: 48000
Channels available...
Channel: 0 - Group: 0 - Analog 1 (1), ASIO sample type: ASIOSTInt32LSB
Channel: 1 - Group: 0 - Analog 2 (1), ASIO sample type: ASIOSTInt32LSB
Channel: 2 - Group: 0 - Analog 3 (1), ASIO sample type: ASIOSTInt32LSB
Channel: 3 - Group: 0 - Analog 4 (1), ASIO sample type: ASIOSTInt32LSB
Channel: 4 - Group: 0 - Adat 1 (1), ASIO sample type: ASIOSTInt32LSB
Channel: 5 - Group: 0 - Adat 2 (1), ASIO sample type: ASIOSTInt32LSB
Channel: 6 - Group: 0 - Adat 3 (1), ASIO sample type: ASIOSTInt32LSB
Channel: 7 - Group: 0 - Adat 4 (1), ASIO sample type: ASIOSTInt32LSB
Channel: 8 - Group: 0 - Adat 5 (1), ASIO sample type: ASIOSTInt32LSB
Channel: 9 - Group: 0 - Adat 6 (1), ASIO sample type: ASIOSTInt32LSB
Channel: 10 - Group: 0 - Adat 7 (1), ASIO sample type: ASIOSTInt32LSB
Channel: 11 - Group: 0 - Adat 8 (1), ASIO sample type: ASIOSTInt32LSB
bOutputReady = true
pASIOBuffers->bInitSuccess
asioDriverInfo.outputBuffers to activate: 12
ptrASIO->createBuffers failed!
AsioDriverList destruction.
```

Go to Reaper

Reaper error initializing asio driver

Suddenly hit a really annoying problem, whereby when I open REAPER I’m just being met with an «Error opening devices» message saying: «There was an error opening the audio hardware: Error initializing ASIO driver.»

Thing is nothing has changed! There was a windows update that came through almost a week ago, but after that installed I used REAPER for several days without any problems. The other day, though, this started happening. If I change the Audio System to something else then it will work, but in the past I’ve found it to have more latency issues, so I’ve preferred to stick to ASIO.

I’ve tried updating the driver(s) to my audio interface (Roland Quad-Capture), but that comes back saying it’s running the latest. I’ve checked the Roland website and found I am. I wasn’t running the latest version of REAPER, so downloaded that but still getting it.

While Googling I saw something about going to the computer’s Device Manager and locating Universal ASIO Driver, then making sure that’s up to date; but I can’t find that anywhere in my Device Manager.

Other than that I feel I’ve exhausted all options, so any help anyone can offer would be greatly appreciated!

«Universal ASIO Driver?» I don’t believe there is any such thing. It’s certainly not something that would ever show up in device manager because drivers tend to be specific to hardware, and device manager is a list of hardware components, not drivers (though it can tell you which drivers they are using).

The closest thing to that I think would ASIO4All, which is a hack intended for devices that don’t actually support ASIO, and also won’t show up in device manager.

Usually the problem you describe is hardware related. It could mean your cable is bad or the port it’s plugged into, or even the audio device itself.

Can you try your Roland on another computer? You just need to troubleshoot and rule out every part of the chain.

You could also try uninstalling your device driver and reinstalling it (with a reboot in between). Something may have become corrupted there.

Источник

Reaper error initializing asio driver

Suddenly hit a really annoying problem, whereby when I open REAPER I’m just being met with an «Error opening devices» message saying: «There was an error opening the audio hardware: Error initializing ASIO driver.»

Thing is nothing has changed! There was a windows update that came through almost a week ago, but after that installed I used REAPER for several days without any problems. The other day, though, this started happening. If I change the Audio System to something else then it will work, but in the past I’ve found it to have more latency issues, so I’ve preferred to stick to ASIO.

I’ve tried updating the driver(s) to my audio interface (Roland Quad-Capture), but that comes back saying it’s running the latest. I’ve checked the Roland website and found I am. I wasn’t running the latest version of REAPER, so downloaded that but still getting it.

While Googling I saw something about going to the computer’s Device Manager and locating Universal ASIO Driver, then making sure that’s up to date; but I can’t find that anywhere in my Device Manager.

Other than that I feel I’ve exhausted all options, so any help anyone can offer would be greatly appreciated!

«Universal ASIO Driver?» I don’t believe there is any such thing. It’s certainly not something that would ever show up in device manager because drivers tend to be specific to hardware, and device manager is a list of hardware components, not drivers (though it can tell you which drivers they are using).

The closest thing to that I think would ASIO4All, which is a hack intended for devices that don’t actually support ASIO, and also won’t show up in device manager.

Usually the problem you describe is hardware related. It could mean your cable is bad or the port it’s plugged into, or even the audio device itself.

Can you try your Roland on another computer? You just need to troubleshoot and rule out every part of the chain.

You could also try uninstalling your device driver and reinstalling it (with a reboot in between). Something may have become corrupted there.

Источник

Reaper error initializing asio driver

I kept getting this error:-

There was an error opening the audio hardware:

Error initializing ASIO driver

I took out All the plugins from the Progam Files/VSTPlugins Folder and that did not work.

In Device Manager I disabled The following Drivers:-
AMD High Definition Audio Device
Realtek High Definition Audio
And that did not work. The saffire Driver still gave the error as above.

I disabled The Creative SB X-Fi Driver AND THAT WORKED for a while.

So In the Start I typed in Playing Audio and ran the Troubleshooter and restarted the Computer but left the Audio Interface switched on and that did work for a while.

Update 7th May 2020
I Switched the Focusrite Interface on first and then the computer. Start Reaper and I get the error message. After a short while the error message disappears after the Saffire driver comes to life in Device manager. Still no sound, but the error message does not show.

I fired up Windows media Player and You Tube to see if there was sound and there was no sound on them.

I unplugged The The Creative SB X-Fi (Driver still disabled) from the back of the computer and rebooted The Interface and The saffire Driver fired up in Device manager.
Fired up Reaper, Still no sound.

I uninstalled The Saffire Driver and rebooted the Computer.
In Device Manager The Saffire Driver Fired up which is impossible but that is what happened. Maybe it did not uninstall.
I hit update Driver and I had the best drivers already installed
Fired up Reaper and there was sound.

The interface was making a very loud continuous buzzing noise so I unplugged (from the Computer) the SEAGATE EXTERNAL HARD DRIVE
AND THAT WORKED FOR A WHILE.

Because the Interface is powered by a Fire Wire, could the external hard drive USB have been robbing the Interface of power?
Or just clashing with it?

I’ve found the Problem, Microsoft no longer support Firewire and the 1394 OHCI Compliant Host Controller (firewire card in Device Manager)

Search for
Fixing FireWire Problems
With Windows 10, 8 and 7

It is on studio1productions
or Via tomshardware

Followed The very good instructions (ABOVE) to install The Legacy Drivers for my Firewire card. Checked the Bios to see if it was enabled.
That did not work.
I have written to Focusrite and await their reply.
I will update ASAP but I’ll probably have to buy a new Interface.

I’ve been in contact with Focusrite by phone. They confirmed that Microsoft no longer support Firewire.
He did say you could try and find a Firewire card to install in your computer but you are better off buying another Interface.
What he said next surprised me and pleased me.
I had better not say exactly what he said, but put it like this, Focusrite will look after you beyond belief.
I bought a Scarlett 18i8 direct from Focusrite and I’m very happy.

I have a Focusrite Saffire Pro 26 Interface.
I use Reaper with ASIO Saffire.
I have Windows X
Note: Focusrite recommend to use Saffire ASIO and not ASIO4all
I have reinstalled The saffire Driver many times direct from Focusrite.

Источник

Reaper error initializing asio driver

Suddenly hit a really annoying problem, whereby when I open REAPER I’m just being met with an «Error opening devices» message saying: «There was an error opening the audio hardware: Error initializing ASIO driver.»

Thing is nothing has changed! There was a windows update that came through almost a week ago, but after that installed I used REAPER for several days without any problems. The other day, though, this started happening. If I change the Audio System to something else then it will work, but in the past I’ve found it to have more latency issues, so I’ve preferred to stick to ASIO.

I’ve tried updating the driver(s) to my audio interface (Roland Quad-Capture), but that comes back saying it’s running the latest. I’ve checked the Roland website and found I am. I wasn’t running the latest version of REAPER, so downloaded that but still getting it.

While Googling I saw something about going to the computer’s Device Manager and locating Universal ASIO Driver, then making sure that’s up to date; but I can’t find that anywhere in my Device Manager.

Other than that I feel I’ve exhausted all options, so any help anyone can offer would be greatly appreciated!

«Universal ASIO Driver?» I don’t believe there is any such thing. It’s certainly not something that would ever show up in device manager because drivers tend to be specific to hardware, and device manager is a list of hardware components, not drivers (though it can tell you which drivers they are using).

The closest thing to that I think would ASIO4All, which is a hack intended for devices that don’t actually support ASIO, and also won’t show up in device manager.

Usually the problem you describe is hardware related. It could mean your cable is bad or the port it’s plugged into, or even the audio device itself.

Can you try your Roland on another computer? You just need to troubleshoot and rule out every part of the chain.

You could also try uninstalling your device driver and reinstalling it (with a reboot in between). Something may have become corrupted there.

Источник

Reaper error initializing asio driver

What is this? Every time I open Reaper I get this error message.

I have a new M Audio Fast Track Pro usb’d to my PC. I’m simultaneously watching the Kenny Gioia Reaper Tutorial I downloaded.

Pick your correct updated drivers and get them from here and install them

Make sure you get the correct ones for your Operating system.

HTH

I also get this error message

I’m using Behringer F-Control (firewire) on Vista. I downloaded the right driver too Does anyone else know about this one?

I also get this error message

I’m using Behringer F-Control (firewire) on Vista. I downloaded the right driver too Does anyone else know about this one?

Try this.
Depending on your O/S.Open the control panel and then go to the Administrative Tools/vent viewer and make a short cut from it to your desktop(Makes things easier).
Now highlight each event and clear it’s log,don’t save them when prompted as they will be old and useless.

Now recreate the problem and go back to the events and copy and past info that you may think can help track it down into Google.

^ thanks for the hint

This is what the log says

Log Name: Security
Source: Microsoft-Windows-Security-Auditing
Date: 1/9/2011 10:46:20 PM
Event ID: 5038
Task Category: System Integrity
Level: Information
Keywords: Audit Failure
User: N/A
Computer: t0Fu3
Description:
Code integrity determined that the image hash of a file is not valid. The file could be corrupt due to unauthorized modification or the invalid hash could indicate a potential disk device error.

File Name: DeviceHarddiskVolume2WindowsSystem32driversf ca202.sys

If Windows Firewall is enabled try disabling it?

I use a free one called Ashampoo,

Small and unobtrusive.

^ thanks, I’ll try that later

Yeah, I’ve even just discovered that they have a new version of the driver, so I installed it. But the error thing shows up again >__

Ok, so I’ve disabled Windows Firewall. Because ashampoo doesn’t work on Vista, I installed Comodo.

But it still doesn’t work D

I’ve installed Live Lite 4 but it gives me the message

«Failed to open the audio device «Behringer FCA202 ASIO».

I’m pissed off, but I’m still going to try installing the updated Live Lite 8 first and see if that one works.

Источник