MXWendler Wiki - Recent changes [en]

File:WII 03.PNG

Admin — Sun, 09 Aug 2026 18:14:49 GMT

Admin deleted page File:WII 03.PNG content before blanking was: ""

File:WII 02.PNG

Admin — Sun, 09 Aug 2026 18:14:42 GMT

Admin deleted page File:WII 02.PNG content before blanking was: ""

File:TUIO 3.png

Admin — Sun, 09 Aug 2026 18:14:33 GMT

Admin deleted page File:TUIO 3.png content before blanking was: ""

File:TUIO 2.png

Admin — Sun, 09 Aug 2026 18:14:28 GMT

Admin deleted page File:TUIO 2.png content before blanking was: ""

File:TUIO 1.png

Admin — Sun, 09 Aug 2026 18:14:24 GMT

Admin deleted page File:TUIO 1.png content before blanking was: ""

Tutorial Connecting a Wiimote to MXWendler

Admin — Sun, 09 Aug 2026 18:14:19 GMT

Admin deleted page Tutorial Connecting a Wiimote to MXWendler content was: "This tutorial applies to Windows only, and all MXWendler versions. <div class="noprint"> == Introduction== </div> In this tutorial we are going to connect a Wiimote to MXWendler Stage Designer and assign the movement of the controller to a pivot of a keystone element. == Connecting the Wiimote to the Operative System == 1. Set a Bluetooth connection on your computer. (eg....", and the only contributor was "Behrooz" (talk)

Triggering Effects with TUIO

Admin — Sun, 09 Aug 2026 18:14:15 GMT

Admin deleted page Triggering Effects with TUIO content was: "TUIO is a protocol intended to connect multitouch environments such as laser scanners, multitouch tables, etc. to interactive installations. It is based on OSC, which itself is the network-based successor to MIDI. Today, many common devices can send TUIO, including IPhones, IPads, Android devices, Kinect Controllers, Wii Controllers and many more. Using TUIO in your setup is...", and the only contributor was "Behrooz" (talk)

Tutorial Controlling StageDesigner with Elgato Streamdeck

Admin — Sun, 09 Aug 2026 18:14:10 GMT

Admin deleted page Tutorial Controlling StageDesigner with Elgato Streamdeck content was: "This tutorial applies to Windows only, and all MXWendler versions. <div class="noprint"> == Introduction== </div> In this tutorial we are going to connect a Wiimote to MXWendler Stage Designer and assign the movement of the controller to a pivot of a keystone element. == Connecting the Wiimote to the Operative System == 1. Set a Bluetooth connection on your computer. (eg. a norm...", and the only contributor was "Admin" (talk)

Tutorials

Admin — Sun, 09 Aug 2026 18:13:18 GMT

Remove mis-titled Streamdeck tutorial link (page was a Wii-tutorial copy, being deleted)

← Older revision		Revision as of 20:13, 9 August 2026
(One intermediate revision by the same user not shown)
Line 54:		Line 54:
	*[[Tutorial Set up the CITP Footage Library on the Media Server]]		*[[Tutorial Set up the CITP Footage Library on the Media Server]]
	*[[Tutorial Time-sync and sending IO Commands over OSC Protocol]]		*[[Tutorial Time-sync and sending IO Commands over OSC Protocol]]
	*[[Tutorial Connecting a Wiimote to MXWendler]]
	*[[Tutorial Controlling MXWendler via TouchOSC]]		*[[Tutorial Controlling MXWendler via TouchOSC]]
	*[[Tutorial Optimum Audio Settings with an Integrated Audio Interface]]		*[[Tutorial Optimum Audio Settings with an Integrated Audio Interface]]
	*[[Tutorial Optimum Audio Settings with an External Audio Interface]]		*[[Tutorial Optimum Audio Settings with an External Audio Interface]]
	*[[Tutorial Controlling StageDesigner with Elgato Streamdeck]]
	*[[Tutorial Eventmaster Toolset Controlling MXWendler by e.g. e2 S3 Image Processor]]		*[[Tutorial Eventmaster Toolset Controlling MXWendler by e.g. e2 S3 Image Processor]]

Triggering

Admin — Sun, 09 Aug 2026 17:25:22 GMT

Remove link to TUIO tutorial (feature removed)

← Older revision		Revision as of 19:25, 9 August 2026
Line 5:		Line 5:
	*[[Events / Widgets and Their Addresses / Intrinsic Values]]		*[[Events / Widgets and Their Addresses / Intrinsic Values]]
	*[[Examples of events]]		*[[Examples of events]]
	*[[Triggering Effects with TUIO]]

About Events

Admin — Sun, 09 Aug 2026 17:25:21 GMT

Remove TUIO/Wii from trigger tool list (feature removed)

← Older revision		Revision as of 19:25, 9 August 2026
Line 6:		Line 6:
	1. Open 'DMX/MIDI/Keyboard Events' in the settings: '''(A)'''		1. Open 'DMX/MIDI/Keyboard Events' in the settings: '''(A)'''
	:'''Menu: Settings → IO Devices → DMX/MIDI/Keyboard Events'''		:'''Menu: Settings → IO Devices → DMX/MIDI/Keyboard Events'''
	2. Determine the trigger by selecting the respective tool: DMX, MIDI, Keyboard, Timer ~~or TUIO (also Wii running Windows)~~. '''(B)'''		2. Determine the trigger by selecting the respective tool: DMX, MIDI, Keyboard or Timer. '''(B)'''

	3. Create an event with the '+' button. '''(C)'''		3. Create an event with the '+' button. '''(C)'''

Hardware

Admin — Sun, 09 Aug 2026 17:25:20 GMT

Remove TUIO and WiiRemote controller support (feature removed)

← Older revision		Revision as of 19:25, 9 August 2026
Line 28:		Line 28:
	*DMX supported ( Enttec, Soundlight, e:cue )		*DMX supported ( Enttec, Soundlight, e:cue )
	*OSC supported		*OSC supported
	*TUIO supported
	*Art-Net supported		*Art-Net supported
	*Windows: WiiRemote controller supported
	{{#mpdftags: pagebreak}}		{{#mpdftags: pagebreak}}
	Memory		Memory

Python plugin reference

Admin — Sun, 09 Aug 2026 16:00:35 GMT

docs: audio streams — mxw.audio capture + audio-producing media plugins (device-rate adaptive)

← Older revision		Revision as of 18:00, 9 August 2026
Line 80:		Line 80:
	\|-		\|-
	\| <code>plugin_playlist_playbackmode_default</code> \|\| Optional. The clip playback mode a freshly added clip of this media starts in: <code>stop</code>, <code>loop</code>, <code>oneshot</code>, <code>bounce</code>, <code>jitter</code> or <code>random</code>. Omitted or unknown defaults to <code>loop</code>. Only seeds the initial mode - a project reload restores the clip's own saved mode.		\| <code>plugin_playlist_playbackmode_default</code> \|\| Optional. The clip playback mode a freshly added clip of this media starts in: <code>stop</code>, <code>loop</code>, <code>oneshot</code>, <code>bounce</code>, <code>jitter</code> or <code>random</code>. Omitted or unknown defaults to <code>loop</code>. Only seeds the initial mode - a project reload restores the clip's own saved mode.
			\|-
			\| <code>plugin_media_has_audio</code> \|\| Optional. <code>1</code> to enable audio output: the host pulls <code>onRenderAudio()</code> and mixes the PCM into the master.
			\|-
			\| <code>plugin_media_audio_channels</code> \|\| Optional (default <code>2</code>). Channel count of the produced audio. There is '''no''' sample-rate key – the rate always follows the output device (see Audio, below).
	\|}		\|}

