Download the latest M Audio Keystation 49e driver for your computer's operating system. All downloads available on this website have been scanned by the latest anti-virus software and are guaranteed to be virus and malware-free. M-Audio Keystation 49 II, Portable 49-Key USB/MIDI Keyboard Controller with Synth-Action Velocity-Sensitive Keys and Studio Software from Sonivox.
Thzman I have tried to respond but some error message has prevented my reply from posting. I have a M-Audio Radium 49 as well (and really like it) sad they discontinued the Radium line-up (or are in process) Try this Keep the Radium 49 unplugged, Have your Mac on but keep Garageband closed completely. Plug in the Radium 49 by USB, the numbers in the screen on the midi keyboard may flucuate for a few seconds then it should settle out at the number 1. Then Open Garageband and then set the preferances in System and Garageband and it should work, I had the same issue. Can not comment on Reason as mine was bundles with something else but I do have Reason Adapted for Korg for a padKontrol. But if this works for Gb maybe thats the issue with Reason. I think the quirk is with the Keyboard (and maybe not just limited to Radium 49'or M-Audio.
HOpe this helps(and posts) Best of luck dwwave p.s. If your e-mail was not disabled I would have e-mailed you the day you posted but understand privacy issues.
Thanks for the advice, but i did what you explained and still nothing works. Ive also contacted tech support at m audio, but they havent helped much either i think maby its my operating system i got my mini mac off ebay so who knows how crapped up the files are.
The weird thing is that when i first got the key board it worked. I went on vacation for a week or so and had the mac unplugged and everything but then magicly the keyboard dident work. My mac dident come with any install discs so i guess ill get osx tiger and see if that works, i need it to run logic pro anyway. Thanks for the help, tech support is susposed to get back to me today, mabye theyll have another idea?
Thzman, Odd thing there, Glad MAudio is working with you, good company! I have a midi controller, a set of monitors and the black box reloaded from them all work just fine, I am wondering if its your mac mini, You can post your dilema on www.versiontracker.com in their online forums, the forums are in macfixit.com (a sub cataegory of versiontracker, some fine brains there!
By chance do you have a friend who has a mac and you could test the Radium 49 on theirs to islolate keyboard verus computer. Or take it into a store that sells mac's, it may work without even installing the drivers.
Or does someone you know have a midi controller to try on your mac? Even though you do not have a install disk you may be able to repair permissions check under the help screen and type in repair pemissions. It may help the mac disk utilty(to the best of my knowledge is on the install disk do you have any disk utilties such as diskwarrior (to defragment and also to get your system cleaned up. ) doubt a virus being a mac. Hopefully Maudio will hep you out and possibly post on www.macfixit.com Sure hope you get it working, if all fails can you return the keyboard? But TIger may help, and leopord is due out soon too. I am running OSX 10.3.9 Panther.
Keep the forum posted with updates. I am sure interested.
Best of luck dwwave.
![Radium 49 Driver For Mac Radium 49 Driver For Mac](http://8e5aac4bc793d119543e-a784f0287de17aca81e7ecc053e60785.r69.cf2.rackcdn.com/811/images/KS49_top_media_8x10.jpg)
Here is something that can fix the M-Audio Legacy Keyboard Driver issue under Windows 10. This worked for me under Windows 10 64-bit. And a similar fix like this has worked for my Tascam US-122 in Windows 7 32-bit using legacy Tascam Windows XP drivers.
1) Download the driver (fiilename: Install M-Audio Legacy Keyboard 500.exe). 2) BEFORE you install the driver, right-click on the downloaded driver file, and select 'Properties'. 3) Click on the 'Compatibility' tab. There, check 'Run this program in compatibility mode for: Windows 7'. (You may also try Windows 8 compatibility, too, but Windows 7 worked for me).
4) Finally, and optionally, check 'Run this program as an administrator'. I checked this, in case Compatibility Mode for Windows 7 needed to make any changes to the Windows 10 operating system that might require administrator approval.
You can try this fix without checking this, and if you still encounter problems, try uninstalling the driver, then reinstalling the driver and checking this. But it is perfectly fine to just check this the first time you install. 5) Plug in your M-Audio legacy keyboard, and you should see the M-Audio keyboard installation window appear while it installs the driver. 6) You should be good to go at this point. Happy music making! Hi Randy, Thanks for posting!
All of our current products being added for compatibility with Windows 10 are listed here: The Radium has been discontinued for some time now and is not being supported for Windows 10 use. I'm not sure I have more to add, but that last driver is certainly your best bet. For anyone else, you can download that driver here: It doesn't hurt to try different USB cables/ports as well.
Even test different software to make sure it's not a problem with software compatibility! Hope this helps!
Hi Randy, Thanks for posting! All of our current products being added for compatibility with Windows 10 are listed here: The Radium has been discontinued for some time now and is not being supported for Windows 10 use.
I'm not sure I have more to add, but that last driver is certainly your best bet. For anyone else, you can download that driver here: Radium49 - Windows 7 Driver It doesn't hurt to try different USB cables/ports as well. Even test different software to make sure it's not a problem with software compatibility! Hope this helps! SOLVED Thanks for the reply, Corey, and that fixed it, thanks! I also received an error message from Windows 10 suggesting that the legacy device was too old to function properly in a USB 3.0 port. I simultaneously moved it to a USB 2.0 port and connected it directly to the port rather to a USB hub.
Not sure which of those two moves (or both) made the difference, but it is now working consistently. There's still some noticeable latency between the keypress and the sound, but I can live with that. Thanks for the help! SOLVED Thanks for the reply, Corey, and that fixed it, thanks! I also received an error message from Windows 10 suggesting that the legacy device was too old to function properly in a USB 3.0 port. I simultaneously moved it to a USB 2.0 port and connected it directly to the port rather to a USB hub.
Not sure which of those two moves (or both) made the difference, but it is now working consistently. There's still some noticeable latency between the keypress and the sound, but I can live with that. Thanks for the help! Here is something that can fix the M-Audio Legacy Keyboard Driver issue under Windows 10. This worked for me under Windows 10 64-bit. And a similar fix like this has worked for my Tascam US-122 in Windows 7 32-bit using legacy Tascam Windows XP drivers.
1) Download the driver (fiilename: Install M-Audio Legacy Keyboard 500.exe). 2) BEFORE you install the driver, right-click on the downloaded driver file, and select 'Properties'.
3) Click on the 'Compatibility' tab. There, check 'Run this program in compatibility mode for: Windows 7'. (You may also try Windows 8 compatibility, too, but Windows 7 worked for me). 4) Finally, and optionally, check 'Run this program as an administrator'. I checked this, in case Compatibility Mode for Windows 7 needed to make any changes to the Windows 10 operating system that might require administrator approval. You can try this fix without checking this, and if you still encounter problems, try uninstalling the driver, then reinstalling the driver and checking this.
But it is perfectly fine to just check this the first time you install. 5) Plug in your M-Audio legacy keyboard, and you should see the M-Audio keyboard installation window appear while it installs the driver. 6) You should be good to go at this point. Happy music making! Here is something that can fix the M-Audio Legacy Keyboard Driver issue under Windows 10.
This worked for me under Windows 10 64-bit. And a similar fix like this has worked for my Tascam US-122 in Windows 7 32-bit using legacy Tascam Windows XP drivers. 1) Download the driver (fiilename: Install M-Audio Legacy Keyboard 500.exe). 2) BEFORE you install the driver, right-click on the downloaded driver file, and select 'Properties'. 3) Click on the 'Compatibility' tab.
There, check 'Run this program in compatibility mode for: Windows 7'. (You may also try Windows 8 compatibility, too, but Windows 7 worked for me).
4) Finally, and optionally, check 'Run this program as an administrator'. I checked this, in case Compatibility Mode for Windows 7 needed to make any changes to the Windows 10 operating system that might require administrator approval. You can try this fix without checking this, and if you still encounter problems, try uninstalling the driver, then reinstalling the driver and checking this. But it is perfectly fine to just check this the first time you install.
5) Plug in your M-Audio legacy keyboard, and you should see the M-Audio keyboard installation window appear while it installs the driver. 6) You should be good to go at this point.
Happy music making! I've found the older legacy keyboards only work in USB 2.0 ports. The driver installation also can act up if the keyboard is attached during install. I always install the legacy driver like normal (never needed to or thought about the compatibility mode, I'll try that next thanks, Pedro Perro posted above) Once both stages of the driver are complete then I plug it into a 2.0 port (hubs will work but not advised) and it shows up in Reason, Ableton, all my Daw software.
Reason is tricky to add a legacy keyboard sometimes, Ableton never has a problem. On a side note, Corey S. The employee mentioned 'It doesn't hurt to try different USB cables/ports as well' Do some research on ALL of your studio equipment.
There are different wire gauges (i.e. 24awg or 28awg) and some of your equipment MAY require the exact cable that came with it. Komplete 6 interface requires their cable and they even specify on their website that incorrect usb cable usage is a leading issue in a lot of home studios. Finding my original cable fixed my latency (strange - I know) issue I had months ago. Currently I label them as soon as they come out of the box.
Hope my info helps someone out there!!! I've found the older legacy keyboards only work in USB 2.0 ports. The driver installation also can act up if the keyboard is attached during install. I always install the legacy driver like normal (never needed to or thought about the compatibility mode, I'll try that next thanks, Pedro Perro posted above) Once both stages of the driver are complete then I plug it into a 2.0 port (hubs will work but not advised) and it shows up in Reason, Ableton, all my Daw software. Reason is tricky to add a legacy keyboard sometimes, Ableton never has a problem.
On a side note, Corey S. The employee mentioned 'It doesn't hurt to try different USB cables/ports as well' Do some research on ALL of your studio equipment. There are different wire gauges (i.e. 24awg or 28awg) and some of your equipment MAY require the exact cable that came with it. Komplete 6 interface requires their cable and they even specify on their website that incorrect usb cable usage is a leading issue in a lot of home studios.
Finding my original cable fixed my latency (strange - I know) issue I had months ago. Currently I label them as soon as they come out of the box.
Hope my info helps someone out there!!!