Did you follow the instructions on MIDI Port Limits to the letter? It's not just enough to show hidden controllers, you HAVE to run the .bat file first.

Lots of great info in this thread.
 
When I have ran across these types of issues with USB DVD drives and midi gear it was due to the midi count limit, power saver settings or a flaky USB cable and hub. While having a rash of USB issues, I'm thinking the cable was flaky (like a scratchy mic cable) and would cause the gear to go offline in the app I was using but not show as unplugged and yet another instance would work ok for a while. I replaced the cable and hub and all the issues dissolved.

This problem sounds very strange...
 
If I start Sonar with my controllers disconnected, I usually get a pop-up dialogue about 20-30 secs after I reconnect my controller:
 
"The above audio/MIDI device was connected to your system. Do you want Sonar to add this device now?  Yes/No"
 
No Sonar restarts, no reboots, etc required.  Plug and play!
 
I have several controllers and they all seem to function this way.  Never had to reboot, but the most I ever had to do was restart the DAW or audio application after turning on a controller.
 
I wonder if you are doing something that prevents Sonar from showing this pop-up device found dialogue?  Like is it popping up on a second monitor somewhere that you have defined that is not visible, or popping under a 32-bit plugin UI?

Anderton
Did you follow the instructions on MIDI Port Limits to the letter? It's not just enough to show hidden controllers, you HAVE to run the .bat file first.

Anderton
Did you follow the instructions on MIDI Port Limits to the letter? It's not just enough to show hidden controllers, you HAVE to run the .bat file first.

Anderton
Did you follow the instructions on MIDI Port Limits to the letter? It's not just enough to show hidden controllers, you HAVE to run the .bat file first.

 
yes I did. The bat file opens the device manager.
Either way, why would Sonar be the only app that won't accept MIDI input?

I have Reason demo version on my computer too, I can play in that.  Just not Sonar.  

abacab
This problem sounds very strange...
 
If I start Sonar with my controllers disconnected, I usually get a pop-up dialogue about 20-30 secs after I reconnect my controller:
 
"The above audio/MIDI device was connected to your system. Do you want Sonar to add this device now?  Yes/No"
 
No Sonar restarts, no reboots, etc required.  Plug and play!
 
I have several controllers and they all seem to function this way.  Never had to reboot, but the most I ever had to do was restart the DAW or audio application after turning on a controller.
 
I wonder if you are doing something that prevents Sonar from showing this pop-up device found dialogue?  Like is it popping up on a second monitor somewhere that you have defined that is not visible, or popping under a 32-bit plugin UI?

funny enough, if I power cycle my MIDI controller, I get this dialog box too!  The MIDI port is selected on the track, but when I hit the keys, I get no incoming MIDI data.  
Sonar is smart enough to detect the presence of the keyboard, but not smart enough to accept the data.  This tells me it might be listening on the wrong port.  I would suggest Cakewalk check into the code for what port to listen to.  I have it on MIDI Omni by the way just as a side note.
 
The only remedy when this happens is to reboot, or close Sonar, open Device Manager, delete the MIDI controller and scan for hardware changes, then re-open Sonar.  
 
And again, when this issue does occur in Cakewalk - i can open Reason or any other standalone synth and the MIDI controller works just fine.  This is isolated to Sonar ONLY.   

Please forgive me if I missed where you have already answered this, but have you tried deleting the TTSSeq.ini file?

AdamGrossmanLG
 

Anderton
Did you follow the instructions on MIDI Port Limits to the letter? It's not just enough to show hidden controllers, you HAVE to run the .bat file first.

Anderton
Did you follow the instructions on MIDI Port Limits to the letter? It's not just enough to show hidden controllers, you HAVE to run the .bat file first.

yes I did. The bat file opens the device manager.

 
You also have to specify the showing of hidden devices after running the bat file. 
 