Line 165:		Line 169:
	\|-		\|-
	\| <code>onRenderFrameGL(frame, texture, width, height)</code> \|\| returns <code>bool</code> \|\| Approach 3: render '''directly into the media texture''' — <code>texture</code> is its raw GL handle. Return <code>True</code> when the frame is in the texture; the pixel upload path is then skipped. Tried before <code>onRenderFrame</code>; a plugin implements one of the two.		\| <code>onRenderFrameGL(frame, texture, width, height)</code> \|\| returns <code>bool</code> \|\| Approach 3: render '''directly into the media texture''' — <code>texture</code> is its raw GL handle. Return <code>True</code> when the frame is in the texture; the pixel upload path is then skipped. Tried before <code>onRenderFrame</code>; a plugin implements one of the two.
			\|-
			\| <code>onRenderAudio(num_frames)</code> \|\| returns interleaved float32 \|\| Audio-producing media: return ''num_frames''×channels interleaved '''float32''' samples (bytes / bytearray / numpy). The host pulls exactly the frames needed for a gapless cushion. Enabled by <code>plugin_media_has_audio</code>; generate at the injected <code>audio_samplerate</code> (see the Audio section).
	\|-		\|-
	\| <code>onClose()</code> \|\| — \|\| The media is destroyed: release per-instance resources.		\| <code>onClose()</code> \|\| — \|\| The media is destroyed: release per-instance resources.
Line 186:		Line 192:

	Parameters are addressed exactly like shader effect parameters, e.g. <code>/mxw/track/2/layer/1/clip/media/1/param/1 0.8</code> or, for a <code>"string"</code>-typed param, <code>/mxw/track/2/layer/1/clip/media/1/param/2 "https://www.mxwendler.net"</code>. The <code>media/1</code> segment reflects the clip's single active media slot (any other index is out of range). Because the host does not persist a param's value, a plugin that wants one to survive a project reload must fold it into its own <code>onSave()</code>/<code>onLoad()</code> and hand the restored value back as <code>onGetParams()</code>'s <code>"default"</code> — which runs after <code>onLoad()</code> already restored the instance state.		Parameters are addressed exactly like shader effect parameters, e.g. <code>/mxw/track/2/layer/1/clip/media/1/param/1 0.8</code> or, for a <code>"string"</code>-typed param, <code>/mxw/track/2/layer/1/clip/media/1/param/2 "https://www.mxwendler.net"</code>. The <code>media/1</code> segment reflects the clip's single active media slot (any other index is out of range). Because the host does not persist a param's value, a plugin that wants one to survive a project reload must fold it into its own <code>onSave()</code>/<code>onLoad()</code> and hand the restored value back as <code>onGetParams()</code>'s <code>"default"</code> — which runs after <code>onLoad()</code> already restored the instance state.

			=== Audio ===

			A media plugin can also '''produce''' audio: implement <code>onRenderAudio(num_frames)</code> returning ''num_frames''×channels interleaved '''float32''' samples, and set <code>plugin_media_has_audio = 1</code> in the manifest (channel count via <code>plugin_media_audio_channels</code>, default 2). The host pulls exactly the frames it needs each render frame into a gapless lookahead cushion, so the sound survives render-loop hitches.

			The '''sample rate always follows the current output device''' – there is no sample-rate manifest key. The host injects the live format as the module globals <code>audio_samplerate</code> and <code>audio_channels</code> (like <code>media_id</code>) before every call; generate at <code>audio_samplerate</code> and the audio adapts if the device is reopened at another rate. (An optional <code>onAudioFormat()</code> returning <code>(rate, channels)</code> may declare the channel count; its rate is ignored.)

			To '''consume''' audio (audio-reactive media), read it with the <code>mxw.audio</code> capture API – see the [[Python command reference]]: <code>mxw.audio.output_capture()</code> for the master mix or <code>mxw.audio.input_capture()</code> for the input device.

	=== OpenGL rules for media plugins ===		=== OpenGL rules for media plugins ===

Python command reference

Admin — Sun, 09 Aug 2026 16:00:34 GMT

docs: audio streams — mxw.audio capture + audio-producing media plugins (device-rate adaptive)

@@ Line 208: / Line 208: @@
 |-
 |<code>mxw.grabber("name").getData()</code> || return the grabber's pixels as a byte list (RGBA, width&times;height&times;4) || <code>px = mxw.grabber("cam").getData()</code>
 |}

Tutorial Opening Different Media

Admin — Sat, 08 Aug 2026 19:27:24 GMT

← Older revision		Revision as of 21:27, 8 August 2026
Line 11:		Line 11:

	MXWendler supports nearly all industry-standard grabber- and live input hardware components through Quicktime and DirectShow interfaces. Grabbers for BNC, DVI and SDI video are possible. Latency can be reduced to a minimum, down to under 0,08 seconds, by overclocking the system. Webcams and NDI can be used as live video sources as well. See also: [[Tutorial NDI Tools]].		MXWendler supports nearly all industry-standard grabber- and live input hardware components through Quicktime and DirectShow interfaces. Grabbers for BNC, DVI and SDI video are possible. Latency can be reduced to a minimum, down to under 0,08 seconds, by overclocking the system. Webcams and NDI can be used as live video sources as well. See also: [[Tutorial NDI Tools]].

	~~===Flash===~~

	MXWendler can read and process Adobe Flash files (.swf). These Flash media can also be interactive. In MS Windows, the file is processed by the native Flash interpreter, meaning that all formats are supported. In OS X, a performance-optimized OpenGL Flash interpreter is used, which supports Action Script up to version 1.0.

	===Images===		===Images===

Main Page

Admin — Sat, 08 Aug 2026 19:20:05 GMT

