mettelus
I noticed that there are two sets of software drivers to load and that two replies to you were deleted from the thread you linked, so I have a concern that those two sets may be conflicting as you have seen this behavior on all software tried so far.

 
yeah I'm worried about that too...  is what prompted me to try both keyboards without any drivers to see if that would have a positive effect.  unfortunately the result was the same :(  Windows could see the keyboards and all midi applications could not.
 

mettelus
uninstall their drivers and see if the keys work without any M-Audio drivers loaded

I think maybe I tried this, it's a good idea... I'll do again right now to be sure...  ok, well both devices do operate as class compliant devices, and I'm not sure you intended for me to try this or not, but I tried running Air49 with and without drivers while attempting to run the 25 in class compliant mode only... I even tried this scenario in reverse.  still no love :(
 

azslow3
Have you already tried uninstall M-Audio drivers for one/both keyboards?

 
absolutely, yes.  and in every combination each with and without.... that is: 
 
49drivers - 25drivers
49drivers - 25nodrivers
49nodrivers - 25drivers
49nodrivers - 25nodrivers
 
I've tried the above with and without a USB hub and even with changing cables, I even attempted using ferite beads on the cords LOL
 

azslow3
They both should be class-compliant, "multiple units" should be no problem for MS drivers (in that respect the replay from M-audio sounds strange).
 

 
yes, it seems they know about this and claim to have fixed it in the drivers, but...  doesn't look that way from my perspective.  I have other issues that simply remains a mystery that I've posted about and not gotten anything solved... it's beyond frustrating.
 

azslow3
If that still does not work and you are familiar with computers, you can try to check properties for the devices in the device manager to find similarities. At least for MS drivers, there must be something which clash.

Well I've checked their Location in General Properties and they do have unique addresses... but this is getting a bit tech for me, I'm just looking at numbers at this point trying to decipher things I don't completely understand.
 

gswitz
Probably asked and answered, but are you using usb2 or 3?

I've have USB2 and USB3...  I've tried both.
 

robert_e_bone
I believe you had mentioned that Windows see both controller, and it is within Sonar that you can only see one or the other.
 
What do music applications running stand-alone outside of Sonar see?  Can both controllers be enabled for use in on or more of these applications?  (Dim Pro, Rapture, etc).
 
Bob Bone

yes, exactly so.  and not just unique to Sonar but every program I have that uses/accesses midi controller. I've tried Ignite, Midi-Ox even my GuitarRig (lol) even tho it doesn't use keyboards for anything it can still see midi devices... seems to be everything.
 
big thanks to everyone trying to help!
 

Don't forget Cakewalk Support. They have often helped me or made good suggestions. They are available during the USA Business day.
 
http://www.cakewalk.com/Support
 
I don't know if this image might help, but it shows how I can plug in a midi device on my computer and then discover what driver it is using. I can also modify that driver by clicking the update driver button and pointing it at a different location.
 

robert_e_bone
1.  what controllers you have
2.  Are you possibly plugging into USB 3 ports?
3.  Are you using a hub?  If so, is it powered?
4.  When both controllers are plugged in, and can be seen in Windows, what does Sonar see in Preferences for midi devices?
5.  What model are controllers, and what version of drivers and firmware do you have for both?
6.  What version of Windows are you running, and what is the status on Windows Update maintenance?

 
sure, you bet Robert :)
 
1. - I have my ART Footpedal via M-Track Midi Ins Outs
    - Source Audio HotHand USB
    - Axiom Air49
    - Axiom 25 (1st Gen)
2. No, everything is connected by way of USB2,  I did try USB3 out of desperation lol
3. Yes, My M-Track is also a USB hub, and it is powered. I've also tried using an Un-powered USB Hub as well as no hubs.
4. Sonar (and all other midi programs) sees my M-Track Midi, my SourceAudio Midi, and ONE of my Axioms.  Which Axiom it is seems dependent on what Axiom was last plugged in.
5. Both Axioms are, and have been fully updated with the latest drivers and firmware both.
6. Windows7 64bit Pro...  Windows Updates are current and fully updated on a regular basis.
 
Gswitz, thank you, that's pretty much how I do things too.
 

azslow3
A bit out of main stream, but does not take much time...
 
In case you have some other computer in the near (preferably with Windows 8), can you connect both keyboards to it and see if the bug is still there?

I have an older spare computer with vista... I can probly set it up with midi-ox and both keyboards pretty easy.

no kidding... could Midi-Ox have caused this problem? maybe I should uninstall it and see...

Hi, Michelle.  Although you have already tried direct connections to USB ports, I would advise against using a hub.  Most manufactures (and users) state the same.  (Don't know about M-audio stuff, but I personally don't trust or use 'em.)
 
Kind regards,
 
Living Room Rocker

So the problem is somewhere within MIDI drivers of your Win7 64bit Pro (can be broader than M-Audio driver).
 
Do you by chance see something in the event log?
 
You can try this:
https://social.technet.microsoft.com/Forums/windows/en-US/c0988c75-da44-4295-b1f8-a6f384ce4b91/usb-midi-not-working-in-windows-7-pro-64bit?forum=w7itprohardware
 
In the part of removing midi1,midi2... and checking that UpperFilters is there.
 
I have "skipped" Win7, so I do not have big experience with that particular version. I hope someone else can give you helpful tips what to check as next.
 
Edit: In Win8 I can see under {4d36e96c-e325-11ce-bfc1-08002be10318} entries for all devices. I think Drivers/midi/wdmaud.drv Alias property should be unique.

I think I found something!  but I don't know what to do about it....  and frustrating that I looked at this a few times before and somehow it wasn't registering on me.
 
I told it to Update the driver, then Browse my computer for Driver Software then Let me pick...  I chose the driver and it installs the right one.  Correcting itself!  BUT  if I fix the Axiom25 the Air49 get's the driver too.  I go and fix the Air49 and it works, but adds it back to the Axiom25, nasty cycle ensues...  like I say, not sure what to do about it now.  Even tho I can see the issue more clearly. 
 

I tried disconnecting the one that was working right, installing the new driver on the other.  and the other way around.  And if I try to fix it with the keyboard unplugged it doesn't take and still shows both drivers...  this is the same thing it's been doing all along, I've only discovered a new way to view the problem, and an easier way to install the correct driver for one of them at a time... 

I have been manually checking that things uninstalled get deleted or not for so long it didn't occur to me to suggest you check to make sure.
 
YAY!!!!!!!!!!

Anderton
.. The tip I gave about ACT in the "tip of the week" pretty much gives the details of how to get controllers to work with ACT. ...

Craig - I searched the Tip of the Week sticky and couldn't find any mention of ACT.  I'm proposing a new rule; A reference to something you've written on a specific subject requires a direct a link to it.  :)

 
This is great news.  Let us know when everything is set up as you wish.
 

rfreeze

Anderton
.. The tip I gave about ACT in the "tip of the week" pretty much gives the details of how to get controllers to work with ACT. ...

Craig - I searched the Tip of the Week sticky and couldn't find any mention of ACT.  I'm proposing a new rule; A reference to something you've written on a specific subject requires a direct a link to it.  :)

You are soooooo right. It was in the Cakewalk blog. I've corrected the post in this thread to reflect reality 

Anderton

rfreeze

Anderton
.. The tip I gave about ACT in the "tip of the week" pretty much gives the details of how to get controllers to work with ACT. ...

Craig - I searched the Tip of the Week sticky and couldn't find any mention of ACT.  I'm proposing a new rule; A reference to something you've written on a specific subject requires a direct a link to it.  :)

You are soooooo right. It was in the Cakewalk blog. I've corrected the post in this thread to reflect reality 

Thanks  :)