FXpansion GURU 1.5 MIDI implementation - Manual (Page 13)

1
Parameter table, ENGINE-GLOBAL parameters (ch10 only)
0: Master Volume
1: Master Pan
2: Master Pitch
3: Master Mute
4: Master Solo
Just-In-Time (Volatile) NRPNs for Graph automation
(ch 1..8 only)
‘Engine’ and ‘Pad’ selection elements in hi-word work as above.
PARAMETER selects a graph step parameter to modify for the next note-on event on
the selected engine and pad:-
0: Volume
1: Pan
2: Repeat
3: Shift
4: Cutoff
5: Resonance
6: Pitch
7: Fine tune
8: Scrub
9: Force Layer
8: MMC implementation – standalone version only
The GURU standalone application responds to MMC for transport and Commit/Undo functions during recording.
MMC commands GURU function
0 and 9 (Stop and Pause) Stop
2 and 3 (Play and Deferred Play) Play
6 and 7 (Record and Record Strobe) Record
4 (FWD) Undo
5 (RWD) Commit
Note: the MMC functions chosen for Undo and Commit may seem illogical – however, they were chosen because the arrange-
ment of these buttons in the GURU user interface resembles the RWD/FWD layout on most MMC transports.
Most hosts do not route MMC to plugins, so if you want to remote-control GURU’s transport controls when running it as a plugin,
you should use the MIDI note assignments for these functions – see sections 2 and 3 for more details.
Of course, as long as the ‘Ignore host transport and tempo’ setting is not enabled, GURU is synchronized to the host transport.
Therefore, whatever you use to control your host’s transport also controls GURU’s synchronized transport.
9: MTC sync – standalone version only
The GURU standalone application is capable of synchronizing to MIDI TimeCode (MTC).
To enable this function, enable the ‘Sync to MTC’ option on the GURU standalone application’s menu-bar:
• On Windows, this is a menu called ‘Preferences’
• On Mac, use the GURU menu-bar item
If you are using GURU as a plugin and need to synchronize to an external source, you must use the host’s sync functions.