Logic Pro "Controller Assignment" problem

[CinningBao]

I have a found, from my perspective, quite a serious bug in the Controller Assignment function of Logic Pro.

I cannot assign two different controllers to the same parameter in two instances of the same plugin.
My process is below, and there is a video (which I will send to Apple if this attempt to solve it doesn't prove fruitful)

- load EQ in empty channel
- open Controller Assignments
- create new Mode with my Controller Zone
- hit Learn Mode
- waggle EQ Gain slider
- it appears in Controller Assignments menu
- move slider on MPK49
- slider is assigned to controller, no problem
- learn mode OFF
- load a second EQ into same channel after first EQ
- Learn Mode ON
- waggle gain in second EQ
- parameter appears in Controller Assignment window - good
- move a second slider on MPK49
- EQ gain in first EQ moves ????? <<- this is not what we would expect



Is anybody else able to test this? It would be useful to know if I have just ignorantly missed an obvious step which fixes the problem, my suspicions are, though, that I haven't.

thanks

[musiclover55547]

You'll most likely need to use another EQ. The Controller Assignments will apply to all instantiations of the same plugin. That's how it works, it's not a bug.

[CinningBao]

Thanks musiclover55547 - I appreciate your comments, but it isn't about the EQ. I first discovered the problem trying to map controllers to multiple SoundToys Tremolator instances.

It's about the ability to map a controller to the same parameter in the two instances of any plugin in one channel.

From my perspective, and I've been doing this loong time, it is a bug. And if the bug is a result of code design, then the code is designed badly if a functional limitation like this exists. I don't know of any other hosts where this limitation exists.

Do you?

[musiclover55547]

Thanks musiclover55547 - I appreciate your comments, but it isn't about the EQ. I first discovered the problem trying to map controllers to multiple SoundToys Tremolator instances.

It's about the ability to map a controller to the same parameter in the two instances of any plugin in one channel.

From my perspective, and I've been doing this loong time, it is a bug. And if the bug is a result of code design, then the code is designed badly if a functional limitation like this exists. I don't know of any other hosts where this limitation exists.

Do you?

I've been away all day and just had the chance to test it in both Logic (v 10.3.2) & Live (v 9.7.3.) For LPX, only the first instantiation now works whereas Live allows for more than one, and each is controlled separately. I'm not sure the team's intent (i.e. is this an error or how the Main App now is and/or an Environment Play) but it's worth sending feedback to Apple via the Logic App.

[CinningBao]

I believe it's a feature of the original code base, probably associated with some kind of efficiency.

With that in mind, and the literal handful of people who end up in this situation, I do not expect Apple/Logic Team to consider it a biggy worth fixing. But I know I am not the only person to raise it as a bug, so there maybe hope for it/us yet.