I'm using Synchronous here on Win10 64-bit and it's working well.
#ERROR INITIALIZING ASIO BUFFERS REAPER WINDOWS#
I don't want Windows 11 on this machine, so disabling secure boot it's not a problem, but thanks for the advice.
#ERROR INITIALIZING ASIO BUFFERS REAPER DRIVER#
Secure Boot is disabled but the asio driver doesn't start, have you something to suggest? If that's not it, post back and let us know exactly what you've done so far step by step, we'll figure it out. Set the ASIO sample rate either in Reaper or in your interface's software, set the WDM sample rate per device in the Sound applet of Windows Control Panel. The most common tripping point I see is that your ASIO and WDM sample rates need to match. Hope this helps a bit understanding the problem, thanks for your help ) I see only asio ins and outs but I don't see them in the Windows mixer.
Then I rebooted and now, if I set Reaper to use the new audio inputs and outputs I get a message like "could initialize asio buffers". Then I checked that secure boot was disabled from system information as you suggested, but the first time that I used the new asio driver in Reaper I received an error message like "can't start asio driver".
I installed Sar and followed a very good tutorial from Gabriel, I believe that this comes from this list. I don't know if those match because I created two hendpoints, one for playback and one for recording but I don't see them in the Windows mixer. Dunno if it's strictly necessary, but I seem to get less errors from SAR than most folk, so I'm guessing that's part of getting it to be stable. I tend to keep all WDM devices using the same sample rate as ASIO across the board here. Once you've done all of those steps, both end points should be attempting to pass or receive signal, and Windows will be able to see them. To get your Recording end point to be visible in the Sound applet of Windows Control Panel,hit Alt+Applications on your master track within Reaper and enable whatever you've called your recording end point there. To get your Playback end point to be visible in the Sound applet of Windows Control Panel, create a track in Reaper, set its input to be whatever you've named your Playback end point and arm the track.ģ. Make sure you've chosen which ASIO driver SAR is meant to wrap in ASIO Configuration, and enabled your new end points in Reaper's range selector combo boxes.Ģ. You won't see the end points in the available WDM choices until those end points are passing signal, because SAR creates routing dynamically.ġ. I need to be able to select it as an input, to capture the microphone and send it to the customer, and I need it also for sending the reaper playback via Chrome.Ĭhrome says "requested device not found". It works now, I see in and outs also via wdm, but not in Chrome where I need to use it.
0 kommentar(er)
