The installer puts a small control surface script in your User Library. null.audio uses it to read Live's tempo changes, and EDIT uses it to add the EDIT Bridge for you. It sends no MIDI, adds no mappings and shows nothing on screen.
Restart Live once
Live reads control surface scripts when it starts. If Live was open while you installed null.audio, restart it once. The panel and the null.audio app say Restart Live once to finish installing null.audio. until you have. If Live was closed during the install, there's nothing to do.
On Windows the installer asks you to quit Live first, so this doesn't come up. You pick the script once instead (below).
macOS: Live picks it by itself
Live puts the script in the first free control surface slot, with its ports set. You don't have to open Live's settings.
If you turned it off in Live's settings, or Live didn't pick it, the panel tells you which row to set, for example: in Live › Settings › Tempo & MIDI, set Control Surface 5 to null audio. That's the row where Live left null.audio as Input and Output.
If there's no such row, set a free Control Surface to null audio, and its Input and Output to null.audio. On macOS, choosing null audio alone does nothing.
Windows: set it once
On Windows, Live can't pick the script by itself yet. The panel tells you when it's needed:
In Options › Settings › Tempo & MIDI, set a free Control Surface to null audio. Input and Output stay on None.
It connects in about a second, with no restart, and Live remembers it from then on.
null.audio in Live's Control Surface list
After you install 1.2, you'll see two new things under Tempo & MIDI in Live's settings. Both are null.audio's, and you can leave them as they are.
- null audio in one of the Control Surface slots. It takes up one of Live's six slots.
- null.audio as a MIDI port, as Input and Output of that slot and in the list of MIDI ports (macOS only). It's there while the null.audio app is running. The app sends no MIDI on it, so it can't reach your armed MIDI tracks.
On Windows there's no port, and Input and Output of the slot stay on None.
If you quit the null.audio app, the port goes away, the slot keeps null audio, and its ports show None. When the app starts again, it all comes back by itself. Setting the slot to None turns the script off, and then the Bridges and tempo changes work as described under Without the script.
When Live's control surface list is full
Live has six control surface slots. If all six are in use, nothing breaks, and you can still add the EDIT Bridge by hand. The panel says All six control surface slots in Live are in use.
- Go to Live › Settings › Tempo & MIDI (on Windows, Options › Settings › Tempo & MIDI).
- Set a Control Surface you don't use to null audio.
- On macOS, set its Input and Output to null.audio. On Windows, set them to None.
- In the EDIT panel, press Check again.
Without the script
EDIT and ALIGN still work without it, with two differences:
- You add the EDIT Bridge to each track yourself, as in 1.1.
- EDIT won't open a clip that plays across a tempo change. Clips where the tempo stays the same work as usual.
If you remove null.audio
The script and the device stay in your User Library when you remove null.audio. Live still starts with a slot on null audio. Without the null.audio app nothing answers it, and nothing else happens.
Still stuck? Write to contact@null.audio. In null.audio, Troubleshooting → Copy support report puts everything I need on your clipboard.