![]() ![]() ![]() Studio One freezes up too, when MIDI devices are removed and added on USB ports, so that’s not even an option. So therefore RECORDING of the Midi in is impossible with Studio One. The MidiBerry program which is the easiest way to get it back online again by disconnecting reconnecting with a quit of the MidiBerry and restart, and reselecting of the MIDI device and Loop out, is not able to hold this thing for long. However that at least proves that it can be held and is not the fault of my USB connection. The only thing that holds this is a desktop CS80 synth from Arturia. It disconnects similarly from Live Professor II. It disconnects from Studio One after 1 minute, the second I play an aftertouch note. I KNOW there’s no one out there who can use this seriously with windows. Reason: added tags, clarification of first paragraph This topic was modified 5 years, 6 months ago by JS. Very frustrating, How can you not know this? How do you not have a driver? This is the reason the Xkey won’t stay connected and the reason it can only be seen by the first DAW or synth opened. The Oxygen 8 v2 is an exceptional MIDI device because it has a driver. They have never failed to put the device, with the same name every day, into every program I open concurrently. I have a current config using 5-6 MIDI keyboards simultaneously and I can recommend that you try to fashion a driver like the one for the M Audio which I use (have installed) two, the ‘Legacy keyboard’ and the ‘Oxygen 8’. Otherwise the MIDI will be blocked by the first program it is run thru, from running to any and all other programs. The simple fact with MIDI is that every device needs a driver. This should work via BLE as Windows can see and attempt to pair with xkey but fails with yellow refusal/retry message. By the way class compliant means BARE MINIMUM. So that not only do Xkey air NOT connect via Windows BLE, (and I’m not going to buy a Widibud when my Yamaha’s BT01 transmits fine, and windows can see Xkey but not connect just as Xkey attempts fail over android where I recieve the message “bad private key”) but also now barely hold a basic Class Compliant MIDI channel. Todays livestream I demonstrate that using my current cocktail of DAWs the xkey disconnects recurringly from 52:30 thru the end, at least 10 times: That's all the advice I can offer for now.I have shown time and time again (in my livestreams) that MIDI devices do not work right without a driver. Remove all power sources from your laptop (including battery), and hold the power button for ~15sec. I don't recommend starting with this, I'm not familiar with how laptops will react to it. This is only likely if you're playing with a single person at a time. Make sure it's not caused by your teammate's audio equipment. Try Discord or Skype as alternatives to Teamspeak, as it may be a problem with that. Chrome works, but CS:GO doesn't)? If it's just the software, reinstall and make sure you get rid of any user settings files it may have left behind. ![]() ![]() Is it isolated to your software audio sources (e.g. Doesn't matter if it's 32/64 bit at this point. Is this isolated to Windows? Try booting off of a flash drive loaded with a lightweight Linux distribution (e.g. If that doesn't work, try renting an audio interface from a local music shop, you can usually get them for very cheap if you're only using it for a day. First step is to isolate your problem, and then go through the usual troubleshooting steps.ĭoes this happen with any kind of audio equipment (3.5mm headphones, USB headphones, on-board speakers, USB audio interface), or is it just limited to what you were using? Try another set of headphones, it could be your current set. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |