|
|
#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,184 |
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,103 |
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,103 |
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,855 |
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,564 |
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,564 |
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,564 |
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,564 |
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,564 |
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 06:33 PM.
Powered by vBulletin® Version 3.8.11
Copyright ©2000 — 2023, vBulletin Solutions Inc.
Содержание
- Error opening devices reaper
- Error opening devices reaper
- Error opening devices reaper
- Error opening devices reaper
- Error opening devices reaper
Error opening devices reaper
Hey guys i went to open up reaper today and discovered this issue which ive never seen before and things before worked perfectly fine but when i opened up reaper i get this message
“
Error opening devices:
Error initializing ASIO Driver
The following MIDI outputs could not be opened:
Microsoft GS Wavetable Synth “
I havent run into this before and have been using a midi for months on reaper. I have windows 10, i went tried to rest midi devices, i have a focusrite interface, i restarted computer, turned off computer and even unplugged usb just to see if that was the issue with no resolve. Now could this be do to not updating drivers or some kind of setting got changed somehow by accident? Not really sure how to fix this so any advice would be greatlt appreciated thank you!!
Hey guys i went to open up reaper today and discovered this issue which ive never seen before and things before worked perfectly fine but when i opened up reaper i get this message
“
Error opening devices:
Error initializing ASIO Driver
The following MIDI outputs could not be opened:
Microsoft GS Wavetable Synth “
I havent run into this before and have been using a midi for months on reaper. I have windows 10, i went tried to rest midi devices, i have a focusrite interface, i restarted computer, turned off computer and even unplugged usb just to see if that was the issue with no resolve. Now could this be do to not updating drivers or some kind of setting got changed somehow by accident? Not really sure how to fix this so any advice would be greatlt appreciated thank you!!
you can try unplug re-plug focusrite interface to see if reaper recognise it..
if this dont work re-install the driver of your soundcard
Источник
Error opening devices reaper
I get the popup window saying that Reaper could not find my Novation Impulse 25 Keyboard (connected via USB) even though it is up, running and was well before I start Reaper.
1. Click ‘Retry’ — nada. goes in a loop going no where back to error message.
2. Exit Reaper and try again — same thing
3. Leave Reaper running, unplug the USB and then reconnect and click ‘Retry’ on the dialog and everything is fine.
Is this a common occurrence with Midi devices? although it has never said it hasn’t found the Roland Octa-Capture also connected or the Line 6 Pod XTLive if that was in use in place of the Octa-Capture.
(I haven’t found a way for both the Octa-capture and Pod XTLive to coexist and get mixed reports on the likes of Asio4all ideas.
Have tried everything, clearing drivers and reinstalling, changing back the firmware to work with automap resettting the midi etc. All to no avail.
If I was happy to unplug the keyboard usb and reconnect it and click retry on the error message then the keyboard works after a fashion…
Totally exasperated everything as the PC is a dual boot XP Pro and Windows 7 Pro box and will take ages to wipe down and reinstall everything as well as tangle with MS to reactivate the Windows bits….
The whole lot is just going to have to sit in heap in the corner until I can summon the will to start all that and the Novation keyboard is going … maybe in the bin.
The PC is an old P35DS4 motherboard, with an E8200 dual core, so circa 2008 machine.
The problem occurs no matter when, no other applications were set to run aside from the Nvidia graphics card, Antivirus TSRs that startup with Windows.
Novation released an updated firmware for the Impulse keyboard when they ceased supporting Automap. To be honest I had barely used the keyboard as the Automap didn’t seem to sit well with Reaper so things like transport controls etc. Never worked. As I read it they also released an updated USB driver to go with the firmware which replaced Automap operation with HUI.
Once or twice pre the update, Reaper would do throw the same error, always highlighting the Impulse device but it wasn’t a repeatable error every Reaper startup. It may have got slightly worse with updating from version 5 reaper to the later version 6 so I did think maybe it is a software timing thing to do with reaper startup what it does and how long it waits post trying to initialise devices. It is strange that it is the Novation Impulse only that is being affected and not the Octa-Capture, so it’s drivers or firmware seem most likely cause.
To me Windows with its registry and never really being convinced that install or more importantly ‘uninstall’ routines do actually do a tidy job, so trying to trace what is going on at that level is fraught with problems. Combine with that that software including Reaper has its own config files in Users/username/app data/roaming/Reaper eg. The midi .ini file that holds device data then things can get more convoluted to diagnose.
I tried to keep the original reaper midi ini file but and get Reaper to create a new one but that changed the error but the impact was the same, it doesn’t matter if I used the old or new drivers firmware or Automap I have gone in circles trying to find a path and I have to admit defeat. If I am honest now, which is essential, then having tried so many things albeit trying to keep track I am no longer confident that I have a full record. When it gets to that stage, the old option really is to admit that and just start with a clean slate by wipe and reinstall. It’s just a pain.
I saw and read in awe the detail you went to helping Tod with Windows 10 issues. To be honest I wondered quite how Tod kept pace with all the detail and actions, knowing that would not have. So I must say that I very much appreciate your kind reply, but I have truly hit a wall with the the problem and I am resigned to the fact If I want to fix it, I have to start again. I simply don’t trust the Novation kit not causing a repeat.
Источник
Error opening devices reaper
Attached Images
Welcome to the Reaper forums.
A search, when you’re used to the forum will find other cases where this has been reported but…..
Was the audio interface switched on before starting Reaper? iIt needs to be, same for keyboard.
Have you changed which USB or other port you plug the interface into? Changing ports can mess with devices being found.
Alternatively start Reaper using the reset startup shortcut that is installed with a windows setup and reconfigure the audio devices etc.
Welcome to the forums indeed!
Also, have you tried removing the duplicate in/out devices MIDIIN2 and MIDIOUT2?
Welcome to the Reaper forums.
A search, when you’re used to the forum will find other cases where this has been reported but…..
Was the audio interface switched on before starting Reaper? iIt needs to be, same for keyboard.
Have you changed which USB or other port you plug the interface into? Changing ports can mess with devices being found.
Alternatively start Reaper using the reset startup shortcut that is installed with a windows setup and reconfigure the audio devices etc.
Welcome to the forums indeed!
Also, have you tried removing the duplicate in/out devices MIDIIN2 and MIDIOUT2?
Источник
Error opening devices reaper
Hey guys i went to open up reaper today and discovered this issue which ive never seen before and things before worked perfectly fine but when i opened up reaper i get this message
“
Error opening devices:
Error initializing ASIO Driver
The following MIDI outputs could not be opened:
Microsoft GS Wavetable Synth “
I havent run into this before and have been using a midi for months on reaper. I have windows 10, i went tried to rest midi devices, i have a focusrite interface, i restarted computer, turned off computer and even unplugged usb just to see if that was the issue with no resolve. Now could this be do to not updating drivers or some kind of setting got changed somehow by accident? Not really sure how to fix this so any advice would be greatlt appreciated thank you!!
Hey guys i went to open up reaper today and discovered this issue which ive never seen before and things before worked perfectly fine but when i opened up reaper i get this message
“
Error opening devices:
Error initializing ASIO Driver
The following MIDI outputs could not be opened:
Microsoft GS Wavetable Synth “
I havent run into this before and have been using a midi for months on reaper. I have windows 10, i went tried to rest midi devices, i have a focusrite interface, i restarted computer, turned off computer and even unplugged usb just to see if that was the issue with no resolve. Now could this be do to not updating drivers or some kind of setting got changed somehow by accident? Not really sure how to fix this so any advice would be greatlt appreciated thank you!!
you can try unplug re-plug focusrite interface to see if reaper recognise it..
if this dont work re-install the driver of your soundcard
Источник
Error opening devices reaper
I get the popup window saying that Reaper could not find my Novation Impulse 25 Keyboard (connected via USB) even though it is up, running and was well before I start Reaper.
1. Click ‘Retry’ — nada. goes in a loop going no where back to error message.
2. Exit Reaper and try again — same thing
3. Leave Reaper running, unplug the USB and then reconnect and click ‘Retry’ on the dialog and everything is fine.
Is this a common occurrence with Midi devices? although it has never said it hasn’t found the Roland Octa-Capture also connected or the Line 6 Pod XTLive if that was in use in place of the Octa-Capture.
(I haven’t found a way for both the Octa-capture and Pod XTLive to coexist and get mixed reports on the likes of Asio4all ideas.
Have tried everything, clearing drivers and reinstalling, changing back the firmware to work with automap resettting the midi etc. All to no avail.
If I was happy to unplug the keyboard usb and reconnect it and click retry on the error message then the keyboard works after a fashion…
Totally exasperated everything as the PC is a dual boot XP Pro and Windows 7 Pro box and will take ages to wipe down and reinstall everything as well as tangle with MS to reactivate the Windows bits….
The whole lot is just going to have to sit in heap in the corner until I can summon the will to start all that and the Novation keyboard is going … maybe in the bin.
The PC is an old P35DS4 motherboard, with an E8200 dual core, so circa 2008 machine.
The problem occurs no matter when, no other applications were set to run aside from the Nvidia graphics card, Antivirus TSRs that startup with Windows.
Novation released an updated firmware for the Impulse keyboard when they ceased supporting Automap. To be honest I had barely used the keyboard as the Automap didn’t seem to sit well with Reaper so things like transport controls etc. Never worked. As I read it they also released an updated USB driver to go with the firmware which replaced Automap operation with HUI.
Once or twice pre the update, Reaper would do throw the same error, always highlighting the Impulse device but it wasn’t a repeatable error every Reaper startup. It may have got slightly worse with updating from version 5 reaper to the later version 6 so I did think maybe it is a software timing thing to do with reaper startup what it does and how long it waits post trying to initialise devices. It is strange that it is the Novation Impulse only that is being affected and not the Octa-Capture, so it’s drivers or firmware seem most likely cause.
To me Windows with its registry and never really being convinced that install or more importantly ‘uninstall’ routines do actually do a tidy job, so trying to trace what is going on at that level is fraught with problems. Combine with that that software including Reaper has its own config files in Users/username/app data/roaming/Reaper eg. The midi .ini file that holds device data then things can get more convoluted to diagnose.
I tried to keep the original reaper midi ini file but and get Reaper to create a new one but that changed the error but the impact was the same, it doesn’t matter if I used the old or new drivers firmware or Automap I have gone in circles trying to find a path and I have to admit defeat. If I am honest now, which is essential, then having tried so many things albeit trying to keep track I am no longer confident that I have a full record. When it gets to that stage, the old option really is to admit that and just start with a clean slate by wipe and reinstall. It’s just a pain.
I saw and read in awe the detail you went to helping Tod with Windows 10 issues. To be honest I wondered quite how Tod kept pace with all the detail and actions, knowing that would not have. So I must say that I very much appreciate your kind reply, but I have truly hit a wall with the the problem and I am resigned to the fact If I want to fix it, I have to start again. I simply don’t trust the Novation kit not causing a repeat.
Источник
-
#1
Такая проблема — внезапно Рипер перестал воспроизводить звук. Вне рипера звук есть, в самой программа — тишина. И не просто нет звука, если я нажимаю на play- то воспроизведение вообще не идет. Что это может быть?
[DOUBLEPOST=1494077211][/DOUBLEPOST]Вот фото настроек аудиодевайса. Вроде же все норм?
-
5 MB
Просмотры: 1.742 -
3,7 MB
Просмотры: 1.589
-
#2
Посмотри какой девайс на воспроизведение стоит,в настройках,и глянь дескретизацию.
-
#3
Если переключить Audio system на WASAPI, звук есть?
[DOUBLEPOST=1494077571][/DOUBLEPOST]Если не ошибаюсь, у Focusrite мультиклиентный ASIO-драйвер.
У вас только рипер запущен или еще какой-то хост использующий ASIO?
-
#4
@mindcube, Если переключить на WASAPI, то звука нет и пишет, что «There was an error opening the audio hardware: WASAPI error: could not initialize» shared input device.
Кроме Рипера ничего не запущено.
-
#5
Покажи настройки в «Audio».
P.S. На ступень выше поднимись от настроек Device
-
#6
@AlexPollack, поставь portable и послушай там. Будет ясно где копать.
-
#7
@Dimilyan, вот скрин вкладки Audio
[DOUBLEPOST=1494158286][/DOUBLEPOST]@Oliver_Cray, поставил portable, та же ситуация. Воспроизведение не начинается, звука нет.
-
75,1 KB
Просмотры: 3.050
-
#8
Самую пресамую первую галочку убери.
-
#10
Раз
поставил portable, та же ситуация
Значит проблема системная.
Попробуй DirectSound если есть. Смени карту на встроенную.
Посмотри эти настройки
-
#11
@Oliver_Cray, DirectSound тоже молчит.
Что странно, так то, что вне рипера звук есть. Например, standalone версия XLN Addictive keys прекрасно играет.
Раньше всегда было так — когда заходил в рипер, в колонках издавались такие характерные звуки, бдыщь бдыщь, будто шнур пару раз воткнул в гнездо. И потом все работало.
Сейчас больше такие не издаются.
-
#12
Например, standalone версия XLN Addictive keys прекрасно играет.
Через тот же драйвер той же карты?
-
#14
@Oliver_Cray, Внезапно Рипер начал работать на DirectSound и WASAPI. На Асио все еще молчит. Оказалось, что многие стэндэлон версии, кроме Adictive Keys, на асио не работают.
Благородные доны, что это может быть? 
-
#16
У меня карта Lynx, использую родные хардверные дрова ASIO. Так вот эти дрова работают для DAW в монорежиме, т.е. если при стартанутом Рипере включить браузер или мультимедиа проигрыватель, то последняя программа заберет на себя фокус при использовании ASIO потока, рипер перестанет воспроизводить звук. Забирает фокус даже любой интернет браузер. В этом случае надо перестартовать Рипер, чтобы он забрал опять фокус на себя (при этом лучше закрыть мультимедиа ПО).
Протестируй, железобетонный способ — это закрыть всё мультимедиа программы и стартануть Рипер, в настройках проекта должны стоять ASIO дрова, звук должен появиться.
-
#18
Вчера все пробовал, ничего не помогало. А сегодня вечером пришел с работы- и работает. Чудеса)
-
#19
Обратите внимание, пользователь заблокирован на форуме. Не рекомендуется проводить сделки.
У меня карта другая, а проблемы похожие. И даже любопытно — отчего? Вроде и карта такая, что драйвера считаются надежными — Roland Quad Capture. Вроде и комп не сильно грузится моими проектами — Performance Meter показывает до 23% CPU, а памяти свободной больше двух третей. Но происходят странные дела:
— Не захотел работать (не было звука) на настройках проекта 48кГц с буфером 64, но заработал 96-128;
— Опять же, как правило при добавлении нового трека или плагина, вдруг прекращается звук и, как описано в первом посте, не идет воспроизведение. Если перезагрузить Рипер — может заработать. Или увеличить буфер. Но бывает и наоборот — при 96-512 перестает звучать, а при уменьшении буфера до 128 — начинает.
Вот хер его знает, что там происходит. Хотя, может оттого, что софт народный? Но на стареньком ноуте такого не наблюдалось. Правда и пихать в проект столько не приходилось, т.к. слабый ноут этого не позволял.
Последнее редактирование: 15 Май 2017
DAZZER
Электронный англоаудиофил
-
#20
Такая же фигня. На встроенной карте не идет воспроизведение вообще нигде. Играет только на Dummy Audio — индикаторы прыгают на треках и мастере, но звук на выход не поступает. Фубар, Вейвлаб — все играют, а Рипер — ни в какую.
Почему-то кажется, что NDI виноват, но удалить его не могу, т.к. нужен. Что делать?
АПД. Пришлось поставить ASIO4All. С ним только и заиграл. Но все же хотелось бы разобраться с этим.
Последнее редактирование: 27 Май 2019
-
#21
@DAZZER, WASAPI exclusive пробовали? Потом сразу перезапустить программу желательно. Я использую режим (polled).
Forum rules
Before you post please read how to get help. Topics in this forum are automatically closed 6 months after creation.
-
bulevardi
- Level 1
- Posts: 45
- Joined: Thu Feb 15, 2018 12:36 pm
- Contact:
(solved) «There was an error opening the audio hardware»
I’m receiving an error message when opening Reaper DAW
«There was an error opening the audio hardware»
Until yesterday I worked with Linux Mint Cinnamon (18 ?)
With a Focusrite Solo, Reaper worked directly out of the box.
Since today, I switched to another OS (Linux Mint XFCE 19), and installed Reaper again.
However, Reaper doesn’t seem to recognize the hardware (see screenshot).
In the Volume Control, the Scralett Solo is already set by default and it’s working as I can play music via VLC Player or Youtube or whatever.
Already switched to other USB port, rebooted, reïnstalled Reaper,…
I already updated the Scarlett firmware via Wine… but still not working.
Any other things I could try?
(I want to work directly via ALSA, not Jack)
Screenshot:
http://users.telenet.be/bulevardi/tmp/s … reaper.png
Thanks in advance!
Last edited by LockBot on Wed Dec 28, 2022 7:16 am, edited 2 times in total.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
Instagram, BandCamp, SoundCloud, Spotify, iTunes,….
Get In Touch^^
-
bulevardi
- Level 1
- Posts: 45
- Joined: Thu Feb 15, 2018 12:36 pm
- Contact:
Re: «There was an error opening the audio hardware»
Post
by bulevardi » Tue May 21, 2019 3:45 pm
Reïnstalled Cinnamon, this went quite quick, as my working files are on a separate disk.
Opened Reaper, error message, went to Reaper Preference menu, ALSA input/output field was blank too, clicked on it, did nothing…
but when fiddling in the blank field, I clicked on the dropdown arrow and the HW: usb audio Scarlett appeared !!
Did a recording, worked perfect.
I’m now wondering that I clicked on the arrow or not when I was testing in Xfce… Grrrr st00pid me.
The Volume Control of Cinnamon is slightly different as UI in comparison with the Pavucontrol in Xfce, but I’m really wondering if that really changed anything…
Should I reïnstall Xfce again to test it out… tempting… :s
Instagram, BandCamp, SoundCloud, Spotify, iTunes,….
Get In Touch^^
-
bulevardi
- Level 1
- Posts: 45
- Joined: Thu Feb 15, 2018 12:36 pm
- Contact:
Re: «There was an error opening the audio hardware»
Post
by bulevardi » Wed May 22, 2019 2:31 pm
Reïnstalled Xfce from scratch. Pavucontrol as volume mixer.
For some reason it is now directly working out of the box…
The input/output fields of the ALSA settings were already filled in with Scarlett in Reaper.
And no latency at all when recording. 
Don’t know what went wrong in the first place. It’s all working, so far so good.
Instagram, BandCamp, SoundCloud, Spotify, iTunes,….
Get In Touch^^
If you are not hearing any audio output from REAPER, you can fix this by first checking all of your hardware, gear, and cable connections. If you are still having the issue, select Options>Preferences>Device in REAPER and select/adjust the settings of the desired audio system.
Producing music without being able to hear any audio from your DAW (Digital Audio Workstation) is obviously impossible.
There is nothing worse than sitting down to produce music and dealing with technical difficulties such as not being able to get any sound from REAPER.
In this step-by-step article, I will show you how to get sound to output from REAPER if you have an issue with it.
What You Will Need To Follow This Tutorial
The only thing you will need to follow in this tutorial is the REAPER DAW itself.
The only exception is if you need to replace a cable or other hardware component in your recording setup.
Step One – Checking Your Hardware/Connections
The first step for restoring sound in REAPER is double-checking all of your hardware and connections.
Cables
Start by checking your speaker cables, headphone cables, power cables, etc. A good way to check your cables is to test them out with other devices.
If you have a faulty cable, it could be causing your audio monitoring issues, so start by replacing it before moving on.
Speakers/Headphones
The next thing to check is the headphones or speakers you monitor with.
You can do this by testing them with another device or by using another app on your computer since REAPER is the audio issue here and not your whole computer.
Audio Interface
The final thing to test out is your audio interface.
To test your audio interface, simply play another source of audio other than your DAW through it to verify that it is working correctly.
After you have tested out your cables, connections, speakers/headphones, and audio interface to verify that your issue is not audio hardware related, you can move on to the next step.
Step Two – Selecting Your Device/Changing Your Settings
The next step to solving your audio monitoring issue is changing around your REAPER preferences.
Start by clicking Options>Preferences>Device in REAPER, and then choose your audio system from the drop-down list.
If you do not see your device on the drop-down list, this indicates that your computer is not recognizing your audio device or that you need to download an audio driver for your device.
To fix this, find an instruction manual from the manufacturer and troubleshoot.
If it’s an audio driver issue, the manufacturer should provide you with a free download link.
To find a download link, start by checking the manufacturer’s website.
Step Three – Change Your Computer’s Settings
One last thing to consider when fixing a monitoring issue in REAPER is your computer’s audio settings.
It’s called something different on each operating system, but find your device’s audio or sound settings and make sure your computer recognizes your audio device and is connected.
If you go through these steps carefully and troubleshoot along the way, you will fix your audio monitoring issue in REAPER!
Why Can’t I Hear Anything In REAPER?
If you have all of your audio hardware, cables, and connections set up correctly, and you still can’t hear anything in REAPER, you probably need to assign your audio device in REAPER preferences.
Select Options>Preferences>Device and choose your audio device from the drop-down menu. If your device is not listed on this menu, you probably need to download an audio driver for your device. This will be available to you from the manufacturer.
If you complete this step and still can’t hear anything in REAPER, try opening up your computer’s audio or sound settings and make sure that your audio device is connected to and recognized by your computer.
How Do You Get Sound In REAPER?
You get sound in REAPER by properly setting up your computer, audio interface, speakers/headphones, and all cables and then configuring your settings in both REAPER and your computer.
Sometimes this process requires a bit of troubleshooting. Just take your time, be patient, and stick with it and you will figure out your sound issue in REAPER.
Does REAPER Support ASIO?
Yes, REAPER does support ASIO.
In fact, on my two previous computers that both ran Windows, I used ASIO as my only sound card/audio driver.
In my time using ASIO on these two computers, they fixed my latency issues and worked great with REAPER.
Here is a link to a free download for the ASIO version that I use.
How Do I Change Audio Output In REAPER?
You change audio output in REAPER by selecting Options>Preferences>Device and choosing your desired output device from the drop-down ‘Audio system‘ menu.
This is a quick and easy way to change your audio output in REAPER.
How Do I Enable Record Monitoring In REAPER?
To enable record monitoring in REAPER, toggle the ‘Record monitoring’ button on any given track until it is in the ‘ON’ position.
You can also select multiple tracks and change their monitoring settings simultaneously.
Check out the following guide to disable monitoring in REAPER.
Can You Use REAPER Without An Audio Interface?
Yes, you can use REAPER without having an audio interface. However, you will have a much harder time recording and properly monitoring in your home studio.
To use REAPER without an audio interface, you can use a USB microphone to record and headphones via your computer’s headphone jack to monitor.
However, keep in mind that it is ideal to have an audio interface for your studio setup.
What Is It that Other DAWs Have that REAPER Doesn’t?
The main thing that REAPER lacks that other DAWs such as Studio One, Logic Pro, and Pro Tools all have covered is a decent virtual instrument plugin collection.
While REAPER is an excellent DAW that you can use for all types of music production, it does not have a single virtual instrument plugin other than ‘ReaSynth,’ a low-quality synthesizer engine.
Does REAPER Have a Guitar Tuner?
While REAPER does not have a guitar-specific tuner, you can use the tuner on the ‘ReaTune’ plugin to tune your guitar.
This plugin is for vocal tuning, but you can still use it to tune other instruments.
What Are Some Features that You Really Like About REAPER?
Some of my favorite things about REAPER are its low price, its simple setup and workflow, and its customizability.
Not only is REAPER quite affordable compared to other DAWs and easy to use, but you can also customize its visual display, toolbars, and hotkeys to suit your music production and recording needs.
Click here for a complete guide on how to fix latency in REAPER.