MIDI control Pickup mode

chapelier fou's icon

When choosing "pickup" mode to control a slider with MIDI, the behavior is erratic. It picks it up correctly the first time, then seems to make some none-sense.

Jeremy's icon

Hi, it's working ok for me. Could you please post a patcher? Are you using both incoming and outgoing mapping or just incoming?

chapelier fou's icon

As simple as that.

SliderMidiMappingBug.maxpat
Max Patch

Jeremy's icon

Sorry, it's working fine with my controller. Could you post more information about what hardware you're mapping to and maybe post a video? Thanks...

chapelier fou's icon

Well, that's weird.
Just to be sure I understand, "pickup" means that if you change the value with the mouse, it will wait till the MIDI fader reaches the current value to change it, isn't it ?
I'm using an AKAI MPK261, a fader outputting an absolute CC. Really basic stuff.

Jeremy's icon

Yes, that's it. Anyone else?

In any case -- please send me a screenshot of your MIDI Setup window. Also tell me your platform + OS info, please. And I'll still take that video if you have a chance. Thanks.

chapelier fou's icon

Mac 10.12.6

Jeremy's icon

Interesting, what's the difference between the different MPK261 ports? If you disable all but one, does it stop behaving strangely?

chapelier fou's icon

It seems that I can't upload a 9MB video.

Jeremy's icon

You can put it on Dropbox or something and send me a link at my email address (jeremy (at) cycling74 (dot) com).

chapelier fou's icon

https://www.youtube.com/watch?v=P6o9HNDM6-w&feature=youtu.be

Jeremy's icon

You may have missed this message in the shuffle: "what's the difference between the different MPK261 ports? If you disable all but one, does it stop behaving strangely?"

chapelier fou's icon

Port A and B are just two USB ports. I'm using only port A.
MIDI is the DIN ports.
Remote, well, I don't know.
Anyway, if I let only port A checked, the result is the same.

Konstantin Kazancev's icon

Support CHAPELIER FOU. The pickup does not work correctly, if the values match, it should stop working but it continues to work and slowing the slider. As an option, you can make it possible to control the activation / deactivation of the pickup function via "mappings" from the outside. But of course it is better if the pickup will work according to the following scheme: moved the slider with the mouse or set a new value to the slider from outside - the pickup turned on and waits for a match as soon as the values matched the pickup turned off.....

exeterdown's icon

I'm using a basic Korg NanoKontrol.
I've tried all three pick-up options (off, pickup, scale) and get the same behavior.

I'm controlling a [dial] in Max and I want to be able to have my midi controller not change the [dial] until they match values; but as soon as I move the Kontrol's knob the [dial] leaps to this new position.

---

Would also be great to have a keyboard shortcut to enter and exit mapping mode.

Jeremy's icon

Hi, could you provide a bit more information -- which controller #, maybe an output log from a MIDI Monitor app, something like that? Thanks, I don't have a NanoKontrol lying around to test, but it's working as expected for me with my KeyStep 37.

exeterdown's icon

I created a fresh patch, placed one dial in it, mapped it including pickup, and it worked perfectly.

I created a new dial, mapped it not including pickup function, the mapping works.
Opened the mapping mode and edited pickup mode to pickup, doesn't work.

I then right-click on the dial, deleted the mapping, remapped it, and made sure to set 'pickup' before closing the mapping mode. Worked.

Jeremy's icon

Thanks, maybe there's a clue there. When I mapped to my 'dial', the original map was without pickup, and I didn't have the mapping window open -- I was able to change it after the fact and it worked fine.

Which sounds like your 2nd scenario, but maybe there's some case where it isn't working properly.

exeterdown's icon

Not exactly like my second scenario.
I've tried a few more combinations, but am never able to change pickup mode after the original mapping. It only works when I select pickup during the original mapping.

Jeremy's icon

Maybe you can shoot a screen movie or something to show me what you're doing. Prose is imprecise, and I can't reproduce the problem based on these descriptions. Thanks!

carlos de anda's icon

Hi,
Has there been any solution to this? I just recently started using a midi controller and I'm having problems with the pickup mode too.

For me, it only seems to work when going from low to high value but it's very finicky when going from high to low.
The best way to replicate this is to create a patch with 2 live.gain objects and map 2 midi faders, both on pickup mode. Set the first live.gain to an initial value to 0db and the other to -70db. Save and close the patch. Now move your first midi fader (or encoder) all the way down and your second fader all the way up.
Open the patch and you'll see that the first one works as it should, you start moving it up and nothing happens until you reach the 0db and then it picks up. The second fader doesn't work properly, the live.gain object is at -70db and the fader is all the way up but as soon as I touch it it will jump to a high value, it doesn't wait until I move it down and reach the -70db point.

I have tried this with both my windows and mac computer and its the same.
Is this a bug?

Also, while I'm here, can someone please explain to me the scale pick up mode? I read the max documentation "Scale: The value scales until it reaches the minimum or maximum value, then is treated like an absolute value." but if I set minimum and maximum values it responds exactly the same as "off" mode.

Thanks

Jeremy's icon

Thanks for the steps, I can reproduce this (incorrect) behavior.

carlos de anda's icon

good :)
I see you work at c74, so do you think this could be fixed with the next update?


this would make a big difference between having to buy a high end midi controller that does the pickup mode thing vs a regular midi controller.
Thanks

Jeremy's icon

I can't make any promises about the release, but it's already fixed (also the busted scale mode) and in internal testing.