Midi motu midi timepiece av12/19/2023 ![]() ![]() So, I wonder if the USB ports the interfaces are plugged into has anything to do with the order in which Windows addresses them. If I don’t reset, as described above, things might stay put (at 2, 3, and 4) until a power fluctuation or some other predictable event causes Windows to push things up to 5, 6, and 7, for example. It happens almost every day - but not always. What I’m noticing lately is that Windows seems insistent on pushing interface #1 to #4. Then, I power up the interfaces in the correct order and everything’s back to normal.īut, like yourself, I leave the USB cables plugged into the same ports and always power up the interfaces before the PC. Yeah, I’m using Uwe Sieber’s Device Cleanup Cmd with a filter that wipes all the MOTU devices out of Windows: DeviceCleanupCmd MOTU* USB\VID_07FD* SWD\MMDEVAPI\MIDII* This way I have no remap issues so far.My “Motus” are always the same 1-2 and 3.Īlso I have several usb synths which are working fine (Moogs,Nord,Tempest,etc). ![]() ![]() There´s a procedure to remove “midi ghost devices” from the device manager (I assume that´s your batch file right?) and after that I have all my usb midi interfaces connected to the same ports to powered usb hubs and I always start them first before my PC. Yep,it happened to me but only after disconnect and reconnect the usb devices to different ports. But if so, have you found a better way to deal with it? Please don’t tell me you’ve never seen this before either. It’s a nuisance and I have to run that batch script almost every day now. This happens to me so frequently that I finally wrote a batch file to administratively purge all registered MOTU ports from the Windows OS so that, when I turn the interfaces back on in the desired order, their OS assignments are restored as before. ![]() Consequently, devices don’t load properly. The assigned numbers keep climbing and, unfortunately, each time this happens, the port preferences in Cubase (or any DAW) are lost. But when, I restart my PC, there’s a good chance that one or more of those interfaces will appear as 4-Port X on MTPAV, or 5-Port X on MTPAV, etc. Plus, there’s eight instances of 2-Port X on MTPAV (your 2nd MOTU interface), and eight instances of 3-Port X on MTPAV (your 3rd MOTU interface). For example, after a clean installation of OS, interfaces, software, etc., you probably see eight instances of Port X on MTPAV in Cubase’s Device Setup > MIDI Port Setup. I have three MOTU midi timepieces AV USB too…īTW, do you have trouble with Windows remapping your MOTU interfaces? I think Windows has trouble telling identical interfaces apart, gets confused, and reassigns them as ‘new’ devices. I’m encouraged to keep trying, at least, a little longer. It’s just another random ghost in the Cubase machine, yelling at me, “go back to Sonar!”īut thank you for verifying your MIDI interfaces are working. I’ll think about trashing my preferences but honestly don’t expect any change. It’s pretty much a clean install of Cubase 9 on Windows 10. So, the short answer is this: I just rebuilt all of my preferences. I can’t seem to go a day in the studio without finding another one. It’s just one more well-documented, years-old bug that remains unfixed. Then, I upgrade to Cubase 9 and all of my preferences disappear - had to rebuild everything from scratch. First, I spend six months learning Cubase 8.5’s eccentricities and workarounds. I’m beginning to think Cubase and I are not meant to be (and that Cubase is one of the buggiest pieces of software I’ve ever used - and this comes from an IT professional of 30 years). I have three MOTU midi timepieces AV USB too and two 4x4 midisport plus an 8x8 and all seems to work as it should. Likewise, which interfaces are affected to begin with is also random. The issue is isolated to each interface so that, for example, if I get it fixed on Interface #1, the other two will continue to exhibit the problem until I get those fixed as well. When restarting Cubase and repeating the exact same steps, sometimes the problem will crop up on a MIDI Track. I can click through a dozen MIDI Devices and MIDI Ports with no effect, but then, suddenly, it’ll work and the problem will go away. Then, I can go back to the original destination MIDI Device and everything’s fine - at least, for a while. Why is this happening?Ĭhoosing another destination for the MIDI Track sometimes makes the problem go away. Sometimes, I’ll see activity only on Interface #1, Port #1, as would normally be expected. So, for example, if I’m routing a MIDI Track to a MIDI Device assigned to Interface #1, Port #1, I might see activity on all ports (1-8) of Interface #1. This is indicated by the MIDI activity LEDs on the interface’s front panel. Sometimes, when Cubase sends MIDI data to a MIDI port on an interface, it replicates the stream to every MIDI output port of the interface. I’ve got three identical 8-port MIDI interfaces (MOTU MIDI Timepiece AV USB). ![]()
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |