Manual

UniWire Manual Supplement 18 Muse Research, Inc.
MIDI Only Option
Check this option to prevent the UniWire instance from transmitting audio data over UniWire. This is
particularly useful if, for example, you’re using a UniWire instance to control a specic plugin’s MIDI
parameters and another UniWire instance is already being used to transmit audio processed by that plugin.
For example, assume that you have the Minimonsta instrument assigned to Receptor CH˛1’s Source slot, the
PSP˛Nitro effect assigned to the FXA slot, and you want to control both plugins from your host sequencer via
UniWire.
To do this:
1 In your host sequencer, create two new virtual instrument tracks: Track˛1 will be used to control the
Minimonsta plugin assigned to Receptor’s CH˛1/Source slot and Track˛2 will be used to control the
PSP˛Nitro plugin assigned to Receptor’s CH˛1/FXA slot.
2 In Track˛1 of your host sequencer, instantiate a UniWire plugin. Set the plugin’s Send˛MIDI˛To parameter to
‘Receptor˛Channel˛1’ and the To˛Control˛The parameter to ‘SOURCE˛VSTi.’
All MIDI data contained in sequencer Track 1 (both notes and MIDI CC) will control the Minimonsta plugin on
Receptor Channel˛1 and audio will be routed out of Receptor CH˛1 back into your host sequencer.
3 In Track˛2 of your host sequencer, create a new instantiation of the UniWire plugin (do not use the
same instantiation you created to control the Minimonsta). Set this plugin’s Send˛MIDI˛To parameter to
‘Receptor˛Channel˛1’ and the To˛Control˛The parameter to ‘FX˛A˛VST˛Effect.’
4 Enable (check) the MIDI Only option.
All MIDI data contained in sequencer Track˛2 will control the PSP˛Nitro plugin on Receptor’s CH˛1/FXA but no
redundant audio from Receptor CH˛1 will be returned to the host sequencer.
Using this method, you can create as many UniWire instantiations as you need to control as many Receptor-
hosted plugins or Receptor Mix parameters as you want.