Manualshelf

11.0

ManualsBrandsMagix Xara ManualsApplicationsSamplitude
341342343344345346347348349350
Table Of Contents
342 HARDWARE CONTROLLER
tracks. Depending on the number of tracks on the controller and your preferred working
method, you can set different step intervals per bank.
MIDI ping to controller: Most controllers expect a periodic incoming MIDI message (ping)
to ensure that there is communication with the application. In addition, different messages
can replace a controller in different operating modes. Enter the message that is to be sent
to the controller.
MIDI ping from controller: As a response to ping messages, controllers usually send a
ping message. So that no confusion results, you can explicitly enter these so that they can
be ignored by the application.
Display interval (ms): Display control occurs in certain time intervals and not continuously.
This limits the amount of display information. A small interval accelerates the display on the
controller, but enlarges the amount of MIDI data that needs to be transferred.
Locator interval (ms): Locator display control also takes place in intervals. If the time
position within an interval changes, only the current value is sent to the controller after it
expires. Reduce this interval and the locator display reacts more directly and quickly.
AnySolo LED: Some controllers possess an LED which indicates that at least one track in
the project has an active "solo" function. Since no button belongs to this LED and it is not
learnable, you can set the corresponding MIDI message here.
Manual hardware ID: For display in "Mackie Control" display mode, an additional
parameter is necessary: the hardware ID. This can be automatically queried with new
firmware versions or manually entered.
Query hardware ID: Activate or deactivate the automatic hardware ID query. Deactivate
this function if you aren't using the "Mackie Control" display mode. This helps to avoid the
wrong interpretation of the query message.
Ignore SysX input data: SysX data sent from the controller won't be processed by the
application.
Don't send SysEx: Samplitude sends different messages via SysEx. What is sent exactly
depends on the selected display mode, locator mode, etc. If problems occur with SysEx
messages while using a controller, then you can use this to eliminate sending of such
messages to the hardware controller.
Fader touch activates track: This option activates the track that belongs to the fader in
the application when a touch-sensitive fader is affected.
No fader update after release for motorized faders: When you move touch-sensitive
faders, the fader messages to the controller are normally ignored by the controller.
However, after release, the controller requires a positioning message. If this isn't sent, the
fader will reset to its last position before being moved. Some controllers don't require this
new position message. They jump upon receiving to the new position first to the old and
then to the new one. To avoid this, deactivate the sending of new positions.