How do I achieve a 40 track mixdown on Matrix?
When Matrix is being used for mixdown and the channel is being fed from the DAW return the main channel input (Line In) can be used to create an extra input channel. This is done by selecting INPUT as the source of the Stereo Cue and then pressing TO MIX within the CUE ST area of the desk's centre section. This will give 32 inputs, a further 8 inputs can be achieved by assigning the Stereo Returns to the MIX bus.
Why can I not select DAW MONITOR mode?
To use DAW MONITOR mode, the channel input must be set to INPUT, and the CHOP source must not be post fader.
Can I meter the Analogue channel meters whilst in DAW Focus mode?
By default the meters follow the console's Focus mode but by pressing the ANALOG button in the SSL/MISC/METERS soft key menu, the meters are locked to the analogue channel levels when switched to DAW.
Is it safe to use SOLO IN PLACE (SIP) when recording?
Yes, if the CHOP is sourced from the input or pre-fader and if all other elements of the monitor or headphone mix are sourced pre fader then the signal will remain unaffected by a solo. Also ensure that the InpCu option in the MISC soft key menu is not enabled as this will cause pre fader sends to mute when a solo mute is received. Otherwise monitor via the non destructive Stereo AFL option which can be selected via the SSL options menu.
What is the best way to use solo in 32 channel mixdown mode?
In 32 channel mixdown mode, solo buttons are only available for the main 16 channel strips, fed by the DAW Return inputs. Enabling the InpCu option in the MISC soft key menu will cause pre-fader sends to be cut when a solo button is pressed, so the 16 LINE IN inputs that are routed through the Cue bus will be muted, as they should be, when a solo button is pressed.
However, if a comprehensive solo functionality is required in the context of a 32 track mixdown from a DAW, the solo function in the DAW will offer more possibilities.
What is Matrix's SuperCue function?
SuperCue allows for the simultaneous monitoring of the channel's input and DAW return signals via the Stereo Cue send bus. The DAW transport record tally is used to mute the DAW return signal. This allows for zero latency source monitoring as well as pre record punch confidence monitoring of the source and track.
Why is the audio cutting in and out during pre-roll?
It has been found that if you are using the Logic auto-punch feature with Matrix SuperCue enabled the audio will intermittently cut in and out during pre-roll. Please refrain from using these features simultaneously and manually drop into record when using Matrix SuperCue with Logic.
Can Matrix be integrated with X-Rack Total Recall?
Yes, Matrix (and AWS) can be integrated with X-Rack. All of the switch and rotary X-Rack controls can be stored along with Matrix's recall objects. Currently you can connect up to four X-Racks to Matrix. This will be expanded to six in a future software release. Each X-Rack is supplied with a 2 meter 9 way D type serial cable to allow connection to Matrix.
This may be extended to a maximum of 15 metres using a suitable pin to pin extension cable.
What is Matrix's SuperAnalogue™ router?
The Matrix SuperAnalogue™ router manages the sends and returns of up to 16 outboard processor units together with the assignment of the console's channel strip insert points. Using the Insert Matrix control panel software, any combination of your outboard gear can be rapidly inserted into any of your console channels, essentially giving you the ability to run your outboard as 'analogue plug-ins' within your DAW.
The Matrix is an analog console and does not have latency.
The Matrix's assignable insert points and effect chain relies on an integrated SuperAnalogue™ router. While this system is programmable, it does not introduce any latency because the signal path remains entirely in the analogue domain. External digital processors however will introduce latency.
Why is the digital output level extremely low and not changing?
Please turn the Matrix on before turning on external AES devices to prevent this issue. Some users have reported no signal over the AES output. In circumstances where measurements were able to be taken, typically the level reads around -138 dBFS and changing levels on the console makes no difference. This has been replicated by SSL, and is due to instances of back-power being fed into the AES inputs from some external hardware during the boot-up sequence of Matrix, which causes the AES outputs to fail.