← Older revision		Revision as of 21:20, 8 August 2026
Line 5:		Line 5:
	== Getting started ==		== Getting started ==
	* [[Introduction]]		* [[Introduction]]
	* [[User Interface ~~V6]]~~		* [[User Interface V7\|User Interface]]
	* [[User Interface\|User Interface V5]]
	* [[Tutorials\|Try a Tutorial]]		* [[Tutorials\|Try a Tutorial]]
	* [[Triggering\|Triggering Events]]		* [[Triggering\|Triggering Events]]

Windows 7 + NDI Tools

Admin — Sat, 08 Aug 2026 19:17:31 GMT

Admin deleted page Windows 7 + NDI Tools content was: "This applies to Windows 7 64Bit and MXWendler version 5.0 and above '''Problem''' The Virtual Input from NDI Tools might not work on some Windows 7 versions due to some problems with windows updates. When you try to open the Virtual Input in Win 7, you might receive a message that you need to install the Windows Update package KB 3033929 (Or any other Windows security...", and the only contributor was "Behrooz" (talk)

Trouble Shooting

Admin — Sat, 08 Aug 2026 19:17:15 GMT

Restore Aero Peek link; remove outdated 'Windows 7 + NDI Tools' link (bot)

← Older revision		Revision as of 21:17, 8 August 2026
Line 36:		Line 36:
	*[[Windows + Unexpected Output Window Size]]		*[[Windows + Unexpected Output Window Size]]
	*[[Windows + No Output in Output Window]]		*[[Windows + No Output in Output Window]]
			*[[Windows + How to Deactivate Aero Peek to Prevent Unwanted Output Blackouts]]
	*[[Windows 7 + AMD + Stuttering Output]]		*[[Windows 7 + AMD + Stuttering Output]]
	*[[Windows 7 + AMD + Output Window On Wrong Screen]]		*[[Windows 7 + AMD + Output Window On Wrong Screen]]
Line 42:		Line 43:
	*[[Windows 7 + Configuration (config.xml)]]		*[[Windows 7 + Configuration (config.xml)]]
	*[[Windows 7 + Richtexteditor Glitches and ClearType]]		*[[Windows 7 + Richtexteditor Glitches and ClearType]]
	*[[Windows 7 + NDI Tools]]

	'''Linux'''		'''Linux'''

Windows XP + No output on second screen

Admin — Sat, 08 Aug 2026 19:17:10 GMT

Admin deleted page Windows XP + No output on second screen content was: "This applies to Windows XP and above and MXWendler version 4.0 and above with NVidia graphics '''Problem''' The MXW UI runs, and you see content updating in the output on the first screen, but not on the second (output) screen. '''Reason''' You have an NVidia graphics board. '''Solution''' 1. Open NVidia system settings. 2. Under 'Multi-GPU Acceleration' enable 'Compatibility Mode'. '''Background''' If you select performance mode, only the first screen rece..."

Re-Converting Video files using AVANTI GUI (Freeware)

Admin — Sat, 08 Aug 2026 19:16:58 GMT

Admin deleted page Re-Converting Video files using AVANTI GUI (Freeware) content was: "Admin edited this site", and the only contributor was "Admin" (talk)

Trouble Shooting

Admin — Sat, 08 Aug 2026 19:15:28 GMT

Remove link to deleted page 'Windows + How to Deactivate Aero Peek...' (bot)

← Older revision		Revision as of 21:15, 8 August 2026
(2 intermediate revisions by the same user not shown)
Line 34:		Line 34:
	*[[Windows 10 + Nvidia and Intel Cards]]		*[[Windows 10 + Nvidia and Intel Cards]]
	*[[Windows + Blackmagic Decklink Capture Cards]]		*[[Windows + Blackmagic Decklink Capture Cards]]
	*[[Windows + How to Deactivate Aero Peek to Prevent Unwanted Output Blackouts]]
	*[[Windows + Unexpected Output Window Size]]		*[[Windows + Unexpected Output Window Size]]
	*[[Windows + No Output in Output Window]]		*[[Windows + No Output in Output Window]]
Line 44:		Line 43:
	*[[Windows 7 + Richtexteditor Glitches and ClearType]]		*[[Windows 7 + Richtexteditor Glitches and ClearType]]
	*[[Windows 7 + NDI Tools]]		*[[Windows 7 + NDI Tools]]
	*[[Windows XP + No output on second screen\|Windows XP + NVidia No output on second screen]]
	*[[Re-Converting Video files using AVANTI GUI (Freeware)]]

	'''Linux'''		'''Linux'''

OSC Reference

Admin — Sat, 08 Aug 2026 19:13:01 GMT

← Older revision		Revision as of 21:13, 8 August 2026
(One intermediate revision by the same user not shown)
Line 1:		Line 1:
	This reference applies to all different OS~~. The presented OSC commands are for most part supported in version 6.0 but will be fully functional in version 6.0.08 and above~~.		This reference applies to all different OS.
	<div class="noprint">		<div class="noprint">

Line 16:		Line 16:
	* Allowed data formats including numeric, symbolic, and “blob” arguments		* Allowed data formats including numeric, symbolic, and “blob” arguments
	* Open-ended, dynamic, URL-style naming scheme for the receivers' address		* Open-ended, dynamic, URL-style naming scheme for the receivers' address


	~~[https://en.wikipedia.org/wiki/Open_Sound_Control [1<nowiki>]</nowiki> Wikipedia Link]~~

	== Contents ==		== Contents ==
	{\|		{\|
Line 25:		Line 21:
	\| style="padding: 0px 10px" \| [[Controlling MXW through OSC]]		\| style="padding: 0px 10px" \| [[Controlling MXW through OSC]]
	\|-		\|-
	~~\| style="padding: 0px 30px" \| ''Receiving OSC commands in MXW''~~		\| style="padding: 0px 10px" \| [[MXW OSC command structure]]
	\|-
	~~\| style="padding: 0px 30px 10px" \| ''Output OSC from MXW: Send vs. Reply''~~
	\|-
	\| style="padding: 0px 10px ~~0px~~" \| [[MXW OSC command structure]]
	\|-
	~~\| style="padding: 0px 30px" \| ''Sending OSC Values''~~
	\|-
	~~\| style="padding: 0px 30px" \| ''Examples''~~
	\|-		\|-
	\| style="padding: 10px" \| [[OSC command reference]]		\| style="padding: 0px 10px" \| [[OSC command reference]]
	\|-		\|-
	\| style="padding: 10px" \| [[OSC Troubleshooting\|Troubleshooting]]		\| style="padding: 0px 10px" \| [[OSC Troubleshooting\|Troubleshooting]]
	\|}		\|}
	[[Category:OSC]]		[[Category:OSC]]
	[[Category:Reference]]		[[Category:Reference]]

Troubleshooting

Admin — Sat, 08 Aug 2026 19:09:50 GMT

Admin deleted page Troubleshooting content was: "#REDIRECT OSC Troubleshooting", and the only contributor was "Admin" (talk)

OSC Reference

Admin — Sat, 08 Aug 2026 19:08:59 GMT

Update link after renaming Troubleshooting -> OSC Troubleshooting (bot)

← Older revision		Revision as of 21:08, 8 August 2026
Line 37:		Line 37:
	\| style="padding: 10px" \| [[OSC command reference]]		\| style="padding: 10px" \| [[OSC command reference]]
	\|-		\|-
	\| style="padding: 10px" \| [[Troubleshooting]]		\| style="padding: 10px" \| [[OSC Troubleshooting\|Troubleshooting]]
	\|}		\|}
	[[Category:OSC]]		[[Category:OSC]]
	[[Category:Reference]]		[[Category:Reference]]

