All of these were read from the app's menu construction; labels are verbatim.
Application menu
Command
Shortcut
Check for Updates…
-
File
Command
Shortcut
New set
⌘N
Open set…
⌘O
Import media…
⌘I
Save set
⌘S
Save set as…
⇧⌘S
Edit
Command
Shortcut
Undo set edit
⌘Z
Redo set edit
⇧⌘Z
Composition
Command
Shortcut
Previous bank
-
Next bank
-
Import banks from set…
-
Edit layers, columns and banks…
-
Media manager…
-
Performance
Command
Shortcut
Pause / resume
Space
Blackout
⌘B
Output settings…
⇧⌘O
Fullscreen output ▸ (one entry per display)
-
Open windowed output
-
Close output
-
Tap tempo
T
Resync beat clock
R
Trigger column 1…10 on selected layer
1 … 9, 0
Clear all layers
⌘⌫ (Delete)
Layout
Command
Shortcut
Compact window
⌘⌥1
Reference window
⌘⌥2
Customize and save layouts…
-
Saved named layout entries
-
Reset standard layout
-
Others
Command
Shortcut
Preferences…
⌘,
Ultimate VJ shortcuts (the in-app help sheet)
-
The last item is the in-app help sheet. Standard AppKit equivalents for Quit, Hide and so on are not
re-declared by the app.
Keys that work without learning
Key
Action
1 … 9, 0
Trigger that column on the selected layer, as a held press
Space
Pause / resume
T
Tap tempo
R
Resync beat clock
Escape
Close the clean output window; cancel a keyboard learn
Return (focused tile)
Send Live
⌥Return (focused tile)
Send Preview only
Clipboard and selection keys
These act on the current selection, are intercepted only in the console window, and never fire while you are
editing text:
Key
Action
⌘A
Select all visible populated clips
⌘C
Copy
⌘X
Move
⌘V
Paste
⌘D
Duplicate
Mouse modifiers in the matrix
Gesture
Action
Plain click
Trigger live, except the preview zone
⌘-click
Toggle in selection
⇧-click
Select rectangle from anchor
⌘⇧-click
Add rectangle
Release on an empty tile
Open Source Browser
Modifier flags are read at mouse-down, so a modifier click never triggers.
About the unmodified keys
Space, T, R and the digits are handled both as local pressed-key handling and as declared menu
key-equivalents. Which of the two wins in the running app - and therefore whether a learned mapping on one
of those keys is ever reachable - is not established from reading the source. If you plan to rely on
them during a show, test that specific combination first.
Not verified
Behaviour of Function, Caps Lock and dead/accent keys: no special handling was found, so they behave as
plain key codes, but nothing in the source confirms it.
