Ableton Forum

Didn't look at your patch, but from what you describe I bet that you're triggering events based on a live.path object and using the second outlet (follow path). Anytime anything in the Live Object Model is changed (adding or removing tracks, clips, etc.), the second outlet of a live.path object re-s...

11olsen wrote:The 2 alternating clips method sounds good, but on the controller side u still use 8 or 16 buttons and a patch is managing the 2 clips, right?

Correct, the fact there are two clips alternating is abstracted away from the interface.

what's the difference between using live itself to create copies of a clip with offsetted startpoints and some follow actions and the MLR method? In order to get the level of control you'd want from a clip chopper (a button mapped to at least each 1/8th note within a loop), you'd have to create a s...

just to clarify what i meant by the buffered system: i wouldn't have any of the audio that i want to chop in live clips. it would all be stored in msp buffers from the get go (or you could record in with a record~ object). you'd simply use blank midi clips to launch certain samples, and you could l...

for a while i've been meaning to finish off some devices doing it in msp instead of with the live api: a sample bank device with a polybuffer~ object which saves all the samples you load with the set; a recorder device which you can drop onto different tracks to record into the polybuffer~; a playe...

I've been out of the Max 4 Live game for over a year now, but dusting off my performance patch for an upcoming show had me all riled up about this issue again. I know this was an issue a lot of people were vocal about when M4L was first released (myself included), and I was hoping with all the time ...

I also created a M4L patch that automatically triggers the next clip in a channel once it reaches the end of the current clip can't you just do this with "follow actions", w/out M4L? No, follow actions only allow you to dictate after how many bars from trigger of the clip should the next ...

Ha, what a coincidence. I use an eerily identical system. I have a DJ template als file with 4 "decks" (channels) with routing setup for my mixer. I create a folder for each genre of music, and create a new als file for each song, labeled "bpm - artist - title". I drop the mp3 in...

if the monome patches you are trying to use are written in Max For Live, the only way to use them is if you own a copy of Max For Live.

For some reason the documentation page that explains this isn't online, but it's a "vignette" called "Live Symbols" or "Using Symbols in Max for Live" and should be on your hard drive. Yeah, I searched through the online documentation, which is apparently not complete....

It's in the documentation somewhere. They did it a little bit differently in Max then in M4L. So, some people do not realize this. I am glad I can be of help. I really like what you are doing with the Ms Pinky stuff. I hope to contribute soon. Mike Ha, you already contributed. Now the next version ...

send ---name and receive ---name sounds like what you are looking for. The three dashes make the name unique to your current patch. So, just add three dashes to the name of the coll. I hope this helps. Great, thanks for the quick reply! I'll have to try this out when I get home from work. Out of cu...

This question might be better suited for the Cycling '74 forums, but it deals specifically with problems with my M4L patches, so I'll throw it out here as well. In my patches, I like to use a lot of send and receive objects as well as named coll objects to help make an easy-to-read workflow. However...

Still keen to revive this thread! How about this one: So far we have no access to the file path of clips in Live. However if you follow a consistent naming policy then you can derive the file name from the clip name (which you do have access to). As long as the file resides somewhere in Max's file ...

Hmm, lots of good fixes in the release notes. A bit weary of trying this due to the fiasco of the last Max update requiring a version of Live that wasn't out of beta yet.

Anyone want to be the guinea pig that tries it and reports back?