Troubleshooting

Admin — Sat, 08 Aug 2026 19:08:58 GMT

Admin moved page Troubleshooting to OSC Troubleshooting Clarify: OSC-specific troubleshooting

New page

Common issues that can arise while using OSC and MXW are generally linked to network malfunctions.

===Network diagnostics===

Make sure that the system you want to control is correctly connected to the same network as the ‘master’ machine.

==== To proof if the two machines are able to communicate in the network try to ping reciprocally the two systems: ====
:* For Windows users:
::1. Open the “Command Prompt” in the ‘master’ system as Administrator
::2. Type <code> ipconfig </code> take note of the IPv4 Address
::3. Repeat for the ‘slave’ system
::4.In the ‘master’ test if the other machine is reachable by typing <code> ping </code> followed by the IP of the ‘slave’ (e.g. <code> ping 192.168.178.7 </code>)
::5. If the machine is reachable a similar message will appear:
</div>
Pinging 192.168.178.7 with 32 bytes of data:
Reply from 192.168.178.7: bytes=32 time<1ms TTL=64
Reply from 192.168.178.7: bytes=32 time<1ms TTL=64
Reply from 192.168.178.7: bytes=32 time<1ms TTL=64
Reply from 192.168.178.7: bytes=32 time<1ms TTL=64

Ping statistics for 192.168.178.7:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
</div>
::* In case it is not reachable the message will show in the statistics
Received = 0 , Lost = 4 (100% Loss)
::* Repeat the steps sending the ping from the ‘slave’ to the ‘master’ IP to proof the connections
:* For Mac OS X users:
::1. Press “Apple” + "SPACE BAR" and search for “Terminal” in the ‘master’ system
::2. Type <code> ping </code> followed by the IP Address of the ‘slave’
::3. Proof if the ping get through
::4. Repeat for the ‘slave’ system pinging the IP of the ‘master’

==== In case of failure to connect: ====
:*Verify that the firewall is not blocking the communication:
::* For Windows users:
:::1. Search for “Firewall & Network Protection” in the “Start” menu
:::2. Deactivate all three (Domain, Private and Public) firewalls by entering the respective window and switching the protection to “Off” in all of them
::* For Mac OS X users:
:::1. In the Apple menu, select “System Preferences”
:::2. In the System Preferences window, select “Security and Privacy”
:::3. In the tab “Firewall” turn off the Firewall by pressing the “Turn Off” Button (10.6 or higher) or by deselecting the checkbox “Block all incoming connections” (10.5 or lower)
</div>
::* In your Router settings page (see the manufacturers manual for instructions) disable AP (access point) isolation, also known as 'Client Isolation' or 'Guest Mode' when active

==== In case of occasional loss of OSC packages: ====
::* The maximum size of every OSC package is defined by the MTU (minimum transport unit) of the network in use. Big packages tend to get lost more easily depending on the characteristics of the network so reducing the amount of big blobs (e.g. preview requests) can lower the loss rate. See
::* In case of loss of small packages, verify if the packages are getting sent and their size with a package sniffer (e.g. "Wireshark") and try different settings on your receiving console/device.


If none of the above solutions solves the issue try by restarting the software and reconnecting all the network chain from start.

For further diagnostics activate the Log of received data in MXW and the dispatch of livesigns (See Points 2.2 and 2.2 d. of the Open Sound Control References) to test the receiving and sending functionality on the wished OSC console, Pd patch or the Protokol App for a mobile option (see point 4.).

5. Troubleshooting

Admin — Sat, 08 Aug 2026 19:07:57 GMT

Admin deleted page 5. Troubleshooting content was: "#REDIRECT Troubleshooting", and the only contributor was "Admin" (talk)

2. MXW OSC command structure

Admin — Sat, 08 Aug 2026 19:07:52 GMT

Admin deleted page 2. MXW OSC command structure content was: "#REDIRECT MXW OSC command structure", and the only contributor was "Admin" (talk)

1. Controlling MXW through OSC

Admin — Sat, 08 Aug 2026 19:07:44 GMT

Admin deleted page 1. Controlling MXW through OSC content was: "#REDIRECT Controlling MXW through OSC", and the only contributor was "Admin" (talk)

OSC Reference

Admin — Sat, 08 Aug 2026 19:04:34 GMT

Remove index numbering from OSC contents (links + sub-items) (bot)

← Older revision		Revision as of 21:04, 8 August 2026
Line 23:		Line 23:
	{\|		{\|
	\|-		\|-
	\| style="padding: 0px 10px" \| [[1. Controlling MXW through OSC]]		\| style="padding: 0px 10px" \| [[Controlling MXW through OSC]]
	\|-		\|-
	\| style="padding: 0px 30px" \| ''~~1.1~~ Receiving OSC commands in MXW''		\| style="padding: 0px 30px" \| ''Receiving OSC commands in MXW''
	\|-		\|-
	\| style="padding: 0px 30px 10px" \| ''~~1.2~~ Output OSC from MXW: Send vs. Reply''		\| style="padding: 0px 30px 10px" \| ''Output OSC from MXW: Send vs. Reply''
	\|-		\|-
	\| style="padding: 0px 10px 0px" \| [[2. MXW OSC command structure]]		\| style="padding: 0px 10px 0px" \| [[MXW OSC command structure]]
	\|-		\|-
	\| style="padding: 0px 30px" \| ''~~2.1~~ Sending OSC Values''		\| style="padding: 0px 30px" \| ''Sending OSC Values''
	\|-		\|-
	\| style="padding: 0px 30px" \| ''~~2.2~~ Examples''		\| style="padding: 0px 30px" \| ''Examples''
	\|-		\|-
	\| style="padding: 10px" \| [[OSC command reference]]		\| style="padding: 10px" \| [[OSC command reference]]
	\|-		\|-
	\| style="padding: 10px" \| [[5. Troubleshooting]]		\| style="padding: 10px" \| [[Troubleshooting]]
	\|}		\|}
	[[Category:OSC]]		[[Category:OSC]]
	[[Category:Reference]]		[[Category:Reference]]

