Support
Installing the Tangerine Automation interface for Flying Faders is as easy as 1 - 2 - 3
For more detailed installation instructions you can refer to the Tangerine for Flying Faders user's manual.
The Tangerine Automation Interface for GML is installed directly inside your console.
For more detailed installation and troubleshooting instructions you can refer to the Tangerine user's manual.
Installing the Tangerine Automation interface for SSL is as easy as 1 - 2 - 3
For more detailed installation and troubleshooting instructions you can refer to the TAI for SSL E/G user's manual.
The Tangerine Automation Interface for SSL J/K is installed directly inside your console.
For more detailed installation and troubleshooting instructions you can refer to the Tangerine users' manual.
The Tangerine Automation Interface supports 3 dedicated workflows. On top of all original computer functions, each workflow offers different modern approaches to automation that certain users may prefer.
Initial set-up of your Tangerine Automation Interface is quick and easy.
After connecting your TAI to the console and to USB, install our Injektor software suite. Using Injektor's setup tab, you can choose your desired workflow and other comfort settings.
Depending on your chosen workflow, you may need to install additional software packages:
All that's left afterwards is setting certain settings inside your DAW (this only needs to be done once). Each DAW has its particularities and configuration steps vary by workflow. Complete information for each DAW and workflow is available in the Tangerine user's manual.
Fader moves and mute switch toggles are sent from your console to your DAW according to the selected automation mode. You can select the automation mode by pressing switches on your console or using onscreen controls.
Within the DAW, volume and mute information will be written to or read from track automation envelopes. How the DAW and console respond to this envelope is dependent on the choice of workflow:
Available automation modes depends on the workflow you're using.
The Injektor, Reaper/SSL and HUI-Hybrid workflows support all available automation modes: OFF, READ, WRITE, LATCH, TRIM WRITE, TRIM LATCH, TRIM READ.
The HUI-OTB workflow does not support TRIM modes. It only supports: OFF, READ, WRITE, LATCH.
Recall-iT is an improvement over SSL Total Recall. Available on SSL consoles with the required hardware, Recall-iT delivers all the same console layout information as Total Recall, but in a lightning-fast interface directly on your computer. Gone are the days of floppy disks.
Both channel mode and bank mode are available. Channel mode shows a single channel strip in its entirety. Bank mode shows a section of the strip for a full bucket of channels (ex: all dynamics for channels 1-8).
If you have been using SSL Total Recall without issue, your console has the required hardware for Recall-iT, you won't need anything else.
If you have never used SSL Total Recall with your console, it must have channel recall multiplexers installed and the center section bus driver card must be complete and functional. Each recallable channel must have its own recall multiplexer daughter card. In the event that your console is missing recall multiplexers on some channels, you can still use Recall-It, but those specific channels won't function.
Don't know where to find recall multiplexers or center section bus driver? We have a visual guide to locating the required hardware for Recall-iT within your console.
If you have an SSL 9000 J/K , your console supports Recall-iT.
When using Recall-iT, the current position of the console's switches and knobs are displayed inside the Injektor software. When a snapshot is created, Recall-iT scans every channel's pararmeters. The resulting high resolution snapshot is saved to file on your computer. When recalling a snapshot file, a distinctive red mark appears around all unmatched knobs and switches. To match, turn the knobs and press the switches until the all marks are cleared.
Since snapshots are saved to your computer, there is no limit to the number of snapshots the TAI can handle.
To save the current console state:
To recall a saved console state:
Voila!