TouchOSC Layout for GrandMA2 – Troubleshooting & FAQ

1.1 TouchOSC not connecting to MA2 (TouchOSC → Bridge)

This generally indicates a local network configuration issue rather than a layout error.

TouchOSC sends MIDI to TouchOSC Bridge on your computer.

Bridge then forwards it to MA2.

If TouchOSC → Bridge fails, MA2 never receives anything.

For this chain to work, three conditions must be true:

1. Tablet and PC must be on the same local network

Same Wi-Fi, same router, same subnet.

Example of a correct setup:

• Tablet: 192.168.1.42
• PC: 192.168.1.10

If your IPs live in different families (10.x.x.x vs 192.168.x.x, or 192.168.0.x vs 192.168.1.x), they are simply not on the same LAN.

2. TouchOSC Bridge must be running on the computer

If Bridge is closed, TouchOSC has nowhere to send MIDI.

Open Bridge first → then open TouchOSC.

3. Your router must allow local traffic

This is where most connection problems happen.

Many ISP routers (Freebox, Livebox, Vodafone, Spectrum…) are designed for internet, not local protocols like:

• UDP packets
• broadcast
• multicast
• peer-to-peer routing inside LAN

So they often:

• block UDP
• block multicast
• isolate Wi-Fi clients
• route packets externally instead of locally
• drop Bridge packets entirely

This breaks TouchOSC → Bridge.

Solution: Use a dedicated local router

Deploying a standard, dedicated local router resolves the majority of these UDP/Multicast drops.

An active internet connection is not required; only a clean local area network (LAN) is necessary.

Check if TouchOSC is actually sending signal (Protokol)

Use Protokol (free from Hexler):

1. Open Protokol on your PC
2. Tap buttons on TouchOSC
3. If you see MIDI events → TouchOSC → Bridge is working

If you see nothing:

• wrong Wi-Fi
• wrong subnet
• ISP router blocking traffic
• Bridge not running
• another network interface stealing priority

Before touching MA2, fix the TouchOSC → Bridge link.

For pictures of the full setup process (TouchOSC → Bridge → MA2), check the Setup Guide page.

1.2 Commands not responding in MA (Bridge → MA2)

If TouchOSC → Bridge works but MA2 does nothing, the problem is now between Bridge → MA2.

Check that MA2 is using the correct MIDI input

Go to : Yellow Ball → Options → MIDI Tab → “MIDI In Device”

Ensure:

• the correct device is selected
• nothing else is using the port

Then : Setup → Remote Inputs → MIDI Remotes → Press the “i” icon

Tap on a TouchOSC button.

If you see data → MIDI is arriving but not mapped correctly.

If you see nothing → MA2 is not listening to Bridge.

MIDI ports can only be opened by ONE program

This is the most common configuration oversight in MA2.

If any of these are open:

• a DAW (Ableton, Logic, Cubase…)
• a visualizer
• MIDI-OX, MIDI Monitor, Protokol or any monitor tool
• another TouchOSC instance
• another MIDI utility

… the port is locked by the operating system, and MA2 will receive zero input.

Close everything except:

• MA2
• TouchOSC Bridge

(Keep Protokol only during testing; close it afterwards.)

Advanced setups with virtual ports work, but only if you know exactly what you’re doing.

Confirm MIDI Remotes are imported correctly

If MA2 is receiving MIDI but nothing reacts:

• Remote table not imported
• XML overwritten incorrectly
• missing plugin installation
• wrong index numbers
• wrong MIDI channel
• Special Masters not assigned

For pictures of the full setup process (TouchOSC → Bridge → MA2), check the Setup Guide page.

1.3 My MIDI Remotes were erased

MA2 overwrites the entire MIDI Remote table every time you import an XML file.

There is no merge function inside MA2.

If you need additional remotes on top of this layout, you technically have two options:

1. Merge the XML files manually with a text editor (copy or paste remote entries without breaking the index numbers).
2. Re-create your custom remote lines manually in MA2 after installing the layout.

Keep in mind: this layout already uses almost all MIDI Remote slots. There are only 17 entries left, so merging is rarely worth it unless you really need those extra triggers.

For a clean solution, the most robust method is to add your custom MIDI Remotes directly inside the plugin before installing. That keeps everything in one place and avoids conflicts.

