Anderton
Well in that case, I'm stumped. Any problems I've encountered in the past were solved by what I mentioned.

Me too! However, I just unchecked Project/MIDI/Other Options/Zero Controllers When Play Stops and ../Send MIDI Sync/Transmit MIDI Start/Continue/Stop/Clock. I don't have any external MIDI devices connected. I'm hopeful this might be a workaround since there have been no glitches to about 10 minutes while starting and stopping playback numerous times. I'll keep you all posted on what happens over a little more time time and also when I try recording some soft synth stuff.

Rasure
You could also check individual USB devices in "Device Manager" to make sure "Allow the computer to turn off this device to save power" is NOT enabled :-)

^^^ This too!!!

If things work after a reboot, it seems some system or SONAR parameter is being restored to a default that works.
 
Just out of curiosity...
 

• What happens if you use an interface's 5-pin DIN MIDI ports instead of USB?
• Any chance you're using a USB 2 interface with a USB 3 port?
• What MIDI playback buffer setting are you using? I don't think that's the problem, but you never know.

soens

Anderton

AdamGrossmanLG
probably just poor coding as usual with Cakewalk.

 
Actually it's almost certain that it isn't, given that no one else is chiming in to say they've experienced this problem.

Not everyone reads every post. I've had USB issues like this since... ever. We'll see if my issues are fixed by these setting changes.

I know not everyone reads every post, but I do monitor posts. Although there are quite a few posts about various issues with USB, particularly audio, I don't recall seeing any that were solved specifically by reboots (of course, I don't read every post either but I do try to keep on top of problems). Most fixes have involved techniques that have already been mentioned, along with quirks like certain interfaces being "wedded" to certain ports so if you unplug them and plug into a different port, the driver doesn't register (and this adds another port to the ongoing list Windows keeps).
 
There have also been threads that have gone on forever where people have offered a zillion different suggestions, only to find out that something was going through an unpowered hub that had multiple peripherals plugged into it, and plugging directly into the motherboard's USB port or a dedicated USB card solved the problem.
 
Because I haven't seen this issue appearing with regularity, if it was indeed "poor coding" then it should be fairly prevalent because the problem would relate to SONAR, as opposed to an interaction within the system. It really helps to isolate the issue as much as possible. A lot of people assume that if SONAR acts up, it's a SONAR problem so they re-install SONAR to no avail...or if Windows acts up, they re-install Windows and it doesn't make a difference because the problem may actually be a piece of hardware or driver.
 
If the problem is solved by exiting and opening SONAR, then that might point to some whacked SONAR preference. If the problem is solved by rebooting the computer, then it sounds like something computer-related. But I can't say for sure because I never needed to come up with a solution past "turn on the peripherals before turning on the computer." BUT that's not universally applicable advice, either 

Thanks for the info (and the sig).

Anderton

soens

Anderton

AdamGrossmanLG
probably just poor coding as usual with Cakewalk.

 
Actually it's almost certain that it isn't, given that no one else is chiming in to say they've experienced this problem.

Not everyone reads every post. I've had USB issues like this since... ever. We'll see if my issues are fixed by these setting changes.

I know not everyone reads every post, but I do monitor posts. Although there are quite a few posts about various issues with USB, particularly audio, I don't recall seeing any that were solved specifically by reboots (of course, I don't read every post either but I do try to keep on top of problems). Most fixes have involved techniques that have already been mentioned, along with quirks like certain interfaces being "wedded" to certain ports so if you unplug them and plug into a different port, the driver doesn't register (and this adds another port to the ongoing list Windows keeps).
 
There have also been threads that have gone on forever where people have offered a zillion different suggestions, only to find out that something was going through an unpowered hub that had multiple peripherals plugged into it, and plugging directly into the motherboard's USB port or a dedicated USB card solved the problem.
 
Because I haven't seen this issue appearing with regularity, if it was indeed "poor coding" then it should be fairly prevalent because the problem would relate to SONAR, as opposed to an interaction within the system. It really helps to isolate the issue as much as possible. A lot of people assume that if SONAR acts up, it's a SONAR problem so they re-install SONAR to no avail...or if Windows acts up, they re-install Windows and it doesn't make a difference because the problem may actually be a piece of hardware or driver.
 
If the problem is solved by exiting and opening SONAR, then that might point to some whacked SONAR preference. If the problem is solved by rebooting the computer, then it sounds like something computer-related. But I can't say for sure because I never needed to come up with a solution past "turn on the peripherals before turning on the computer." BUT that's not universally applicable advice, either 

Well, then can you explain how when the MIDI controller is not working in Sonar, it works fine in standalone VST applications (in the same moment)?   Here is what I have done:
 
-when MIDI controller stops working in Sonar, I keep Sonar open and open a VST app and they keyboard works.
-I then close Sonar, keyboard still works in VST app
-I then close the VST app, re-open Sonar, still doesn't work.
-I then reboot and then it SOMETIMES works again in Sonar.
 
