Now, we'll come to a topic that really gives us wings. There are sometimes situations when we think "come on, doesn't this work in Max? It should!" and often, scripting is there to help us. For example, can you remember when we talked about attributes; I mentioned that some attributes can't be changed dynamically. Now, let's change them all!
Consider this situation: you build an oscillator and it doesn't have any MIDI in or the one in which you just want to give the user the possibility to determine the frequency in Hz or as a note. Simple enough. However, we don't want to have two dials and switch between them; we want one [live.dial]
, and we want to just switch units. Try to move the [live.dial]
object's unit attribute into the patcher to create a message box; it won't work. Alright, this might have something to do with the automations in Ableton Live and Max4Live devices, but we won't use our filter mini app in Live anyway. So, let's try something different...