Controller assignments lost when changing midi devices

[Chadlly22]

I have a good deal of assignments programmed for use with my Edirol PCR-300. They work great as long as I don't add any other midi devices to my setup. For instance, they will be working fine, but then I connect a padKontrol midi controller, and the assignments no longer work. They are still present in the controller assignments window, but they do not work. If I add another assignment at that point, it will work.

 

So basically, I have to disconnect my padKontrol every time I want to use my controller assignments.

-very confused.

[Chadlly22]

I'm beginning to wonder if this is specific to my setup.

 

Could someone please try connecting (or disconnecting) an additional midi controller and check to see if your controller assignments (not key commands) are still usable.

 

Thanks!!

[Chadlly22]

This is killing my workflow!! and is a terrible bug.

 

It takes a lot of time to program controller assignments (multiple mixing banks, etc).

 

If controller assignments only work when used with the exact same midi setup that they were programmed in, that is ridiculous.

 

That means you could never add another controller to your setup (unless you reprogram) or you can't take your laptop and controller offsite (unless you bring all of your other controllers with you).

 

Could someone PLEASE confirm for me that your controller assignments (for controller A) no longer work when you connect or disconnect Controller B?

[stovetop]

 

Could someone PLEASE confirm for me that your controller assignments (for controller A) no longer work when you connect or disconnect Controller B?

 

 

I have the exact same problem with my padKontrol as well. My keyboard controller and my alphatrack lose all their assignments with the padKontrol is plugged in. With the keyboard control it is no big deal since I don't use much more than the standard pitch bend and modulation (which all work fine) but... the alphatrack is completely hosed with the padKontrol...so I have to choose one or the other... what's the deal?

[stovetop]

I have also noticed that my key assignments with the padKontrol are off by an octave...

 

the pad is assigned to C1 for example... and this is what is shown on the padKontrol's LED when I hit the pad.. but logic is recieving C0

[fader8]

This is killing my workflow!!

 

This doesn't always work, but you can try it. Close Logic. Plug in the PadKontrol. Open Audio MIDI Setup, MIDI tab. If the PadKontrol is the leftmost device, move it all the way over to the right. Save the configuration. Restart your Mac.

 

Open Logic and see if your old controller assignments work. Like I said, no guarantees but it works sometimes.

 

This dynamic enumeration of MIDI ports is a fatal flaw of OSX's Core MIDI. Not a Logic problem, but still, an Apple problem nonetheless.

[fader8]

I have also noticed that my key assignments with the padKontrol are off by an octave...

 

the pad is assigned to C1 for example... and this is what is shown on the padKontrol's LED when I hit the pad.. but logic is recieving C0

That's normal. Octave numbering varies per manufacturer. There's nothing in the MIDI standard that locks that down, unfortunately.

[fadercraig]

This is killing my workflow!! and is a terrible bug.

 

It takes a lot of time to program controller assignments (multiple mixing banks, etc).

 

If controller assignments only work when used with the exact same midi setup that they were programmed in, that is ridiculous.

 

That means you could never add another controller to your setup (unless you reprogram) or you can't take your laptop and controller offsite (unless you bring all of your other controllers with you).

 

Could someone PLEASE confirm for me that your controller assignments (for controller A) no longer work when you connect or disconnect Controller B?

 

Unfortunately this appears to be the case, happens to me A LOT, but not always. One thing ive found that can 'maybe' help, when ive finished with controller A, i shut down the 'puter completely, disconnect...plug in controller B, restart.

 

I have a handful of assignments so i can reprogram them on the fly quickly...at gigs often :/

 

I would have more controller assignments but the way it wigs out is random so i keep it to an amount i can redo at sound check in 5 minutes.

 

bugs the f**k out of me.

 

cheers.

Cx

[damian]

While my experience with this bug is not quite the same-- I can definitely attest that the same flaky controller assignment bug has been residing in Logic since at least version 7.

 

Not only does the plist file get nuked whenever a crash happens, when a controller is unplugged, or whenever Logic decides to simply dump the file-- it also happens in Mainstage 2. When I found the same issue in Apple's 'flagship' live performance app I was left shaking my head.

 

Heck, if you go into expert mode, Logic doesn't even map things to the proper Audio track object. What you will find is that an unselected fader, for example, will be mapped 4 channel strips away. It takes trial and error to get things mapping and then whoosh-- 200 mappings are lost because something flakes out.

 

I am disgusted to still see this bug in the codebase-- indeed, in the shared Logic/Mainstage codebase.

 

As a result, I am using Ableton Live as a part of my live rig-- when, due to CPU efficiency, I would much rather use Logic. Somebody wake these guys up-- this bug has been around for WAY too long now.