Either way, why would Sonar be the only app that won't accept MIDI input?

 
Maybe it's aware of more MIDI devices than other apps and therefore ties up those ports...I don't know what's weird about your system.
 
All I know for sure is I've used dozens of MIDI controllers over the years, probably close to 50, and SONAR has recognized every single one unless there was an issue with the MIDI port limit or a driver written so that the controller had to be used with a specific port. In the former case, I deleted the ghosted MIDI devices. With the latter, if I didn't remember which MIDI port I had used originally, I had to de-install and re-install the driver.
 

thedukewestern
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..?  

Once you go into Control Panel | Power Options you should see a few power options available. Out to the right of the names click on "Change Plan Settings" for whichever one is selected. Then in the next dialog box near the bottom should be "Change Advanced Power Settings". That will then show the various devices and you can then select "Disabled" for the USB settings.


The other setting is in the Device Manager under the USB controllers. Right click on the various hubs and select Properties, then go to the tab for Power Management and you will see a check box for "Allow Computer To Turn Off The Device To Save Power". Uncheck it. There may be several hubs listed so you will want to look at them all.

Anderton

AdamGrossmanLG
 

Anderton
Did you follow the instructions on MIDI Port Limits to the letter? It's not just enough to show hidden controllers, you HAVE to run the .bat file first.

Anderton
Did you follow the instructions on MIDI Port Limits to the letter? It's not just enough to show hidden controllers, you HAVE to run the .bat file first.

yes I did. The bat file opens the device manager.

 
You also have to specify the showing of hidden devices after running the bat file. 
 

Either way, why would Sonar be the only app that won't accept MIDI input?

 
Maybe it's aware of more MIDI devices than other apps and therefore ties up those ports...I don't know what's weird about your system.
 
All I know for sure is I've used dozens of MIDI controllers over the years, probably close to 50, and SONAR has recognized every single one unless there was an issue with the MIDI port limit or a driver written so that the controller had to be used with a specific port. In the former case, I deleted the ghosted MIDI devices. With the latter, if I didn't remember which MIDI port I had used originally, I had to de-install and re-install the driver.
 

Wow, I just got a flashback of when Cakewalk shipped some versions with a midi breakout for the old gameport. I think I may still have it around somewhere.

AdamGrossmanLG

abacab
This problem sounds very strange...
 
If I start Sonar with my controllers disconnected, I usually get a pop-up dialogue about 20-30 secs after I reconnect my controller:
 
"The above audio/MIDI device was connected to your system. Do you want Sonar to add this device now?  Yes/No"
 
No Sonar restarts, no reboots, etc required.  Plug and play!
 
I have several controllers and they all seem to function this way.  Never had to reboot, but the most I ever had to do was restart the DAW or audio application after turning on a controller.
 
I wonder if you are doing something that prevents Sonar from showing this pop-up device found dialogue?  Like is it popping up on a second monitor somewhere that you have defined that is not visible, or popping under a 32-bit plugin UI?

funny enough, if I power cycle my MIDI controller, I get this dialog box too!  The MIDI port is selected on the track, but when I hit the keys, I get no incoming MIDI data.  
Sonar is smart enough to detect the presence of the keyboard, but not smart enough to accept the data.  This tells me it might be listening on the wrong port.  I would suggest Cakewalk check into the code for what port to listen to.  I have it on MIDI Omni by the way just as a side note.
 
The only remedy when this happens is to reboot, or close Sonar, open Device Manager, delete the MIDI controller and scan for hardware changes, then re-open Sonar.  
 
And again, when this issue does occur in Cakewalk - i can open Reason or any other standalone synth and the MIDI controller works just fine.  This is isolated to Sonar ONLY.   

Well, if I just rolled over to your place and handed my computer to you, you could plug your controller in and use Sonar just fine.
 
At that point, you would need to answer the question, "what is the difference between those two computers?".
 
You would see that the problem is isolated to your computer, for whatever reason, and not Sonar only.