I have followed every trouble shooting guide to the letter. With all due respect Dave-I do know what I am doing. However, M-Audio has since released a 64-bit Windows 7 driver for the MIDISport and I connected mine back up and they work just fine. I had to stop using them when I upgraded to Windows 7 64-bit because there wasn't 64-bit drivers available so I bought a Cakewalk UM-3G which has 64-bit drivers. I've been using a pair of MIDISPort 2x2s for probably 10 years. Does the LED light when you connect it? It has to be plugged into your computer's USB ports or a powered hub, but NOT an unpowered USB hub. this video is a good exhibit for the case.Well, its possible (but unlikely) the hardware has failed.
I can only imagine the amount of Roli Blocks and Soundgrid problems, which occurredĭue to the effects of phased deprecations. The guy in the video is having the same problem, but with a driver for his waves soundgrid. but this video explained that this was probably my specific issue.
but the strategy is to not really mention anything about any of it.
So I’d think that if this is true and apple already know it, then apple tend to manage these deprecations of driver bit depth support, in an incremental and phased fashion. in the case of the BT Midi, it simply won't work untill the 2X2 driver was taken out of its enclosing folder and moved somewhere else. I think it’s because, if Bluetooth Midi needs to work at 64bit into the core Midi system, then a 32bit Midi driver may force the USB subsystem, to pull down to 32bit. in my case on high sierra, the 32bit Midi driver of the 2X2, was hobbling another unit needing to run on the core Midi system, using Mac OS’s 64bit Bluetooth Midi driver.Īfter looking into it a little, it seems 64bit Bluetooth Midi drivers can’t live alongside a 32bit Midi driver. it runs right into a serial MTP AV and I was only using the one port in any case. I had to switch out my 2X2 for a Roland UM ONE MKII.
0 kommentar(er)
