Automation Quick Access change deletes other controllers

[willstuart100]

Hi there,

 

I've had a recurring issue. I use a Korg SP-250 as my main controller, but recently added an M-Audio Oxygen 25 to my setup to have more control surface functionality.

 

When I change the Automation Quick Access controller from the default volume fader to a rotating knob (Track > Track Automation > Automation Preferences) it learns the new control, but the mod wheel then ceases to send out signal (or at least it stops working, and nothing shows up in the transport bar when I move it).

 

I can restore functionality by deleting com.apple.logic.pro.cs, but I'm just wondering if I can the learn a new command for Automation Quick Access without losing the mod wheel?

 

On that note, I'm not sure what the default function for the mod wheel is, so I can't relearn it manually. It seems on midi drum tracks to be a sort of filter sweep, but without requiring a plug in that it operates. Maybe knowing what the mod wheel ss triggering, rather than just what it sounds like, would mean I could just relearn all commands?

 

Any thoughts much appreciated.

 

Will

[Atlas007]

By default ModWheel sends MIDI CC#1?

If I understand well, you are trying to allocate two different controllers to the same parameter. To do such thing I think you would have to do the Learn procedure from the Expert View in the Controller Assignments window...

Alternately, you could use Transform (in the Environment) to transform an incoming CC into another one, making two different MIDI controllers sending their respective CC but ending to be interpretated by Logic as the same CC, hence controlling the same paramenter...

Reading about all these could shed some light.

[Eriksimon]

When I change the Automation Quick Access controller from the default volume fader to a rotating knob (Track > Track Automation > Automation Preferences) it learns the new control, but the mod wheel then ceases to send out signal (or at least it stops working, and nothing shows up in the transport bar when I move it).

 

I can restore functionality by deleting com.apple.logic.pro.cs, but I'm just wondering if I can the learn a new command for Automation Quick Access without losing the mod wheel?

 

No, this is expected and designed behaviour, otherwise Learned parameters and the original MIDI CC could conflict with eachother, or double up on eachother. Messy.

So, anytime you assign a parameter using the Learn function (or AQA), that MIDI event will no longer be available. If you want it back, you can delete the assigned function from the Controller Assignments window (cmd-K), which is way more elegant (and simple) than deleteing the .cs file.

 

On that note, I'm not sure what the default function for the mod wheel is, so I can't relearn it manually.

 

Nothing to "relearn" there. Modwheels send MIDI CC 1* by default, and you get it back if you remove whatever assignment you have "taught" it. Or, in other words: the original assignment is still there (in your controllers' hardware), it is just being "remapped" in Logic. Remove the remapping, and the Modwheel goes back to sending MIDI CC 1 (which is most commonly (but not exclusively) used to add vibrato to sounds.)

 

* CC's are numbered 1 to 127.

CC 1, 7, 10 and 64 are the most commonly used ones (modwheel, volume, pan and sustain respectively)