5. Troubleshooting

Admin — Sat, 08 Aug 2026 19:04:14 GMT

Admin moved page 5. Troubleshooting to Troubleshooting Remove leading index prefix from title

New page

2. MXW OSC command structure

Admin — Sat, 08 Aug 2026 19:04:13 GMT

Admin moved page 2. MXW OSC command structure to MXW OSC command structure Remove leading index prefix from title

New page

View source for 2. MXW OSC command structure
← 2. MXW OSC command structure
Jump to navigationJump to search
You do not have permission to edit this page, for the following reason:

The action you have requested is limited to users in the group: Users.

You can view and copy the source of this page.

Commands to the MXW OSC interface always follow the same syntax:

<code>/mxw/<address of widget> [MSGID] <float|integer|string></code>

for example:

<code>/mxw/track/1 0.5</code> 
or: 
<code>/mxw/set play patch1</code> 
or: 
<code>/mxw/playlist MSGID0001 info</code> 

Commands always begin with /mxw/ and it is followed by the address of the receiver and an argument that can be a numeric value, a string, or a combination of both.
The only optional element is the “Message-ID”.

== 2.1 Sending OSC Values ==
</div>
The command receivers listen to a value that is either a float or an integer (if they are widgets), or to strings (e.g. to choose patches or clips).
==== Faders ====
Receivers in MXW connected to faders in the user interface are responding to Float values. Floats are always in the range of 0.0 to 1.0 and will be scaled to the actual range of the recalled widget. 
For instance, the speed fader has a range in MXW that goes between -5 and 5 and its active range is dependent on the type of played media. If a float value like 0.6 is sent to the OSC address of the clip speed, the fader moves to the value 1.0 (original speed of the clip).

==== Buttons and Checkboxes ====
Widgets in MXW that have an '''ON/OFF''' state accept integers as values. Buttons have the functions Press and Release assigned respectively to <code>1</code> and <code>0</code> and checkboxes have assigned ON and OFF respectively to <code>1</code> and <code>0</code>. This means that if one wants to send a button press, e.g. a "play" button press, a value "0" has to be sent (to send a command, like with a mouse-click, a button must be pressed and released after)

==== Drop-down Boxes and Combo Boxes ====
Drop-down lists and Combo Boxes are indexed with integers ranging between <code>1</code> and the maximum number of elements. For example to select the third element of a list the integer <code>3</code> will be sent to the address of the Combo Box.

=== String Tokens ===
</div>
Specific string tokens can also be sent to the command receivers and they can respectively activate specific functions paired with a numeric value or another string. The usable strings are <code>play</code><code>info</code> <code>select</code> <code>preview</code> <code>clear</code>.
==== play ====
The string play can be sent together with another string containing the name of a saved patch in the address <code>/mxw/set </code> to start the playback of the recalled patch.

<code>/mxw/set play patch1</code>.
==== info ====
The string variable info can be sent to a specific address to acquire information about one field or clip through a reply sent by MXW.
The reply bundle coming from MXW will also be sent through OSC and will have this format:

* A reply header composed by:

1. Message <code>mxw/reply</code> 
2. <code>MSGID</code> (if specified in the info request) 
3. Address pattern of the request 
4. Time as a long variable 

* The actual '''reply content''' following this table: 

{| class="wikitable"
|-
! ADDRESS !! REPLY CONTENT
|-
| <code>/mxw/playlist info </code>|| 1. State of the playback (<code>play</code>, <code>paused</code>, <code>stopped</code>)
|-
| <code>/mxw/playlist/container/active info </code>|| 1. Active container index 2. Number of columns 3. Number of rows
|-
| <code>mxw/playlist/container/active/column/1/row/1 info </code>|| 1. Label of media in the container in column 1, row 1
|-
| <code>/mxw/track/active/layer/active/clip info </code>|| 1. Length of media 2. Width 3. Height 4. ms per frame 5. Completition of cache (<code>cachecomplete</code>/<code>cachenotcomplete</code>) 6. Path directory of the active clip
|-
| <code>/mxw/preload/1 info </code>|| 1. Length of media 2. Width 3. Height 4. ms per frame 5. Completition of cache (<code>cachecomplete</code>/<code>cachenotcomplete</code>) 6. Path directory of the media of the first preload
|-
| <code>mxw/keystone info </code>|| 1. Active keystone element index 2. Name of active keystone element 3. Amount of total keystone elements 4. Names of keystone elements separated by commas 5. Active softedge index 6. Name of active softedge 7. Amount of total softedges 8. Names of softedges separated by commas 9. Active grabber element index 10. Name of active grabber element 11. Amount of total grabber elements 12. Names of grabber elements separated by commas 13. Active blacklevel element index 14. Name of active blacklevel element 15. Amount of total blacklevel elements 16. Names of blacklevel elements separated by commas
|-
| <code>mxw/keystone/element/1 info </code>|| 1. Element name 2. Element type 3. Video track number 4. Video layer number 5. Precision 6. Number of pivots x 7. Number of pivots y 8. Scale 9. Opacity 10. Rotation of element number 1
|-
| <code>/mxw/keystone/element/1/pivot/col/1/row/1 info </code>|| 1. Pivot translation x 2. Translation y 3. Translation z 4. UV value x 5. UV values y 6. UV normalized x 7. UV normalized y 8. RGB COLOUR
|-
| <code>mxw/layermanager info</code>|| 1. Active layer index 2. Name of active layer 3. Amount of total layers 4. Names of layers separated by commas
|-
| <code>mxw/set info</code> || 1. Active patch index 2. Name of active patch 3. Amount of total patches 4. Names of patches separated by commas
|-
| <code>mxw/trackmanager info</code>|| 1. Active track index 2. Name of active track 3. Amount of total tracks 4. Names of tracks separated by commas
|-
| Addresses of Drop-down Boxes and Combo Boxes in MXW (e.g. <code>mxw/render/effect info</code>)|| 1. Index and Name of currently selected item 2. Amount of total items 3. Names of items separated by commas
|-
| Addresses of Faders in MXW (e.g. <code>mxw/render/opacity info</code> )|| 1. Value of position of fader (<code>0 .. 1</code>)
|-
| Addresses of Buttons/Checkboxes in MXW (e.g. <code>mxw/track/1/crossfade info</code>)|| 1. State of the widget (<code>0 = released/OFF , 1 = pressed/ON</code>)
|-
|colspan="2" | NOTE: The token <code>active</code> can be substituted with an integer corresponding to the index of the wished element
|}

As an example, if we send:

<code>/mxw/playlist/container/active info</code>

MXWendler will reply:

