Jitter and Max for Live

Users who wish to combine Jitter modules in their Max for Live devices should seek out Part 1 and Part 2 of the online Best Practices in Jitter tutorials as a place to start.

Recommendations for Using Jitter in a Max for Live Device

Here are some specific recommendations for using Jitter in a Max for Live device:

• If you are using Vizzie in a Max for Live device, you will need to use a PROJECTR module or a vs.projectr Vizzie abstraction in your device.
• If you are using jit.world in a Max for Live device, you will need an implicitly named context or a --- (triple-dash) named context.
• When you export a Max for Live project which includes a named context, a new instance of that context will be created during the export to the .amxd device. If the patch that includes that named context is open when you export the Project, you will see an error in the console that ob3d does not allow multiple bindings. The patch you're working on will no longer work as expected until you close it and then relaunch it after your export.
• Jitter operates in Ableton Live’s interface update thread. This has two major effects:
• Jitter frame updates will be interrupted by the Live application’s interface redraws.
• The maximum frame rate is dependent on the Ableton application’s audio buffer size.