Push 3, automate audio clip parameters ?

[[jur]]

It was a genuine question about doing this natively from Push.
That said, the discussion about the possibility of doing this with M4L and parameter automation is quite interesting ! I'm too stupid to answer the question without actually trying to patch it...
So let's prove it's possible...or the contrary

Hope this is what you were looking for ...

https://unavisionagradable.gumroad.com/l/gqxrmv

What's the result then?
The automations apply to the currently selected clip in the parent track of the device I suppose?

[AlexDLarge]

The device is dynamically applying the automations to the playing clip. As you said in a previous post, if you trigger CLIP A the device will control the clip’s A pitch and gain, and by turning “off” observe you can have animations to those parameters stored in that audio clip. If you hit CLIP B, the device will now control that new clip and if it has an already stored automation it will animate it.

In a future update I will include an option to control several clips from other tracks with the controls and automation from a single clip. I don’t know if this is going to be so useful but I think it could be weird enough to have a try. Also it could be interesting to create the automations on a midi track and the send the mappings dynamically to other audio tracks …

[chapelier fou]

@AlexDLarge :

Thanks, I'm a quite experienced M4L user, so I didn't need this (and posted code above), but it will probably be useful to others !

A few notes on your patching, if you don't mind ?

- any [print] object should be removed when you share a device.
- seeing the two messages "del 5" and "del 20", that's a red light for me. Usually this could be much cleaner, waiting for operation results to trigger the next actions in the right order.

[AlexDLarge]

Yeah, I made this while traveling from a shooting so didn’t pay much attention to the patch “cleaning” …

[chapelier fou]

No probs, I read somewhere that you were relatively new to Max (really impressive achievements so far !) so that's why I allowed myself to point these little "issues".
(Also bought your MTR sequencer because I was curious, and also thought that there was room for cleaning the patch)

[AlexDLarge]

Yeah, thanks a lot.

To tell you the truth I discovered the “trigger” object a couple of weeks ago! I need to redesign some of my devices and get rid of all those “delays” and so on. Now I’m working on a global preset storer and those “trigger” objects with “bang” sequences are wonderful!

Thanks for the tips and the support!

[chapelier fou]

“trigger” object

Maybe the most important object in Max !

[AlexDLarge]

Absolutely!! I don’t know how I’ve been able to do things without it! I need to go back to the basics and revisit some of the “less fancy but so useful” objects in Max!