Loading Profile...
Greetings,
I have an Alesis Q49 midi controller that at one point DID work but no longer plays on my computer.
I have tried researching what the issue could be and keep finding myself to Windows 7 Midi issues.
I am using a USB to connect the midi controller and when it is connected Windows recognizes the device and says it installs the drivers
The one thing I can see that is apparent is under control panel my Midi device is unspecified.
I cannot figure out how to get this device to work
Help get this topic noticed by sharing it on
Twitter,
Facebook, or email.
Twitter,
Facebook, or email.
Alesis Q 49 windows 7 unspecified device
This topic is no longer open for comments or replies.
-
Hello it sounds like you have another device blocking your USB performance.
Which model and make of computer do you use?Comment -
-
Hello, Thanks for the reply!!!
-
-
Still not sure what to do? Can anyone assist?
-
-
I'm facing same problem . It seems that Q49 is not compatible with win 7 !!!!!
what to do now ?? -
-
Can anyone at least point us in the right direction? I was pointed here from Windows 7 support
-
-
Hello it looks like a driver from logitech may be causing this issue can you please email me at sbangs@alesis.com
-
-
We are having this issue and are running thin clients, no Logitech drivers installed to my knowledge. What driver are you talking about? -
-
Logitech provides OEM drivers to several manufacturers for their components these can include soundcards and USB hubs inside your system. These have been known to cause issues with midi and audio devices they have provided us with a Patch.
-
-
What do we have to do that get that patch?
-
-
I as well am curious as I spoke with Nick from Alesis support.
He sent me links to download files that were listed as Windows 7 - USB Audio Codec & Windows 7 .INF .PNF Files
Are these the files you speak of?
Funny thing is...When I went drag the files into my System 32>Driver folder it prompted admin permissions and since I am under the admin account I clicked on the admin continue and still denied me permission. -
-
I’m
frustrated
I'm experiencing the similar thing when connecting QX49 (using windows muiltipoint server 2011. which is based on windows server 2008)... hope there's some kind of driver uploaded at the product page. Otherwise no one can use Q/QX49 using windows 7/server...while Ableton support the OS. Such a weird situation.. -
-
Sathya, we have the latest version of an update on the site for you. This is not a driver but and update to the QX49 itself. Could help you:
http://www.alesis.com/contentmgr/show...
(Make sure to follow the direction it comes with.) -
-
Yes I had tried that. But it won't install.
Seems like the updater tool won't install the firmware if it can't detect the USB controller...
I don't know what's in there, but it surely can't make the device get detected as midi controller or some sort. Still under unspecified category.- view 10 more comments
-
-
-
-
-
-
-
-
-
-
-
I will bring this to the attention of the right people to see if theres anything on our side we can change in the future to avoid this.
-
-
yes please. I really hope there's some kind of driver specifically made for products. I think it will help avoid conflicts because m-audio's MIDI controller was also in the same situation for many people until I think they made a driver.
-
-
-
Here's your fix guys:
For the First Method, you'll need at least two cores on your processor and a motherboard that supports virtual machines...
Load VirtualBox (free VM software)
Install windows XP into it
Install your Abelton onto that windows XP
Now you can see your controller.
Second method:
Goto Start, Control Panel, Device Manager....
Find your Q49... It will have a yellow bar beside it...
It may be under Other Devices, or Universal Serial Bus Controllers.
Right click it, Disable it, then Uninstall the drivers.
unplug the keyboard, then reboot your system and leave it unplugged.
Boot up your system fully to desktop, then Plug the controller back in....
It will probably load drivers at this point, sometimes this appears to work...
One time it did not work, so I told the driver prompt I wanted to manually install the drivers,but I counldn't find them so I went to sound and game controllers, and loaded the yamaha USB MIDI driver. It got an error, said that it could not install the drivers. I then deleted the yellow device in device manager, ( I was frustrated) but I noticed that now I had a MIDI controller named QX49 sitting in Sound, Video, and Games controllers list in device manager, and it's not got the yellow line.
I started up Studio One, and there it was, and I have verified that the midi events are getting to Studio One by looking at the MIDI Monitor App.
Hope This Helps someone..
Tony The Tiger... -
-
I'm having similar problems getting Pro Tools 8.0.5 on a Win 7 (64bit) install to accept and acknowledge my Q49. No drivers are installed. To spice it all up, I am running my Win / in a Boot Camp on a Mac computer - which makes me think that maybe not all Win Codecs are part of the drivers that Boot Camp uses?
When I try to circumvent the problem of Windows not accepting the Q49, by MIDI plugging it into my Mbox2, all I have acheived so far is getting Pro Tools to accept the MIDI on a MIDI track, but I can't make it export it to an aux channel - so I can't hear it...:(
Any thoughts?-
You won't be able to hear anything unless you assign the midi to a sound set/virtual instrument. It sounds like everything is working correctly since you're tracking midi information.
-
-
-
-
Can't you just write a small driver, just to force win 7 to recognize the Q49 and release it ? is it so hard?
The problem lies in Windows 7. In early release versions of Windows 7 everything worked fine. Later, after some automatic OS updates, Win 7 stoped recognizing the Q49. So yeah, they in Microsoft did something wrong, but can't you, der Alesis team, do something about it instead of pointing the way to Microsoft support page?
I got no Logitech devices, and nothing changed on hardware side, when I could work with the Q49.
Stupid situation where sofware and hardware manufacturers can't solve their problems, and their customers become victims- view 3 more comments
-
-
-
-
Yeah, It does! And Q49 gets it's 9v when connected over USB, all 3 buttons get illuminated when pressed.
http://i49.tinypic.com/14d258x.jpg
Ok, I got a fresh system reinstalled twice by now. Q49 won't get recognized on a fresh windows 7 64-bit SP1. And because I tried to replace the system files without getting Q49 to work once again on a fresh system without ANY drivers installed for rest of the hardware, I had later to reinstall windows once more. But, don't take it pesonal, it's just the way I like to be sure about my OS is clean and "untouched".
So far, nothing helps. The currious thing is that it even don't work MIDI wise, when powered with a 9v 600mA adapter and plucked into M-audio's MIDI-IN (Other MIDI-keys DO work, but not Q49).
I've opened it today for the first time. Bye bye warrenty (it's anyway over a year that I've bought). Inside looked everything fine, everything's connected...but didn't looke deeper under the keys... no damage outside, inside... I just don't know what's wrong by now.
Well, you may be will hate to hear that, but I'm done with the Q49. Will spend more money for Midi-keyboard next time, and make sure it has drivers or a least a clear claim by the manufactrurer that it is supported with my OS. -
-
Its 100% supported on win7. You may need to swap out your controller from the sound of your troubles:
WORLD HEADQUARTERS
United States
Tel: 401.658.5760
United Kingdom
Tel: 0044 (0) 1252 896000
Germany
Tel: +49 2154 812 99-0 -
-
EMPLOYEE
EMPLOYEE
