abacab
Max Output Level: -30.5 dBFS
- Total Posts : 4464
- Joined: 2014/12/31 19:34:07
- Status: offline
If Sonar crashes and you are using LoopBe, it may leave the LoopBe driver running
I normally have LoopBe30 configured with one internal MIDI port in Sonar, so it activates when I launch Sonar, and it stops when I quit Sonar. Sonar had crashed on me the day before, and it turned out that LoopBe was still active. I had to reboot to clear this up.
I discovered this issue when I was trying to figure out why my PC was not sleeping yesterday. I have my PC setup to sleep after 60 minutes with no activity.
If you run a Windows cmd prompt as administrator, and enter "powercfg -requests" you can see the drivers and devices listed that can keep the computer awake.
Yesterday, I saw this even with Sonar shut down, and as a result my PC would not sleep:
C:\WINDOWS\system32>powercfg -requests
SYSTEM:
[DRIVER] nerds.de LoopBe30 - Internal Midi Ports (WDM) (ROOT\*LOOPBE30\0000)
An audio stream is currently in use.
I guess that this can mean that when Sonar gives the error "SONARPLT.exe has stopped working", it may not have time to clean up everything.
DAW: CbB; Sonar Platinum, and others ...
|
brundlefly
Max Output Level: 0 dBFS
- Total Posts : 14250
- Joined: 2007/09/14 14:57:59
- Location: Manitou Spgs, Colorado
- Status: offline
Re: If Sonar crashes and you are using LoopBe, it may leave the LoopBe driver running
2017/03/08 18:16:53
(permalink)
abacab
I had to reboot to clear this up.
For future reference, I would guess that restarting SONAR and opening a project that uses the driver would reset it without having to reboot.
SONAR Platinum x64, 2x MOTU 2408/PCIe-424 (24-bit, 48kHz) Win10, I7-6700K @ 4.0GHz, 24GB DDR4, 2TB HDD, 32GB SSD Cache, GeForce GTX 750Ti, 2x 24" 16:10 IPS Monitors
|
abacab
Max Output Level: -30.5 dBFS
- Total Posts : 4464
- Joined: 2014/12/31 19:34:07
- Status: offline
Re: If Sonar crashes and you are using LoopBe, it may leave the LoopBe driver running
2017/03/08 18:53:49
(permalink)
brundlefly
abacab
I had to reboot to clear this up.
For future reference, I would guess that restarting SONAR and opening a project that uses the driver would reset it without having to reboot.
The driver starts every time I launch Sonar, as it is configured in Prefs > MIDI > Devices > 01. Internal MIDI. Have not even actually used a project with LoopBe recently. I restarted Sonar several times, but LoopBe was hung in Windows. It did not even show in task manager, as this is a driver, not a task or process. The only thing I didn't try was disabling/enabling LoopBe in device manager. Reboot was probably just as quick though, only takes about 60 secs here.
DAW: CbB; Sonar Platinum, and others ...
|
AdamGrossmanLG
Max Output Level: -62 dBFS
- Total Posts : 1436
- Joined: 2014/07/13 03:40:34
- Status: offline
Re: If Sonar crashes and you are using LoopBe, it may leave the LoopBe driver running
2017/03/08 19:28:01
(permalink)
Why do you use LoopBe to begin with?
|
abacab
Max Output Level: -30.5 dBFS
- Total Posts : 4464
- Joined: 2014/12/31 19:34:07
- Status: offline
Re: If Sonar crashes and you are using LoopBe, it may leave the LoopBe driver running
2017/03/08 19:34:27
(permalink)
AdamGrossmanLG
Why do you use LoopBe to begin with?
Because it's useful to have a virtual MIDI cable.
DAW: CbB; Sonar Platinum, and others ...
|
AdamGrossmanLG
Max Output Level: -62 dBFS
- Total Posts : 1436
- Joined: 2014/07/13 03:40:34
- Status: offline
Re: If Sonar crashes and you are using LoopBe, it may leave the LoopBe driver running
2017/03/08 21:50:02
(permalink)
abacab
AdamGrossmanLG
Why do you use LoopBe to begin with?
Because it's useful to have a virtual MIDI cable.
for what use case? just wondering. :)
|
gustabo
Max Output Level: -49.5 dBFS
- Total Posts : 2591
- Joined: 2009/01/05 17:32:38
- Status: offline
Re: If Sonar crashes and you are using LoopBe, it may leave the LoopBe driver running
2017/03/08 23:24:20
(permalink)
abacab
brundlefly
abacab
I had to reboot to clear this up.
For future reference, I would guess that restarting SONAR and opening a project that uses the driver would reset it without having to reboot.
The driver starts every time I launch Sonar, as it is configured in Prefs > MIDI > Devices > 01. Internal MIDI. Have not even actually used a project with LoopBe recently.
I restarted Sonar several times, but LoopBe was hung in Windows. It did not even show in task manager, as this is a driver, not a task or process.
The only thing I didn't try was disabling/enabling LoopBe in device manager. Reboot was probably just as quick though, only takes about 60 secs here.
I leave mine running at all times, why would I not want that to be?
Cakewalk by Bandlab - Win10 Pro x64 - StudioCat Platinum Studio DAW - 32 GB Ram - MOTU UltraLite-mk3
M-Audio Keystation 88ES - Akai MPD26 (hot-rodded) - Alesis DM10 - a few guitars, a few amps
Novation Launch Control - Korg nanoKONTROL2 - PreSonus FaderPort - DAW Remote HD on iPad
Adam A7X - Behritone C50A
PreSonus Monitor Station v2 (controlling the mons)
https://www.facebook.com/groups/sonarusergroup/
|
abacab
Max Output Level: -30.5 dBFS
- Total Posts : 4464
- Joined: 2014/12/31 19:34:07
- Status: offline
Re: If Sonar crashes and you are using LoopBe, it may leave the LoopBe driver running
2017/03/08 23:49:52
(permalink)
gustabo
abacab
brundlefly
abacab
I had to reboot to clear this up.
For future reference, I would guess that restarting SONAR and opening a project that uses the driver would reset it without having to reboot.
The driver starts every time I launch Sonar, as it is configured in Prefs > MIDI > Devices > 01. Internal MIDI. Have not even actually used a project with LoopBe recently.
I restarted Sonar several times, but LoopBe was hung in Windows. It did not even show in task manager, as this is a driver, not a task or process.
The only thing I didn't try was disabling/enabling LoopBe in device manager. Reboot was probably just as quick though, only takes about 60 secs here.
I leave mine running at all times, why would I not want that to be?
I do too, but when I shut Sonar down, the LoopBe driver (loopbe30.sys) is normally inactive until I start Sonar or another audio app that uses it. The loopbe monitor gizmo (loough.exe) in the notification tray is always active, and that is not what I am referring to. The problem I am speaking of only occurs when Sonar exits abnormally. The LoopBe driver is left "hung" in an active state that prevents Windows power management from entering sleep mode.
DAW: CbB; Sonar Platinum, and others ...
|
abacab
Max Output Level: -30.5 dBFS
- Total Posts : 4464
- Joined: 2014/12/31 19:34:07
- Status: offline
Re: If Sonar crashes and you are using LoopBe, it may leave the LoopBe driver running
2017/03/08 23:53:13
(permalink)
AdamGrossmanLG
abacab
AdamGrossmanLG
Why do you use LoopBe to begin with?
Because it's useful to have a virtual MIDI cable.
for what use case? just wondering. :)
Application to application. One use case, Liquid Notes: http://www.re-compose.com/liquid-notes-music-software.html Just import your MIDI tracks into Liquid Notes and hit play. Liquid Notes routes the MIDI data back to your sequencer, using all software instruments of your original arrangement. When you have completed the editing process, simply record your music back to your sequencer.
DAW: CbB; Sonar Platinum, and others ...
|
Rob[at]Sound-Rehab
Max Output Level: -47 dBFS
- Total Posts : 2819
- Joined: 2011/02/03 04:31:35
- Location: Sound-Rehab, Austria
- Status: offline
Re: If Sonar crashes and you are using LoopBe, it may leave the LoopBe driver running
2017/03/09 11:15:17
(permalink)
abacab
AdamGrossmanLG
Why do you use LoopBe to begin with?
Because it's useful to have a virtual MIDI cable.
I'm using loopMIDI with zero issues (live and studio). very reliable. not sure if it does all you need it to do but may be worth to check ... https://www.tobias-erichsen.de/software/loopmidi.html
GOOD TUNES LAST FOREVER +++ Visit the Rehab +++ DAW: Platinum/X3e, win10 64 bit, i7-3930K (6x3.2GHz), Asus Sabertooth X79, 32 GB DDR3 1600MHz, ATI HD 5450, 120 GB SSD OCZ Agility3, 2x 1TB WD HDD SATA 600 Audio-Interface: 2x MOTU 1248 AVB, Focusrite OctoPre, (Roland Octa-Capture) Control-Surface: VS-700C VSTi: WAVES, NI K10u, FabFilter, IK, ... (too many really)
|
abacab
Max Output Level: -30.5 dBFS
- Total Posts : 4464
- Joined: 2014/12/31 19:34:07
- Status: offline
Re: If Sonar crashes and you are using LoopBe, it may leave the LoopBe driver running
2017/03/09 13:40:13
(permalink)
Rob[atSound-Rehab]
abacab
AdamGrossmanLG
Why do you use LoopBe to begin with?
Because it's useful to have a virtual MIDI cable.
I'm using loopMIDI with zero issues (live and studio). very reliable. not sure if it does all you need it to do but may be worth to check ...
https://www.tobias-erichsen.de/software/loopmidi.html
Thanks, but I have zero issues with LoopBe, (crash is not caused by LoopBe, by the way) and it works reliably. Not bashing this product, or Sonar. But I do wonder if Sonar could be better at releasing all resources when it crashes. Or maybe it does, and this is a Windows thing. Who knows ... Not looking for a fix, since this is easily resolved (reboot), and I actually have very few Sonar crashes. I just thought I should share this info about LoopBe remaining active following a Sonar crash, and the quirks regarding Windows sleep function. This could be very annoying if you want your PC to sleep. If you Google for "why won't my Windows sleep", you will get over 36 million results. Detecting the cause can be very difficult, as there are many possible reasons, so this is just one small drop in the pond (solved) ...
DAW: CbB; Sonar Platinum, and others ...
|
brundlefly
Max Output Level: 0 dBFS
- Total Posts : 14250
- Joined: 2007/09/14 14:57:59
- Location: Manitou Spgs, Colorado
- Status: offline
Re: If Sonar crashes and you are using LoopBe, it may leave the LoopBe driver running
2017/03/09 17:15:32
(permalink)
abacab
The driver starts every time I launch Sonar, as it is configured in Prefs > MIDI > Devices > 01. Internal MIDI.
I'm no O/S architecture genius, but my understanding has always been that drivers are loaded by the O/S at startup, ready for use by any app that needs them. And that would include drivers for virtual/emulated hardware. In the case of MIDI drivers, SONAR should only call the driver when it reads/writes the port, and that should only happen if the port is used in the project. Having " An audio stream is currently in use." as part of the status description suggests the port is actually in use, as opposed to just having the driver loaded by the O/S. And that makes me wonder if the crash is actually related to LoopBE. I had LoopBE1 installed for a long time on my old Win7 machine and never had any issues recovering from a SONAR crash. But I also never let that PC sleep because it had unrelated issues when waking up. I don't think I've reinstalled it since moving to a new machine with Win10.
SONAR Platinum x64, 2x MOTU 2408/PCIe-424 (24-bit, 48kHz) Win10, I7-6700K @ 4.0GHz, 24GB DDR4, 2TB HDD, 32GB SSD Cache, GeForce GTX 750Ti, 2x 24" 16:10 IPS Monitors
|
abacab
Max Output Level: -30.5 dBFS
- Total Posts : 4464
- Joined: 2014/12/31 19:34:07
- Status: offline
Re: If Sonar crashes and you are using LoopBe, it may leave the LoopBe driver running
2017/03/09 17:51:42
(permalink)
brundlefly
abacab
The driver starts every time I launch Sonar, as it is configured in Prefs > MIDI > Devices > 01. Internal MIDI.
I'm no O/S architecture genius, but my understanding has always been that drivers are loaded by the O/S at startup, ready for use by any app that needs them. And that would include drivers for virtual/emulated hardware. In the case of MIDI drivers, SONAR should only call the driver when it reads/writes the port, and that should only happen if the port is used in the project. Having "An audio stream is currently in use." as part of the status description suggests the port is actually in use, as opposed to just having the driver loaded by the O/S. And that makes me wonder if the crash is actually related to LoopBE.
I had LoopBE1 installed for a long time on my old Win7 machine and never had any issues recovering from a SONAR crash. But I also never let that PC sleep because it had unrelated issues when waking up. I don't think I've reinstalled it since moving to a new machine with Win10.
I agree that all Windows drivers are always present at boot time. What I am saying here is that Sonar grabs this LoopBE driver every time Sonar is started, just like every other MIDI device configured in Sonar MIDI prefs. This happens regardless of a LoopBE port being assigned to a track in a project. The in use status appears even at the Sonar start page with no project loaded. If I start Sonar and look at "powercfg -requests" I will see " An audio stream is currently in use". This is normal. If I exit Sonar normally, this status goes away. The crash is DEFINITELY NOT related to LoopBe. I was testing a SONiVOX plugin crash for another forum member in another thread. That crash is reproducible every time I access a certain feature with my mouse in an AUDIO FX. I can confirm that the LoopBE " An audio stream is currently in use." status is an artifact remaining after the Sonar crash and exit. The LoopBe port is present in Sonar, but not is use. The only MIDI in used with the tested VST was my keyboard controller. The VST itself was used in the FX bin of an audio track. Maybe my Windows O/S architectural terminology is incorrect, but what I am trying to describe is real, and reproducible. This is just info to be aware of in the event of a Sonar crash. The resources used by Sonar may not be fully released. That's all it is. It could be Sonar, or LoopBE, or Windows, but it's probably not worth pursuing a fix.
DAW: CbB; Sonar Platinum, and others ...
|
brundlefly
Max Output Level: 0 dBFS
- Total Posts : 14250
- Joined: 2007/09/14 14:57:59
- Location: Manitou Spgs, Colorado
- Status: offline
Re: If Sonar crashes and you are using LoopBe, it may leave the LoopBe driver running
2017/03/09 19:59:15
(permalink)
abacab
brundlefly
abacab
The driver starts every time I launch Sonar, as it is configured in Prefs > MIDI > Devices > 01. Internal MIDI.
I'm no O/S architecture genius, but my understanding has always been that drivers are loaded by the O/S at startup, ready for use by any app that needs them. And that would include drivers for virtual/emulated hardware. In the case of MIDI drivers, SONAR should only call the driver when it reads/writes the port, and that should only happen if the port is used in the project. Having "An audio stream is currently in use." as part of the status description suggests the port is actually in use, as opposed to just having the driver loaded by the O/S. And that makes me wonder if the crash is actually related to LoopBE.
I had LoopBE1 installed for a long time on my old Win7 machine and never had any issues recovering from a SONAR crash. But I also never let that PC sleep because it had unrelated issues when waking up. I don't think I've reinstalled it since moving to a new machine with Win10.
I agree that all Windows drivers are always present at boot time. What I am saying here is that Sonar grabs this LoopBE driver every time Sonar is started, just like every other MIDI device configured in Sonar MIDI prefs. This happens regardless of a LoopBE port being assigned to a track in a project. The in use status appears even at the Sonar start page with no project loaded. If I start Sonar and look at "powercfg -requests" I will see "An audio stream is currently in use". This is normal. If I exit Sonar normally, this status goes away.
The crash is DEFINITELY NOT related to LoopBe. I was testing a SONiVOX plugin crash for another forum member in another thread. That crash is reproducible every time I access a certain feature with my mouse in an AUDIO FX. I can confirm that the LoopBE "An audio stream is currently in use." status is an artifact remaining after the Sonar crash and exit.
The LoopBe port is present in Sonar, but not is use. The only MIDI in used with the tested VST was my keyboard controller. The VST itself was used in the FX bin of an audio track.
Maybe my Windows O/S architectural terminology is incorrect, but what I am trying to describe is real, and reproducible. This is just info to be aware of in the event of a Sonar crash. The resources used by Sonar may not be fully released. That's all it is. It could be Sonar, or LoopBE, or Windows, but it's probably not worth pursuing a fix.
Yeah, I hear where you're coming from. I just couldn't see why SONAR would be touching a driver for a port that isn't used in a project. I would have thought that having a driver checked in MIDI devices is just to have SONAR make it avialable for selection in track I/O pick lists. I suppose it's possible that some state initialization occurs regardless of whether a port is used or not, but I would not have expected that.
SONAR Platinum x64, 2x MOTU 2408/PCIe-424 (24-bit, 48kHz) Win10, I7-6700K @ 4.0GHz, 24GB DDR4, 2TB HDD, 32GB SSD Cache, GeForce GTX 750Ti, 2x 24" 16:10 IPS Monitors
|
arachnaut
Max Output Level: -67 dBFS
- Total Posts : 1168
- Joined: 2007/05/05 17:24:33
- Location: Sunnyvale, CA USA
- Status: offline
Re: If Sonar crashes and you are using LoopBe, it may leave the LoopBe driver running
2017/03/09 21:15:56
(permalink)
I use Loopbe30 all the time to send MIDI data from external programs (like Reaktor, Fractal Tune Smithy, etc.) to Sonar.
I've used it in Windows since the XP days.
I don't ever recall any type of crash where the system was hung in the LoopeBE driver.
I have 2 MIDI ports enabled and do not use the shortcut detection monitor.
- Jim Hurley - SONAR Platinum - x64 - Windows 10 Pro ASUS P8P67 PRO Rev 3.0; Core i7-2600K@4.4GHz; 16 GB G.SKILL Ripjaws X; GeForce GT 740; Saffire Pro14 MixControl 3.7; Axiom 61 64-Bit audio, SR: 48kHz, ASIO 256 samples latency, Rec/Play I/O Buffers 512k, Total Round Trip Latency 13 ms, Pow-r 3 dither
|
abacab
Max Output Level: -30.5 dBFS
- Total Posts : 4464
- Joined: 2014/12/31 19:34:07
- Status: offline
Re: If Sonar crashes and you are using LoopBe, it may leave the LoopBe driver running
2017/03/09 21:57:58
(permalink)
brundlefly
Yeah, I hear where you're coming from. I just couldn't see why SONAR would be touching a driver for a port that isn't used in a project. I would have thought that having a driver checked in MIDI devices is just to have SONAR make it avialable for selection in track I/O pick lists. I suppose it's possible that some state initialization occurs regardless of whether a port is used or not, but I would not have expected that.
Have you ever run Sonar with a MIDI driver that was not multi-client? Try to start another application at the same time that needs to access that driver.
DAW: CbB; Sonar Platinum, and others ...
|
abacab
Max Output Level: -30.5 dBFS
- Total Posts : 4464
- Joined: 2014/12/31 19:34:07
- Status: offline
Re: If Sonar crashes and you are using LoopBe, it may leave the LoopBe driver running
2017/03/09 22:18:41
(permalink)
arachnaut
I use Loopbe30 all the time to send MIDI data from external programs (like Reaktor, Fractal Tune Smithy, etc.) to Sonar.
I've used it in Windows since the XP days.
I don't ever recall any type of crash where the system was hung in the LoopeBE driver.
I have 2 MIDI ports enabled and do not use the shortcut detection monitor.
I got LoopBe30 with Liquid Notes and that setup for use with Sonar. It think it is pretty nifty. I have also tried using it to patch a MIDI port between various applications, and it always seems stable and reliable. I think LoopBe30 is working as designed, and is throwing a flag at Windows power management that basically says "hey there, don't go to sleep while I have an audio stream in use!". Normally this only appears when the driver is being used by Sonar. This flag should be removed when Sonar exits. as it does when Sonar exits gracefully. Just for grins, I tried this in Reaper. In my PC, Reaper has LoopBe assigned in MIDI device prefs as "01. Internal MIDI Enabled+Control". When I start Reaper, Windows does not get the active stream flag until I assign the MIDI input to an actual track in a project. So, it would appear that Sonar reserves the driver exclusively when it starts, whereas Reaper waits until you actually use it. I crashed Reaper intentionally and the LoopBe active stream status remained in Windows powercfg afterwards. My thoughts are that this may be a Microsoft bug. How is that possible? 
DAW: CbB; Sonar Platinum, and others ...
|
brundlefly
Max Output Level: 0 dBFS
- Total Posts : 14250
- Joined: 2007/09/14 14:57:59
- Location: Manitou Spgs, Colorado
- Status: offline
Re: If Sonar crashes and you are using LoopBe, it may leave the LoopBe driver running
2017/03/09 22:22:47
(permalink)
abacab
brundlefly
Yeah, I hear where you're coming from. I just couldn't see why SONAR would be touching a driver for a port that isn't used in a project. I would have thought that having a driver checked in MIDI devices is just to have SONAR make it avialable for selection in track I/O pick lists. I suppose it's possible that some state initialization occurs regardless of whether a port is used or not, but I would not have expected that.
Have you ever run Sonar with a MIDI driver that was not multi-client? Try to start another application at the same time that needs to access that driver.
I don't know; my MOTU is multiclient. Is LoopBE not? I have used it in the past to send MIDI from one release of SONAR to another without a problem. And I have used it with Notion as well. But neither client would have been trying to use the same port at the same time. One would always be using the OUT, and one the IN.
SONAR Platinum x64, 2x MOTU 2408/PCIe-424 (24-bit, 48kHz) Win10, I7-6700K @ 4.0GHz, 24GB DDR4, 2TB HDD, 32GB SSD Cache, GeForce GTX 750Ti, 2x 24" 16:10 IPS Monitors
|
AdamGrossmanLG
Max Output Level: -62 dBFS
- Total Posts : 1436
- Joined: 2014/07/13 03:40:34
- Status: offline
Re: If Sonar crashes and you are using LoopBe, it may leave the LoopBe driver running
2017/03/09 22:46:00
(permalink)
arachnaut
I use Loopbe30 all the time to send MIDI data from external programs (like Reaktor, Fractal Tune Smithy, etc.) to Sonar.
I've used it in Windows since the XP days.
I don't ever recall any type of crash where the system was hung in the LoopeBE driver.
I have 2 MIDI ports enabled and do not use the shortcut detection monitor.
wait, but cant you just insert Reaktor as a VST synth? Why do you need LoopBe for it?
|
gustabo
Max Output Level: -49.5 dBFS
- Total Posts : 2591
- Joined: 2009/01/05 17:32:38
- Status: offline
Re: If Sonar crashes and you are using LoopBe, it may leave the LoopBe driver running
2017/03/09 23:55:02
(permalink)
To connect a non-vst standalone midi capable app with a daw host.
Cakewalk by Bandlab - Win10 Pro x64 - StudioCat Platinum Studio DAW - 32 GB Ram - MOTU UltraLite-mk3
M-Audio Keystation 88ES - Akai MPD26 (hot-rodded) - Alesis DM10 - a few guitars, a few amps
Novation Launch Control - Korg nanoKONTROL2 - PreSonus FaderPort - DAW Remote HD on iPad
Adam A7X - Behritone C50A
PreSonus Monitor Station v2 (controlling the mons)
https://www.facebook.com/groups/sonarusergroup/
|
abacab
Max Output Level: -30.5 dBFS
- Total Posts : 4464
- Joined: 2014/12/31 19:34:07
- Status: offline
Re: If Sonar crashes and you are using LoopBe, it may leave the LoopBe driver running
2017/03/10 00:10:34
(permalink)
gustabo
To connect a non-vst standalone midi capable app with a daw host.
+1 Yup!
DAW: CbB; Sonar Platinum, and others ...
|
gustabo
Max Output Level: -49.5 dBFS
- Total Posts : 2591
- Joined: 2009/01/05 17:32:38
- Status: offline
Re: If Sonar crashes and you are using LoopBe, it may leave the LoopBe driver running
2017/03/10 00:37:50
(permalink)
abacab
gustabo
To connect a non-vst standalone midi capable app with a daw host.
+1
Yup!
I use it to connect a standalone app that remaps midi channels and note assignments of my e-drums to Sonar.
Cakewalk by Bandlab - Win10 Pro x64 - StudioCat Platinum Studio DAW - 32 GB Ram - MOTU UltraLite-mk3
M-Audio Keystation 88ES - Akai MPD26 (hot-rodded) - Alesis DM10 - a few guitars, a few amps
Novation Launch Control - Korg nanoKONTROL2 - PreSonus FaderPort - DAW Remote HD on iPad
Adam A7X - Behritone C50A
PreSonus Monitor Station v2 (controlling the mons)
https://www.facebook.com/groups/sonarusergroup/
|
arachnaut
Max Output Level: -67 dBFS
- Total Posts : 1168
- Joined: 2007/05/05 17:24:33
- Location: Sunnyvale, CA USA
- Status: offline
Re: If Sonar crashes and you are using LoopBe, it may leave the LoopBe driver running
2017/03/10 00:41:53
(permalink)
AdamGrossmanLG
arachnaut
I use Loopbe30 all the time to send MIDI data from external programs (like Reaktor, Fractal Tune Smithy, etc.) to Sonar.
I've used it in Windows since the XP days.
I don't ever recall any type of crash where the system was hung in the LoopeBE driver.
I have 2 MIDI ports enabled and do not use the shortcut detection monitor.
wait, but cant you just insert Reaktor as a VST synth? Why do you need LoopBe for it?
Yes, that is true now, but previous versions of Sonar were not very reliable with multiple channels of MIDI. So it is a habit I got into.
- Jim Hurley - SONAR Platinum - x64 - Windows 10 Pro ASUS P8P67 PRO Rev 3.0; Core i7-2600K@4.4GHz; 16 GB G.SKILL Ripjaws X; GeForce GT 740; Saffire Pro14 MixControl 3.7; Axiom 61 64-Bit audio, SR: 48kHz, ASIO 256 samples latency, Rec/Play I/O Buffers 512k, Total Round Trip Latency 13 ms, Pow-r 3 dither
|
abacab
Max Output Level: -30.5 dBFS
- Total Posts : 4464
- Joined: 2014/12/31 19:34:07
- Status: offline
Re: If Sonar crashes and you are using LoopBe, it may leave the LoopBe driver running
2017/03/10 20:05:35
(permalink)
Update: I did some more testing and it does appear that LoopBe30 is multi-client. I can run a standalone application (Liquid Notes) that uses a single port routed to a VSTi in my DAW, as well as using that same port to drive a standalone soft synth at the same time. I'm not sure that I need to do this, but it proves that I can.  Anyway, the point of whether the driver is actually active in Windows after a DAW crash is not clear to me at this point. The fact that this is a multi-client driver makes it hard to determine if it is really stuck. The driver is still available and works when called on by an application, even after it appears to have a "stuck" stream in Windows powerfcg. Bottom line: So maybe this is just a Windows powercfg issue. Anyway, once powercfg shows LoopBe with an active stream, it can prevent Windows 10 from sleeping with an idle timer. The only solution I have found for that so far is to reboot. Sonar rarely crashes for me, so this is not a huge issue. But wondering why my PC was not sleeping intermittently was driving me nuts! I will continue to use LoopBe and Sonar and enjoy both Anyway, here is the free version: http://www.nerds.de/en/loopbe1.htmland the 30 port version http://www.nerds.de/en/loopbe30.html LoopBe1 is a native Windows™ WDM kernel mode driver, so expect the lowest possible latency. Programs do not need to link with special libraries, so LoopBe1 works with every MIDI or DirectMusic™-capable application.
DAW: CbB; Sonar Platinum, and others ...
|
tlw
Max Output Level: -49.5 dBFS
- Total Posts : 2567
- Joined: 2008/10/11 22:06:32
- Location: West Midlands, UK
- Status: offline
Re: If Sonar crashes and you are using LoopBe, it may leave the LoopBe driver running
2017/03/10 21:08:49
(permalink)
I'm guessing, but what I think might be happening is this.
Loop.be gets the 'in use' signal from the DAW. The driver then does as it should and notifies Windows that it's in use. Amongst other things that should prevent Windows paging the driver out to the swap file or allowing the driver/device to go to sleep.
Loop.be will then notify Windows it's no longer in use when and if it receives a "thanks, done with you now” signal from the software it's providing a service for. If that software, Sonar in this instance, crashes then it doesn't send the 'release' signal to the driver which in turn doesn't tell Windows it's no longer in use. The crashing application might even be supposed to send that signal on crash, but once into a crash situation all bets are off as to what happens.
I've used Loop.be for years and never had a problem with it causing crashes, but I've seen Sonar crashes leave it active. I've also seen both Sonar and Live not release the audio driver either if they crash. I've also seen games and Photoshop crash and leave the video driver locked to the application's resolution or even a frozen screen and/or the audio driver emitting a constant (loud) noise and Windows unable to return to the usual state of affairs without a reboot.
I guess the motto is that if something crashes on a Windows system then at least log off and back on again and if that doesn't return things to normal then it's time for that old faithfull - reboot Windows.
Sonar Platinum 64bit, Windows 8.1 Pro 64bit, I7 3770K Ivybridge, 16GB Ram, Gigabyte Z77-D3H m/board, ATI 7750 graphics+ 1GB RAM, 2xIntel 520 series 220GB SSDs, 1 TB Samsung F3 + 1 TB WD HDDs, Seasonic fanless 460W psu, RME Fireface UFX, Focusrite Octopre. Assorted real synths, guitars, mandolins, diatonic accordions, percussion, fx and other stuff.
|
abacab
Max Output Level: -30.5 dBFS
- Total Posts : 4464
- Joined: 2014/12/31 19:34:07
- Status: offline
Re: If Sonar crashes and you are using LoopBe, it may leave the LoopBe driver running
2017/03/11 00:24:42
(permalink)
tlw
I'm guessing, but what I think might be happening is this.
Loop.be gets the 'in use' signal from the DAW. The driver then does as it should and notifies Windows that it's in use. Amongst other things that should prevent Windows paging the driver out to the swap file or allowing the driver/device to go to sleep.
Loop.be will then notify Windows it's no longer in use when and if it receives a "thanks, done with you now” signal from the software it's providing a service for. If that software, Sonar in this instance, crashes then it doesn't send the 'release' signal to the driver which in turn doesn't tell Windows it's no longer in use. The crashing application might even be supposed to send that signal on crash, but once into a crash situation all bets are off as to what happens.
I've used Loop.be for years and never had a problem with it causing crashes, but I've seen Sonar crashes leave it active. I've also seen both Sonar and Live not release the audio driver either if they crash. I've also seen games and Photoshop crash and leave the video driver locked to the application's resolution or even a frozen screen and/or the audio driver emitting a constant (loud) noise and Windows unable to return to the usual state of affairs without a reboot.
I guess the motto is that if something crashes on a Windows system then at least log off and back on again and if that doesn't return things to normal then it's time for that old faithfull - reboot Windows.
I believe that is a very lucid synopsis of the situation! At least we no longer live in the bad old days before the Windows NT kernel, where an app crash usually brought the whole Windows system down! It's mostly up to the drivers now to provide the blue screen entertainment these days. Progress ...
DAW: CbB; Sonar Platinum, and others ...
|