1. Controlling MXW through JavaScript: Difference between revisions
No edit summary |
No edit summary |
||
| Line 2: | Line 2: | ||
JavaScript allows instead to script any animation and behaviour sequence. Additionally, JavaScript allows you to emit values to I/O devices like DMX, OSC or MIDI and set various internal variables in media and in the software. | JavaScript allows instead to script any animation and behaviour sequence. Additionally, JavaScript allows you to emit values to I/O devices like DMX, OSC or MIDI and set various internal variables in media and in the software. | ||
The JavaScript engine used by the MXWendler scripting is Duktape, standardized under ECMAScript E5/E5.1. (more info at the Duktape [https://duktape.org/index.html website]) | |||
ADD INTERFACE INFORMATIONS (HOW TO PROGRAM SCRIPT IN THE MXW GUI AND SCREENSHOTS) | |||
To facilitate debugging, a script-wide function "print_console" is available. | To facilitate debugging, a script-wide function "print_console" is available. | ||
Revision as of 10:39, 3 November 2022
Although there are many ways to control MXWendler with a lot of I/O devices, e.g. mouse buttons, keyboard, DMX and MIDI devices, and automation commands in MXWendler using events in the playlist, some desired behaviours are too complex to be offered through a GUI element. JavaScript allows instead to script any animation and behaviour sequence. Additionally, JavaScript allows you to emit values to I/O devices like DMX, OSC or MIDI and set various internal variables in media and in the software.
The JavaScript engine used by the MXWendler scripting is Duktape, standardized under ECMAScript E5/E5.1. (more info at the Duktape website)
ADD INTERFACE INFORMATIONS (HOW TO PROGRAM SCRIPT IN THE MXW GUI AND SCREENSHOTS)
To facilitate debugging, a script-wide function "print_console" is available.