I am still attempting to get this thing to work properly. Would take a driver, or money back but I refuse to waste my time even turning this thing on from now on. I must be asking too much to expect a WHOLE DAW to open and run an instrument track with this thing. You drop the instrument “Analog Lab” from Arturia on the track and set the instrument to Nazgul presetīefore you can even play A NOTE, the Xkey has become disconnected. You run Xkey into a midi and watch the Yellow meter rising and falling with the inputted signals. You open Studio One (as I have just in the last 30 minutes) Sorry but I had to laugh thinking about that guy, tryin to run 6 of these Hydrogen powered beasts into Windows. I heard there was a guy on these boards who bought 6 of these things and was trying to run them in Windows… Now it will show up again for between 15 seconds all the way up to a few minutes. Restart the Xkey (especially in the case where it has shut off)ĬLOSE any additional MIDI receiving programs (with the exception of LoopMidi which runs all the time) Unplug and plug into a different USB port It will be unavailable in the DAW from the moment that the DAW is started, and has proven to NOT be Reattatchable without ALL of the following: Inside the daw, it will shut off and stop recieving signal from the xkey air MIDI device Here is a list of problems the Xkey Air is throwing up in my situation. – Route it (via Windows Bluetooth API where necessary) to any and all open. – Take the BLE signal (with all aftertouch at top sensitivity) Yamaha’s driver is good at this, with only Rare NAME CHANGES due to some programs like Ableton Live Lite and LMMS M Audio Legacy Keyboard Driver and Oxygen 8 driver (running at the same time on my system, always) are even better, with NO name change EVER.Īs Apparently the ONLY person currently existing who has the experience to talk about MIDI driver value in windows I would make a checklist similar to the one at the website, but for the driver: Silently and with no stress for the user. Like I said a Really GOOD driver would take the bluetooth signal and run it through a Windows API which could deliver it with its XKEY AIR 37 (or 25) name to ANY AND ALL program which take MIDI. I’m surprized you maintain your Bluetooth SIG status allowing the huge Bluetooth brand on the device with the device not operating in Windows. Whats the word on Beta testing of this firmware?Ī Driver is still needed, if only for people who wanna make Xkey Plus changes on the fly in the claimed supported Windows platform. When the Bluetooth firmware is available through the XKey Program? Eager to try it through bluetooth and cut out USB problems altogether. If you are having disconnections it SEEMS likely it is your USB device. The USB was disconnecting all the time before I switched to my current USB device. I had changed the Xkey Plus settings to Aftertouch Noise Floor = 8 (from 4, now changed back) and Aftertouch Period = 50 ms (now reverted to original 16). Also I increased the LoopMidi value for “Detects feedback from” to 20000 commands per 3 seconds and the Sysex Buffer to 512 KB. You don't need a separate MIDI interface for this keyboard-it IS the MIDI interface.I removed the USB 2.0 x 7 hub (cheap USB hub) from my equation and that solved the problem of the disconnects. Radium is also a USB MIDI interface that speaks directly with your computer without any extra devices. Designed to meet the needs of today's electronic musicians, Radium puts you in control of any 16 MIDI-assignable parameters within your favorite software programs. The M-Audio Radium 61-Key USB MIDI Controller is a new breed of controller.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |