Tutorials

Max for Live Best Practices, Part 2

Welcome to the second part of our tutorial series specifically designed for Max for Live users who are interested in creating their own devices.

We will suggest tips and practices that will help you work smarter as a developer and help create a good user experience — for others, or just for you. We’ll share best practices for patching, and provide advice about how to avoid common problems you may encounter in developing your Max for Live devices.

In this video, I'll concentrate on some basic UI design approaches, including working with Live 10 themes, Live device width and good design, and best practices for working with live.* objects.

I'll also be looking at issues related to performance, including OS compatibility, avoiding problems with Undo history, device latency, and device updating.

(Download the Max for Live Production Guidelines discussed in the video.)

Learn More: See all the articles in this series

by Tom Hall on January 8, 2020

video
Creative Commons License
Florent Ghys's icon

Florent Ghys

thanks for doing this!!

what would be the best practice if one wants to control internally a live.object while at the same time being "automated and stored" and without clogging Ableton Live's undo history?

live.remote~? but going into the signal domain sounds overkill for some low priority Max messages within MIDI devices
having two parallel and separated circuits, one internally-controlled and "hidden" while the other is "automated and stored"?
other ideas?