[Solved] Not all keyboards recognized

OK. You all recommended I upgrade from X3 to Professional so I did.
 
So far, the only problem I have is Sonar Professional doesn't recognized one of my keyboards. When I open Sonar X3 it and all keyboards (all M-Audio) are recognized. I checked the the MIDI settings and all seems normal.
 
Suggestions?
 
John

slartabartfast
What are your keyboards?
Which one is not recognized?
How are the ones that show up in SONAR labeled?
How are the keyboards connected to the computer? 
Do the keyboards all show up as working in the Windows device manager?
Does changing the USB socket (if applicable) change which keyboard(s) are recognized?
Does power cycling the computer with the keyboards attached and powered on change anything?
 

+1 this question is like a needle in a hay stack.
what device, does it take drivers, plug and play ?
The more info you leave the faster your issue will be solved.

find "%APPDATA%\Cakewalk\Sonar Professional" and delete TTSSEQ.ini from there. Sonar will re-create it and you have to re-enable all midi devices. Some users have got it solved that way in recent Sonar versions.
Note that this file is different for X3 and Professional, that is why one can work and other not.

Thank you, azslow3. I will try that. 
 

 azslow3 Thank you! That did it!
 
John
 

Although it should not be this way, I find I have to restart my PC after plugging in a USB keyboard, or it will not be recognized. Just restarting Sonar does not work.
 
 

Well, it helped that the two Oxygen 49 keyboards were NOT identical. When I first hooked up the newer Oxy49 along with the Oxy49 Blue, only the newer one would work.
 
(Now that I think about it, perhaps the "delete TTSSEQ.ini" trick may have worked then, too.)
 
Anywho, I checked the M-Audio web site and it turned out that the Oxy49Blue did have a legacy driver. So though the older Oxy49Blue was also class compliant, I use it with its driver so the computer and Sonar saw them as the two different machines that they are. 
 
It's good to know that there could be issues so as not to buy two identical units. Perhaps, for instance, an Oxy49 and Oxy61 might work OK together. I dunno. 
 
John
 

I prefer simple explanations, when there is no prove they are "too simple". Not only inside Sonar, but also inside mentioned INI files, controllers are mentioned by port names. Identical names can trigger the problem. Different driver normally expose different name.
 
After previous discussion in another thread, I have tried to find a method to give different name to device. I have managed to show Sonar other name... But the change was reverted after reboot and I can not test myself that it works for the purpose (I do not have identical devices).
 

OK, just checked. It's each time I reboot Sonar Pro.
 
John
 
 

Here's my  TTSSEQ.ini file contents after Sonar re-creates it and the system is working:
 
[MIDI Input Devices]
0=nanoPAD 1 PAD
1=Oxygen 49
2=Oxygen 8 v2 MIDI In
3=Oxygen 49 MIDI In
MaxInPort=3
[MIDI Output Devices]
MaxOutPort=-1
[MIDI Echo Devices]
MaxEchoPort=-1

jjdubs
Here's my  TTSSEQ.ini file contents after Sonar re-creates it and the system is working:
 
[MIDI Input Devices]
0=nanoPAD 1 PAD
1=Oxygen 49
2=Oxygen 8 v2 MIDI In
3=Oxygen 49 MIDI In
MaxInPort=3
[MIDI Output Devices]
MaxOutPort=-1
[MIDI Echo Devices]
MaxEchoPort=-1

If your start Sonar with this file already in place, which keyboard are you missing, "Oxygen 49 MIDI In" or "Oxygen"?
 
You can try to edit the file, replacing "not detectable" device. F. e. "Oxygen 49" -> "Nxygen 49". Or remove it completely. If Sonar is able to redetect it, after locking the file you will be forced to re-enable only one keyboard or Sonar restart (instead of all). Not perfect, but less work...
Other options to try: enable "User friendly names" and/or change the order. With some luck Sonar can start to work without file reset...

OK, maybe not. I quit. :-/