THD-Labs

How do I install the Tangerine Automation Interface ?

Installation is simple;

  1. Connect the SSL's VCA 50 pins flat cables to the interface.
  2. Connect the "Automation enabler dongle" to the SSL's 50 pins "keyboard" connector on one side and to the "Tangerine Automation Interface" accessory port with a Cat5/RJ45 cable.
  3. ​Connect the Interface's USB port to the computer running the DAW.

How do I set up audio track outputs from the DAW?

Depending of the "mix mode":

1. In OTB mode : DAW tracks audio output must be configured to be Pre-fader; this can be done by creating a pre-fader send from the DAW mixer on each track

2. In ITB and hybrid mode​ : Track volume changes are made in the DAW, not the SSL VCAs.  Audio output is taken from the output assignment in the DAW mixer

How do I setup the Tangerine Automation Interface and my DAW to work together ?

When the interface is installed and up and running, from the configuration setup mode, select the desired fader scale, mix mode (ITB/OTB) and "after write go to..." mode.  The interface is now ready to be used. On the computer side, make sure that the "plug and play" USB interface is seen in the midi "setup" control panel.

In the DAW's preferences,

  1. Configure Midi communication:
    Configure the control surface setup to sequentially assign the Tangerine Automation Interface's multiple HUI ports to the DAW's channel in a 8 channels per bank sequence.
  2. Configure the automation preferences:
    Configure the DAW's automation preference so that it doesn't change automatically to "READ" or "LATCH' after a automation "WRITE" (it should be on "do nothing"or "no change"), The tangerine will take car of that.
  3. Setup for Midi PLAY/STOP messages:
    The Daw should be configured to transmit and receive Midi Transport commandes, this is usualy refered as "MIDI BEAT CLOCK" or "MIDI SYNC". If using "Protools", in the SETUP/MIDI/MIDI BEAT CLOCK menu, enable communication with the Tangerine Automation Interface's port #5.

How do I use the Tangerine Automation interface ?

On the SSL: the faders moves and mutes switches status will send the correct information to the DAW according to the selected automation mode, The automation mode are selected by pressing the channels status switches.

In the DAW: Volume and mute information will be "read from" or "written to" the track's as volume envelopes. Depending on the selected MIX CONFIGURATION MODE, the volume information will be sent to the SSL's VCAs and mutes (OTB mode) or will be controlling the DAW's volumes while the SSL's VCAs are set at 0db (ITB mode).

The different automation modes

In OTB mode: OFF, READ, WRITE, LATCH

In ITB and HYBRID modes: OFF, READ, WRITE, LATCH, TRIM WRITE, TRIM LATCH TRIM READ.

What about Total Recall? How does it work?

We named it "Recall-IT", it uses Internet Technology to display the SSL's layout as a web page.

In "recall-it' mode, the Tangerine Automation Interface scans the switches and potentiometers from the SSL console.  The data is saved in the DAW as a high-resolution MIDI NRPN data stream and recorded on a MIDI track. This way, the console's recall setup is saved as part of the automation session.

Playing back the MIDI track from the DAW's automation session loads the saved recall setup to the Tangerine Automation Interface.

The Tangerine Automation system uses dynamic web page, generated from it's built-in web server to display a view of the actual "matched" and "unmatched" potentiometers/ switches, from the last loaded recall setup. 

What are OTB, ITB and HYBRID mix modes?

These terms refer to different ways the Tangerine Automation Interface and the SSL signal flow are configured. All following workflows are possible:

1. OTB mix mode

       SSL is used for:

  • Fader moves input to DAW 
  • VCA volume control from DAW
  • Audio summing

       DAW is used for:

  • Volume and mute automation data, write/read/edit to and from SSL

2. HYBRID ITB/OTB mix mode​

       SSL is used for:

  • Fader moves input to DAW 
  • Audio summing​

       DAW is used for:

  • Internal volume control of audio tracks
  • Volume and mute automation data, write/read/edit to and from tracks

3. Pure ITB mix mode​

       SSL is used for:

  • Fader input to DAW
  • Audio monitoring

       DAW is used for:

  • Internal volume control of audio tracks
  • Volume and mute automation data, write/read/edit to and from tracks
  • Audio summing

What are the ''PROS'' and ''CONS'' of the OTB and ITB mix modes ?

1. In OTB Mode

      PROS :

      +​ External dynamic processing can be used "in insert" on the SSL since the received audio signal will be pre-fader

      CONS :

      -​ A maximum of 32 automation tracks can be used if protocols are the DAW software

      - Live fader automation TRIM modes can't be used, the VCA data is not sent from the DAW software when this mode is selected (fader is set to 0 db...)

      - TRIM as to be done directly on the track volume envelope (Is this really a con...?)  

2. In hybrid ITB/OTB mode​

      PROS :

      +​ There is no track count limitation. Protools can be used (accessing the 32+ tracks is done by fader bank switching in the DAW software.)

      + Automation TRIM modes can be used from the SSL faders

      CONS :

      -​ External dynamic processing can't correctly be used "in insert" on the SSL, because the received audio signal will be Post-fader, thus affecting the threshold setup of the processing units

3. In ITB mode

      PROS :

      +​ There is no track count limitation. Protools can be used (accessing the 32+ tracks is done by fader bank switching in the DAW software.)

      + Automation TRIM modes can be used.

      CONS :

      -​ Everything is "in the box"; SSL is only used as a remote