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.

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.

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.

Why do you use LoopBe to begin with?

AdamGrossmanLG
Why do you use LoopBe to begin with?

Because it's useful to have a virtual MIDI cable.

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. :)

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?
 

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.

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.

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