Preview Mode

After opening a Live device in Max for editing, there are two copies of the device -- the one you are editing and the one inserted into a track in Live. Preview Mode permits you to listen to the device you are editing while Live runs in the background. The copy of the device inserted in the Live track is disabled.

Audio, MIDI, timing, and messages (including Live API commands) are sent between Max and Live in order to make this happen.

Preview Mode is always enabled when you begin to edit a device in Max.

Uses of Preview Mode

• You can turn preview mode off as you are editing a device to compare the edited version of a device with the original version.
• You can turn preview mode off after saving a device to see how its user interface appears in the Live device view.
• Preview mode will increase the latency of a Live device slightly. Turn preview mode off to hear the device with its original defined latency.

Preview Mode Caveats

• The memory state of Max objects is not made consistent between devices as you enable and disable preview mode. For instance, if you change a number box to 74 in a device in Live and then edit the device, the number box will be set to zero when the edited version is opened.
• However, parameter state will be updated when toggling preview mode. If you set a live.dial to 47 in Max, then disable preview mode, the dial will be updated to 47 in Live. If you then set the dial to 61 in Live, then enable preview mode again, the dial will be updated to 61 in Max.
• Changes to parameter values in Max while in preview mode are undoable in Live.
• Preview mode implements communicating between a send object in Live and a receive object in Max (or vice versa), but the performance of the communication will be reduced compared to the performance of send and receive within a single application.
• The grab object cannot communicate with a receive object unless both objects are in the same device, so you cannot use grab to communicate between devices in preview mode.
• Some Max objects monopolize a resource on your computer. The udpreceive object, for example, reserves a UDP port for itself so that no one else can access the port. This has the potential to create problems when you have two udpreceive objects in two copies of the same device. In this specific case, we have made the UDP objects release the port when they are disabled as a result of a preview mode switch. However, other third-party objects with similar resource-monopolizing issues may not work properly with preview mode.
• Max objects that share data via symbolic names, such as table, coll, and buffer~, do not share data across the boundary between Max and Live. For instance, if you have sample data loaded into a buffer~ object named toto in Live, and you edit another device with a buffer~ object named toto, the buffer~ object in the device in Max will not share data with the object in Live.