<code>mxw/reply /mxw/playlist/container/active &emsp;&emsp;&emsp;&emsp;&emsp; 980451 &emsp;&emsp;&emsp;0 &emsp;&emsp;&emsp;&ensp;3 &emsp;&emsp; &emsp; 20</code> 
Reply Message Address of Request Time Index Col. Row

====select====
The token select can be added to different addresses to select the single elements on a list of many using a string. This command is can be used in combination with the token <code>info</code> as the names of the elements can be recalled with <code>info</code> first and then selected with the <code>select</code> token.
The receivers that respond with the token select are:
* trackmanager
* layermanager
* combo-boxes

<code>/mxw/trackmanager select track2</code>

====active====
The token active is used in the receiver address and can be used in multiple situations to act on the selected element of a list. For example the command:

<code>/mxw/track/active/fader 0.5</code>

will move the fader of the selected (active) track to his middle position, setting its opacity to 50%.

====preview====
The string preview can be used to get in return an OSC blob, containing a 128x128px '''jpg''' file that is a preview of the currently played media or a thumbnail of the selected clip. Here are the available addresses for a preview:
{| class="wikitable"
|-
! NAME !! ADDRESS
|-
| Render || <code>/mxw/render preview</code>
|-
| Track || <code>/mxw/track/active preview</code>
|-
| Layer || <code>/mxw/track/active/layer/active preview</code>
|-
| Clip || <code>/mxw/track/active/layer/active/clip preview</code>
|-
| Preload || <code>/mxw/preload/"preload index" preview</code> <code>/mxw/preload/7 preview</code>
|-
| Patch/Set || <code>/mxw/patch/"patch index" preview</code> E.G.<code>/mxw/patch/3 preview</code>
|-
|colspan="2" | NOTE: The token <code>active</code> can be substituted with an integer corresponding to the index of the wished element
|}

====clear====

The function clear can be sent to the preloads to empty one of the preload spaces.

E.G. <code>mxw/preload/1 clear</code> will clear the first preload slot.

=== Message-ID ===
</div>
The “Message-ID” allows for clear communication and categorization of replies. When a command that generates a reply is sent, it is possible to prepend the command with a “Message-ID” which will be then in the reply as well. This message must have the format <code> MSGIDXXXX </code> and it must follow the OSC address like in the following example:

<code>/mxw/preload/3 MSGID0123 info</code>

will return a reply similar to:

<code>/mxw/reply MSGID0123 /mxw/preload/3 112 320 240 40 cachecomplete c:\footage\clip.avi</code>

== 2.2 Examples ==
To address the main fader and fade the opacity of the render from zero to full in ten steps, you would send a command sequence:
 
<code>/mxw/render 0.0</code> 
<code>/mxw/render 0.1</code> 
<code>/mxw/render 0.2</code> 
<code>/mxw/render 0.3</code> 
<code>/mxw/render 0.4</code> 
<code>/mxw/render 0.5</code> 
<code>/mxw/render 0.6</code> 
<code>/mxw/render 0.7</code> 
<code>/mxw/render 0.8</code> 
<code>/mxw/render 0.9</code> 
<code>/mxw/render 1.0</code>

Finer-grained values can be sent if needed. The commands will be evaluated as soon as they arrive in MXW and the last command before a new frame is drawn will set the widget's value.

<code>/mxw/track/active 0.5</code> Sets the active track opacity to 0.5

<code>/mxw/track/1 0.5</code> Sets track 1 opacity to 0.5

<code>/mxw/preload/1/trigger 1.0</code> Adds a layer with the contents of preload slot 1

<code>/mxw/track/1/layer/1/opacity 0.5</code> Sets the opacity of the first layer of the first track to 0.5 (if there is a layer playing content)

<code>/mxw/set 5</code> The active track will load patch 5

<code>/mxw/track/active/layer/active/clip/speed 0.6</code> Sets the speed of the clip of the active layer of the active track to 1.0 (0.6 translates to 1.0 in a -5 .. +5 range)

<code>/mxw/track/active/layer/active/clip/speed 0.5</code> Sets the speed of the clip of the active layer of the active track to 0.5 (clip stops)

<code>/mxw/trackmanager 1</code> Activate the first track

<code>/mxw/trackmanager 3</code> Activate the third track

<code>/mxw/trackmanager select track3</code> Activate the third track

<code>/mxw/track/2/layer/1/clip/effect/2 select ag_AnimWarp</code> Instructs the clip of the first layer of the second track to load the effect with the name "ag_AnimWarp" in the effect slot number 2

<code>/mxw/track/2/layer/1/clip/effect/1/param/1 0.8</code> Set to the value of 0.8, the parameter 1 of the first effect of the clip of the first layer of the second track

<code>/mxw/preload/2 c:/footage/clip.avi</code> Preload slot 2 will load c:/footage/clip.avi (and answer with info). Note the direction of the slashes.

<code>/mxw/preload/2 clear</code> Preload slot 2 will unload

<code>/mxw/preload/2 info</code> Preload 2 will answer with clip info like 
<code>/mxw/reply /mxw/preload/3 112 320 240 40 cachecomplete
c:\footage\clip.avi</code>

<code>/mxw/preload/2 MSGID0123 info</code> Preload 2 will answer with clip info like 
<code>/mxw/reply MSGID0123 /mxw/preload/3 112 320 240 40 cachecomplete c:\footage\clip.avi</code>

<code>/mxw/master/load_showfile c:/footage/showfile.mxw</code> Load the stated showfile

<code>/mxw/master/load_keystonefile c:/footage/keystonefile.mxw_keystone2</code> Load the stated keystonefile

1. Controlling MXW through OSC

Admin — Sat, 08 Aug 2026 19:04:12 GMT

Admin moved page 1. Controlling MXW through OSC to Controlling MXW through OSC Remove leading index prefix from title

New page

MXW is designed to be a high-performance real-time video software for media servers. It interactively composites high-resolution footage and interactive media.
OSC commands can be generated, sent, and received by MXWendler and a wide range of applications: signaling frameworks like Pure Data, Max/MSP, TouchOSC, and TouchDesigner, audio workstations like Ableton Live, Logic, or Protools, programming environments like Processing, Perl, Java, Unity, and TidalCycles, other Multimedia, Sensoring, Signal Processing software, Microcontrollers and many more, offering a compatible and fast intercommunication method.

Separating the media server from the controlling infrastructure offers various creative and usability options:

*Control multiple machines from one single point
*Control a single machine from multiple points
*Replicate a state into a remote system
*Custom user interfaces
*Intercommunication with external software and platforms
*Control via WAN
*Control via a microcontroller
*Connect scene-analysis with scene-composition systems
*Extract control features e.g mapping or triggering