The only problem app is Sonar here.

AdamGrossmanLG
 
Well, then can you explain how when the MIDI controller is not working in Sonar, it works fine in standalone VST applications (in the same moment)?   Here is what I have done:
 
-when MIDI controller stops working in Sonar, I keep Sonar open and open a VST app and they keyboard works.
-I then close Sonar, keyboard still works in VST app
-I then close the VST app, re-open Sonar, still doesn't work.
-I then reboot and then it SOMETIMES works again in Sonar.

Can you reproduce this using a different MIDI controller, or is it only happening to one particular device?

AdamGrossmanLG

Anderton
If the problem is solved by exiting and opening SONAR, then that might point to some whacked SONAR preference. If the problem is solved by rebooting the computer, then it sounds like something computer-related. But I can't say for sure because I never needed to come up with a solution past "turn on the peripherals before turning on the computer." BUT that's not universally applicable advice, either 

Well, then can you explain how when the MIDI controller is not working in Sonar, it works fine in standalone VST applications (in the same moment)? 

In SONAR, MIDI is part of a system and has a different set of Preferences and constraints than a stand-alone VST. See TStorm's post above. He seems to confirm my thinking "then it might point to some whacked SONAR preference."
 
Also, are you sure that SONAR is not actually seeing MIDI as opposed to not producing sound? For example, only one device at a time can access ASIO. If you have a stand-alone VST that wants ASIO, and SONAR set to ASIO, only one of them will produce audio.
 

Base 57
Not to be argumentative, but I can run Dim Pro and Rap session (ASIO) standalone at the same time as SONAR through the same output pair of my Orion 32+. So not being able to run 2 ASIO apps at the same time is not universal. You can't however run 2 different ASIO interfaces at the same time AFAIK.

Good to know...maybe I need to use an ASIO interface with more outputs, and assign the devices to separate ASIO outs.

Like RME, Antelope drivers do allow two Orions to be connected to the same computer for 64 analog I/0. However I don't think we would be able to hook your RME and my Antelope to the same computer and use them at the same time with ASIO.
 
And yeah, the rat's nest (I call it the snake pit) is ridiculous. But I don't have to do much re-patching and I can track through my analog board so latency is irrelevant.
 
Sorry to get off topic. We need to get Adam's midi working right. Did you try the TTSSeq thing?

So I just built a brand new PC and bought a brand new Impact Nektar - COMPLETELY different interface from my AKAI MPK before....

STILL SAME ISSUE!   I have to reboot now in order to get it to work inside Sonar... yet it works in standalone softsynths.
 
Hmmm.. if it works in standalone softsynths, that eliminates OS and hardware....  what's left... SONAR!   What a joke.

If you are talking about removing the hidden devices here:  http://www.harmonycentral.com/articles/solving-the-windows-midi-port-problem
 
well I did this already on both machines.   

AdamGrossmanLG
So I just built a brand new PC and bought a brand new Impact Nektar - COMPLETELY different interface from my AKAI MPK before....

STILL SAME ISSUE!   I have to reboot now in order to get it to work inside Sonar... yet it works in standalone softsynths.
 
Hmmm.. if it works in standalone softsynths, that eliminates OS and hardware....  what's left... SONAR!   What a joke.

AdamGrossmanLG
Sonar's underbelly still runs on code from the 90's so I'm not surprised.

 
Since this follows you from machine to machine and hardware device to device, there has to be something that is a constant in the formula for the issue to manifest. We can probably get to the bottom of this, but we need to rule possible contributors out logically. Without doing this we couldn't even begin to apply a code side fix.
 
1) You mention that you built your PC. Is there any add-on USB/Peripheral/Bluetooth Adapter devices that you have always used? It could be the most obscure inconsequential part.
2) Besides SONAR, has there been any synth or other software application always installed? Again, it could be the most innocuous utility, we just need to know the entire picture.
3) Are you migrating settings into SONAR or have backed up setup files you go to?
4) Are you  using your own templates?
5) What version(s) of Windows have you been using?
6) Other setup procedures you perform on new systems?
 
Have you tried toggling the settings TStroms mentions above? I read through the entire thread and you don't mention it. I'd recommend that they both be on.
Edit > Preferences > Project > Midi
'Zero Controllers When Play Stops'
'Transmit MIDI Start/Continue/Stop/Clock'


 

Actually - I get this also - and am looking for control panel - power options... but I dont see any of the advanced menu items shown here in the screenshot..?  

AdamGrossmanLG
I only have 1 device for my Impact LX49+ so nothing for me to do here, oh and I am able to load up any standalone softsynth and it plays using my keyboard just fine.  Just not Sonar (yet the problem can't be Sonar, Sonar simply is never broken).

I believe your time would be spent more productively trying out Seth's suggestions (and answering his questions), as well as testing with 5-pin DIN plugs, than mischaracterizing what those trying to help you are saying.
 
By your logic, if you're the only one experiencing this particular problem, then the problem must be you.