Hey everyone!  Maybe you can help my baffled ass out here, hopefully so because i've tried everything...
 
I have a Radium 49 M-audio brand Midi keyboard.  It worked on my dell inspiron 1501 in windows 7 with Sonar x1 perfectly.  I got another laptop when HD crashed and this one is a Gateway model MT6728 (Intel pentium T2330 @ 1.60 GHz, 2 gb memory , 32 bit op sys, it's fast enough, I could use more RAM I know....)  I use a 4300054 Gigaware USB audio adapter due to my headphone jack being broken, and I downloaded and tried everry driver possible pretty much for the Radium 49 from M-audio and I assume the one WIndows installs from WinUpdate is the newest (correct) one as well and even tried some compatibility modes too in between the things I've found to try via google etc... 
 
The computer sees the keyboard BY NAME and everyting in device mgr, not only on the usb port but in the sound driver list too as a keystation loader so it's not the cord or anything like that acting up, but Sonar WILL NOT see it in the preferences>Midi menu anywhere.   After screwing around and trying stupid stuff like vista driers etc... I havfe gotten cakewalk to somehow acknowledge its been plugged in but never in the list on the midi menu....
 
I am out of options and I bet it's a simple fix maybe someone can help a flailer out?
 
This computer had come with Vista Home Prem on it and I originally thought it had to be Vista for sure, so after installing win7 I was sure it'd work, but not the case.   I am so sick of working on the computer 10 times more than my music lately so I appreciate any help.
 
Thanks
 
Joey C

First you probably should determine if the keyboard is properly installed and working. Then if it is, you can worry about settings in Sonar. 

btw Win 7 32 or 64?

Is the device recognized in the Windows device manager, and is it working properly?


http://pcsupport.about.com/od/windows7/f/open-device-manager-windows-7.htm



Is the device communicating with the computer on another application?

http://avid.force.com/pkb/articles/en_US/troubleshooting/en398363 

Or if you are just looking for something to try without figuring out what is wrong, try running the driver installation executable as administrator.

http://www.techsupportalert.com/content/three-tips-running-programs-administrator-windows-7.htm

check to make sure input echo is on..i always do that.

Does Sonar see the Gigaware audio adapter under audio devices? Can you play a sample file through it in Sonar? 

If that works, then plug-in the Radium. 

Make sure you have ASIO mode selected, but also try WDM or MME mode if that doesn't work. This equipment is really below the specs needed for X1. 

Okay thaks everyone Im totally appreciative but it's gonna be a bit more tricky...

To SLARTABARTFAST:

Thanks, but yeah i made sure those 3 things were in order while Vista was installed and I assume the fact that im running win7 now with exact same results means that im still S.O.L. but i'll try again as I await more replies....  The Device mgr sees it by name, and says working properly while the little MIDI icon is in the tray and Midi-ox says "no devices" or something like that. So that's out and of course I run everything as administrator but tried without, a few compatibility tries like XPsp3 etc....  thanks though.

To Chuckbaby:
Ya with my track record in Sonar as well as in general "Life" situations one would expect that I'd space-case it! I too forget to do the obvious often.  Even LiveProfessor, a lightwieght app that runs vst's (maybe more too?),  i think for live purposes, didn't see it either.  LOL! I am surprised this forum is NOT littered with my countless requests for help with this type of ****, but nope...this is my first post and i've been a Cakewalk dude whose read this forum a majority of the time since Guitar Tracks Pro came out & changed everything for me, years ago!  THat is a testamet to the quality help on htis forum for i simply have always found the answer without having to post.  But I digress.....

And to daveyny5:
Thanks to u as well but yea the very problem i have is the fact that sonar doesn't see my device. so... wah wah wah.... no dice so far but to all of you: thanks, and here's more info....

I'm using only a usb cord not midi cables for a connection and this would be the culprit one would think, but it worked before & tried 3 cables.  Also, I have a diff laptop so I am thinking it has to do with my Gateway MT6728  But apparently no one uses Sonar with the same model or they never have problems that would result in a google search, their solved post on any forums, or fixya.com etc...  My lack of $$$, and archaic computer equipment are gonna to sabatoge my art again... for Cry-eye!

Thanks to u as well but yea the very problem i have is the fact that sonar doesn't see my device. so... wah wah wah....

OK, so Windows sees it (in Device Manager), but Windows doesn't? That's unusual. What driver mode are you using (ASIO, WDM, MME)? 

Device manager is primarily a measure of logical devices. It is quite possible to have a device for which drivers have been installed, but the device itself is not even connected, and still have device manager report it as working normally. 

The fact that Midiox also apparently does not see the device as a MIDI input, makes it likely that the problem is not due to a setting in Sonar, leaving the probable cause in the Windows to keyboard logical connection i. e. a driver or physical connection problem. If clicking on the midiox icon brings up a message from midiox that says "there are no MIDI input devices", that is what you would expect in this circumstance. This is not a Sonar problem.

Have you tried connecting other devices to the same USB port, and have you tried the keyboard in all available USB ports? Have you tried connecting the keyboard as the only USB device connected to the computer?

Just to be clear running an application on Windows under an administrator account is not identical to running an application as administrator. To run the driver installation as administrator, you would need to locate the program "Install M-Audio Legacy Keyboard 5_0_0.exe" found here and right click on the icon which will give you a menu option to "run as administrator." Before I tried to re-install the driver, I would delete it from the device manager and also from the installed program list if that is an option.

JOE, Slartabart bring up a great point and just triggered something in my memory.
make sure the device is always plugged in to the same port you installed the drivers to.
this is critical now with win8 + sonar x2.

you seem like a good dude, hope all works out.

in my studio here, we have a usb/midi in-out cable for a lot of the bone yard synths that don't have usb and if that particular sound card doesn't have a midi returns.
we use a midi sport uno.

M-Audio lists the Radium series as a series 1 MIDI device. 

http://www.m-audio.com/index.php?do=support.faq&ID=d3734a1e12cc7b665370bd72e2745bdf


Series II devices are "class compliant" with the MIDI USB standard, but series I devices are not. The drivers installed by Windows or from the Windows Update website are class compliant drivers. Hence one would expect that those drivers would not work with the Radium. Although the Radium may be "recognized" by Windows if the drivers are installed, it would not be expected to work correctly since it is not a compatible device for those drivers.

The driver I referenced earlier, is supposed to support the Radium and other M-Audio keyboards. You should probably try to be certain there are no traces of the Windows class compliant drivers linked to the Radium to avoid confusion. Hence the recommendation to remove the device from device manager before installing the new driver.


Before you delete the device in device manager, you can double click the device icon to open the properties window. If when you click the driver tab, you find that the driver provider is Microsoft then you have your answer. It needs to be an M-Audio driver to have any chance of working.

I have an M-Audio Radium 49 that I use with Sonar X2, Win 7 64-bit, and it works fine after downloading and installing the M-Audio Legacy Keyboard Driver, which is available from the M-Audio site (the one @slartabartfast mentioned earlier) and should come up when you select drivers for the Radium 49/61.  It definitely did not work with only the class-compliant drivers - it had to have the M-Audio driver installed.  Note - mine is plugged in via USB, but you could try plugging your in via MIDI and see if it works that way.