MIDI I/O works only when using preview mode. MIDI input arrives from Live and MIDI output is sent to Live.
When authorized only via Live, the Max application will not use its own MIDI drivers. The use of the send~ and receive~ objects to pass audio between Max for Live devices is not supported. If Max and MSP are authorized when editing a Live device, Max Consoles that are not a part of the Live device will use the regular Max audio drivers. If you open a file with dac~ or adc~ objects when you are not editing a device, or when Preview Mode is turned off, you will not hear any sound. When you open a Max patcher such as a help file, the dac~ objects in the patcher will be mixed with the output of the device you are currently editing. Input and output are limited to two channels (MSP supports up to 512 channels of audio I/O). If you turn preview mode off, all audio I/O for the Max application will stop. Its audio input is the input to a Max device you are editing, and its audio output is the output from that Max device. When authorized only via Live, the Max application will not use its own audio drivers. The grab object cannot be used to communicate from a send to a receive between devices. But the Live authorization state can only be set properly when launching from Live.Ĭommunication between devices using send and receive is supported, but there may be some latency involved when sending data between devices. In other words, your fully authorized copy of Max is never limited by launching the application via Live.Īnother way to put it is this: Max can determine its own authorization state whether you launch it from the OS or from Live. If you own both Max and Max for Live, you can launch Max either way, but you will only obtain Live's authorization if you launch Max by clicking the edit button in Live.Īny limitations imposed by a Live authorization will not exist when Max is fully authorized (or when it is in demo mode). Once Max's demo mode has expired, if you do not own a Max authorization, you can only launch Max by clicking on the edit button in Live. If you have purchased Max for Live, Max devices will have an edit button in Live that will launch Max and open the specified device.
MSP and Jitter work during demo mode, but after that, they require product-specific authorization. Note that when launching Max via Live, you will not see the demo dialog, nor will you be informed when the demo period expires.Ī Max authorization comes in three varieties: you can purchase Max alone, or Max/MSP to work with audio, or Max/MSP/Jitter to work with both audio and visual media.
Max msp trial windows#
Once demo mode expires, you will not be able to launch Max from the Finder or Windows Explorer without purchasing an authorization from Cycling '74. Click the Demo mode to continue launching Max. You will see a dialog informing you of the remaining demo period that also permits you to authorize the software.
Max msp trial mac os#
During the demo period, you can launch the Max application by double-clicking on it from the Mac OS Finder or Windows Explorer. Max's own copy protection and authorization system starts in demo mode, typically a one-time 30-day period in which it is fully functional. Before we describe these limitations, it's worth describing how Max will be in any particular authorization state. When the Max application receives its authorization from Live alone, a number of limitations apply. Max can be running on its own authorization, via a Live authorization, or both.
Max for Live is integrated with Max's own copy protection and authorization system.