Logic Pro Automatic setting Format and Mode parameters for Learn Mode

[frodo.jedi]

Hi all,
I am sending CC messages from Max/MSP to Logic in order to automatize the control of some faders/effects parameters by means of Control Surface Assignments.

For some reasons, when performing the Learn Mode procedure, Logic sets in the Value section, the parameters Format to "2's complement" and Mode to "Relative". This produces a mistaken behavior of the control: basically instead of being a continuous control it is a discrete one (with only two values, 0 and 127). Instead the correct values to get a continuous control are Format = "unsigned" and Mode = "Scaled".

So far the only way I found to make it work is to manually change the settings when doing the learning.

Do you know if there is a way to automatically set such settings for a given controller (in my case Max/MSP)?

I have already checked all the Logic preferences and even destroyed (and recreated) the file com.apple.logic.pro.cs in ~/Library/Preferences where all the control surface assignments are listed.

Thanks in advance

Cheers

 

[Peter Ostry]

The problem are misinterpretations during the learning process. Since the failures are almost everytime "2'n complement" and "Relative" I believe in a bug when data arrives in a certain way or, in opposite, not in a certain way.

You may be able to work around by testing several methods of sending data. Logic tries to analyze incoming numbers, so you can try to deliver in a way that goes around the hidden trap.

First I would send a controller with value 35 (doesn't matter, but not 1 or 127) and look if Logic jumps on the train with a single value. This would not be optimal, but if it reacts instantly and correctly, the problem may be solved. If Logic waits for a second event, send the same but with a higher value to show a series. Something like that, it's a debugging process.

I can imagine, that Logic reacts always the same for the same sequence. Therefore, if you don't send your real data but just the tested sequence, you may have won.

 

[frodo.jedi]

Hi Peter,
thank you so much for your answer. The problem was that max msp was sending too many messages at once
and Logic could not manage them apparently. I have filtered the repeated cc values that I was sending (using the [change] object) and everything works

 

[Peter Ostry]

Well, this tells us that Logic interprets a couple of identical events as only one event and sets the parameters in a wrong manner. So it isn't a bug, just not perfect. Interpreting streams is often a complex task.

Good that you got it working with a single [change] because my suggested method is more complicated. You would send only two events, but need several objects. No advantage in this case.