ā¦make stuff?
Seriously, Iāve always learned good things by having an idea and then just trying to implement it in Live, rather than getting bogged down in tutorials. Thatās a never-ending path to get lost on.
Also it opens you up to finding things by accident. Plenty of that in Live.
(Examples off top of head - use a rack to create a wet/dry control on any set of chains; automate enable on/off for heavy racks on individual scenes; turn any channel into an oscillator using a gate or env follower and play live like a synth; create a matrix mixer using the return channels and play with feedback; instant franken-poly by sending midi to multiple channelsā¦Etc etc.)
Something that really helped me recently was doing a lot more Max programming. Trying to implement basic Live features makes you see how much is packed into Live, and appreciate it.
Live can be used like a daw, or like a modular, and you can record the output of the master in some other app. Itās fun to stop-start the sequencer to trigger stuff and then record tails. You canāt do that within Live because recording is locked to the sequencer.
Live is also great as an audio router or midi router. You buy some latency but often it doesnāt matter. Being aware of latency was a big level up for me with Live. Most of that was experimenting, you have to become a bit of a scientist! Do tests. I have a huge folder of test sessions with a single idea in them. This helps you understand the session directory structure and the role of all the files. āCollect All and Saveā is very important :]
+1 on the manual too, very high quality. Reading the info box for everything is highly recommended.
