|
|
|
07-09-2018, 10:37 AM
|
#1
|
Human being with feelings
Join Date: Oct 2015
Posts: 739
|
Bug with Wait for MIDI output device
Showstopper bug! Reaper freezes and doesn't come back when I get this error.
https://www.dropbox.com/s/e19w08mxdn...error.PNG?dl=0
I seems MIDI device loses connection to device. Still I think Reaper shouldn't just die because of this.
Expected behavior: As note says, I would unplug MIDI device, then plug it back in, and Reaper would resume.
Actual Behavior/Bug: Reaper gives notice, then nothing happens after I unplug/replug device. Reaper stays frozen, and I cannot close it. It is impossible to close window, no [X] button on it, it just stays there forever. Even ending task in Task manager is not working. I have to restart computer.
Please, at least add "Cancel" button, so that I can skip the notification window. It is non-critical error, there should be no need to restart computer.
If you need any more info, or my reaper ini files, please let me know.
EDIT: Windows 64 last update, Reaper last version 64bit
Last edited by sonicowl; 07-10-2018 at 01:58 AM.
|
|
|
07-10-2018, 01:44 AM
|
#2
|
Human being with feelings
Join Date: Nov 2017
Location: Heidelberg, Germany
Posts: 797
|
I recommend you to add at least which OS version and which REAPER version you have.
And while I agree it will be nice in case they fix that, not existing graceful operations with buggy/faulty hardware should not be called "show stopper bug". That is more not completely implemented feature.
|
|
|
07-10-2018, 02:02 AM
|
#3
|
Human being with feelings
Join Date: Oct 2015
Posts: 739
|
Quote:
Originally Posted by azslow3
I recommend you to add at least which OS version and which REAPER version you have.
And while I agree it will be nice in case they fix that, not existing graceful operations with buggy/faulty hardware should not be called "show stopper bug". That is more not completely implemented feature.
|
Noted. I added OS and Reaper version.
Regarding "showstopper"... Imagine this happens in a middle of live show, suddenly there is a device related pop-up which you cannot exit, no way to bypass or ignore it, Reaper is locked even if device is unplugged, you cannot even restart Reaper, and the only way to continue is to reboot computer - if this is not showstopper bug, then what should really happen to categorize it as showstopper?
It is a total showstopper, it literally stops everything, and you have to reboot computer. Can it be any worse?
|
|
|
07-10-2018, 02:24 AM
|
#4
|
Human being with feelings
Join Date: Jun 2009
Location: Croatia
Posts: 24,790
|
Is Audio->Warn when unable to open MIDI devices checked or not? If it's checked, might wanna uncheck it, could help.
Also since this is BCR2000 (a control surface), there's a similar checkbox in Preferences->Control/OSC/web, [ ] Warn when errors opening surface MIDI devices.
|
|
|
07-10-2018, 09:29 AM
|
#5
|
Human being with feelings
Join Date: Oct 2015
Posts: 739
|
Quote:
Originally Posted by EvilDragon
Is Audio->Warn when unable to open MIDI devices checked or not? If it's checked, might wanna uncheck it, could help.
Also since this is BCR2000 (a control surface), there's a similar checkbox in Preferences->Control/OSC/web, [ ] Warn when errors opening surface MIDI devices.
|
Hvala ti, ED.
"Audio->Warn when unable to open MIDI devices" was checked, I unchecked it now. I hope it will help.
"Preferences->Control/OSC/web" was checked too, unchecked it now. I have Klinke MCU control surface still loaded in Control/OSC/web, but I disabled MIDI device in/out, so it should be unrelated to BCF2000.
Actually, it is not BCR2000 (rotary), but BCF2000 (faders). I have BCR too, but that one never gives error.
I don't use OSC. I used Klinke MCU, but not anymore. I will use ReaLearn now, but error happens even when ReaLearn is not used. Basically, Reaper is not even connected to BCF2000. It happens even with empty project, meaning Reaper is not even using BCF2000 for anything.
Last edited by sonicowl; 07-10-2018 at 09:35 AM.
|
|
|
07-10-2018, 10:05 AM
|
#6
|
Human being with feelings
Join Date: Nov 2017
Location: Heidelberg, Germany
Posts: 797
|
Quote:
Originally Posted by sonicowl
Regarding "showstopper"... Imagine this happens in a middle of live show, suddenly there is a device related pop-up which you cannot exit, no way to bypass or ignore it, Reaper is locked even if device is unplugged, you cannot even restart Reaper, and the only way to continue is to reboot computer - if this is not showstopper bug, then what should really happen to categorize it as showstopper?
It is a total showstopper, it literally stops everything, and you have to reboot computer. Can it be any worse?
|
I have tested with my controller what happens when I unplug it during playback (both in and out enabled). It disappears from REAPER. Re-pluging does not return it till REAPER is restarted, but nothing is locked (Win10 / 64).
Your case sounds like some lockup in the device/USB controller or cable and/or related drivers. I mean user land programs can try to be prepared for more types of system failure, but that is the device/cable/driver which is faulty and the "show stopper", not REAPER.
REAPER csurf examples have no re-connection/stalled USB transfers handling. I guess the same is true for internal MIDI processing.
Till now I have not found the way to inform REAPER on the fly about connection status from csurf (I have hot-(re)plug capable "Not a Mouse" plug-in). And that is the point which can be improved. But that is a future request, not bug fixing.
|
|
|
07-10-2018, 12:53 PM
|
#7
|
Human being with feelings
Join Date: Oct 2015
Posts: 739
|
Quote:
Originally Posted by azslow3
I have tested with my controller what happens when I unplug it during playback (both in and out enabled). It disappears from REAPER. Re-pluging does not return it till REAPER is restarted, but nothing is locked (Win10 / 64).
Your case sounds like some lockup in the device/USB controller or cable and/or related drivers. I mean user land programs can try to be prepared for more types of system failure, but that is the device/cable/driver which is faulty and the "show stopper", not REAPER.
REAPER csurf examples have no re-connection/stalled USB transfers handling. I guess the same is true for internal MIDI processing.
Till now I have not found the way to inform REAPER on the fly about connection status from csurf (I have hot-(re)plug capable "Not a Mouse" plug-in). And that is the point which can be improved. But that is a future request, not bug fixing.
|
I can also unplug BCF2000 device while Reaper is running. It behaves exactly as you describe, I get windows notification chimes sound, and device simply is not there anymore. And, btw, you don't have to restart Reaper, you can make button "Reset all MIDI devices". So it is just one button click, and device is back. So it is not USB cable problem.
But in case of above reported error situation is different. There is no windows ping/chimes sound when it goes into error, so device is not really disconnected. It is still present in Device Manager. And it still works, I can see it sends data in MIDI-OX. It is just Reaper that hangs. Clearly device is faulty in some way, I'm not arguing that device is all good. But Reaper should handle it better, at least alow me to close notification window, and alow me to restart it.
So I disagree with you, that it is not Reaper's problem. Reaper shouldn't totally hang if something goes wrong in communication with hardware device. It is ok to give me alert notificationwindow, but I should be able to close that alert, and continue working without that device.
And surely it is not acceptable that Reaper freezes to the point that it is impossible to close it no matter what, and only thing to do is to restart computer. Surely device is weak and possibly at fault, is is cheap Behringer after all, but Reaper should handle it better, even if device or driver is responsible for data corruption. Total freeze and need to restart computer cannot be the best response we can get from Reaper.
Last edited by sonicowl; 07-10-2018 at 01:00 PM.
|
|
|
07-10-2018, 12:56 PM
|
#8
|
Human being with feelings
Join Date: Jun 2009
Location: Croatia
Posts: 24,790
|
If the device is faulty in a way that it created a feedback loop, all sorts of hell can break loose, and having things recursively happening like that can lead to unpredictable scenarios that are not all that easy to break out of...
|
|
|
07-10-2018, 03:07 PM
|
#9
|
Human being with feelings
Join Date: Oct 2015
Posts: 739
|
Quote:
Originally Posted by EvilDragon
If the device is faulty in a way that it created a feedback loop, all sorts of hell can break loose, and having things recursively happening like that can lead to unpredictable scenarios that are not all that easy to break out of...
|
But this device is not even used by Reaper when it reports the error. It happened to me even with empty project, no tracks at all. And device is not enabled in any remote control. So, basically, Reaper shouldn't have anything to do with it at all. So how can there be any loop with the device? It is just sitting there unused. Yet it gives me this error. Must be some mixup in Reaper's system files, I guess. I would like to troubleshoot this, but how? Anybody has any idea where to start?
Or, at least if developers could change that notifocation, so that it can be closed - I'd be ok with that. I don't mind restarting just Reaper if something goes wrong. I just hate restarting entire system, it's just too annoying.
|
|
|
07-10-2018, 03:25 PM
|
#10
|
Human being with feelings
Join Date: Jun 2009
Location: Croatia
Posts: 24,790
|
One other thing you could try is trashing your MIDI hardware settings (reaper-midihw.ini). Back it up somewhere, then remove from Reaper's resources folder, then restart Reaper and see if the device message still pops up. It kinda shouldn't.
|
|
|
07-10-2018, 04:23 PM
|
#11
|
Human being with feelings
Join Date: Nov 2017
Location: Heidelberg, Germany
Posts: 797
|
You have mentioned you are not using BCF. Do you mean it is not enabled in REAPER MIDI devices and it is not used by Control Surfaces? And then you mention MIDI-OX, so you probably also has MIDI looping software. I mean something on the software side can unintentionally clash/lock/loopback (in addition MIDI devices in Windows can be access by at least 3 different APIs and I do not know how good they inter-operate).
|
|
|
07-11-2018, 12:44 AM
|
#12
|
Human being with feelings
Join Date: Oct 2015
Posts: 739
|
Quote:
Originally Posted by azslow3
You have mentioned you are not using BCF. Do you mean it is not enabled in REAPER MIDI devices and it is not used by Control Surfaces? And then you mention MIDI-OX, so you probably also has MIDI looping software. I mean something on the software side can unintentionally clash/lock/loopback (in addition MIDI devices in Windows can be access by at least 3 different APIs and I do not know how good they inter-operate).
|
I use BCF with ReaLearn now. ReaLearn is a plugin, and connects to BCF only when it is on track. Last few times I got this error I didn't have any tracks in project, it happened soon after starting Reaper. Before I used BCF with Klinke MCU, and even before that with OSC.
MIDI-OX is running here, but BCF is not in it normally, I added it temporarly while Reaper was in error, just to see if it works.
|
|
|
07-11-2018, 12:49 AM
|
#13
|
Human being with feelings
Join Date: Oct 2015
Posts: 739
|
Quote:
Originally Posted by EvilDragon
One other thing you could try is trashing your MIDI hardware settings (reaper-midihw.ini). Back it up somewhere, then remove from Reaper's resources folder, then restart Reaper and see if the device message still pops up. It kinda shouldn't.
|
(reaper-midihw.ini) seems really messy here, a bit more in it than what I would expect, duplicated entries. BCF and BCR change names, Windows update usually messes the drivers, old stuff. Will trash it and see.
Code:
[mididevcache]
on0=Microsoft GS Wavetable Synth
oa0=
ot0=1531293552
on1=Launchpad Mini
oa1=
ot1=1483710321
on2=USB Trigger Finger Out [1]
oa2=
ot2=1531293552
on3=LoopBe Internal MIDI
oa3=
ot3=1531293552
on4=HDSP9652 Midi Port 1
oa4=
ot4=1531293552
on5=HDSP9652 Midi Port 2
oa5=
ot5=1531293552
on6=nanoKEY
oa6=
ot6=1467910185
on7=Axiom AIR Mini 32 MIDI Out
oa7=
ot7=1531293552
on8=Axiom AIR Mini 32 HyperCtrl
oa8=
ot8=1531293552
on9=2- BCR2000
oa9=
ot9=1461353675
on10=B-CONTROL Port 1
oa10=
ot10=1526142177
in0=Launchpad Mini
ia0=
it0=1483710321
in1=USB Trigger Finger In [1]
ia1=
it1=1531293552
in2=LoopBe Internal MIDI
ia2=
it2=1531293552
in3=HDSP9652 Midi Port 1
ia3=
it3=1531293552
in4=HDSP9652 Midi Port 2
ia4=
it4=1531293552
in5=nanoKEY
ia5=
it5=1467910185
in6=Axiom AIR Mini 32 MIDI In
ia6=
it6=1531293552
in7=Axiom AIR Mini 32 HyperCtrl
ia7=
it7=1531293552
in8=2- BCR2000
ia8=
it8=1461353675
in9=B-CONTROL Port 1
ia9=
it9=1526142177
on11=MIDISPORT 2x2 Out A
oa11=
ot11=1531293552
on12=MIDISPORT 2x2 Out B
oa12=
ot12=1531293552
on13=2- BCR2000 port 1
oa13=
ot13=1525971956
on14=2- BCR2000 port 2
oa14=
ot14=1525971956
on15=2- BCR2000 port 3
oa15=
ot15=1525971956
on16=B-CONTROL Port 2
oa16=
ot16=1526142177
on17=B-CONTROL Port 3
oa17=
ot17=1526142177
in10=MIDISPORT 2x2 In A
ia10=
it10=1531293552
in11=MIDISPORT 2x2 In B
ia11=
it11=1531293552
in12=2- BCR2000 port 1
ia12=
it12=1525971956
in13=2- BCR2000 port 2
ia13=
it13=1525971956
in14=2- BCR2000 port 3
ia14=
it14=1525971956
in15=B-CONTROL Port 2
ia15=
it15=1526142177
in16=B-CONTROL Port 3
ia16=
it16=1526142177
on18=nanoKEY 1 CTRL
oa18=
ot18=1526142014
on19=2- USB Trigger Finger Out [1]
oa19=
ot19=1470075008
on20=2- Axiom AIR Mini 32 MIDI Out
oa20=
ot20=1470075008
on21=2- Axiom AIR Mini 32 HyperCtrl
oa21=
ot21=1470075008
on22=4- BCR2000 port 1
oa22=
ot22=1517771825
on23=4- BCR2000 port 2
oa23=
ot23=1517771825
on24=4- BCR2000 port 3
oa24=
ot24=1517771825
on25=3- MIDISPORT 2x2 Out A
oa25=
ot25=1470075008
on26=3- MIDISPORT 2x2 Out B
oa26=
ot26=1470075008
in17=nanoKEY 1 KEYBOARD
ia17=
it17=1526142014
in18=2- USB Trigger Finger In [1]
ia18=
it18=1470075008
in19=2- Axiom AIR Mini 32 MIDI In
ia19=
it19=1470075008
in20=2- Axiom AIR Mini 32 HyperCtrl
ia20=
it20=1470075008
in21=4- BCR2000 port 1
ia21=
it21=1517771825
in22=4- BCR2000 port 2
ia22=
it22=1517771825
in23=4- BCR2000 port 3
ia23=
it23=1517771825
in24=3- MIDISPORT 2x2 In A
ia24=
it24=1470075008
in25=3- MIDISPORT 2x2 In B
ia25=
it25=1470075008
on27=2- B-CONTROL Port 1
oa27=
ot27=1517841525
on28=2- B-CONTROL Port 2
oa28=
ot28=1517841525
on29=2- B-CONTROL Port 3
oa29=
ot29=1502401078
in26=2- B-CONTROL Port 1
ia26=
it26=1517841525
in27=2- B-CONTROL Port 2
ia27=
it27=1517841525
in28=2- B-CONTROL Port 3
ia28=
it28=1502401078
on30=Launchpad Mini 16
oa30=
ot30=1531293552
in29=Launchpad Mini 16
ia29=
it29=1531293552
on31=loopMIDI Port 1
oa31=
ot31=1531293552
on32=loopMIDI Port 2
oa32=
ot32=1531293552
on33=loopMIDI Port 3
oa33=
ot33=1531293552
on34=loopMIDI Port 4
oa34=
ot34=1531293552
in30=loopMIDI Port 1
ia30=
it30=1531293552
in31=loopMIDI Port 2
ia31=
it31=1531293552
in32=loopMIDI Port 3
ia32=
it32=1531293552
in33=loopMIDI Port 4
ia33=
it33=1531293552
in34=nanoKEY 1 CTRL
ia34=
it34=1487157944
on35=2- Launchpad Mini 16
oa35=
ot35=1502405505
in35=2- Launchpad Mini 16
ia35=
it35=1502405505
on36=4- Launchpad Mini 16
oa36=
ot36=1517771825
in36=4- Launchpad Mini 16
ia36=
it36=1517771825
on37=2- MIDISPORT 2x2 Out A
oa37=
ot37=1517771825
on38=2- MIDISPORT 2x2 Out B
oa38=
ot38=1517771825
in37=2- MIDISPORT 2x2 In A
ia37=
it37=1517771825
in38=2- MIDISPORT 2x2 In B
ia38=
it38=1517771825
on39=MIDI4x4
oa39=MIDIOUT1 (MIDI4x4)
ot39=1531293552
on40=MIDIOUT2 (MIDI4x4)
oa40=
ot40=1531293552
on41=MIDIOUT3 (MIDI4x4)
oa41=
ot41=1531293552
on42=MIDIOUT4 (MIDI4x4)
oa42=
ot42=1531293552
in39=MIDI4x4
ia39=MIDIIN1 (MIDI4x4)
it39=1531293552
in40=MIDIIN2 (MIDI4x4)
ia40=
it40=1531293552
in41=MIDIIN3 (MIDI4x4)
ia41=
it41=1531293552
in42=MIDIIN4 (MIDI4x4)
ia42=
it42=1531293552
on43=2- BCF2000 port 1
oa43=
ot43=1531293552
on44=2- BCF2000 port 2
oa44=
ot44=1531293552
in43=2- BCF2000 port 1
ia43=
it43=1531293552
in44=2- BCF2000 port 2
ia44=
it44=1531293552
on45=BCF2000 port 1
oa45=
ot45=1525971956
on46=BCF2000 port 2
oa46=
ot46=1525971956
in45=BCF2000 port 1
ia45=
it45=1525971956
in46=BCF2000 port 2
ia46=
it46=1525971956
on47=BCF2000
oa47=
ot47=1526142177
on48=MIDIOUT2 (BCF2000)
oa48=
ot48=1526142177
in47=BCF2000
ia47=
it47=1526142177
in48=MIDIIN2 (BCF2000)
ia48=
it48=1526142177
on49=BCR2000 port 1
oa49=
ot49=1531293552
on50=BCR2000 port 2
oa50=
ot50=1531293552
on51=BCR2000 port 3
oa51=
ot51=1531293552
in49=BCR2000 port 1
ia49=
it49=1531293552
in50=BCR2000 port 2
ia50=
it50=1531293552
in51=BCR2000 port 3
ia51=
it51=1531293552
|
|
|
07-11-2018, 01:21 AM
|
#14
|
Human being with feelings
Join Date: Oct 2015
Posts: 739
|
Yea, trashed (reaper-midihw.ini), opened Reaper and cheched Midi devices - all devices were there, properly connected.
Then I checked newly created (reaper-midihw.ini) with explorer/notepad, redundant entries are removed.
Switched back to Reaper, and BOOM, again error message. It is empty project, no tracks, nothing. Only thing I did was open project, check preferences, switch to Explorer and notepad and switch back to reaper - FREEZE.
Actually, Reaper is not really frozen, I can move and use "Reaper Preferences" window (I left it open before switching to Explorer). I can switch folders in Reaper Preferences, all works in that window. I can also move "REAPER - Wait for MIDI output device" notification. But I cannot close the damn notification. It is waiting for output, but that output never happens! ESC doesn't work, no way to get rid of that notification.
So, what is this? Doesn't even make sense, I wasnt, even working in Reaper.
I suspect Reaper is not even frozen in the back, it just sits behind that notification window, waiting for something to happen, but it never happens.
Please, Justin, add [X] on that notification window, so I can close it. Or enable that it can be skipped by ESC. Or let it self destruct after 10 seconds.
OK, i'm off, restarting computer. BRB
|
|
|
07-11-2018, 01:38 AM
|
#15
|
Human being with feelings
Join Date: Oct 2015
Posts: 739
|
Hmm, after trashing (reaper-midihw.ini) at first it appeared that all devices were connected as before.
But now I see that some are connected and some disconnected, but differently than I had it before trashing. It seems that MIDI devices are defined somewhere else, and not just in (reaper-midihw.ini).
|
|
|
07-11-2018, 02:24 AM
|
#16
|
Human being with feelings
Join Date: Jun 2009
Location: Croatia
Posts: 24,790
|
Yeah I suppose check reaper.ini as well. There are lines "midiins", "midiins_cs", "midiouts", "midiouts_clock", might wanna trash those as well.
|
|
|
07-11-2018, 03:13 AM
|
#17
|
Human being with feelings
Join Date: Oct 2015
Posts: 739
|
Quote:
Originally Posted by EvilDragon
Yeah I suppose check reaper.ini as well. There are lines "midiins", "midiins_cs", "midiouts", "midiouts_clock", might wanna trash those as well.
|
You mean these?
midiins=471900017
midiins_h=135042
midiins_cs=1678151760
midiins_cs_h=141312
midiouts=1886723708
midiouts_h=4095
midiouts_clock=6144
midiouts_clock_h=1536
midiouts_clock_nospp=0
midiouts_clock_nospp_h=0
This seems to be unrelated to any device, it is just some numbers. How would I trash these anyway, set them all to zero? Or delete those lines?
|
|
|
07-11-2018, 03:40 AM
|
#18
|
Human being with feelings
Join Date: Jun 2009
Location: Croatia
Posts: 24,790
|
Delete those lines.
Also, might as well try a fresh portable install?
|
|
|
07-12-2018, 08:36 AM
|
#19
|
Human being with feelings
Join Date: Nov 2017
Location: Heidelberg, Germany
Posts: 797
|
Quote:
Originally Posted by sonicowl
I use BCF with ReaLearn now. ReaLearn is a plugin, and connects to BCF only when it is on track. Last few times I got this error I didn't have any tracks in project, it happened soon after starting Reaper. Before I used BCF with Klinke MCU, and even before that with OSC.
MIDI-OX is running here, but BCF is not in it normally, I added it temporarly while Reaper was in error, just to see if it works.
|
"ReaLearn is a plugin" - correct.
"and connects to BCF only when it is on track" - not really, it does not work with devices, it works with MIDI provided by REAPER.
So you have BCF MIDI input (and, from the error, also BCF MIDI output) enabled in REAPER. Independent from the existence of any tracks/plug-ins.
For Klinke, corresponding IO should be disabled in REAPER. But csurf plug-ins normally use REAPER API for opening/accessing MIDI, so you can get the same error.
For OSC approach, BCF should be disabled in REAPER. And MIDI processing is done by OSCII-Bot, so I seriously doubt you could get any REAPER errors about BCF in such scenario. Till you had it enabled, but then I wonder how OSCII-Bot could work with it in parallel. Could be done with MIDI-OX and looper (which you do not mention).
Too insane for me, I surrender
|
|
|
07-19-2018, 05:18 AM
|
#20
|
Human being with feelings
Join Date: May 2009
Posts: 29,260
|
Quote:
Expected behavior: As note says, I would unplug MIDI device, then plug it back in, and Reaper would resume.
|
If that is by chance a modal dialog, have you tried clicking Escape or ALT+F4?
Quote:
REAPER csurf examples have no re-connection/stalled USB transfers handling.
|
There is a Reset all MIDI devices action (I have it assigned to a shortcut and a toolbar button), anytime I have a midi device disconnect (including Csurf I think) it resets and reconnects to the device - this is what prevents me from having to restart reaper. What would happen if you created the same and clicked the keyboard shortcut when this message appears?
I've never had the hang issue described here though or I did and didn't realize it due to the above, but I'm not on the very latest version either.
__________________
Music is what feelings sound like.
|
|
|
07-19-2018, 08:47 AM
|
#21
|
Human being with feelings
Join Date: Mar 2015
Location: India Mumbai
Posts: 816
|
i have seen this happening on two of my computers
and with various midi hardware like the matrix brute
or Maschine mk3. but mostly Usb midi devices .
I understand termination of a service due to feedback loops
but hanging the whole daw does not make much sense
|
|
|
07-20-2018, 03:11 AM
|
#22
|
Human being with feelings
Join Date: Oct 2015
Posts: 739
|
Quote:
Originally Posted by karbomusic
If that is by chance a modal dialog, have you tried clicking Escape or ALT+F4?
|
Will try next time I get error.
Quote:
Originally Posted by karbomusic
There is a Reset all MIDI devices action (I have it assigned to a shortcut and a toolbar button), anytime I have a midi device disconnect (including Csurf I think) it resets and reconnects to the device - this is what prevents me from having to restart reaper. What would happen if you created the same and clicked the keyboard shortcut when this message appears?
I've never had the hang issue described here though or I did and didn't realize it due to the above, but I'm not on the very latest version either.
|
I have toolbar button too for Reset all MIDI devices action, but not keyboard shortcut. Will try, but I think that notification window steals all keys. If there was option to close that window, all would be good. I would just click on reset devices button then, and all would work.
Please, Justin, if you read this by any chance, can you just make a simple [Close] or [Cancel] button on that window? https://www.dropbox.com/s/e19w08mxdn...error.PNG?dl=0
I think that would be enough to continue with work without any problems.
|
|
|
07-20-2018, 03:16 AM
|
#23
|
Human being with feelings
Join Date: Oct 2015
Posts: 739
|
Quote:
Originally Posted by zookthespook
i have seen this happening on two of my computers
and with various midi hardware like the matrix brute
or Maschine mk3. but mostly Usb midi devices .
I understand termination of a service due to feedback loops
but hanging the whole daw does not make much sense
|
Related report: https://forum.cockos.com/showpost.ph...13&postcount=1
I'm not the only one with this issue.
|
|
|
Thread Tools |
|
Display Modes |
Linear Mode
|
Posting Rules
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is Off
|
|
|
All times are GMT -7. The time now is 11:22 AM.
|