Sabina

I need to freeze the patch so the js code will be embedded in the device.

Hello, 
I need to freeze the patch so the js code will be embedded in the device.



freeze-button-greyed-out-in-inspector

https://docs.cycling74.com/max7/vignettes/live_freezing 

freeze button greyed out , in inspector

Loukas Perreault

Hi! Is anyone aware of the Function create_audio_clip (class Clipslot). It's listed in the LOM manual but don't seem to work (also for class Track) :

live.object: 'ClipSlot' object has no attribute 'create_audio_clip'

At first I tought it was because I was using it under Ableton 11, so I installed Ableton 12 trial and still don't work.

My guess is that 12 trial is version .0.1 and the LOM manual refers to .0.5

I was wondering if anyone using 12.0.5 tried create_audio_clip function because I don't think I can update from the trial version... or maybe I'm wrong... Thanks!

Function "create_audio_clip" (class Clipslot and Track) missing (LOM)

function-createaudioclip-class-clipslot-and-track-missing-lom

tyler mazaika

Hi folks, I’m attempting to override a subset of Push2s default controls from within a Max for Live Device. With minimal success. The documentation states for ‘grab_control’ that “

This releases all standard functionality of the control, so that it can be used exclusively via Max for Live.” (

https://docs.cycling74.com/max8/vignettes/live_object_model?q=LOM)

But when I grab_control anything, such as Push’s control named Global_Mute_Button, I don’t get any control from within my Max for Live Device. Instead the corresponding MIDI CC/Note message goes into the sequencer inputs (e.g. the “Ableton Push 2 (Live Port)” input, MIDI CC 60 in the case of the Global_Mute_Button). This hardly seems “used exclusively via Max for Live” and is not helpful for an Audio-type devices (which can’t get that MIDI info).

When I enable “grab_midi” on Push2, I get MIDI outputs direct from the [live.object] in my device. Similar output from something in my device is more-or-less what I am expecting is possible when I use grab_control. (The grab_midi output itself is problematic for me because it doesn’t disable to default functionality of the Global_Mute_Button. And if I grab_control the Global_Mute_Button, then grab_midi stops reporting the MIDI changes corresponding to that control).

Am I misunderstanding how this is supposed to be able to work?

Hi folks, I’m attempting to override a subset of Push2s default controls from within a Max for Live Device.  With minimal success.  The documentation states for ‘grab_control’ that “This releases all standard functionality of the control, so that it can be used exclusively via Max for Live.”  (https://docs.cycling74.com/max8/vignettes/live_object_model?q=LOM)

But when I grab_control anything, such as Push’s control named Global_Mute_Button, I don’t get any control from within my Max for Live Device.  Instead the corresponding MIDI CC/Note message goes into the sequencer inputs (e.g.  the “Ableton Push 2 (Live Port)” input, MIDI CC 60 in the case of the Global_Mute_Button).  This hardly seems “used exclusively via Max for Live” and is not helpful for an Audio-type devices (which can’t get that MIDI info). 

When I enable “grab_midi” on Push2, I get MIDI outputs direct from the [live.object] in my device.  Similar output from something in my device is more-or-less what I am expecting is possible when I use grab_control.  (The grab_midi output itself is problematic for me because it doesn’t disable to default functionality of the Global_Mute_Button.  And if I grab_control the Global_Mute_Button, then grab_midi stops reporting the MIDI changes corresponding to that control). 

I also tried setting up a ‘MaxForLive’ control surface and did a register_midi_control and grab_control etc., but never achieved useful output.

In Live’s preferences > Link/MIDI, I have both Push2 and ‘MaxforLive’  control surfaces using “Ableton Push 2 (Live Port)” for their Inputs / Outputs.

I know it’s possible with some external max objects to get MIDI directly from certain ports into my M4L device, but that’s not ideal as it wouldn’t avoid the potential of other MIDI tracks getting undesirable MIDI CC/Note message inputs if they are receiving MIDI input from “Ableton Push 2 (Live Port)” or “All Ins”.



Hi folks, I’m attempting to override a subset of Push2s default controls from within a Max for Live Device.  With minimal success.  The docu

using-control_surface-grab_control-is-not-putting-midi-out-where-i-expect-it-push2

Attached are sample project (and corresponding amxd build) that reproduce the problem for me.  Per Facebook user group it _should_ work the way I expect, I'm probably just setting it up incorrectly.

When I drag this device into a track, the 'Mute' 'Solo' and 'Stop Clip' buttons are grabbed, but when I press their buttons I don't get any output within my device (which I'm expecting to see printed).


Thank you, I appreciate it!  So to summarize:

1. grab_control to takeover the control you want
2. get_control to get the id of the same control
3. Use that id to assign a [live.observer] to listen to this control (on the property 'value')

(In truth I had also tried testing with an observer, but hadn't set the property correctly…).

Perhaps I'd update the documentation for 'grab_control' to read:

Parameter: control
Take ownership of the control. This releases all standard functionality of the control, so that it can be used exclusively via Max for Live.  

The controls output can be obtained by observing its value property.

@SKEWBORG:

Thanks for this file, works great.

One question though, how would i address the grabbed Element from within live? 
Let´s say i want to light up the grabbed mute button, where would i send that command to?

Send to the control_surface live.object:

     call send_midi [ 176 | 144 ] [ control/pitch number ] [ value ]

For the Mute button is CC 60, so "call send_midi 176 60 127" will turn it on to bright red (I think), with different values changing the color.

Here's a rather sloppy diagram of the assignment mappings I pieced together a while back.  Green is for MIDI notes, and blue is for CCs.  If anything here is wrong you can reverse-engineer it yourself by getting the output from the control_surface while grab_midi is enabled.

thanks for your input but i´d rather use the same method as in the example, we do get the values from  a control and i know there´s a way to send messages to grabbed controls, besides the user mode, i just can´t figure it out myself :)

Hi Tyler, thanks for your effort but this doesn´t make sense for me We can access all control elementsthrough the api and do it with the script Skewborg posted, it would work two ways without having to go into usermode where you don´t have a display and so on.

The only problem here is that i have a hard time to find out how to acces an elemnt from live, like lighing up a button, based on his code.

The MIDI CC / note addresses from the diagram above are the same whether you are in User Mode or not, and you can change button colors with the same messages.  AFAIK there is no API-based way to set colors.

i think there is, here´s a fully working example, it checks for all available controls and makes them accessible from live to push and vice versa, without having to go into usermode.

The reason why i am asking for skewborgs´s help is that it is much more lightweight than what i am posting here.

can´t credit anyone because i don´t remember where i got it from, have fun.

AFAIK there is no API-based way to set colors.
---
Here´s the way to set colours via API.

Thanks Tyler for all your useful information. I am able to repeat what you have suggested to get the note buttons pressed on the Push2 to appear in Max for Live and able to set the colours by sending it a midi message. The problem I am having, only the "loud" notes played on the Push2 find their way through to Max for Live. Notes that usually go through fine when Live has control are totally ignored when putting Max in control only about a velocity of 50 on upwards gets any attention. It's like the default sensitivity controls have been ignored. Wouldn't have thought I need to override the sensitivity using the sysex commands to the Push2. Anyone else have the same problem or have found workarounds? My rough notes in the screen grab below.


I have done some more testing and have narrowed down the problem:

The translation from finger velocity (physical interaction between the human finger and the Push2) to the velocity that appears in Max for Live, is dependant on two things:

1. The Push2 "Pad sensitivity", "pad gain" and "pad dynamics", ok so this is the obvious one and makes sense.

AND


2. Whether the Push2 midi messages are sent to:

 2.1 Live then to Max (the default, i.e. receive via the Max midiin object)

OR
 2.2 Directly to Max (the  "call grab_control Button_Matrix" and "call get_control Button_Matrix" messages to live.object and setting up a live.observer to fetch what row,col and velocity was pressed).

Funky chicken hey? So the only work around I have is to do a calibration stage, twiddle the "Pad sensitivity", "pad gain" and "pad dynamics" Push2 knobs until a reasonable smooth response is obtained and the low end is responsive enough, then multiply that velocity by a further gain so the full range can be obtained.

So why on earth have the Ableton people done this? Tut tut tut!

Using control_surface grab_control is not putting MIDI out where I expect it (Push2)

TJ Spurge

**EDIT: I was able to resolve the issue by editing an existing max patch called Mappable Clip Legato by bencodec. **

Hello all. I am extremely new to M4L but I’ve learned enough to make a device which lets me move the start and end of the loop bracket in a specific clip slot. Now I would like to be able to go a step further and have the same ability in any currently playing clip. I think I’m supposed to be using highlighted_clip_slot or detail_clip but I’m stuck. Any suggestions on where in the reference to look or what to search for? Any suggestions about some patches I can look at with similar capabilities? I can provide the patch I made if anyone wants it. Thank You!

**EDIT: I was able to resolve the issue by editing an existing max patch called Mappable Clip Legato by bencodec. **

Hello all. I am extremely new to M4L but I’ve learned enough to make a device which lets me move the start and end of the loop bracket in a specific clip slot. Now I would like to be able to go a step further and have the same ability in any currently playing clip. I think I’m supposed to be using highlighted_clip_slot or detail_clip but I’m stuck.  Any suggestions on where in the reference to look or what to search for?  Any suggestions about some patches I can look at with similar capabilities? I can provide the patch I made  if anyone wants it. Thank You!

**EDIT: I was able to resolve the issue by editing an existing max patch called Mappable Clip Legato by bencodec. **

Hello all. 

setting-loopstart-and-loopend-for-highlightedclipslot

Setting loop_start and loop_end for highlighted_clip_slot?

Marc Assenmacher

Am am sending data from one device to multiple different devices in Ableton.

The sender device has a send object and every receiver device has an receive object coupled with a gate.

To select the receiving device I compare the current selected tracks id with the devices track id. If they match I open the gate, if they don't I close the gate.

It seems Ableton prioritizes devices in the current selected track and afterwards works through changes in other devices. Because of that, when changing the current selected track, I have a short time when gates are opened in two devices at the same time and data gets messed up.

I tried many different approaches like delayed banging etc. but nothing seems to work.

The only solution I can think of is specifically sending the data just to the device on the current selected track by id or something else.

Is there a way to approach that? Or does someone know another approach to try?

For anyone interest, here are my test devices. They contain some more unrelated stuff though.

Test - Receiving Device.amxd

Test - Sending Device.amxd

The sender device has a send object and every receiver device has an receive object coupled with a gate.
To select the receiving device I compare the current selected tracks id with the devices track id. If they match I open the gate, if they don't I close the gate.

It seems Ableton prioritizes devices in the current selected track and afterwards works through changes in other devices. Because of that, when changing the current selected track, I have a short time when  gates are opened in two devices at the same time and data gets messed up.

I tried many different approaches like delayed banging etc. but nothing seems to work.

The only solution I can think of is specifically sending the data just to the device on the current selected track by id or something else.

------

For anyone interest, here are my test devices. They contain some more unrelated stuff though.

Am am sending data from one device to multiple different devices in Ableton.
The sender device has a send object and every receiver device ... 

sendreceive-to-a-specific-device-in-ableton

send/receive can use the "---" prefix to the names (e.g. [receive ---MyDevice]) if you want to send to specific device.  (And use [forward] instead of [send] if you need to change targets).  

If you go that route you just need a way to share among all your devices that unique target name.  I've done this in the past by making a [dict] for the whole class of related devices that each device can write into.  Structured something like this: 

{
 "023MyDevice" : {
   "id" : "id 78",
   "unique_key" : "023",
   "parent_track_id" : "id 4"
   "receive_address" : "023ReceiveName"
 },
 "024MyDevice" : …
}

But also, maybe to solve your problem you can just observe the selected_track in each device instead of only in your "brain" device?  Send/Receive timing between devices always indeterminate.

prepend then send ID to your message and receive it with route. 


I know that I can use send/receive prefixes, but how do I get the prefix ids when I add devices in Ableton on the fly? Is there a way to retrieve the prefix ID after adding a device to a track? That would solve my problem!

I haven't used the forward object yet, but it seems suitable!

When I observe the selected track in every device the timing gets out of hand even more. I had it that way initially. In the end I will have about 60-80 receiver devices, so I though at least staring the process from one device will be more accurate than from 60-80 different devices. But it did not help to much.

@Double_UG:
This is a nice approach as well! But in the end I will send to all devices at the same time and filter out a the receiving end again. I think this will work but Tylers approach seems to be more performant to me.

Still I will try both ways and see which one works best! Thanks for the helps so far.

Ok, I implemented @TYLER MAZAIKA solution with send and forward and simply used the track id plus the tab number as unique id. This simplified my patches by an enormes amount, since I was able to solve two problems in one go. Simply amazing!

Cool, I'm glad that worked for you.  re: "Is there a way to retrieve the prefix ID after adding a device to a track?" 

Note that using the --- value may be more beneficial later if you need to be able to move your receiver devices around (in which case the track id may become invalid?).  But with that many receiver devices I'm gonna assume that there is one very particular way this will get set up :)  

Oh wow. I never knew that  --- is also replaces with a unique ID in messages. I though this is limited to send/receive objects only. Is there any documentation regarding --- ? I never found one.

I made the patches about purely for the purpose of testing. I my end product there will be some additions and changes.  But there will only every be one receiver device per track, so the track ID is suitable in my case.

Thanks regardless for your help and efforts. It helped a lot and will help me for future patching!

On the use of three dashes (---) to generate unique IDs, there is (rather well-hidden) documentation for Max near the end of https://docs.cycling74.com/max8/vignettes/dollar_sign_and_pound_sign and for Max for Live at https://docs.cycling74.com/max8/vignettes/live_symbols.

send/receive to a specific device in Ableton

Noah Giom

I'm working on a device that needs to change its behavior depending on whether a certain live.dial is being automated/modulated in Live vs if it is being dragged with the mouse or controlled with MIDI. Is there any way to get this information into the patcher? A boolean value would be ideal (1 if the dial is being automated/modulated, 0 if not).

I'm working on a device that needs to change its behavior depending on whether a certain live.dial is being automated/modulated in Live vs ... 

how-to-tell-if-a-live-dial-is-being-automatedmodulated

Look at the DeviceParameter api in the LOM, particularly the automation_state property.  It feels funny to set it up because you need to get the id of your device’s local dial just like it’s in a different device (e.g. get it through the LOM rather than normal Max code).

And actually if memory serves you may want “is_enabled” property too.

Thanks so much! That's exactly what I needed. I'm very new to the Live Object Model so I appreciate your help.

For anyone who might have the same question as me:
The automation_state property only reports automation, not modulation (when the parameter is being controlled by another device like Shaper or LFO). But in these cases the parameter is actually disabled, so I can tell if that's happening with the is_enabled property. Combining automation_state and is_enabled gives me a single flag to tell if the parameter is being controlled externally :-)

How to tell if a Live dial is being automated/modulated?

I am having this weird problem, that everything inside of a bpatcher opened with pcontol starts bugging after changing the selected track in Ableton. Opening the same content from a patcher does not make any problems.

pcontrol_Test.amxd

pcontrol_Test_bpatcher.maxpat

Any help/articles/information is appreciated!

------------------------------------------------------------------------ 

Add test device to a track in Ableton Live

patcher dial works, bpatcher dial does not work anymore

If yes, is it more likely a bug or is there an explanation and fix for this issue?

------------------------------------------------------------------------ 
Apple M1 Max
maxOS Monterey 12.6.5
Ableton Live 11.3.4
Max 8.5.4 (Full Version)

Hello,
I am having this weird problem, that everything inside of a bpatcher opened with pcontol starts bugging after changing the selected ... 

pcontrol-bpacther-bug-while-changing-selected-track

I found a workaround putting the bpatcher inside of a patcher. Still this doesn't seem right to me.

Although I found a workaround I would like to report this, if someone else can confirm this behaviour.

I only see one dial in the .amxd when I open the window, and none in the device view.  It seems to work okay when I switch tracks.  But I'm really not clear on what I'm supposed to be observing.

Is this one of these "I want the same UI to be visible and usable in both the device view and a separate window" kinds of things?  If so I would never trust those to work in Ableton the way they do in Max.  


<being speculation>

I'd suspect there is "magic" happening between Ableton/Max where Ableton lets Max devices know when they should be redrawing/updating their UI / able to respond to user interaction (mouse/keyboard).  If you have a portion of a device visible in two places at once (bpatcher in the Device View, and opened as a window), then Ableton is probably telling the Device View one it is not visible and shouldn't respond to user events when it's Track isn't selected or visible.  And since the window one and Device view [I'm guessing] share the same memory that flag applies to both of them.  

(It would be interesting to know how collapsing the device view or stuffing it in a Device Rack or Chain affects this, since changing Track isn't the only way to make a device "hidden" from the view).

In this case I'd guess your workaround works because, since the bpatcher is buried in a patcher and not normally visible in the DeviceView, Ableton/Max is not paying attention to that bpatcher view as something that needs to be drawn on the screen.  But in that case why not skip the bpatcher part.


If you do want to have "clone ui" in device view and a window it's pretty easy to do using pattr objects with @bindto.  Or if you're comfortable with Javascript to use MaxobjListener to get different objects to share values.  The trick with both is to make sure, if you're Automating controls, that you're careful about how the values get "round-tripped" between the views, so that you can still record and playback parameter automation.

Tyler is correct. When all (boxed) views of a bpatcher are closed/hidden, UI objects are not updated anymore. And a bpatcher view in a window is not officially registered as an opened view. The fact that you can still open the bpatcher in a window is a kind of easteregg in Max or C74 forgot to block this.  

Interesting. I kind of get it now. So I hope this behaviour will stay the same so my workaround will continue to work.

I don't think pattrstorage will work for me since I am having one device to control hundreds of devices and rack macros all over my Live set and I target them over the current track ID.

I bet javascript could help me out, but I haven't got into coding yet.

pcontrol bpatcher bug while changing selected track

I am currently working on a custom tab button.

I came up with this, which works perfectly. It is important to use the 

Tab Object within an example of what I need:

Sadly when implemented within my greater patch with 20 tab objects and 25 tabs, it absolutely kills my performance when switching between devices and triggering all 500 buttons at the same time.

Does anyone come up with an easier and better performing solution?

I am currently working on a custom tab button.


I am working on multiple Max For Live devices, but this is not necessarily related to M4L. 

I need a custom tab button where I can freely arrange the tab buttons.

I send the tab selection through send/receive from my MasterDevice to a SubDevice_n  – back and forth in both directions.

Both devices need to be able to change the value.

Of course there is no loop allowed, but SubDevice_n can not make use of "set" value.

I switch between SubDevice_1, SubDevice_2, SubDevice_3, ...    Everytime I switch the device, all my tab objects need to be set to the last values of the current device.

In the end I will have about 20 tab objects with 25 tab buttons each in my MasterDevice and equivalent 20 dials in my sub devices.

I came up with this, which works perfectly. It is important to use the INITIALIZE button.

Apple M1 Max
maxOS Monterey 12.6.5
Ableton Live 11.3.4
Max 8.5.4 (Full Version)

Hello,
I am currently working on a custom tab button.

--------------------------------------
Requirements:
I am working on multiple Max ... 

custom-tab-button

could you explain the logic in somewhat simpler relations ?
maybe I had more wine then allowed for this task, but I can't
see through the depenencies between tabs, devices , set or updated values, who controls what ? 
"master" seems to have stubborn 4 fields which are either all on or off ?

at the end - 500 GUI elements is not what you want.
Can you organise that 500 values to be controlled and updated
hidden, without any automation and other slowups from live system,
and bring only stuff needed to be visible to front ?

if I see it right you need 20 tabs, each having 25 buttons.
Maybe they controll something internally, separated, irrelevant,
but as you say :
every tab that is currenty visible, sets values for all other tabs ????
That would mean all 20 tabs share same button selection, no matter which of 20 tabs is in control.




To make the patch work you need to use the initialize button first!

I have just updated the patch with some additions to make everything more clear.  
Also you can use presentation view to better understand how it is supposed to work.

In the end I will have indeed 20 different tab objects with 25 buttons each and 500 UI elements with at least 264 visible at the same time. There can be the possibility to change that part of my project idea, but right now I am trying to find a fix.

I will think about your other questions and hopyfully come back with more feedback, but for right now I want to give your the opportunity to understand the problem. ;)

Also here is a patch with just the tab object. Because I think this is the part that needs improvement:

So to be clear, when you mean "tab" buttons you mean a set of buttons of which only one can be non-zero at a time (and also one MUST be non-zero at a time)?   And your desire is for them be arranged in positions on the screen other than what [live.tab] or [tab] object allow?

This seems like a case where, if at all possible, you want to code this in a typed language like JS rather than Max (especially for the number of objects you're talking about... loading lots of M4L devices that have tons of Max objects in them will always be much slower than equivalent code in JS).

But in Max you could save yourself some complexity and objects with a few tricks.  This would be easier to implement and scale better to the quantity of buttons you're looking at.

thanks a lot for this lesson. Your tab object is so much cleaner and better than mine. I will implement it and see how much my performance goes up.

In general I think I should start my project over in JS, but I have no coding experience so far. My project got pretty huge by now an I fear of letting down several month of work. :(

Ok, I implemented your solution and the performance got way worse. :D I will try something else tomorrow.

I think non working tabs in your first patches confused me.
once removed and ignored, one could see relation between 4 selected devices and master - sub dials.


here is a bit simplified link between master and 4 sub dial groups.
now just 6 of them as example, you can add as many as you wish.
and also add tabs to it in whatever configuration you want.
what matters is current selected number 0 - 24.



I would use number objects instead of live dials,
don't like the look of them, and they take too much space
on the screen.
this is only personal preference.


25 individual buttons per "tab" will be more difficult to implement in an efficient way.

would need a lot of patch cords or a bunch of send-receive or forward
objects, or scripting, but it is up to you to test that.



Thanks @SOURCE AUDIO. The gate switch combo is awesome! I implemented this in some form at various places in my project now and it makes things easier! 

By the way, I was able to reduce the performance load by combining my data with pak, pack, unpack, zl.change and not updating all the buttons at the same time.

With this I was also able to implement the way straight forward tab buttons from @TYLER MAZAIKA. ;)

Custom Tab Button

Michael DeFiore

As post title describes, I'm trying to append $1 (the actual text "$1") to a message. The Max Console returns--> "$" variable out of range (1). Is this just the equivalent of a compile warning or an actual error that need addressing? The code works fine otherwise. Any idea what best practice is here?

I'm trying to add a "$1" to the end of a message and store the result in a message box. Example: message [1 2 3] ---> [append $1] = [1 2 3 $1] stored in a message box.

Note that I tried [append /$1] but the result is (per example above) [1 2 3 /$1].

As post title describes, I'm trying to append $1 (the actual text "$1") to a message.  The Max Console returns--> "$" variable out of range (1). Is this just the equivalent of a compile warning or an actual error that need addressing? The code works fine otherwise. Any idea what best practice is here?

I'm trying to add a "$1" to the end of a message  and store the result in a message box. Example: message [1 2 3] ---> [append $1]  =  [1 2 3 $1] stored in a message box. 

Hi,
As post title describes, I'm trying to append $1 (the actual text "$1") to a message. 

append-dollar1-yields-dollar-variable-out-of-range-1-error

If what you say is correct - "append $1 to a message" there should be no error  all.
append $1 will append anyhing received in left top message
middle message appends $1  because of backslash.

I was trying to use the actual [append] object as in [append $1]. I see now that the message object itself accepts as input another message with an append in it. 

Many thanks Source Audio and Len! [append \$1] seems to work just fine.

[Append $1] yields "$" variable out of range (1) error

I realized today that I cannot use the --- for my buffer object I am using for gen.

Does anybody know a solution to create an unique name space in max for live within a gen~ ?

hi together,
I realized today that I cannot use the --- for my buffer object I am using for gen.
Does anybody know a solution to create an unique name space in max for live within a gen~ ?

hi together,
I realized today that I cannot use the --- for my buffer object I am using for gen.
Does anybody know a solution to create an ... 

buffer-name-for-gen

I believe you are mistaken. As long as you type the buffer name as an argument to the max [gen] object (as opposed to only inside the gen code) this should work.

thanks for the suggestion, but it is not working for me. also I would need the buffer length ...
but it seems already the @bufname is invalid.

Don't use "---bumi" in the gen~ patcher, use "bufname".

E.g. within gen~, use [buffer bufname],  [dim bufname], etc.   

The attribute "@bufname ---bumi" on the gen~ object tells the gen~ that where gen~ uses "bufname", it will map to whatever ---bumi is in Max. 

Super! Now I understood and it works just fine.
Thanks to both of you.

Is this somewhere described or maybe this falls more into the category of things which are just basic knowledge which I might not have :)


Cycling '74 Forums

Ok, thanks, it seems that somehow mc.jit.catch~ dependency is missing from the project, making it unable to freeze the device. Bit weird, I...

UPDATE : It only works with the beta version of Ableton 12.0.5.

https://www.sebairstein.com/sascalematrixamxd hi I patched this for everyone who continues to use a Push2. On the Live12 Beta it continues...

EDIT: I was able to resolve the issue by editing an existing max patch called Mappable Clip Legato by bencodec. Hello all.

On the use of three dashes (---) to generate unique IDs, there is (rather well-hidden) documentation for Max near the end of...

Thanks so much! That's exactly what I needed. I'm very new to the Live Object Model so I appreciate your help. For anyone who might have...

Thanks for your replies. Interesting. I kind of get it now. So I hope this behaviour will stay the same so my workaround will continue to...

By the way, I was able to reduce the performance load by combining my data with pak, pack, unpack, zl.change and not updating all the...

I was trying to use the actual [append] object as in [append $1]. I see now that the message object itself accepts as input another message...

Super! Now I understood and it works just fine. Thanks to both of you. Is this somewhere described or maybe this falls more into the...