![]() I go through this every time I sit down to compose / record / diddle. all that matters is that you are using several controllers but not always having them connected or powered on every session. In a manner of speaking it doesn't really matter what controllers you are using at all. One haphazard peripheral gets plugged in and now all my templates have to be rewired? Most modern sequencers reference ports by name. You didn't by chance boot Logic with one of the interfaces unplugged/inactive. I think the Intel systems are more sensitive to USB port order so it's possible the portable USB drive is what did the damage. That may have been enough to juggle the Mac's view of MIDI ports. The likely culprit is that I plugged in a portable USB drive the other day to transfer some files. It's just so weird that I haven't seen this behavior in years. You could try unplugging the Novation, boot Logic then after Logic's loaded plug the Or even Logic happens to pick up the order differently. Port order can can change if Logic is started with one of the interfaces not present or if the Mac, No unresponsive corporate motherships.:-) And the problem is that then all my templates, which expect to find interface "A" first, are now behaving strangely because interface B has taken its place. That's pretty much what's happened to me. But if your system (or Logic) decides that interface "B" should be assigned to 1,2,3 instead of interface "A", then. The environment cables are assigned to ports "1, 2, 3." etc. This problem occurs regardless of your template, because the environment cabling doesn't "stick" to a specific hardware port. Thanks for trying to help, but I do use templates all the time. Hopefully the configuration of your Environment's midi-cables will remain intact. How about creating a simple customized template that contains the midi-cabling configuration (including proper mdi-cable order) of your Novation Remote 255L and Midi Express? Whenever I chose any of these templates to start a new project, all of the midi cabling remain intact without fail. And on a couple of these customized templates, in addition to the MidiOverLan CP3 program, I also use MOTU's MTPAV which has 8 midi ins and 8 midi outs. ![]() I have a dozen or so customized templates of large sequencing projects which require a lot of midi cabling, mostly using Music Lab's MidiOverLan CP3 program which has MANY midi ins and outs. I would not venture to guess to the cause of your problem, but I think I might have a work-around solution that might be helpful. Time to start reading the Nuendo brochures again. The system apparently can "see" the difference between the Motu and the Novation. Environment cables should be tied to physical/logical ports, not just handed out on a 'first come, first serve' to whoever shows up on the midi bus first. It points up, I think, a flaw in Logic's "logic". ![]() I've tried messing around in the AudioMidi setup tool but don't see any thing here that will help. ![]() So the cables that used to be connected to the Remote25SL are now connected to the Motu Midi Express, which wreaks havoc on my project.Īny ideas a) what causes this, and b) how to re-order the ports so it goes back the way it was before? So what? Well, the dumb cables in the environment don't move when the ports do. "Remote25SL 1.3" followed by "Midi Express 1.4". Now if I look at the "outputs & Ports" page in the Environment, it's reversed. I eventually discovered it was because Logic had some how changed the order of MIDI ports. It requires some special Environment cabling to work properly with Logic.Įverything was working fine until lately all my projects stopped responding to MIDI from my master keyboard. I've also got a Novation Remote25SL which works as a control surface/controller with 3 out ports. I've got a MOTU Midi Express with 4 ins and outs - it's my main interface. ![]()
0 Comments
Leave a Reply. |