Hi,
 
I've just had a problem occur with my Sonar 7 install concerning the M-Audio Axiom 61 USB keyboard I use. When I attempt to confirm the selection of it as the MIDI input, Sonar 7 still tells me there's no MIDI input selected. I've checked that Windows 7 is seeing the Axiom and it is, and using MIDI-OX, I can see MIDI data coming in from the keyboard. Can anyone help with what might be causing Sonar 7 to not accept the Axiom as an input?
 
I'd post an image but I don't seem to even be able to link to one, let alone upload one.
 
Ian
 
 

Welcome to the forum!
 
The only thing that comes to mind without further information is that you may have SONAR in ASIO mode and it is seeing a different audio driver (Edit->Preferences->Audio->Driver Settings/Playback and Recording). Try setting that driver mode to "WDM" and see if SONAR will see the Axiom (Edit->Preferences->MIDI->Devices).
 
Which version of Windows are you running? and what audio interface are you using?

ASIO versus WDM, oh dear.
 
A bit of tech info re the spec of my system (and no laughing at the back because of how old it is!):
 
Windows 7 64 bit, SP1
Mobo: Asus P5W64 WS Pro
CPU: Intel QX9770
Memory: 8GB DDR2
Graphics: ATI Radeon X1950 + nVidia GeForce 8800 GTS
Sound: Terratec EWS 88MT
SSD: Intel X25-M
 
There are a number of external PCs and an old Roland Sound Module being controlled (PCs via MolCp3, module via a MOTU Express 128) by Sonar, and their analog outputs come in via the Terratec. The only way I can record the sound from the Terratec to an audio track in Sonar is by using the ASIO drivers. Anything else seems to have problems with choppiness, degradation and/or timing.
 
Sonar 'sees' the Axiom on the MIDI Devices Input section, it just won't accept my checking of the box for it as an input. When I go to click 'OK' it gives the message that no input has been selected.
 
HTH
 
Ian

ASIO is far preferred, trust me. I have a couple M-Audio MIDI controllers, and if I recall correctly, the drivers they came with were also ASIO. If I had either plugged into my computer via USB, I immediately got conflicts (it seemed I could not just choose it for MIDI, it wanted the ASIO spot too ). The only way I got around this was to route one via MIDI cables into my audio interface (i.e. unplug it from USB completely). I am not sure if you are experiencing the same issue. Do you have that option to connect it via MIDI cables to your interface? My system is still set up this way, and I have MIDI assigned to my audio interface's MIDI, not the controller itself.
 
Another option is to disconnect/reconnect the USB and see if this will reset anything. For me, this did not help.
 
I would also recommend sending M-Audio an email, and ask them specifically "How do I use my Axiom as a MIDI controller only without the ASIO drivers being loaded?"
 
 

Hmm. Well, I could try and find a power supply for the Axiom, and plug its midi output to the MOTU, so that could potentially get me an input other than via the USB. But it puzzles me why the Axiom, which a controller only and produces no sound whatsoever, would need ASIO drivers?
 
Ian

Honestly, I would send an email to M-Audio and let them know your setup and ask them directly (before buying anything). I have an old Ozone and Keystation 61ES, and the Ozone drivers were updated for Win7 64 and caused me numerous conflicts. I honestly never dug deep enough into that to find out why, but even with a new audio interface I was unable to plug it in via USB for MIDI.
 
M-Audio would be the best source of information, and the real answer for your setup. I wish I could give you a better solution. I have contacted them in the past and their email response was pretty quick.

I wouldn't need to buy anything. I have a box of power supplies of various types including ones with variable settings that can be used with different types of equipment, so I will have something in there that can power the Axiom, and I have a number of spare MIDI leads to use to connect via the MOTU unit (that is otherwise under-employed). However, I will send an email to M-Audio next week asking them about the issue. I expect they will say that because the Axiom works fine outside of Sonar that it's therefore a Sonar problem, but we'll see.
 
Thanks
 
Ian

I had the Axiom 49? any how it was the smaller version of yours and there were no drivers needed for MIDI input. My son gave it to me second hand so I had no instructions or information. I just plugged it in with the USB and Windows 7 flashed a message that the drivers had been installed and it was ready to use. I showed on my list of input options, The same goes for my Yamaha DX drums, just plug it in and it works. 
Like you say, I don't see that there would or could be any ASIO drivers as it is not an audio devise. 
Try a different USB port. 

I just checked the Axiom manual and it had something in there that may be the issue (pg 33 of the user guide):
 
plug symbol disappears.
 
There is a setting in the keyboard to determine if the MIDI is routing out the MIDI port or the USB port, and this toggles that functionality. It is possible that Win7 recognizes the USB connection, but the keyboard is not actually active through the USB port, so this is something to check as well.
 
 

That wouldn't be it unfortunately, as the computer is able to see midi info over the USB via the MIDI-OX program. I did check it however, and it was set to USB (which is when the MIDI plug icon in the display is off).
 
I have also tried various different USB ports on the PC and they made no difference either, all worked as far as MIDI-OX was concerned, but not as far as Sonar recognizing the input properly. My conclusion so far is that it definitely appears to be a Sonar issue of some kind.
 
What's weird is that this keyboard has worked via USB as an input up till recently, so I don't know why it suddenly doesn't want to work now.