Hey people!
First-time poster here. Have been lurking around the forum for around a year now, and already learned so many new things, it’s a really cool place you have going! I thought if I’d join the conversation it would be nicer and maybe eventually I could even give back something!
I’ve been trying to transition my modular workflow more into Ableton throughout this past year, and every now and then I end up banging my head against the wall for some seemingly simple thing that I just can’t figure out by myself. One major thing that I often find myself lacking is some triggerable sample and hold-thingy, that would let me hold a modulation value (say, from a M4L LFO) whenever “something” happens (say, MIDI note is triggered). I thought I had a breakthrough a couple of days ago when I found this Modulation Tools Set M4L pack that seemingly does what I need, but unfortunately it also had it’s problems…
The Sample and Hold module in that pack would be ABSOLUTELY PERFECT, if it wouldn’t break the undo history of Ableton whenever it’s triggered. I tried to look into the problem and found there’s lot’s of conversation about it online, but since I have no experience with programming anything with M4L, I’m not quite sure if this is something that could be fixed or not. I tried this one proposed solution (https://help.ableton.com/hc/en-us/articles/209066909-Unable-to-undo-due-to-certain-Max-for-Live-devices) of settings the “Parameter Visibility” to “Hidden” in the device properties, but as a consequence the trigger input wasn’t mappable anymore…
Does any of you use some sort of sample and hold M4L tricks in your Live sessions? Am I missing something obvious? What’s your solution?
Cheers and thank you for any input!