<div class="noprint">
== 1.1 Receiving OSC commands in MXW ==
</div>

To enable OSC receiving open the software MXWendler: 
1. In '''Menu: Settings → Input and Output ''(CTRL+1)'' →''' in the tab '''OSC''', activate the box '''Receive OSC''' ( '''(A)''' In the following picture) 
2. Set the port ( 7000 is recommended as an OSC Standard) 
3. The box '''Log received data''' will log commands in the Error and Log Window visible through '''Menu: Settings → Error and Log Window ''(CTRL+SHFT+L)'' ''' 

This is particularly useful for testing and troubleshooting as it will make visible what OSC commands are received by MXW. The logging of data has a performance impact on the system so it is important to turn it off when not in use.
As this option is marked (r) in the menu, to activate the changes, please restart the software.
<div class="noprint">

== 1.2 Output OSC from MXW: Send vs. Reply ==
</div>
MXW can send OSC commands as well. Multiple distinct options are available in '''Menu: Settings → Input and Output ''(CTRL+1)'' →''' tab '''OSC''' : 

[[File:mxwIO.png|728px]]

{{#mpdftags: pagebreak}}

=== Broadcast and Receive Time over OSC '''(B)''' ===
This option will broadcast the MXW time into the selected subnet to synchronize the time among a pool of machines.
To achieve this a selection mechanism is applied: every machine sends its time until it receives the time from a machine with a lower IP address. In the end, the machine with the lowest IP is selected as the 'master' and controls the pool clock.
IO Events can be forwarded by selecting the relative checkbox. You can for example connect a MIDI device and it will send the MIDI events to the pool.

=== Receive OSC over RS232 '''(C)''' ===
Check this box if the OSC commands are received through a Serial Port instead of a network port. Options for port selection and integer indexing are available.

=== Send OSC '''(D)''' ===
This option will send any action on the running host to another host/network defined in the command options. Moving a track slider will generate the commands that make the track slider in the remote machine move to the same position. The goal is to make another machine (pretended it carries the same media data) produce exactly the same result as the master machine by sending osc commands to replicate the same behaviour.
Sometimes it is desireable to send only a selction of the generated actions. You can filter the sent commands using the following rules:
 
- Adding a + before a *token*, [comment(optional)] 
- Adding a - before a token*, [comment(optional)] 
 
The *token* is a part of the string like "playlist" or "opacity", a comment can be added after a comma in case we want to specify the reason of the filter. So adding the line <code>+,*playlist*</code> will result into that only commands containing the keyword "playlist" will be sent. In the same way using the filter <code>-,*opacity*, opacity_does_not_change</code> any command referring to "opacity" will not be sent through and everything else will.

=== OSC reply channel '''(E)''' ===
Many OSC commands are capable of asking for specific information e.g. the name of a clip in the preload or the playback status of the playlist. This option must be active in MXW to allow the software to reply to the received OSC commands. Options for a specific IP address of the host/subnet and Port are given in the settings. The last checkbox “Send periodical livesigns” allows to receive a constant periodical flow of data from MXW regarding performance and render information, useful as well for diagnostic reasons.

6. External links

Admin — Sat, 08 Aug 2026 19:03:08 GMT

Admin deleted page 6. External links content was: " 1 http://www.cnmat.berkeley.edu/OpenSoundControl/ 2 http://www.opensoundcontrol.org 3 https://www.linuxjournal.com/content/introduction-osc 4 https://hexler.net/touchosc 5 https://www.cxnetwork.com.au/osc-open-sound-control/ 6 https://en.wikipedia.org/wiki/Open_Sound_Control ", and the only contributor was "Hendrik" (talk)

OSC Reference

Admin — Sat, 08 Aug 2026 19:02:08 GMT

Remove useless '6. External links' entry from contents (bot)

← Older revision		Revision as of 21:02, 8 August 2026
Line 38:		Line 38:
	\|-		\|-
	\| style="padding: 10px" \| [[5. Troubleshooting]]		\| style="padding: 10px" \| [[5. Troubleshooting]]
	\|-
	~~\| style="padding: 10px" \| [[6. External links]]~~
	\|}		\|}
	[[Category:OSC]]		[[Category:OSC]]
	[[Category:Reference]]		[[Category:Reference]]

4. Practical examples: Pure Data and TouchOSC

Admin — Sat, 08 Aug 2026 19:01:11 GMT

Admin deleted page 4. Practical examples: Pure Data and TouchOSC content was: "Pure Data (or just Pd) is an open-source visual programming language for multimedia available for free at http://puredata.info/ and, given its flexibility, it is a very useful tool for integration/interfacing needs as well as a diagnostic tool. Thanks to its built-in graphic libraries it is possible to create simple GUIs for controlling external software and its extensibility...", and the only contributor was "Hendrik" (talk)

OSC Reference

Admin — Sat, 08 Aug 2026 19:00:26 GMT

Remove outdated 'Practical examples: Pure Data and TouchOSC' entry from contents (bot)

← Older revision		Revision as of 21:00, 8 August 2026
Line 36:		Line 36:
	\|-		\|-
	\| style="padding: 10px" \| [[OSC command reference]]		\| style="padding: 10px" \| [[OSC command reference]]
	\|-
	~~\| style="padding: 0px 10px 0px" \| [[4. Practical examples: Pure Data and TouchOSC]]~~
	\|-
	~~\| style="padding: 0px 30px" \| ''4.1 Install Pure Data''~~
	\|-
	~~\| style="padding: 0px 30px" \| ''4.2 MXW Pd Patch''~~
	\|-
	~~\| style="padding: 0px 30px 0px" \| ''4.3 OSC for portable Devices: TouchOSC and Protokol''~~
	\|-		\|-
	\| style="padding: 10px" \| [[5. Troubleshooting]]		\| style="padding: 10px" \| [[5. Troubleshooting]]

1. Controlling MXW through Python

Admin — Sat, 08 Aug 2026 18:59:05 GMT

Admin deleted page 1. Controlling MXW through Python content was: "#REDIRECT Controlling MXW through Python", and the only contributor was "Admin" (talk)

Python Reference

Admin — Sat, 08 Aug 2026 18:58:04 GMT

Point TOC to de-numbered 'Controlling MXW through Python'; drop index prefixes (bot)

← Older revision		Revision as of 20:58, 8 August 2026
Line 10:		Line 10:
	{\|		{\|
	\|-		\|-
	\| style="padding: 10px" \| [[1. Controlling MXW through Python]]		\| style="padding: 10px" \| [[Controlling MXW through Python]]
	\|-		\|-
	\| style="padding: 10px" \| [[~~Python command reference \| 2.~~ Python command reference]]		\| style="padding: 10px" \| [[Python command reference]]
	\|-		\|-
	\| style="padding: 10px" \| [[~~Python imgui reference \| 2.~~ Python imgui reference]]		\| style="padding: 10px" \| [[Python imgui reference]]
	\|-		\|-
	\| style="padding: 10px" \| [[~~Python plugin reference \|~~ Python plugin reference]]		\| style="padding: 10px" \| [[Python plugin reference]]
	\|-		\|-
	\|}		\|}
	[[Category:Python]]		[[Category:Python]]
	[[Category:Reference]]		[[Category:Reference]]

