myelin05

I'm new to Max for Live, working my through the tutorials, and I'm wondering if there is an existing patch to turn on/off a device in Live when a scene is launched?

I'm sure I'll slowly acquire the knowledge to make this myself, but I thought it's very likely that this device has already been made! Does anyone know of a device that does this, or can you point me to a tutorial that will help me build it?

I'm new to Max for Live, working my through the tutorials, and I'm wondering if there is an existing patch to turn on/off a device in Live when a scene is launched?  

I'm sure I'll slowly acquire the knowledge to make this myself, but I thought it's very likely that this device has already been made!  Does anyone know of a device that does this, or can you point me to a tutorial that will help me build it?

max-for-live-patch-to-turn-device-onoff-when-a-scene-is-launched

Maybe its easier to just automate the device to go on/off in the envelope settings of the midi/audio clip. No max for live device is needed for this,its a built in function :)

Thanks! That works perfectly. Never though of that solution before. :)

Thanks!  That works perfectly. Never though of that solution before.  :)


Try googling "Dummy clips" one of the most powerful things you can do in Live is send the audio to another track, put the monitor to "in" but still have clips there which modulate the incoming audio. Once you use it you'll never go back to having audio/midi data in the same clip as your automation.

http://abletonlife.com/a-detailed-guide-to-dummy-clips-in-ableton-live

Try googling "Dummy clips" one of the most powerful things you can do in Live is send the audio to another track, put the monitor to "in" but still have clips there which modulate the incoming audio. Once you use it you'll never go back to having audio/midi data in the same clip as your automation.
Heres a quick link :)
http://abletonlife.com/a-detailed-guide-to-dummy-clips-in-ableton-live


You must assign the on/off state of the device to a mocro to make this work.

A macro control was actually what I was trying to change, so this worked well. :)

I think its waste to map a Macro to the on/off button. Golden rule of Ableton Live.

The very last thing you clicked on or off/ or turned as a dial will be the 1st thing you see when you go into the clip/Automation settings (plus timeline). If you don't see it then turn off "Show only modulated parameters".

Macros are there to allow you to combine multiple parameters to one knob which can also have minimum and maximum/inverted values.

Try assigning a dial to a macro and the on/off button but set the threshold (in macro mapping) for the on/off button to a number like 2. Then when you turn the knob to 1 or 0 then it also turns off the effect, an incredibly powerful feature in a live situation which frees up a button on your midi controller.

And don't forget you can make a macro group within another macro group, this allows for amazing nested options where you can control over a 100 parameters with one knob, overkill, but its possible.

I think its waste to map a Macro to the on/off button. Golden rule of Ableton Live.
The very last thing you clicked on or off/ or turned as a dial will be the 1st thing you see when you go into the clip/Automation settings (plus timeline). If you don't see it then turn off "Show only modulated parameters".
Macros are there to allow you to combine multiple parameters to one knob which can also have minimum and maximum/inverted values.
Try assigning a dial to a macro and the on/off button but set the threshold (in macro mapping) for the on/off button to a number like 2. Then when you turn the knob to 1 or 0 then it also turns off the effect, an incredibly powerful feature in a live situation which frees up a button on your midi controller.
And don't forget you can make a macro group within another macro group, this allows for amazing nested options where you can control over a 100 parameters with one knob, overkill, but its possible.


Since we're on the topic of macros, I've got another question for you. I like to assign macros 5-8 to toggle switches on my nanoKontrol2 to turn on and off effects when I'm playing keyboard patches. The nanoKontrol2 supports midi feedback, so if I turn on a macro in Ableton, the led reflects that on the controller, but when I switch devices to control 8 different macros, I always have to hit the toggle button once so they can sort of get on the same page. Then after that, the leds on the controller and the values in Ableton are synced up. Is there a workaround to avoid this initial hiccup? I'm just using a user remote script for the macro mapping, could that be the issue? It's really annoying to have to press a toggle button once before it's truly synced up with Ableton. I could use knobs for the macros, but I like to be able to use buttons because I can hit two or three simultaneously with one hand.

Since we're on the topic of macros, I've got another question for you.  I like to assign macros 5-8 to toggle switches on my nanoKontrol2 to turn on and off effects when I'm playing keyboard patches.  The nanoKontrol2 supports midi feedback, so if I turn on a macro in Ableton, the led reflects that on the controller, but when I switch devices to control 8 different macros, I always have to hit the toggle button once so they can sort of get on the same page.  Then after that, the leds on the controller and the values in Ableton are synced up.  Is there a workaround to avoid this initial hiccup?  I'm just using a user remote script for the macro mapping, could that be the issue?  It's really annoying to have to press a toggle button once before it's truly synced up with Ableton.  I could use knobs for the macros, but I like to be able to use buttons because I can hit two or three simultaneously with one hand.


I'm not sure about the user remote script. I do know that most controllers with live need a very very specific user script to be constantly updated,

Live only sends midi data back if something actually happens with macros, eg. If no knobs are being automated then Live doesn't send any data, this means the nanocontrol 2 doesn't update.

The toggle button pretty much forces live to send out the parameter positions without having to turn them.

I'd advise getting a more up to date user remote script.

I'm not sure about the user remote script. I do know that most controllers with live need a very very specific user script to be constantly updated,
Live only sends midi data back if something actually happens with macros, eg. If no knobs are being automated then Live doesn't send any data, this means the nanocontrol 2 doesn't update.
The toggle button pretty much forces live to send out the parameter positions without having to turn them.
I'd advise getting a more up to date user remote script.
Good luck.


Thanks for the very helpful suggestions, do you by chance know how to make a user or remote script that updates the nanoKontrol2 automatically as you say? Or perhaps there is a magical max for live patch that does this updating for us?! I've just been using an edited version of the basic user remote script that comes with Live.

Thanks for the very helpful suggestions, do you by chance know how to make a user or remote script that updates the nanoKontrol2 automatically as you say?  Or perhaps there is a magical max for live patch that does this updating for us?!  I've just been using an edited version of the basic user remote script that comes with Live.


Max for Live patch to turn device on/off when a scene is launched?