joe mugg

How can I get the range and units of a macro in an MFL device to change according to what it's mapped to?

Rather than having the macro display 0 - 127 with no units regardless of its mapping, I'd like it to automatically update to 50L - C - 50R when mapped to pan, 30 - 22k Hz when mapped to freq, X ms - X s when mapped to attack/decay/release, etc. Just like Live's native macros in a rack.

I'm new to MFL, but live.dial inspector > Parameter > Unit Style > Native seemed to be what I needed, yet this didn't produce the desired result. Any guidance?

I'm new to MFL, but live.dial inspector > Parameter >  Unit Style > Native seemed to be what I needed, yet this didn't produce the desired result. Any guidance?


context-sensitive-macro-unitsranges

When you say mapping, do you mean having a dial connected to a live.object that pointed to a parameter in live?

In the inspector of live.dial and you can change the unit style and the range, thus allowing you to set that up in the ways you specify.

That's correct: a live.dial connected to a mapping subpatcher (similar to the mapping setups in "Envelope" and "LFO", factory devices which ship with the "Max for Live Essentials" pack). Clicking the mapping subpatcher allows me (via a mechanism I don't 100% understand, since I borrowed this code from an existing device) to link each dial freely to any parameter in Live. But when I do this, the dial's units don't change accordingly.

I tried your solution before, but doesn't changing each dial's unit and range in the inspector change it permanently? That is, if I set up a dial to be 5-5000 ms, even after mapping it to panning or a tuning, it will always say 5-5000 ms?

What I want is a dynamic unit name/range that updates according to whatever the dial is linked to in Live, like how Live's native macros work. I know this is possible as I've seen it with other M4L devices. I just don't know how to do it myself.

Gotcha, and yes it'll stay the way it is setup in inspector.

I'm not sure, but if you say you've seen it, I'd definitely start at the patch where you've seen it happen. please post if you find it, I'd like to see how they do it, ;)

I don't know if there's an easier way, but off the top of my head you can always set it up so that whenever you change the path your patch also "gets" the min/max value of the new parameter and maybe you can feed that back in somehow.

Gotcha, and yes it'll stay the way it is setup in inspector.
I'm not sure, but if you say you've seen it, I'd definitely start at the patch where you've seen it happen. please post if you find it, I'd like to see how they do it, ;)
I don't know if there's an easier way, but off the top of my head you can always set it up so that whenever you change the path your patch also "gets" the min/max value of the new parameter and maybe you can feed that back in somehow.
sry couldn't help more


Quote from above: "you can always set it up so that whenever you change the path your patch also "gets" the min/max value of the new parameter"

That's exactly what I'm asking about haha, how to get the knobs on on my device to automatically update their units and ranges according to whatever they're mapped to. I don't know how to do this.

I know of a device that does it (available for free here: 

http://www.maxforlive.com/library/device.php?id=646),

 and I've attached its code below, as requested. Sadly, I'm new to M4L, so this patch is above my head, with lots of embedded patchers and objects I'm unfamiliar with. Take a look to see if you can make sense of the signal flow and identify at which point the macro knobs are updated with each new parameter's info.

I know of a device that does it (available for free here: http://www.maxforlive.com/library/device.php?id=646), and I've attached its code below, as requested. Sadly, I'm new to M4L, so this patch is above my head, with lots of embedded patchers and objects I'm unfamiliar with. Take a look to see if you can make sense of the signal flow and identify at which point the macro knobs are updated with each new parameter's info.

Haha, ya I know, what I meant by getting is the actual action of using the message "get" into a live.object. (check the LOM)

My point, for it to work for your particular patch it'll take a good bit of twiddling with it to make it happen. I don't believe you'll be able to just copy and paste larger portions from another patch that's built to work a certain way.

I was thinking that maybe for your particular situation (which I'm not exactly sure what it is) you could make a rudimentary version of this where instead of having the range and type displayed on the dial, you connect the dial to a patch that 1) gets the desired info from the end location of the path 2) sets a scale object to respond within that range 3) marks this range in an interface object (like an integer box)

Again just throwing ideas you may be able to work with

Haha, ya I know, what I meant by getting is the actual action of using the message "get" into a live.object. (check the LOM)
My point, for it to work for your particular patch it'll take a good bit of twiddling with it to make it happen. I don't believe you'll be able to just copy and paste larger portions from another patch that's built to work a certain way.

Again just throwing ideas you may be able to work with


Context-sensitive macro units/ranges