alfonso santimone

what i really miss in live.* UI objects are the data attributes.

setmin and setmax for dials, and sliders etc...

attributes to set the live.menu content and some way to autopopulate it ( in other words it needs all the features of max umenu ).

setmin and setmax for dials, and sliders etc...
attributes to set the live.menu content and some way to autopopulate it ( in other words it needs all the features of max umenu ).

max4live-max-6-petition-for-data-attributes-on-live-ui-objects

this is a problem with live, and all linear environments, in that one cannot change ranges of data lanes that change over time after runtime. you cannot even do this with live's fx etc

so the solution would be to have native max UI visible to the Live midi/key learn system?

to gain the required flexibility that max can offer...

so the solution would be to have native max UI visible to the Live midi/key learn system?
to gain the required flexibility that max can offer...

I don't understand the setmin / setmax argument. I first assumed you referred to setting a minimum and maximum value, but that is already possible. Then realized the "setminmax" 

As pid already said; this is a Live issue, not Max.

And no; I don't think that making Max objects "visible" would make for a good solution. In fact, I wouldn't be surprised if that broke more than it 'solved'. There is a good reason why the Live objects behave as they do.

Heck; this is also related (to my knowledge anyway) why you can dynamically add / remove objects from a Max patch but cannot use this same approach with live.* objects in a Live device.

Its the nature of the beast. It takes a little tweaking but its not impossible to work around this.

Personally I never considered this a major issue. An annoyance at times, sure, but nothing a different design or approach couldn't fix.

I don't understand the setmin / setmax argument. I first assumed you referred to setting a minimum and maximum value, but that is already possible. Then realized the "setminmax" message. There's a different there ;-)

Personally I never considered this a major issue. An annoyance at times, sure, but nothing a different design or approach couldn't fix.


for sure i'll find workarounds. again a time was just facing some limitation. for example i have an umenu in my max4live stuff. but it can't be automated. so i have to put a live.dial to drive that umenu. then i can't set dynamcally the max value of the live.dial to the umenu items number. i start to think that i'd use standard pattrized max UI objects cibtrolled by OSC

Avoiding that missing scope between max ui objects and live midi and key learn. All the best

for sure i'll find workarounds. again a time was just facing some limitation. for example i have an umenu in my max4live stuff. but it can't be automated. so i have to put a live.dial to drive that umenu. then i can't set dynamcally the max value of the live.dial to the umenu items number. i start to think that i'd use standard pattrized max UI objects cibtrolled by OSC
Avoiding that missing scope between max ui objects and live midi and key learn. All the best


sure i meant messages and not attributes. little but relevant mistake on my side! the same that is possible with native Max UI. But now it's clear to me that this kind of integration between the Max world and the Live world is still to come. As it is now is very powerful. Only not so powerful for my particular needs. But they are two great softwares! I must say that Max wins for its flexibility. Ideally would be great to reconstruct Live in Max. Live4Max! sorry...i'm just really doin some jokes. I guess i still circumvent the midi learn for native Max UI objects using OSC. I'll hope to not encounter other bottlenecks! i'll give a try to CNMAT osc objects in M4Live devices...

sure i meant messages and not attributes. little but relevant mistake on my side! the same that is possible with native Max UI. But now it's clear to me that this kind of integration between the Max world and the Live world is still to come. As it is now is very powerful. Only not so powerful for my particular needs. But they are two great softwares! I must say that Max wins for its flexibility. Ideally would be great to reconstruct Live in Max. Live4Max!  sorry...i'm just really doin some jokes. I guess i still circumvent the midi learn for native Max UI objects using OSC. I'll hope to not encounter other bottlenecks! i'll give a try to CNMAT osc objects in M4Live devices...


Max4Live / Max 6 Petition for data attributes on live.* UI objects