1.4 Plugin / Special Master issues

Make sure you run MA2 version 3.8 or higher.

If needed, go to Executor Page 101 and manually re-run the assignment macro or the LUA plugin.

To see what the plugin actually did, check the Command Line feedback and the System Monitor window. They will show you the full execution log, including any errors.

1.5 Macros or XML not importing

You are probably using MA2 v3.7 or lower.

Upgrade to 3.8.x.

1.6 Layout feels laggy on old devices

This layout contains around 9,500 objects, multiple pop-ups and scripted modules.

Most modern tablets handle it without issues, but very old devices may feel slower, especially when many pop-ups are open at the same time.

Quick things to try first:

• close background apps
• keep the device plugged in

I have tested the layout on a wide range of tablets and phones and it runs smoothly in normal conditions.
However, legacy hardware may experience performance throttling due to the rendering demands of TouchOSC and the high object count.

If you are using an older tablet and need a lighter version of the layout, contact me. I can prepare a simplified variant or remove specific modules for you without breaking the internal logic.

2.1 Do I need MA hardware to output DMX?

Yes. MA2 onPC requires official MA hardware for DMX output.

2.2 Can I use the layout with a real MA2 console?

Yes. If your PC is in the same session, everything works great.

2.3 Can I use wired MIDI instead of TouchOSC Bridge?

Yes, TouchOSC can send MIDI either over Wi-Fi (via Bridge) or directly over USB, depending on your device.

1. TouchOSC Bridge (Wi-Fi MIDI) — easiest

This is the default method and the one recommended for most users.

• Tablet communicates over Wi-Fi
• TouchOSC Bridge runs on your computer
• Bridge creates a virtual MIDI port that MA2 receives

This is the simplest setup and requires no extra cables or drivers.

2. USB-MIDI (wired) — more stable, for advanced users

In this case, TouchOSC behaves like any other USB-MIDI controller.

Some tablets can act as a USB-MIDI device when connected with a cable.

In this case:

• TouchOSC sends MIDI directly over USB and behaves like any other USB-MIDI controller
• No Wi-Fi
• No TouchOSC Bridge involved
• MA2 receives MIDI from the USB port instead of the Bridge port

This method requires:

• a tablet that supports USB MIDI peripheral mode
• a proper USB OTG / USB-C cable
• manual selection of the USB MIDI port inside TouchOSC

It is more stable than Wi-Fi and often has lower latency, but configuration varies depending on the device.

Which one do I recommend?

• For plug-and-play: use TouchOSC Bridge (Wi-Fi)
• For advanced users / maximum stability: USB-MIDI (wired)

Both ways work with this layout as long as MA2 receives MIDI from the correct input port.

2.4 Does the layout sync between two tablets?

Not yet.

Multi-tablet sync is planned, but requires major internal rewriting.

2.5 Is the layout safe to edit?

Yes, as long as you use the built-in Edit Mode in the layout.

Edit Mode blocks all MIDI to MA2, so nothing can trigger cues or commands by mistake. It is designed for safe renaming and recoloring during rehearsals or setup.

If you want deeper modifications (adding pages, rebuilding UI, editing scripts or groups), use the TouchOSC Editor on a computer. Advanced editing is not recommended during a live show.

2.6 Can I request features?

Yes. Most additions come from user requests.

2.7 Is it compatible with MA3 Mode2?

Yes. Confirmed working on grandMA3 2.1.1.5 using Mode2 (engine 3.9.60.82)

All features of the layout have been tested and function as expected.

If MA3 introduces changes in future updates, compatibility will be reviewed again.

2.8 TouchOSC Mk1 vs Mk2

This layout will never be available for Mk1.

Why:

• Mk1 lacks almost everything the layout uses internally
• Porting would require rebuilding around 9,500 objects manually

Backporting to Mk1 is architecturally unfeasible and unsupported.

2.9 Required MA2 Version (3.8+) and downgrading

Why MA2 3.8 is required

The layout was fully developed and tested on MA2 3.8.x, so all macros, plugin actions and MIDI Remote behavior match this version.

Can I downgrade to an older MA2 version?

Yes, it is technically possible, but not officially supported.

Downgrading requires manually editing the XML headers of:

• MIDI Remote XML
• Macro XML

so that the older MA2 version accepts them.

This is only recommended if you know what you’re doing.