1. Controlling MXW through Python

Admin — Sat, 08 Aug 2026 18:58:03 GMT

Admin moved page 1. Controlling MXW through Python to Controlling MXW through Python Remove leading index prefix from title

New page

MXWendler StageDesigner embeds '''Python 3.12'''. Python is used in two ways:

* '''Command interface / scripting''' – the module <code>mxw</code> controls the running software (playlist, layers, clips, media, I/O, widgets by their address, ...) from the script console or from within a plugin.
* '''Plugins''' – self-contained folders that add a media source or a playlist item and are called back by the host through a defined set of functions (''hooks'').

'''The presented Python interface is supported in version 7.2. and up'''

== Where to go ==

The detailed documentation lives on three dedicated pages; this page only points to them so nothing is documented twice.

{| class="wikitable"
|-
! Topic !! Page
|-
| The <code>mxw</code> command interface – software info, <code>playlist</code>, <code>io</code>, <code>widget(address)</code>, <code>media(name)</code>, <code>preload(n)</code>, <code>grabber(name)</code> || [[Python command reference|Python command reference]]
|-
| Drawing plugin settings panels with <code>mxw_imgui</code> (MXWendler's Dear ImGui binding) || [[Python imgui reference|Python ImGui reference]]
|-
| Writing '''plugins''' – media and playlist – the manifest (<code>mxw_plugin.ini</code>), the hooks, per-instance state, examples || [[Python plugin reference|Python plugin reference]]
|}

== Quick start ==

A minimal look at each entry point; follow the links above for the full reference.

'''Scripting.''' From the script console (or any hook), the <code>mxw</code> module reaches the software:

<syntaxhighlight lang="Python" line>
import mxw
mxw.print_console("frame " + str(mxw.framecounter))
mxw.playlist.play()
mxw.widget("/mxw/track/active/layer/active/opacity").setValue(0.5)
</syntaxhighlight>

'''Plugins.''' A plugin is a folder holding a manifest and a Python module:

<pre>
plugins/playlist/python/plugin_my_item/
mxw_plugin.ini the manifest: identity, menu entries
mxw_main.py the Python module with the hook functions
</pre>

The host discovers it at startup, shows it in the user interface and calls its hooks at the right moments. See the [[Python plugin reference|Python plugin reference]] for the manifest fields, the full hook list for media and playlist plugins, plugin locations, installing extra packages with <code>mxw-pip</code>, and complete examples.

== See also ==

* [[Python command reference|Python command reference]] – the <code>mxw</code> module
* [[Python imgui reference|Python ImGui reference]] – drawing plugin panels with <code>mxw_imgui</code>
* [[Python plugin reference|Python plugin reference]] – writing media and playlist plugins

6. External Resources

Admin — Sat, 08 Aug 2026 18:56:05 GMT

Admin deleted page 6. External Resources content was: "#REDIRECT External Resources", and the only contributor was "Admin" (talk)

5. Troubleshooting scripts

Admin — Sat, 08 Aug 2026 18:55:59 GMT

Admin deleted page 5. Troubleshooting scripts content was: "#REDIRECT Troubleshooting scripts", and the only contributor was "Admin" (talk)

4. Practical examples

Admin — Sat, 08 Aug 2026 18:55:55 GMT

Admin deleted page 4. Practical examples content was: "#REDIRECT Practical examples", and the only contributor was "Admin" (talk)

1. Controlling MXW through JavaScript

Admin — Sat, 08 Aug 2026 18:55:51 GMT

Admin deleted page 1. Controlling MXW through JavaScript content was: "#REDIRECT Controlling MXW through JavaScript", and the only contributor was "Admin" (talk)

JavaScript Reference

Admin — Sat, 08 Aug 2026 18:51:36 GMT

Point TOC to de-numbered page titles; drop index prefixes (bot)

← Older revision		Revision as of 20:51, 8 August 2026
Line 16:		Line 16:
	{\|		{\|
	\|-		\|-
	\| style="padding: 10px" \| [[1. Controlling MXW through JavaScript]]		\| style="padding: 10px" \| [[Controlling MXW through JavaScript]]
	\|-		\|-
	\| style="padding: 10px" \| [[~~JavaScript command reference \| 2.~~ JavaScript command reference]]		\| style="padding: 10px" \| [[JavaScript command reference]]
	\|-		\|-
	\| style="padding: 10px" \| [[~~4. Practical examples \| 3.~~ Practical examples]]		\| style="padding: 10px" \| [[Practical examples]]
	\|-		\|-
	\| style="padding: 10px" \| [[~~5. Troubleshooting scripts \| 4.~~ Troubleshooting scripts]]		\| style="padding: 10px" \| [[Troubleshooting scripts]]
	\|-		\|-
	\| style="padding: 10px" \| [[~~6. External Resources \| 5.~~ External Resources]]		\| style="padding: 10px" \| [[External Resources]]
	\|}		\|}
	[[Category:JavaScript]]		[[Category:JavaScript]]
	[[Category:Reference]]		[[Category:Reference]]

6. External Resources

Admin — Sat, 08 Aug 2026 18:51:22 GMT

Admin moved page 6. External Resources to External Resources Remove leading index prefix from title

New page

1 https://en.wikipedia.org/wiki/JavaScript
2 https://developer.mozilla.org/en-US/docs/Web/JavaScript 
3 https://curlie.org/Computers/Programming/Languages/JavaScript/ 
4 https://duktape.org/index.html

5. Troubleshooting scripts

Admin — Sat, 08 Aug 2026 18:51:21 GMT

Admin moved page 5. Troubleshooting scripts to Troubleshooting scripts Remove leading index prefix from title

New page

'''Problem'''

JavaScript is not functioning as intended. No corresponding action happens when the trigger button for the event is pressed.

'''Hints'''

# Open the JavaScript console by pressing Ctrl+Shift+J (Mac:Command+Shift+J) and look for error messages.
# Check for syntax errors in your code and ensure that interface functions are written correctly.
# Check that predefined hooks and functions like e.g. on_trigger() are written correctly. Syntax highlighting and coloring may help you identify these issues.
# When resolving widgets, verify the used widgets address (e.g. "/mxw/render/opacity") and make sure that it is valid. To find the correct address, maybe refer to the list of address suggestions available in the 'Receiver' menu.