Novation remote sl 用户指南
16
5.3 AUTOMAP AND THE REMOTE SL’S MIDI PORTS
The ReMOTE SL has three virtual MIDI ports over the USB connection. USB ports 2 and 3 are used for transfer of
Automap data between the ReMOTE SL and the computer. Port 2 is used for transferring Automap data between a
sequencer program and the ReMOTE SL (i.e. Sequencer Automap). Port 3 is used for transferring Automap data between
the Automap Server software and the ReMOTE SL. If you are using Automap, it is important to only select port 2 or 3 in
your software where instructed in this guide.
The ReMOTE SL has three virtual MIDI ports over the USB connection. USB ports 2 and 3 are used for transfer of
Automap data between the ReMOTE SL and the computer. Port 2 is used for transferring Automap data between a
sequencer program and the ReMOTE SL (i.e. Sequencer Automap). Port 3 is used for transferring Automap data between
the Automap Server software and the ReMOTE SL. If you are using Automap, it is important to only select port 2 or 3 in
your software where instructed in this guide.
USB Port 1 is used for transfer of all non-Automap data between the ReMOTE SL and your computer. This includes
keyboard note and aftertouch, pitch bend, modulation, expression and sustain pedals, and program/bank change data. All
factory standard (non-Automap) templates send data on USB Port 1 too. Ensure only ReMOTE SL Port 1 is selected as the
input to MIDI tracks in your sequencer.
keyboard note and aftertouch, pitch bend, modulation, expression and sustain pedals, and program/bank change data. All
factory standard (non-Automap) templates send data on USB Port 1 too. Ensure only ReMOTE SL Port 1 is selected as the
input to MIDI tracks in your sequencer.
When controlling plug-ins using Automap Universal, it is important to remember that the keyboard, joystick and pedal
inputs on the ReMOTE SL will NOT follow the currently selected Automap-wrapped plug-in. They will always send data
to whichever MIDI track is record enabled in your sequencer, meaning you can simultaneously play a soft-synth from
the keyboard and use the controls to tweak the parameters of a different plug-in. If you select an Automap-wrapped
instrument plug-in for control then you must also record enable the corresponding MIDI or instrument track in your
sequencer before the keyboard, joystick and pedals will control it.
inputs on the ReMOTE SL will NOT follow the currently selected Automap-wrapped plug-in. They will always send data
to whichever MIDI track is record enabled in your sequencer, meaning you can simultaneously play a soft-synth from
the keyboard and use the controls to tweak the parameters of a different plug-in. If you select an Automap-wrapped
instrument plug-in for control then you must also record enable the corresponding MIDI or instrument track in your
sequencer before the keyboard, joystick and pedals will control it.
5.4 AUTOMAP TEMPLATES AND STANDARD TEMPLATES –
WHAT IS THE DIFFERENCE?
Templates 1-33, 35 & 36 on the ReMOTE SL are ‘standard’ templates, so called because when they are selected the
ReMOTE SL functions as a standard MIDI controller. A standard MIDI controller allows you to set what MIDI message
each of its controls sends. If you want to control software or hardware that responds to MIDI then you need to know what
messages it responds to. This information can usually be found in the documentation for the software or hardware. Once
you know this, you can set up the controls on a standard MIDI controller to send those messages.
WHAT IS THE DIFFERENCE?
Templates 1-33, 35 & 36 on the ReMOTE SL are ‘standard’ templates, so called because when they are selected the
ReMOTE SL functions as a standard MIDI controller. A standard MIDI controller allows you to set what MIDI message
each of its controls sends. If you want to control software or hardware that responds to MIDI then you need to know what
messages it responds to. This information can usually be found in the documentation for the software or hardware. Once
you know this, you can set up the controls on a standard MIDI controller to send those messages.
We have used this method to program the standard templates on the ReMOTE SL to work with popular software
instruments (except templates 35 and 36, which are blank user standard templates). These templates can be used where
it is not possible or desirable to use Automap Universal for controlling software instruments, for example when using a
software instrument as a stand-alone program rather than a plug-in within a sequencer.
instruments (except templates 35 and 36, which are blank user standard templates). These templates can be used where
it is not possible or desirable to use Automap Universal for controlling software instruments, for example when using a
software instrument as a stand-alone program rather than a plug-in within a sequencer.
With standard templates there is only one-way communication from the ReMOTE SL to the software or hardware you are
controlling and the ReMOTE SL has no way of knowing when a parameter is changed from the software or hardware itself.
For example, if you change a parameter on a software instrument with the mouse, the parameter value displayed on the
ReMOTE SL will not update to reflect that change.
controlling and the ReMOTE SL has no way of knowing when a parameter is changed from the software or hardware itself.
For example, if you change a parameter on a software instrument with the mouse, the parameter value displayed on the
ReMOTE SL will not update to reflect that change.
The Automap templates have been set up such that the controls send MIDI messages that are recognised by the Automap
software i.e. the Automap Server or Sequencer Automap implementation. The Automap software then “automatically
maps” those MIDI messages to different plug-in or sequencer parameters, depending on what you select to control.
Because Automap incorporates two-way communication between your computer and the ReMOTE SL, the Automap
software can send display data back to the ReMOTE SL to automatically name the controls and let you know which
parameter each control is currently assigned to. Additionally you can see the current value of each parameter, even if it is
being changed using the mouse.
software i.e. the Automap Server or Sequencer Automap implementation. The Automap software then “automatically
maps” those MIDI messages to different plug-in or sequencer parameters, depending on what you select to control.
Because Automap incorporates two-way communication between your computer and the ReMOTE SL, the Automap
software can send display data back to the ReMOTE SL to automatically name the controls and let you know which
parameter each control is currently assigned to. Additionally you can see the current value of each parameter, even if it is
being changed using the mouse.
5.5 RECORDING PARAMETER AUTOMATION WHEN USING AUTOMAP
To record control movements from the ReMOTE SL in a sequencer when using a standard template, you must record
enable a MIDI track and then put the sequencer into record. MIDI control data will then be recorded onto the MIDI track
when you operate a control on the ReMOTE SL.
To record control movements from the ReMOTE SL in a sequencer when using a standard template, you must record
enable a MIDI track and then put the sequencer into record. MIDI control data will then be recorded onto the MIDI track
when you operate a control on the ReMOTE SL.
When using an Automap template, MIDI control data is converted into Automation data by the Automap software i.e. the
Automap Universal Server or Sequencer Automap implementation, to allow control over software parameters. This means
that control movements will not be recorded as MIDI data.
Automap Universal Server or Sequencer Automap implementation, to allow control over software parameters. This means
that control movements will not be recorded as MIDI data.