|
|
#1 |
|
Human being with feelings Join Date: Apr 2012 Posts: 156 |
Installed the latest version yesterday and opened Reaper no problems. Today I go to open Reaper its still ok. Proceed to open another project and Reaper shuts down. I open Reaper again and Get the «Error Opening Devices»Error initializing ASIO driver. |
|
|
|
|
#2 |
|
Human being with feelings
Join Date: Sep 2008 Location: UK Posts: 3,435 |
And if you go to the audio devices page is the correct ASIO driver selected? Have you tried switching to another driver and back again? |
|
|
|
|
|
#3 |
|
Human being with feelings Join Date: Jun 2015 Posts: 8,384 |
I had this with WASAPI. Actually I can no longer use my WASAPI guitar device because of it. ASIO still works though. |
|
|
|
|
|
#4 |
|
Human being with feelings Join Date: Apr 2012 Posts: 156 |
Yes correct audio device is selected. Yes I did select another audio device and went back again. Still same message |
|
|
|
|
|
#5 |
|
Human being with feelings Join Date: Jun 2015 Posts: 8,384 |
Did you try reinstalling the ASIO driver? |
|
|
|
|
|
#6 |
|
Human being with feelings Join Date: Apr 2012 Posts: 156 |
Quote:
Originally Posted by Softsynth Did you try reinstalling the ASIO driver? yes still same message |
|
|
|
|
|
#7 |
|
Human being with feelings
Join Date: Apr 2011 Location: St George, UT _ USA Posts: 2,866 |
Same Error(s) here on both PC Win10 Pro DAW(s) ….. (1) Wasapi, (1) Saffire ASIO. Reaper v5.941; Windows 10 Pro64, Insider Preview Build 17733. (latest)
Last edited by sostenuto; 08-09-2018 at 07:12 PM.
|
|
|
|
|
|
#8 |
|
Human being with feelings Join Date: Apr 2012 Posts: 156 |
I would have to think it has something to do with the latest install but i could be wrong. Funny I haven’t had a problem like that in a long while and the last time I got that message I uninstalled my Roland Duo capture the reinstalled and working great since |
|
|
|
|
|
#9 |
|
Human being with feelings Join Date: Apr 2012 Posts: 156 |
Anybody help me please? |
|
|
|
|
|
#10 |
|
Human being with feelings
Join Date: Mar 2013 Posts: 5,750 |
Quote:
Originally Posted by slooky Anybody help me please? Just in case: have you already rebooted your computer in the meantime? Otherwise, if you haven’t already, make a fresh portable Reaper install (with the same or a previous version) to a separate folder (side by side to your existing install) to check if the behavior is the same there: http://lacinato.com/cm/blog/25-reaperportable Or try if rolling back to a previous version (by installing it over your current version) makes any difference: http://reaper.fm/download-old.php |
|
|
|
|
|
#11 |
|
Human being with feelings Join Date: Apr 2012 Posts: 156 |
Thank you very much Solger. I have rebooted the computer. I am going to do a portable install now. |
|
|
|
|
|
#12 |
|
Human being with feelings Join Date: Apr 2012 Posts: 156 |
I tried rolling back to a previous version and still had the same error.
Last edited by slooky; 08-11-2018 at 02:33 PM.
|
|
|
|
|
|
#13 |
|
Human being with feelings
Join Date: Mar 2013 Posts: 5,750 |
Quote:
Originally Posted by slooky I tried rolling back to a previous version and still had the same error. Maybe check/disable the ‘Close audio device’ settings in Preferences > Audio first, just in case. Otherwise, in order to try narrowing down the possible source of the issue, you could do the following: 1) On your existing install: export your entire Reaper config via Preferences > General first (by checking all category boxes on the left) Or try this (before the export/import option): 1) Options > Show REAPER resource path …
Last edited by solger; 08-11-2018 at 02:40 PM.
|
|
|
|
|
|
#14 |
|
Human being with feelings Join Date: Apr 2012 Posts: 156 |
Quote:
Originally Posted by solger Maybe check/disable the ‘Close audio device’ settings in Preferences > Audio first, just in case. Otherwise, in order to try narrowing down the possible source of the issue, you could do the following: 1) On your existing install: export your entire Reaper config via Preferences > General first (by checking all category boxes on the left) Or try this (before the export/import option): 1) Options > Show REAPER resource path … Close audio device is already checkmarked. I did change ASIO to Dummy Audio, closed Reaper, reopened changed back to ASIO and it all worked So first option I don’t really know how to import …
Last edited by slooky; 08-11-2018 at 06:49 PM. Reason: wrong
|
|
|
|
|
|
#15 |
|
Human being with feelings Join Date: Apr 2012 Posts: 156 |
Hello Solger: I opened Reaper in safe mode and put in RPP file and everything works. What I have found is one particular RPP file when it gets loaded and go to open another Rpp file it shuts down, then when i open again I get the error. it only seem to happen when I load that particular file and open another file. I have tried numerous Rpp files and that is the only one it happens to. Weird |
|
|
|
|
|
#16 |
|
Human being with feelings
Join Date: Mar 2013 Posts: 5,750 |
Quote:
Originally Posted by slooky … I have tried numerous Rpp files and that is the only one it happens to. Weird Yeah, very strange. Quote: I guess that file I will have to delete which is unfortunate,, their was a lot of work that went into that file. Before deleting the file, you could check out the following things:
Quote: Hello Solger: I opened Reaper in safe mode and put in RPP file and everything works. Just to clarify: what exactly do you mean with ‘safe mode’ or how did you do that? Quote: So first option I don’t really know how to import … Just as general side note: info about configuration export/import can be found here: www.reaper.fm/videos.php#HB4C3njFxRg
Last edited by solger; 08-12-2018 at 03:57 AM.
|
|
|
|
|
|
#17 |
|
Human being with feelings Join Date: Apr 2012 Posts: 156 |
Not really sure how I did the safe mode. I put Ctrl Shift then opened Reaper and Reaper opened up with no Rpp file.Then I added a RPP file. |
|
|
|
|
|
#18 |
|
Human being with feelings
Join Date: Mar 2013 Posts: 5,750 |
Quote:
Originally Posted by slooky Not really sure how I did the safe mode. I put Ctrl Shift then opened Reaper and Reaper opened up with no Rpp file.Then I added a RPP file. Ah, I see. Then you probably have Preferences > General > Open project(s) on startup set to something like [Last active project]. Loading Reaper with the Ctrl/Shift button pressed starts it with a new project. Under Windows the same can be achieved by using the create new project shortcut in the Windows Start Menu:
|
|
|
|
|
|
#19 |
|
Human being with feelings Join Date: Apr 2012 Posts: 156 |
Quote:
Originally Posted by solger Ah, I see. Then you probably have Preferences > General > Open project(s) on startup set to something like [Last active project]. Loading Reaper with the Ctrl/Shift button pressed starts it with a new project. Under Windows the same can be achieved by using the create new project shortcut in the Windows Start Menu:
Wow I never even seen that before but now I know its there because I just took a look.I always open up from the app from the desktop. Thanks for that |
|
|
|
|
|
#20 |
|
Human being with feelings
Join Date: Mar 2013 Posts: 5,750 |
Quote:
Originally Posted by slooky I created a zip file Rpp Thanks. I had a quick look and your .RPP file seems to behave fine here (as a side note: I can’t really check if the issue might be plugin related though, since I don’t have all of the plugins used in the .RPP file). Did you already have time to check if using the Open with FX offline (recovery mode) option (mentioned in post #16) makes any difference?
Last edited by solger; 08-14-2018 at 11:30 AM.
|
|
|
|
|
|
#21 |
|
Human being with feelings Join Date: Apr 2012 Posts: 156 |
Quote:
Originally Posted by solger Thanks. I had a quick look and your .RPP file seems to behave fine here (as a side note: I can’t really check if the issue might be plugin related though, since I don’t have all of the plugins used in the .RPP file). Did you already have time to check if using the Open with FX offline (recovery mode) option (mentioned in post #16) makes any difference? Thank you Solger: No i am very hesitant, I had no recording being done for 4 days so i missed doing that but I will check now.
Last edited by slooky; 08-14-2018 at 05:41 PM. Reason: New post
|
|
|
|
|
|
#22 |
|
Human being with feelings Join Date: Jan 2015 Posts: 63 |
You’re not alone. Just downloaded Reaper 6 and have the exact same issue. EDIT: I just realized this thread was from 2018. I just assumed it was a Reaper 6 problem. Anyone experiencing this with reaper 6 or has any clue what I can do about it? |
|
|
|
|
|
#23 |
|
Human being with feelings Join Date: Nov 2019 Location: Canada Posts: 14 |
Quote:
Originally Posted by Wizz EDIT: I just realized this thread was from 2018. I just assumed it was a Reaper 6 problem. Anyone experiencing this with reaper 6 or has any clue what I can do about it? Same issue, sort of, WASAPI Multichannel stopped working in Reaper with Rodecaster Pro multi channels when I updated from 5.98x to 6.x. It will work with only 2 stereo in the IN/Out device Rodecaster Stereo NOT the 14 Channel (Rodecaster Multi) for input. It worked flawlessly then just stopped. Any of you updated Windows 64bit (1909) I had a system update just prior to the problem as well. It’s either Reaper or MS. Very Frustrating. ASIO4ALL works however no problem BUT I have to change the in/out to hear back after recording. Not Ideal.
Last edited by RobertJohn; 12-16-2019 at 08:07 AM.
|
|
|
|
|
|
#24 |
|
Human being with feelings Join Date: Jul 2016 Posts: 3 |
Hello, I know the topic is old but as some people still experience this problem sometimes… I now and then face it too : the ASIO is not recognised anymore, sometimes even after restarting. I think it systematically happens after a crash, which is rare with reaper but some VST’s mess things up sometimes. first , and other softwares that might use sound as well (web browser, audio/video player), then it works back to normal. Best. |
|
|
|
|
Forum Jump |
All times are GMT -7. The time now is 04:50 AM.
Powered by vBulletin® Version 3.8.11
Copyright ©2000 — 2023, vBulletin Solutions Inc.
If you got error “Error opening sound device” while using Audacity to record sound, don’t worry. You can fix the error by following the simple instructions below.
Audacity website has provided tips to fix this issue. But it seems not very easy to follow through the instructions. If you’ve tried the solutions on their website but the error persists, try the six solutions in this post.
There are six solutions for you to try to fix this error. You may not have to try them all. Just work your way down at the top of the list until you find the one that works for you.
- Ensure the external sound device is plugged in (desktop only)
- Ensure the external sound device is enabled
- Ensure audio device settings in Audacity are configured correctly
- Turn off Software Playthrough in Audacity
- Update the audio driver
- Restart the Windows Audio Endpoint Builder service
Solution 1: Ensure the external sound device is plugged in (desktop only)
If you’re using a desktop computer, ensure the device you use to listen to the sound such as external speakers, is plugged in.
If you’ve plugged the external sound device into the computer, ensure they are recognized by your computer.
How to check: In the system tray, if you see a red x with circle icon the speaker icon, it indicates the external sound device (for example, your speakers or your microphone) is not connected to the computer. In this case, unplug the device then replug it. After that, if the issue is still there, refer the steps in Solution 2 to check if the device is disabled.
Solution 2: Ensure the external sound device is enabled
If the external speakers or microphone is disabled, error “Error open sound device. Try changing the audio host, recording device and the project sample rate” would occur. So when you get this error, check if the device is disabled. If it’s disabled, enable it manually.
Follow steps below to check if the speakers are disabled:
1) Right-click on the speaker icon in the system tray, and select Playback devices.
2) If you see the Speakers disabled, right-click on the item, then select Enable. If you see the Speakers enabled, skip this step.
If you’re using a laptop computer, you also need to check if the microphone device is disabled.
Follow these steps:
1) Right-click on the speaker icon in the system tray, and select Recording devices.
2) If you see the Microphone disabled, right-click on the item, then select Enable. If you see the Microphone enabled, skip this step.
Solution 3: Ensure audio device settings in Audacity are configured correctly
This error can be caused by incorrect audio device settings in Audacity. So check and ensure the audio device settings in Audacity are configured correctly.
Follow these steps:
1) Open Audacity.
2) Click Edit in the menu bar and select Preferences.
3) Click Devices.
3) Ensure the Host field set to Windows WASAPI.
After you set the Host to Windows WASAPI, you’ll see the values of Device field under Playback and the Device under Recording change automatically.
5) Click the OK button.
6) Check to see if you can record successfully.
Solution 4: Turn off Software Playthrough of input in Audacity
Software Playthrough should not be enabled when you record sound. If it’s enabled, error “Error opening sound device” will probably occur.
Follow below steps to check if Software Playthrough is checked. And uncheck it if you need.
1) Open Audacity.
2) Click Edit in the menu bar and select Preferences.
3) Click Recording.
4) Under Playthrough, if you see Software Playthrough of input is checked, uncheck it. Then click the OK button. If not, skip this solution then try other solutions.
Solution 5: Update the audio driver
If the installed audio driver is outdated, it may not support the Audacity record feature. To fix the error, you can try to update the audio driver.
You can update the audio driver manually. Just go to your PC manufacturer’s website or the sound card manufacturer’s website to check for and download the latest audio driver. If you don’t have the time, patience or computer skills to update the driver manually, you can do it automatically with Driver Easy.
Driver Easy will automatically recognize your system and find the correct drivers for it. You don’t need to know exactly what system your computer is running, you don’t need to risk downloading and installing the wrong driver, and you don’t need to worry about making a mistake when installing.
You can update your drivers automatically with either the FREE or the Pro version of Driver Easy. But with the Pro version it takes just 2 clicks (and you get full support and a 30-day money back guarantee):
1) Download and install Driver Easy.
2) Run Driver Easy and click Scan Now. Driver Easy will then scan your computer and detect any problem drivers.
3) Click the Update button next to a flagged audio driver to automatically download and install the correct version of this driver (you can do this with the FREE version).
Or click Update All to automatically download and install the correct version of all the drivers that are missing or out of date on your system (this requires the Pro version – you’ll be prompted to upgrade when you click Update All).
4) After updating the driver, check to see if you can record sound successfully.
Solution 6: Restart the Windows Audio Endpoint Builder service
If Windows Audio Endpoint Builder service is not running properly, this error would occur. So restart the Windows Audio Endpoint Builder service to try to fix the “Error opening sound device “ issue.
Follow steps below:
1) On your keyboard, press the Win+R (Windows logo key and R key) at the same time to invoke the run box.
2) Type services.msc and press Enter to open the Services window.
3) Click Windows Audio Endpoint Builder, then click Restart. The follow the on-screen instructions.
4) Check to see if you can record successfully.
Hopefully the solutions above help you resolve the problem. If you have any questions, please feel free to leave your comments. I’d love to hear of any ideas or suggestions.
11
11 people found this helpful
Error Opening Device (Read 6768 times)
|
Vortex
YaBB Newbies Phoner is great! Posts: 9 Joined: 24. Feb 2016 |
Error Opening Device |
Print Post |
|
If I try and use Phonerlite I get the error message «Error Opening Device». I can use Phoner Beta OK on the same computer, except people can hardly hear me even when the microphone volume is set at max. When I use other softphones people can hear me OK. |
||
|
|
IP Logged|
Phoner Admin YaBB Administrator Posts: 11261 Joined: 12. Oct 2003 |
Re: Error Opening Device |
Print Post |
|
Please take a look at Options/Configuration/Sound. Do you have enabled «Automatic gain control» there? If so, disable this and save the config. |
||
|
|
WWW
|
|
Vortex
YaBB Newbies Phoner is great! Posts: 9 Joined: 24. Feb 2016 |
Re: Error Opening Device |
Print Post |
|
The Error message seemed to be because the bluetooth headset was starting slower than the phonerlite software, so it couldn’t see the headset at startup. I Still have the problem of low volume. I don’t have ‘automatic gain control’ enabled. The problem does not occur in Zoiper or X-lite with the same hadrware. Is there any way to increase the maximum microphone volume level? Also is it possible to pay and get the 729 codec? Thanks. |
||
|
|
|
|
Phoner Admin YaBB Administrator Posts: 11261 Joined: 12. Oct 2003 |
Re: Error Opening Device |
Print Post |
|
I don’t have that device here for testing. PhonerLite is just a hobby project of mine. I can’t test with all devices. G.729 is no technical problem, but the license is the problem. Please take a look here: http://www.sipro.com/Licensing-Terms-G-729.html |
||
|
|
WWW
|
Audacity is a free virtual studio software for Windows computers and it’s a great tool to edit music files for free. However, some users have reported having problems when trying to record or play their files using Audacity. The error message read “Error opening sound device” and it has bugged users all over the world.
There are a couple of causes and methods which can be used to solve the problem and we recommend you follow through the rest of the article to find out just what to do to solve the problem.
What Causes Audacity “Error opening sound device” Error?
It’s usually a permissions issue which started to appear after a specific Windows Update because it has reset some permissions settings for apps which are allowed to use your microphone.
Solution 1: Let Apps Use Your Microphone
This little option may have always been turned on before but it might have been changed by new programs being installed or by a Windows Update which might have turned it off for various security reasons. This solution is the simplest and it can save you hours of pain so make sure you don’t skip this method.
Windows 10 Users:
- Click the gear icon in the lower left section of the Start menu in order to open the Settings app. You can also search for it.
- Scroll down until you see the Privacy section and make sure you click on it. At the left side of the window, you should see the App permissions section. Scroll down until you reach Microphone and click on this option.
- First of all, check if the Microphone access for this device option is on. If it’s not, click on Change and set the slider to on.
- After that, switch the slider under the “Allow apps to access your microphone” option to On and scroll down in the list of installed apps on your computer to locate Skype. Switch the slider next to the Skype entry on the list to on.
- Reopen Audacity and check to see if the problem persists.
Further Troubleshooting for Windows 10 and Older Versions of Windows
It’s possible that one of your core sound devices may have been disabled by a program or by a new Windows Update. Also, this can fix the problem if there are other similar tools installed on your computer which might try to access sound devices at the same time as Audacity.
- Right-click on the volume icon located at your taskbar and choose the Sounds option. If this icon is not located at your taskbar, you can locate Sound settings by opening Control Panel, switching the view to Category and selecting Hardware and Sound >> Sound.
- Check to see if your microphone is enabled under the Recording tab. Switch to this tab by clicking at the top of the window and locate the Microphone you are using. It should be located at the top and be selected.
- Click on it once and click the Properties button at the lower right part of the window. In the Properties window which opens, check under Device usage and set the option to Use this device (enable) if it wasn’t already and apply the changes.
- Navigate to the Advanced tab in the same properties window and check under Exclusive mode.
- Uncheck the boxes next to the “Allow applications to take exclusive control of this device” and “Give exclusive mode applications priority”. Apply these changes as well and repeat the same process for your Speaker device in the Playback tab before you close these windows. Reopen Audacity and check to see if the error persists.
Note: Even if you are a Windows 10 user, you should still try out the second set of steps as they managed to solve the problem for some Windows 10 users when the above has failed.
Solution 2: Use the Built-in Voice Recorder and Switch to Audacity
It’s quite possible that a third party app is hogging one of your sound devices and it’s almost impossible to take ownership of it once more. The reason why opening Voice Recorder which is built into your Windows OS might work is because this app is verified by Microsoft and it has better permissions than any third-party app.
The Voice Recorder is available on all versions of Windows so make sure you use it to solve the Audacity “Error opening sound device” error!
- Search for Voice Recorder’s shortcut on the Desktop and double-click it, or search for it in the Start menu. If you struggle finding it, you can use the command below.
- Search for “Command Prompt” by typing it either right in the Start menu or by pressing the search button right next to it. Right-click the first entry which will pop up as a search result and select the “Run as administrator” context menu entry.
- Type in the command below in the window and make sure you press Enter after typing each one. Wait for the Voice Recorder window to open to know that the command worked
explorer.exe shell:appsFolder\Microsoft.WindowsSoundRecorder_8wekyb3d8bbwe!App
- Click the microphone button in order to start a recording. Close Voice Recorder and reopen Audacity to see if the problem still appears.
Kevin Arrows
Kevin Arrows is a highly experienced and knowledgeable technology specialist with over a decade of industry experience. He holds a Microsoft Certified Technology Specialist (MCTS) certification and has a deep passion for staying up-to-date on the latest tech developments. Kevin has written extensively on a wide range of tech-related topics, showcasing his expertise and knowledge in areas such as software development, cybersecurity, and cloud computing. His contributions to the tech field have been widely recognized and respected by his peers, and he is highly regarded for his ability to explain complex technical concepts in a clear and concise manner.
Back to top button
i was writing this docker command for falco installation :
i wrote this:
docker run —rm -i -t —privileged -v /root/.falco:/root/.falco -v /proc:/host/proc:ro -v /boot:/host/boot:ro -v /lib/modules:/host/lib/modules:ro -v /usr:/host/usr:ro -v /etc:/host/etc:ro falcosecurity/falco:latest
but it gave me this error
- Setting up /usr/src links from host
- Running falco-driver-loader for: falco version=0.34.1, driver version=4.0.0+driver, arch=x86_64, kernel release=5.19.0-38-generic, kernel version=39
- Running falco-driver-loader with: driver=module, compile=yes, download=yes
================ Cleaning phase ================
-
- Check if kernel module ‘falco’ is still loaded:
- OK! There is no ‘falco’ module loaded.
-
- Check all versions of kernel module ‘falco’ in dkms:
- OK! There are no ‘falco’ module versions in dkms.
[SUCCESS] Cleaning phase correctly terminated.
================ Cleaning phase ================
- Looking for a falco module locally (kernel 5.19.0-38-generic)
- Filename ‘falco_ubuntu-generic_5.19.0-38-generic_39.ko’ is composed of:
- driver name: falco
- target identifier: ubuntu-generic
- kernel release: 5.19.0-38-generic
- kernel version: 39
- Found a prebuilt falco module at /root/.falco/4.0.0+driver/x86_64/falco_ubuntu-generic_5.19.0-38-generic_39.ko, loading it
- Success: falco module found and inserted
2023-04-04T10:29:22+0000: Falco version: 0.34.1 (x86_64)
2023-04-04T10:29:22+0000: Falco initialized with configuration file: /etc/falco/falco.yaml
2023-04-04T10:29:22+0000: Loading rules from file /etc/falco/falco_rules.yaml
2023-04-04T10:29:22+0000: Loading rules from file /etc/falco/falco_rules.local.yaml
2023-04-04T10:29:22+0000: The chosen syscall buffer dimension is: 8388608 bytes (8 MBs)
2023-04-04T10:29:22+0000: Starting health webserver with threadiness 8, listening on port 8765
2023-04-04T10:29:22+0000: Enabled event sources: syscall
2023-04-04T10:29:22+0000: Opening capture with Kernel module
2023-04-04T10:29:22+0000: Trying to inject the Kernel module and opening the capture again…
2023-04-04T10:29:22+0000: Unable to load the driver
2023-04-04T10:29:22+0000: An error occurred in an event source, forcing termination…
Events detected: 0
Rule counts by severity:
Triggered rules by rule name:
Error: error opening device /host/dev/falco0. Make sure you have root credentials and that the falco module is loaded: No such file or directory
please help me to solve