LAWO ruby User Manual

ruby

User Ma nual

Version: 6. 0. 0/ 4

To obtain the latest documentati on and software downloads, please visit :

www.lawo.com/downloads

Edition: 18 January 2018

Copyright

All rights reserved. Permission t o reprint or elect ronically reproduce any document or graphic in whole or

in part for any reason is expressly prohibited, unless prior written consent is obtained from the Lawo AG.
All t rademarks and registered trademarks belong to their respect ive owners. It cannot be guaranteed that

all product names, products , t rademarks, requisiti ons, regulations, guidelines, s pecificat ions and norms

are free from trade mark rights of third parties.

All entries in t his document have been thoroughly checked; however no guarantee for correctness can be

given. Lawo AG cannot be held responsible for any mis l eading or incorrect information provided throughout

this m anual.

Lawo AG reserves the right to change specifications at any t im e without notic e.

© Lawo AG, 2018

3/82

Table of Cont en t s

ruby User M anual V ersion: 6.0.0/4

Table of Con tents

1. Introduction ... .... .... .... .... .... .... ....... .... .... .... .... .... .... ....... .... .... .... .... .... .... ....... .... .... .... .... .... .... ....... .... .... .. 5

2. Important Safety Instruct ions ... .... .... .... .... .... .... ....... .... .... .... .... .... .... ....... .... .... .... .... .... .... ....... .... .... .... .... 6

3. The Hardware .... .... .... .... .... .... ....... .... .... .... .... .... .... ....... .... .... .... .... .... .... ....... .... .... .... .... .... .... ....... .... .... .. 8

3.1 System Components . . .... ....... .... .... .... .... .... .... ....... .... .... .... .... .... .... ....... .... .... .... .... .... .... ....... .... .... 9

3.2 DSP Core Compatibility ... .... .... .... .... .... .... ....... .... .... .... .... .... .... ....... .... .... .... .... .... .... ....... .... .... .... . 10

3.3 Controls Overview ... . . .... .... .... .... .... .... .... ....... .... .... .... .... .... .... ....... .... .... .... .... .... .... ....... .... .... .... ... 11

3.4 Control Surface Variants ... .... .... .... .... .... .... ....... .... .... .... .... .... .... ....... .... .... .... .... .... .... ....... .... .... .... 14

3.5 Placement Options . . . .... ....... .... .... .... .... .... .... ....... .... .... .... .... .... .... ....... .... .... .... .... .... .... ....... .... .... 16

3.6 Accessories . . . .... .... ....... .... .... .... .... .... .... ....... .... .... .... .... .... .... ....... .... .... .... .... .... .... ....... .... .... .... .. 17

4. Installation ... . . ....... .... .... .... .... .... .... ....... .... .... .... .... .... .... ....... .... .... .... .... .... .... ....... .... .... .... .... .... .... ....... . 18

4.1 Preparation . . .... .... ....... .... .... .... .... .... .... ....... .... .... .... .... .... .... ....... .... .... .... .... .... .... ....... .... .... .... .... 19

4.2 Installing Countersunk Frames .. . . .... ....... .... .... .... .... .... .... .... ....... .... .... .... .... .... .... ....... .... .... .... .... .. 20

4.3 Wiring .. . . .... .... .... .... .... .... ....... .... .... .... .... .... .... ....... .... .... .... .... .... .... ....... .... .... .... .... .... .... ....... .... .. 21

4.4 Working with the CAN Bus .. .... ....... .... .... .... .... .... .... ....... .... .... .... .... .... .... ....... .... .... .... .... .... .... ..... 23

4.5 CAN Bus Addressing ...... .... .... .... .... .... .... ....... .... .... .... .... .... .... ....... .... .... .... .... .... .... ....... .... .... .... . 24

4.6 Powering the Device .... . .... .... ....... .... .... .... .... .... .... ....... .... .... .... .... .... .... ....... .... .... .... .... .... .... ....... . 26

4.7 Exchanging the MF Key Labels ....... .... .... .... .... ....... .... .... .... .... .... .... ....... .... .... .... .... .... .... ....... .... . 27

5. Operation ... . . .... .... .... ....... .... .... .... .... .... .... ....... .... .... .... .... .... .... ....... .... .... .... .... .... .... ....... .... .... .... .... .... . 28

5.1 The Fader Strip ..... .... .... .... .... .... .... ....... .... .... .... .... .... .... ....... .... .... .... .... .... .... ....... .... .... .... .... .... ... 29

5.2 The Central Module(s) .. .... .... .... .... .... .... ....... .... .... .... .... .... .... ....... .... .... .... .... .... .... ....... .... .... .... .... 35

5.3 Assigning Fader Strips ..... .... .... ....... .... .... .... .... .... .... ....... .... .... .... .... .... .... ....... .... .... .... .... .... .... .... 37

5.4 DSP Parameter Control ... .... .... .... .... .... .... .... ....... .... .... .... .... .... .... ....... .... .... .... .... .... .... ....... .... .... . 39

5.5 Bus A ssign ... . .... .... .... .... .... .... ....... .... .... .... .... .... .... ....... .... .... .... .... .... .... ....... .... .... .... .... .... .... ..... 41

5.6 Conference Bussing (Mix Minus/ N-1) . . . .... .... .... .... .... .... ....... .... .... .... .... .... .... ....... .... .... .... .... .... .... . 43

5.7 VCA Grouping .... .... ....... .... .... .... .... .... .... ....... .... .... .... .... .... .... ....... .... .... .... .... .... .... ....... .... .... .... .. 45

5.8 Pool & RAVE NNA Sources ... . .... .... ....... .... .... .... .... .... .... ....... .... .... .... .... .... .... ....... .... .... .... .... .... .. 47

5.9 Working with Layers .... . .... .... .... ....... .... .... .... .... .... .... ....... .... .... .... .... .... .... ....... .... .... .... .... .... .... ... 50

5.10 Fader Mappings ... . ....... .... .... .... .... .... .... ....... .... .... .... .... .... .... ....... .... .... .... .... .... .... ....... .... .... .... .... 52

5.11 Configurable Surface Functions . .... .... .... .... ....... .... .... .... .... .... .... ....... .... .... .... .... .... .... ....... .... .... .... 53

5.12 Snapshots ....... .... .... .... ....... .... .... .... .... .... .... ....... .... .... .... .... .... .... ....... .... .... .... .... .... .... ....... .... .... 55

5.13 The SYS Menu ...... .... .... .... .... .... .... ....... .... .... .... .... .... .... ....... .... .... .... .... .... .... ....... .... .... .... .... .... .. 58

ruby User M anual

Table of Cont en t s

4/82 V ersion: 6.0.0/4

6. Maintenance .... . ....... .... .... .... .... .... .... ....... .... .... .... .... .... .... ....... .... .... .... .... .... .... ....... .... .... .... .... .... .... ..... 60

6.1 Checking the Hardware Status ... . .... .... .... ....... .... .... .... .... .... .... ....... .... .... .... .... .... .... ....... .... .... .... .. 61

6.2 Updating Firmware ...... .... .... .... .... .... ....... .... .... .... .... .... .... ....... .... .... .... .... .... .... ....... .... .... .... .... .... . 62

6.3 The Special Functions M ode ... .... .... .... .... .... .... ....... .... .... .... .... .... .... ....... .... .... .... .... .... .... ....... .... .. 63

6.4 Replacing Defect ive Parts ... . . .... .... .... ....... .... .... .... .... .... .... ....... .... .... .... .... .... .... ....... .... .... .... .... .... 69

6.5 Locating the Control Surface Serial Number .. . . .... .... .... .... ....... .... .... .... .... .... .... ....... .... .... .... .... .... .. 70

6.6 Cleaning the Control Surface .... . ....... .... .... .... .... .... .... ....... .... .... .... .... .... .... ....... .... .... .... .... .... .... .... 71

7. Trouble-shooting ........ .... .... .... .... .... .... ....... .... .... .... .... .... .... ....... .... .... .... .... .... .... ....... .... .... .... .... .... .... ... 72

7.1 Solving Connectivity Iss ues .... .... .... .... .... .... .... ....... .... .... .... .... .... .... ....... .... .... .... .... .... .... ....... .... ... 73

8. Appendices ... . . .... .... .... .... ....... .... .... .... .... .... .... ....... .... .... .... .... .... .... ....... .... .... .... .... .... .... ....... .... .... .... .. 74

8.1 Part Numbers . . . .... .... ....... .... .... .... .... .... .... ....... .... .... .... .... .... .... ....... .... .... .... .... .... .... ....... .... .... .... 75

8.2 Dimension Drawings .. ....... .... .... .... .... .... .... ....... .... .... .... .... .... .... .... ....... .... .... .... .... .... .... ....... .... ... 76

8.3 Connector Pin-Outs ... . .... .... .... .... .... .... .... ....... .... .... .... .... .... .... ....... .... .... .... .... .... .... ....... .... .... .... . 77

8.4 The 12V DC Power Supply . . . .... .... .... .... ....... .... .... .... .... .... .... ....... .... .... .... .... .... .... ....... .... .... .... .... 78

8.5 The User Labels Software .. . . .... .... .... .... ....... .... .... .... .... .... .... ....... .... .... .... .... .... .... .... ....... .... .... .... . 79

ruby User M anual V ersion: 6.0.0/4 5/82

1. Introduction

1. In trod uction

Welc ome t o ruby.

About this M anual

This document describes all aspects of the ruby control s urface, inc luding its hardware components, ins tallati on,
connections, operation and maintenance. The specificat ion is valid for Version 6.0.0.x.

The surface requires a DSP Core such as POW ER CORE and, optionally, may run with a Vis Tool M K2 touch­sc reen interface. You c an find more information on these products in the relevant manuals.

All Lawo manuals are av ailable from the Download-Center at www.lawo.com (after Login).
Look out for the following which indicate:

Notes - points of clarification.

Tips - useful tips and short cuts.

WARNINGS: Alert you whe n an action should always be observed!

Lawo User Registration

For access to the Download-Center and to receive regular product updates, please register at:

www.lawo.com/user-registration.

ruby User M anualV ersion: 6.0.0/46/82

2. Importan t Safety Instructions

2. Impo rtant Safety Instructions

General Safety

Warning

Exposure to exc es sive sound pressure levels can lead to impaired hearing and cause damage to the ear.
Please read and observe ALL of the following notes:

·

Check all of the hardware devices for transport damage.

·

Any devices showing signs of mechanical damage or damage from the s pillage of li quids MUST NOT
be connect ed to the mains supply or disconnected from t he mains immediately by pulling out the
power lead.

·

All devices MUST be grounded. Grounding connectors are provided on all devices. In addition, all low­voltage devices ex t ernal to the system mus t als o be grounded before operation.

·

For Sc andinavian countries, ALWAY S use a grounded mains c onnection, to prevent the devic e from
being grounded through Ethernet or other signal connections.

·

Do NOT use the sy stem at extreme temperatures - observe the temperature range and humidity
specified in the installation instructions.

·

Do NOT expose devices to liquids which may drip or splash.

·

Do NOT place objects filled with liquids, such as vases, upon a device.

·

Only service s t aff may replace batteries.

·

CAUTION: Danger of explosion if battery is incorrectly replaced - Replace only with the s ame or
equivalent ty pe.

Servic i ng of components ins ide a devic e MUST only be carried out by qualified servic e personnel according t o
the following guidelines:

·

Before removing parts of the casing, shields, etc . t he devic e MUST be s wit c hed off and disc onnected
from all mains.

·

Before opening a device, t he power supply capacitor MUST be disc harged with a suitable resistor.

·

Components that c arry heavy electric al loads, such as power transistors and resistors, s hould NOT
be touched until cool to avoid burns.

Servic ing unprotected powered devic es may only be c arried out by qualified service personnel at their own
risk. The following inst ruct ions MUST be observed:

·

NEVER touch bare wires or circ uitry .

·

Use insulated tools ONLY.

·

DO NOT t ouch met al s emi-c onductor cas ings as t hey can bear high voltages.

Eye Safety

Warning

This equipment may use Class 1 Laser products which emit i nvisible las er radiation that may lead to eye
injury.

·

NEVER look directly into optical components or optical fibre cables.

·

Fit protecti on caps t o c l os e any unused optical c omponents.

·

Connect all optic al fibre cables BEF ORE t urning on the equipment.

ruby User M anual V ersion: 6.0.0/4 7/82

2. Importan t Safety Instructions

Defective Parts/Modul es

Warning

ruby contains no user-serviceable parts. Therefore DO NOT open the devices other than to perform the

procedures described in this m anual.
In the event of a hardware defect, please s end the s yst em component t o your loc al service representative

together with a detailed description of the fault. W e would like to remind y ou to please check carefully
whether the failure is caused by erroneous configuration, operation or connection before sending parts for
repair. Please contact our servi c e department before sending parts for repair.

First Aid (in the ca se of electric shock)

Warning

DO NOT touch t he person or his /her clothing before power is turned off, otherwise you risk sus taining an
electric shock yourself.

Separate the person as quickl y as poss ible from the electric power source as follows:

·

Switch off the equipment.

·

Unplug or disconnect t he mains cable.

·

Move the person away from the power source by us ing dry ins ulating material (such as wood or
plastic).

If the person is unconscious:

·

Check their pulse and reanimate if their respiration is poor.

·

Lay the body down and turn it to one side. Call for a doctor immediately.

Having sust ained an electric shock, A LWAYS consult a doctor.

ruby User M anualV ersion: 6.0.0/48/82

3. The Ha r dware

3. Th e Hardware

This chapter describes the system components, controls, options and accessories.
Topics inc lude:

·

System Components

·

DSP Core Compatibility

·

Controls Overview

·

Control Surface Variants

·

Placement Options

·

Accessories

ruby User M anual V ersion: 6.0.0/4 9/82

3. The Ha r dware

3.1 System Components

A complete sys t em consist s of up to four components:

·

ruby Control Surface (essential) – available in single or split-frame configurations.

·

DSP Core (essential) – all audio interfacing, routing, control and signal processing.

·

VisTool MK2 (optional) – runs on an ext ernal PC to provide real-time dis play s and touch-sc reen control.

·

Key Panels (optional) – a range of panels offering additional keys and talkback c ontrol.
This document describes the ruby control surface.
For more information on other c omponents , s uch as t he DSP Core or Vi sTool MK2, please refer to t he manuals

for those products.

ruby User M anualV ersion: 6.0.0/410/82

3. The Ha r dware

3.2 DSP Core Compatibilit y

The ruby control surface is compatible with the following DSP Core products:

ruby User M anual V ersion: 6.0.0/4 11/82

3. The Ha r dware

3.3 Controls Overview

Each control surface consis ts of at least one Fader Module (with 4 fader strips), a s ingle Central Module, and up
to 6 additional Central Modules running in monitor mode.

Some of the control functionality i s fixed (sy s tem-defined), while some is programmable by t he configuration.

3.3.1 Fader Modules

Fader Module

Each Fader Module provi des four identical fader st rips, each with an ACCESS key, 100mm motorised fader,
backlight and label display.

The upper sect ion includes a rotary control and four s mall MF Key s (1, 1a, 2, 2b). Their functions are labeled by
the OLED displays.

There are then three large MF Keys (3, 4, 5) with foil-printed labels.
All MF K ey s are defined by the configuration.

ruby User M anualV ersion: 6.0.0/412/82

3. The Ha r dware

3.3.2 Central Modules

The Central Module (full mode)

Central Module (monitor mode)

Each control surface must inc lude one Central Module. If additional Central Modules exis t , t hen these must run in
monitor mode.

The Central Module (full mode)

The upper section inc ludes four s ets of rotary encoders and small M F Key s which interact wit h the 12 Functi on
Buttons: INP, DYN, LIM, etc. Their functions are labeled by the OLED displays . W hen none of the Function
Buttons are active, the c ontrols are defined by the configuration (MF Key s 29 t o 42 and VCAs 3 to 6). W hen a
Function Butt on is press ed, then the controls provide DSP parameter c ontrol, bus assign, sy stem options and
snapshots. To the left are two large MF Keys (45 & 46) with foil-printed labels.

In the lower sect ion are more large MF Keys (1 to 28) with foil-printed labels, and two rotary encoders (VCAs 1, 2)
which are labeled by the displays .

All MF K ey s and VCAs are defined by the configuration.

Central Modules (monitor mode)

Physically, these modules are identical to the full mode Central Module, but they provide slightly different
functionality.

Each module provides the same programmable MF Keys and VCA encoders, but in t he upper s ection the 12
Function Buttons are NOT supported. This means that there is no access to DSP parameters, bus assign,
sy stem options and snapshots. All controls are defined by t he configuration. Note that t he 12 Function Butt ons
cannot be programmed by the configuration and, therefore, will remain blank.

ruby User M anual V ersion: 6.0.0/4 13/82

3. The Ha r dware

3.3.3 Programmable Functions

Programmable controls, suc h as MF Keys and V CA encoders, are defined by the c onfiguration s tored on t he
DSP Core. They can be edited using the ON-AIR Designer s oftware, allowing you t o change the operation as
required.

In most cas es, the large MF Keys are labeled by foil-printed labels and, by default, t he c ontrol s urface ships with
the labels for the s tandard template functions. If you change the MF Key functionality, then you will need t o
exchange the foil-printed labels. P rinted sheets with the most c ommon labels are included with each control
surface frame.

ruby User M anualV ersion: 6.0.0/414/82

3. The Ha r dware

3.4 Control Surface Variants

8-fad er sing le frame

12-fa der split-frame

ruby can exist as a single or multi-frame control surface.
A choic e of four main and five extender frames are available. Frames c an be combined to increase the fader c ount

or create a split-frame surface. Each frame connects to the DSP Core via CAN bus, and is powered from its own
12V DC power supply (included). All frames include CAN BUS I N and CAN BUS LI NK OUT connectors for easy
daisy-chaining.

In total, a single control surface can include any number of frames as long as t he maxim um number of faders
does not exceed 60.

One of the frames must inc lude a Central Module but this can ex ist only once. Therefore, any additional Central
Modules will run in monitor mode. A s i ngle control surface can include up to 6 "monitor mode" Central Modules.

3.4.1 Main Frame Layouts

Four main frames are available. Each one includes a Central Module:

4-fader

8-fader

12-fader

16-fader

3.4.2 Extender Frame Layouts

Five extender frames can be added, either to increase the fader count or create a split-frame console.

4-fad er extender

8-fad er extender

12-fa der extender

16-fa der extender

Central Module ext.

ruby User M anual V ersion: 6.0.0/4 15/82

3. The Ha r dware

3.4.3 Split- f ram e Configurati ons

By combining different frames, you can easily create a surface suitable for multiple operators.
In the example below, the surface includes three frames:

·

1 x 8-fader main frame (for the Assis tant Operator)

·

1 x 12-fader main frame (for the Main Operator)

·

1 x 4-fader extender frame (for the Presenter)

By setting the correct CAN bus addresses, the order of fader strips and position of the Central Module is
flexible. In our example, the Main Operator's s tati on can house the Central Module plus fader strips 1, 2, 3, etc ,
even thoug h its CAN bus is wired after the Ass istant's s t at ion.

Multi-frame Con figuration

A si ngle control surface can support up to 60 faders, a single Central Module and up to 6 monitor mode
Central Modules.

ruby User M anualV ersion: 6.0.0/416/82

3. The Ha r dware

3.5 Placement Options

Each frame is available in one of three versions to provide different placement options. Note t hat t he version mus t
be specified at the time of ordering; t here is no possibili t y to convert the frame later.

Table Top

Countersunk

Coun tersunk Short

The differences in construction are:

·

Tabl e Top - designed to be mounted on a table-top surface. This version includes a leather front buffer

and styli sh side/rear profiles.

·

Countersunk - designed to fit flush within your studio furniture. This version comes with different front,

rear and side profiles.

·

Countersunk Short - the same as Countersunk but with shorter side profiles and no upper cover plate to

hide the cables (i.e. the rear panel connectors will be visible).

ruby User M anual V ersion: 6.0.0/4 17/82

3. The Ha r dware

3.6 Accessories

Each c ontrol surface frame ships with the following additional items:

·

1 x ext ernal 12V DC power supply - t o power the frame.

·

1 x 2m IEC power cable (country-specific) - to connect mains t o t he 12V DC power supply.

·

1 x 3m RJ45 cable - to c onnect t he CAN bus from the surface to the DSP c ore or another frame.

·

Printed sheets with a s election of foil printed labels - to label the MF Key s .
If your control surface c onsists of multiple frames, then you will receive one set of acc es s ories per frame (as every

frame requires its own power, CAN bus and MF Key labels).

ruby User M anualV ersion: 6.0.0/418/82

4. Installa tion

4. In stallatio n

This chapter describes how to install the control surface.
Topics inc lude:

·

Preparation

·

Installing Countersunk Frames

·

Wiring

·

Working with the CAN Bus

·

CAN Bus Addressing

·

Powering the Devic e

·

Exchanging the MF Key Labels

ruby User M anual V ersion: 6.0.0/4 19/82

4. Installa tion

4.1 Preparation

A si ngle control surface can consis t of one or more frames.

Unpacking

Each frame is delivered in its own box with all included accessories.
Please c heck t he c ontents of t he s hipping boxes , and in t he event of any t ransport damage, c ontact your local

Lawo repre sentative or email [e-mail].

Please take note of the Tec hnical Data label, which includes y our s erial number, l ocated on t he underside of
each frame. Write down the serial number for your records BEFORE mounting!

Dimensions and Weight

The dimensions and weight of the frame depend on its s ize and version: table-top, countersunk or countersunk
short. Drawings for 8-fader frame versions are included in t he Appendices. Drawings for other frame si zes are
available fr om the Download-Center at www.lawo.com (after Login).

Temperature and Cooling

The control surface is designed for normal studio installati on and needs no special air c onditioning.

Power Consumption & Electrical Voltage

Please see the 12V DC Power Supply appendix.

ruby User M anualV ersion: 6.0.0/420/82

4. Installa tion

4.2 Installing Countersunk Frames

Countersunk

Coun tersunk Short

Countersunk frames are optimized for easy countersunk mounting.
The frame has rounded-off edges so that it will fit s m oothly i nto holes cut by a wood milling machine.
For the countersunk (regular) versi on, all cables can be hidden in the cable t ray and connected t o t he console

inlets from the open underside of the tray.
For the countersunk short version, the t able mus t be designed t o provide a s mall opening in order to properly

cable the devic e.
All countersunk frames have flat s ide parts wit hout edges. Therefore, the installer must provide some kind of

support onto which t he surface will rest.
Please see the dimension drawings for details.

ruby User M anual V ersion: 6.0.0/4 21/82

4. Installa tion

4.3 Wiring

Each frame requires two connections: power and CAN bus.
In a split -frame configuration, you will need to daisy -c hain the CAN bus AND connect power to each frame:

Multi-frame Con figuration

All c onnectors are positioned on the rear panel, and so you must mak e sure that these are access ible. In the
table-top and countersunk versions, t he cable tray has an open underside and rear acc es s holes:

Rear View (single frame)

4.3.1 Power

Every frame is delivered with it s own external 12V DC power supply:

12V DC Po wer Supply (9 55/50 -80)

For dimensions, weig ht and electrical specification, please see the 12V DC Power Supply appendix.
The PSU is delivered with a 2m IEC power cable.

Ø

To conne ct power to the fra m e:

1. Connect the 12V DC power supply to the DC IN connector on the frame.

2. Using the IEC cable provided, connect your AC mains to the ext ernal power supply.

WARNING: The control surf a ce frame MUST be connected to t he mains us ing the power cable supplied with

the sy stem.

ruby User M anualV ersion: 6.0.0/422/82

4. Installa tion

4.3.2 Grounding

A grounding screw is provi ded beside the CAN bus connector to ground the frame. Use a M4x8 screw only.

4.3.3 CAN Bus

Can bus connections m ust be made using a s tandard (straight 1:1) network c able: STP-CAT 5 cable with RJ45
connectors on both ends.

The CAN bus uses only one of four available pairs of wires in the CAT-5 cable. S ee the Connector Pin-Out.

Every frame is delivered with a suit able cable.

Cabling

The following instructions desc ribe how to connect a ruby control surface to the DSP Core. Note that all
connections MUST be point-to-point; a s witc h or hub i s not allowed. The control surface can be hot-plugged via
CAN, and so the cabling can be performed while the frames are powered.

Ø

To conne ct a single fram e:

Rear View (Sin gle Frame)

1. Conn ect the DSP Core CAN connector directly to the control surface CAN BUS IN.

2. Fit the CAN bus terminator supplied with the sys tem to the CAN BUS LINK OUT.

Ø

To conne ct mul tip l e frames:

The CAN bus must be looped in a daisy chain fashion:

1. Start by c abling the DSP Core CAN connector to the first frame' s CAN BUS IN.

2. Th e n loop the first frame ' s CAN BUS LINK OUT to the CAN BUS IN connector on the next frame.

3. Continue to loop the CAN bus through the remaining frames (and any optional Key P anels). They may

be connected in any order.

4. On the last frame or Key Panel in the chain, fit the CAN bus terminator supplied with the sy stem.

ruby User M anual V ersion: 6.0.0/4 23/82

4. Installa tion

4.4 Working with the CAN Bus

Each control surface module, Key Panel and Vis ual Ext ension (sapphire only ) has a CAN bus address which
defines its role within the sys t em. In addition, t he CAN bus s peed defines t he max im um dist ance which you can
run the cables:

Transfer Speed

Maximum Distance

500 kbit/sec (recommended)

60 m

100 kbit/sec

300 m

Both s ettings are read by the s ys tem c onfiguration AND stored on eac h phys ic al module. They MUST match
exactl y to ensure correct operation.

The system configuration can be edited using the ON-AIR Designer software:

·

CAN bus a ddress is defined in the Frames -> S urface window.

·

CAN bus spe ed is defined in the Project window.
On each physical module, the settings can be adjusted by entering the s pecial functions m ode.
Now is a good time to c heck and, if necessary, adjust the CAN bus address and CAN speed sett ings for each

control surface module and Key Panel. A CAN speed of 500 kbit/ s ec is recommended.

ruby User M anualV ersion: 6.0.0/424/82

4. Installa tion

4.5 CAN Bus Addressing

The CAN bus address, als o known as t he Frame ID, is a unique address which defines the role of each c ontrol
surface module within the sy s tem.

Using the ON-AIR Designer, you can define the layout of your console by as s i gning a module to each CAN Bus
addr ess position (v ia the Frame -> S urface window):

·

Address 01 to 0F (hexadecimal) c an be assigned to Fader Modules.

·

Address 10 (hexadecimal) is always the Central Module. Every lay out inc ludes t his assi gnment.

·

Address 12 to 17 (hexadecimal) can be assigned to additional Central Modules (in monitor mode).

Frame -> Surface: ruby 4+1 CA N Bu s Add resses (hexa decimal)

Each address must be unique, so do not assign the same address to m ore than one module. If you do so,
this can lead to control conflicts and odd behaviour of the surface.

To mirror faders or other controls, use t he programmable logic features of the DSP Core, s uc h as " fader
mapping" or "source replicati on".

Default CAN Bus Addresses

By default, each frame ships with t he following CAN bus addresses : the first Fader Module on the left = Hex
Address 01; the next Fader Module = Hex Address 02; and so on; the Central Module = Hex Address 10.

Default CAN Bus Addresses (hexadecimal)

For a single-frame console no further configuration is required, as t he modules will map correctly to the s t andard
template.

ruby User M anual V ersion: 6.0.0/4 25/82

4. Installa tion

Multi-frame Configuatio n

For a multi-frame configuration y ou will need to adjust t he CAN bus addresses on the phys ical modules (using
the speci al functions mode).

By setting the CAN bus address to matc h t he Frame -> Surface c onfiguration, you can define which frames will
control the different sets of fader strips; which frame includes the Central Module (Address 10); and which
frames incl ude monitor mode Central Modules (if applicable).

Frame -> Surface menu: ruby 15 + 1 +6 Example

Control Surfac e Layers (Fader Mappin g s)

Each Fader Module supports two layers. This means that t he module set t o hex address 01 controls fader strips
1 to 4 (Layer 1) and 5 to 8 (Layer 2); the module set to hex address 02 controls fader strips 9-12 and 13-16; and
so on. The diagram below illust rates all t he fader s trip mappings. A single control s urface c an support up 60
physic al fader strips, each with t wo layers:

Fader Mapping s

ruby User M anualV ersion: 6.0.0/426/82

4. Installa tion

4.6 Powering the Device

A complete sys t em can have several components: t he control s urface, DSP Core, VisTool MK2 and Key Panels:

1. The system has no on/off switch but starts automatically when power is applied .

Please inst all a m as t er syst em power switch where applicable.
Components can be powered in any order. So, for example, y ou c an begin VisTool operations without power t o

the control surface. Remember though that without power to the Core, there is no DSP, no routing m atrix and no
control sy stem!

2. Let’s ass ume t hat y ou turn on the master power switch for all sy stem c omponents:

·

You will see an initial flicker of LEDs on the control surface modules.

·

If the Core is POWER CORE, then you will s ee t he boot-up progress on the front panel display and t he

STATUS LED lights in white (st eady s t at e).

·

As s oon as boot-up is c omplete, t he front panel display will s how the Welcome page and the STATUS

LED begins t o blink at regular intervals.
The console is now ready for operation - this tak es approximately 20 s ec onds from power on.
At t he end of boot-up process , the DSP Core loads its warm start data. This is the stat e of all set t ings at t he las t

shut down. It means that when you turn on, you will get back to wherever you were at t he last power off.

Plea se note: if you load a new configuration, or perform a firmware update, then the DSP Core will cold start.
A cold s tart ignores t he warm start data, and resets all i nternal logic states and audio DSP parameters to the
default values stored in the configuration.

If this i s t he first t im e y ou have powered the DSP Core "out of the box", t here will be no configuration and
therefore no sett ings .

·

Go to www.lawo.com and download the latest firmware release onto a service c omputer. Use t he
Firmware Update Tool (SoP E x plorer) to check and update the sys t em c omponents.

·

Then, open one of the standard configurations (incl uded in the ON-AIR Designer) or build y our own. Use
the "Transfer Config -> Unit" function to load the configuration onto the DSP Core.

These procedures are described in the manual for your DSP Core.

ruby User M anual V ersion: 6.0.0/4 27/82

4. Installa tion

4.7 Exchanging the MF Key Labels

The functions of all MF Keys are defined by the ON-AIR Designer. The large MF Keys are labeled by foil-printed
labels and, by default, the control surface ships with the labels for the s t andard template functions. If y ou c hange
the MF Key functi onality , then y ou will need to exchange the foil-printed labels. Printed sheets with the m ost
common labels are shipped with each frame.

To replace a label:

1. First remove t he button cap.

It helps to use a s mall s crewdriver to l ift up the butt on cap (as the c aps are recessed). However, y ou must t ake
care not to sc ratc h t he s urface.

2. Insert the foil plate between the button body and the transparent button cap.

3. Fasten the button cap back onto the button body by press ing it !

Remove Button Cap

Insert Printed Foil

Label Exchange Complete

ruby User M anualV ersion: 6.0.0/428/82

5. Opera t i on

5. Operation

This c hapter describes t he operation of the surface once a DSP Core has been connected and configured.
Topics inc lude:

·

The Fader Strip

·

The Central Module(s)

·

Assigning Fader Strips

·

DSP Parameter Control

·

Bus A ssign

·

Conference Bussing (Mix Minus/ N-1)

·

VCA Grouping

·

Pool & RAVE NNA Sources

·

Working with Layers

·

Fader Mappings

·

Confi gurable Surface Functions

·

Snapshots

·

The SYS Menu

ruby User M anual V ersion: 6.0.0/4 29/82

5. Opera t i on

5.1 The Fader Strip

Each Fader Module provides 4 identical fader strips.
Any fader strip can control any ty pe of source or summing bus and, depending on the configuration, s upport l ayer

switc hing and fader mapping. This enables lots of signals to be controlled from very few physical faders.
All MF Keys are programmed by the configuration and are defined per source. Note that MF Key 5 is only

available if Layer 2 is disabled.
All other controls provide the s ame " fixed" functionality regardless of the configuration.

1 Rota ry Control

Turn the rotary c ontrol t o adjust s ource-related parameters. The available
parameters depend on the type of source and its c onfiguration; tap down on
the control to step through all possible parameter options.

2 MF Keys 1, 1 b , 2, 2b & OLED

The 4 small MF key s are programmed by t he c onfiguration and are defined
per source. Funct ions are labeled on the OLED display and can include
PFL, bus as signment, AutoGain, Aut oMix, Conference enable/talback .

3 ACCESS / ACCESS 2 (MF Key 5)

The ACCESS key s are used for:

·

Laye r S wi tching* – select either ACCESS 1 or ACCESS 2 to s witch
the fader strip between layers; the active lay er is indicat ed by a fully lit
(green) key.

·

Central Module Assign – selec t an ACCESS key (white) to assign
the source to the Central Module (e.g. to adjust it s DSP parameters).

·

Strip Assign - double-press an ACCESS key (yellow) and turn the
Rotary Control (1) to selec t a new s ource. Then press the TAKE MF
Key (2) to confirm the fader strip assignment.

*If Layer 2 i s dis abled by t he c onfiguration, then ACCESS 2 operates as
MF Key 5. In this inst ance, t here is no lay er switc hing and the button c an
perform a different function s uc h as P FL or talk back .

4 Fader

The fader is a long life, 100mm motorised fader with a scale from - to
+9dB. It adjusts the level of the assigned source or summing bus. A
number of fader options, i ncluding a 0dB notch, can be s et from the SYS
menu.

5 Backligh t

The backlight indicat es eit her signal present or the type of s ource/summ ing
bus. The colors us ed and their meaning are defined by the c onfiguration.

6 Label Display

This display always shows the name of the source or s umming bus c ontrolled by the fader s trip. In addition, y ou
may see two lines of user labels (if us er labels are enabled); these can be edited during runtime using either

VisTool MK2 or the User La bels software.

7 MF Keys 3 & 4

The two large MF keys are programmed by the configuration and are defined per source. In our ex ample, they are
channel ON and PFL

ruby User M anualV ersion: 6.0.0/430/82

5. Opera t i on

5.1.1 Fader Strip Rotary Control

The rotary c ontrol st eps t hrough a number of functions including input gain, panning and input s ignal s elec t ion (for
pool sources). The exact sequence of parameters depends on the type of source and its c onfiguration. The
example below shows the parameters available for a mono microphone source on a console configured for 5.1:

Rotary Control Parameters for Mono Mic Source

1. Turn the rotary control to adjust the first parameter (e.g. Mic gain) - the display shows t he parameter and

its valu e (e.g. +42dB).

2. Press down on the rotary control to step to the next function – digital Gain – and turn to adjust.

3. Keep pressi ng down to step through the available parameters. When you reach the end of t he sequence,

the control returns to the first parameter.

4. When you are happy with all of the setti ngs, l et go of the rotary c ontrol - after a few sec onds, the displays

return to t heir default mode (of labeling the MF Keys).

Tap down on a rotary c ontrol to interrogate parameters without making a change - the displays s how each
para meter fu n ction and its value.

Input Gain

On fader strips controlling a microphone source, you can adjust two gain setti ngs:

·

Mic ga in – t his is t he analogue pre-amplifier gain before analogue-to-digital conversion; it may be set

from +0dB to +70dB. If you have a high level m ic s ignal, use t he 20dB P AD to lower the mic gain, s ee

INP parameters.

·

Gain – this is digital gain within the channel DSP path; it may be set from -30dB to + 18dB.
On fader strips controlling other sources, suc h as line level, AES or SDI, there is no mic gain, only digital gain.
On fader strips controlling a summing bus, t here is no input gain (mic or digital).

When adjusting input gain, use the s i gnal present indicator to help set a good input level - the indicator is
usually green or yellow for a good operating level; if the light turns red, then the source is overloading and
may c ause dis t ortion.

Pan or Balance

Pan parameters vary acc ording to whether the source is mono, s tereo or surround.
On a mono source y ou can adjust:

·

Left/Cen tre / Rig ht pan position

·

Front/Rear pa n position

·

Slope – from 0.0 to 1.0 (see below).

·

LFE – low frequency effect level, from -120 to +9 dB.

Front/rear pan, slope and LFE level are only available if a surround bus is c onfigured on your console and
surround parameters are enabled on the source.

ruby User M anual V ersion: 6.0.0/4 31/82

5. Opera t i on

The Slope adjust s s ignals feeding the disc rete centre channel within the surround field. It may be used to balance
between disc rete and phantom centre signals. To see t he effect, posit ion the source at front c entre, and adjust
the slope to a setting of 1.0; the signal feeds only the discrete centre output. Now s et the s lope t o a value of 0.0;
the signal feeds only l eft and right (phantom centre).

On a stereo source you can adjust the left/right balance, front/rear pan and LFE level. Centre slope is not
available.

On a surround (5.1) source you can adjust LFE level only; the surround source is assigned directly to the
surround bus (e.g. left to left, centre to c entre, etc.)

If a surround source is as signed to a stereo bus, then the source is m ixed onto the bus according to t he surround
downmix parameters set within the configuration. If a surround source is assigned to a mono bus, then t he s t ereo
downmix is converted to mono by s ubtract i ng 3dB from, and then summing, t he L and R channels.

Signal Select (Pool or RAV ENNA Sources)

If a pool or RAVENNA source is as signed to the fader strip, then the rotary control can be used to select the input
signal or stream. These operations appear at the end of the parameter sequence. See Pool & RAVENNA

Sources.

5.1.2 Fader Strip Backlight

The backlight indicates either signal present or the type of source (or summing bus).
For bus masters, the backlight always indicates the ty pe of bus. The c olours are defined by the

configuration.
For input sources, the backl ight can indicate the type of source or show when signal is present. For

each source there are three poss i bilit i es :

·

Signa l Present only – the backlight illuminates when signal is present. Up to 8 level
thresholds can be configured, each with its own colour code and st at e.

·

Source Colour onl y – the backlight indicat es the s ource ty pe. The source colour c an be
static, or individual colours can be driven by logical triggers - for example, to indicate a
change of status s uc h as as signed to PGM, off-air recording, incoming call, et c .

·

Mix Mode – combines both options, where signal present tak es priority.

In the configura tion, use the Source Color and Source Color Mode options (in the Source or Sum Bus
branch of the 'Tree Definition') to defi ne the colour coding and mode of operation.

The signal present thresholds are defined globally (in System -> Definition -> Parameter = S i gnal Present).

ruby User M anualV ersion: 6.0.0/432/82

5. Opera t i on

5.1.3 Fader Strip Label Displays

The display at t he bottom of the fader strip always shows the name of the ass igned source or summing bus. In
addition, it may show two lines of user labels (if user labels are enabled).

Display Names only

Displa y Names

The source and summing bus dis play names are defined by the c onfiguration. If a fader is controlling a s umming
bus, then the label is pre-fixed with a sign to help distinguish bus masters from input sources (e.g. PGM).

In the configura tion, use the Display name option (in the Source or Sum Bus branch of the 'Tree Definition')
to edit the display name.

User Labels

To see user labels on the console, they must be enabled in the configuration. There are three possibili t i es: user
labels on, off or toggle.

Once user labels are enabled, you will see three lines of text in each fader strip label display:

User Labels enabled

The two user label lines c an be edited during runtime using either VisTool MK2 or the User Labels software.

User labels are configure d globally from the S yst em -> Definition -> Param = Fader branch of the 'Tree
Definiton'. There are options to set the mode (on, off or toggle) and text s ize (small or large).

ruby User M anual V ersion: 6.0.0/4 33/82

5. Opera t i on

Editing Us er Labels from VisTool MK2

1. There are two ways t o open the 'Edit User Labels' window:

·

Press a USER LABEL MF Key (if one is configured). Y ou c an us e a Logic -> Vis pageSwitch element
within the 'Tree Definition' to configure this option.

·

Start the VisTool MK2 Editor software manually, and select Edit User Labe l s f rom the Util menu:

VisTool MK2 Editor (Util menu)

A pop-up window appears showing the Id, Name, Display name and user label lines (Line 1 & Line 2) for all
sources and busses defined in the configuration:

Edit User Labels Window

Note that you will see all s ources and busses even if they are not assigned to a fader st rip.

2. Click in the Li ne 1 or Line 2 fields to edit or add a name. You may enter up to 8 characters in each

line.

3. Select OK - the window closes , and the labels on the c onsole update accordingly.

Note that the Name and Display fields are defi ned by the configuration and cannot be edited during runtime.
(Use the Reference name and Display name in S ource -> Parm to c onfigure these options. )

You can use the Import and Export fields to load and save all labels to an .xml file.

Note that:

·

User labels for all source and busses in the configuration are s aved when y ou save a snapshot. This
means that you can save and recall labels for specific s hows along with other settings, see Snapshots.

·

The last User Labels are st ored in the console's warm start data. This means t hat when you power on
you will get back to wherever you were when the power was last t urned off!

ruby User M anualV ersion: 6.0.0/434/82

5. Opera t i on

Editing Us er Labels from the Dedicated Softw are

As an alternative to V i sTool MK2, you can use the dedicated Use r La be l s Softwa re . This m ust be inst alled on
an external computer connected to the system network. See the User Labels Software for details.

ruby User M anual V ersion: 6.0.0/4 35/82

5. Opera t i on

5.2 The Central Module(s)

Every control s urfac e incl udes one Central Module running in full mode. If your surfac e has additional Central
Modules, then these must run in monitor mode.

5.2.1 The Central M odule

Config uration Example

MF K ey Layou t

1 Rota ry Controls, Small MF Keys & OLEDs

The four sets of rotary controls, small MF K ey s and OLED displays i nteract with t he 12 Function Buttons (3).
When none of the Function Buttons (3) are active, the controls have a default functionality t hat is programmed by

the configuration.
If a Function Button (3) is pressed, then the controls can be used to adjust t he relevant parameters. For example,

to c ontrol EQ parameters on a MIC source, first press ACCESS on t he MIC fader st rip; t hen press t he EQ
Function Button on the Central Module - you can now use t he four sets of controls t o adjust the EQ parameters.
The parameter value and button functions are shown in the OLED.

2 MF Keys 45 & 4 6

These two MF K eys are programmed by the c onfiguration. On consoles with more than one lay er, they usually
provide global layer swit c hing.

ruby User M anualV ersion: 6.0.0/436/82

5. Opera t i on

3 Fu n ction Buttons

The dual engraved function buttons are used for:

·

Pa rame ter Control – pr ess INP, DYN, LIM, DEL, EQ or INS to map parameters for the s ource in
ACCESS onto the four sets of rotary c ontrols (1).

·

Bus Assign – press BUS and t hen selec t a page (1 to 5) to map bus ass ignments onto the Fader
Module's s m all M F K ey s.

·

VCA Assign (optional) – press BUS and then select VCA 1 or V CA 2 to map VCA ass ignments onto
the Fader Module's small MF Keys. Note that V CAs mus t be enabled in the configuration to support this
function.

·

Sna pshot Control – pre ss and hold S NAP LOAD and select a s napshot (1 to 5) to load. SNAP SAVE
works in a s im ilar manner. The configuration can define an UNLOCK MF Key t o protect the s napshot
save and load functi ons.

·

Press SYS to map the sy stem options onto the four sets of rotary controls (1).

4 Ambient Light Detectors

The two detectors automatically adjust the brightness of buttons and displays ac c ording to the ambient light l evel.
Two detectors are included so that if one is c overed by a sc ript, the surface does not dim! The c onfiguration can
disable the sensor or assign an on/off MF Key.

5 MF Keys (1 to 2 8) & Rotary Controls (VCA 1 & 2)

The 28 MF Keys and two rotary controls are programmed by the c onfiguration. In our example, t he MF K eys are
programmed for monitor source select ion and the rotary c ontrols for monitor level. The t wo dis plays always show
the name and parameter value related to the rotary control functions (e.g. SPK and DJ HP).

Depending on the configuration, each rotary control can adjust two parameters: turn to adjust the first (e.g.
monitor level); push down and turn to adjust the s ec ond (e.g. monitor balance).

In the configura tion, use the Surface -> Central Module branch of the 'Tree Defintion' to defi ne the
functionality.

5.2.2 Central Modules (monit or m ode)

On a Central Module running in monitor mode, all controls are defined by the configuration.
Each module provides 46 MF Keys and six rotary controls (VCA 1 to 6), following t he s ame MF Key /V CA layout

as on the m ain Central Module. The displays always s how the name and parameter values related to t he rotary
control funct ions.

Depending on the configuration, each rotary control can adjust two parameters: turn to adjust t he first; push down
and turn to adjust t he sec ond.

Note that the 12 "Function Buttons" are not supported and cannot be programmed. Therefore, they will remain
unused.

In the configura tion, use the Surface -> Central Module (monitor mode) branch of the 'Tree Defi ntion' to define
the funct ionality.

ruby User M anual V ersion: 6.0.0/4 37/82

5. Opera t i on

5.3 Assigning Fader Strips

Any s ource or summing bus defined in your configuration can be assigned to any fader strip. P lease note:

·

All sources assigned to fader st rips are acti ve in the m ix, inc luding sources as signed to Layers 1 and 2

and any invisible fader strips.

·

The maximum number of sources which can be summed simultaneously depends on the resources

provided by your DSP Core.

·

In t he configuration, if t he Only Default option is enabled for a fader strip, then its source cannot be

reassigned.

·

In the configuration, if the global S ave Value option i s disabled, then you cannot reassi gn a source if its

fader is open.

·

In the configuration, s ources are made available for as signment using the List E nable option (in the

Source -> Parm branch of the 'Tree Definition').

·

A s ource can be assigned only once; you c annot as sign a s ource to two different faders. However, you

can map a fader so that it can be controlled from two different locations, see Fader Mappings.

·

Your user rights may globally dis able the "s ource ass i gn" m ode.

5.3.1 Assigning a Source (or Bus) to a Fader Strip

1. Doub le-pr ess the ACCESS key on the fader strip layer you wish t o assi gn. You must press twic e in

quick succes sion - the ACCESS key t urns yellow to indicate that you are in “source assign” mode.

In the configur a tion, if the global S ave Value option is NOT selected, then you must close the fader before
you can enter "source ass ign" m ode.

Alternatively, press and hold the ACCESS key to enter “source ass ign”. Note that, if y ou use this met hod, you
will need to keep pressing the k ey throughout the rest of the operation.

2. Turn the rotary control to s c roll t hrough the available options - t he name of the select ed source is s hown

in the display, in our example SDI1.

Summing busses are prefixed with a to distinguish them from input sources.

3. Press the Take MF K ey to assign the selec t ed s ource or bus.

You will see the label at the bottom of the fader strip update, and the ACCESS key , MF Keys and rotary c ontrol
return to t heir default mode of operation.

If the assigned source was controlled from a different fader st rip, then the source is moved – in other words,
you will see a blank fader strip where the source used to be.

If the fader label does not update, then t he ass ignment has failed. This may oc cur i f you have reached the lim it
of source s ums s upported by the DSP resources.

ruby User M anualV ersion: 6.0.0/438/82

5. Opera t i on

5.3.2 Clearing a Fader Strip

You can use the same procedure to remove t he c urrent source, or bus, from a fader s trip leaving it blank. Note
that removing a source from the control surface will remove it from the mix.

1. Doub le-pr ess the ACCESS key on the fader strip you wish to remove. You must press twic e in quick

succession - the ACCESS key turns y ellow and the MF Keys update.

In the configur a tion, if the global S ave Value option is NOT selected, then you must close the fader before
you can enter "source ass ign" m ode.

2. Press the Remv MF Key - the c urrent source is removed leaving a blank fader st rip.

ruby User M anual V ersion: 6.0.0/4 39/82

5. Opera t i on

5.4 DSP Parameter Control

Parameters for the source, or summing bus, in ACCESS are controlled from the Central Module. This allows y ou
to adjust parameters for each source, or summing bus, one at a ti me.

Your user rights or the configuration (Source -> Parm and Sum Bus -> P arm) can disable acc es s t o c ertain
parameters.

5.4.1 Operati ng Principl es

1. Put a s ource, or summing bus, “into acc ess” by pressing i ts ACCESS k ey - the ACCESS key t urns

white, and the Central Module updates to s how parameters for your selection.

In our example, the input parameters for a mono mic s ource are in view:

2. Use the rotary controls to adjust the variable parameters - e.g. Mic, Gain or Pan.

3. Press t he small M F K eys t o change a switc hed parameter - e.g. 48V, PAD or 80Hz. The button c olours

indicate:

·

Red = enabled (on).

·

Yellow* = dis abled (off).
In our example, 48V and the 20dB PAD are both turned on; the 80Hz Rumble filter is off.
*The parameter sets are colour-coded and so the " off" st ate varies depending on the chosen function butt on - for

example, yellow is used for INP parameters; blue for EQ; etc .

4. To adjust a different source, press a different ACCESS key - t he Central Module updates accordingly:

Input Parameters (for a stereo line-level source)

Only one source, or summing bus, can be in access at a time.

If you have an extern al VisTool MK2 display, t hen you may be able to view the parameters graphically . See
the "VisTool MK2 User Guide".

ruby User M anualV ersion: 6.0.0/440/82

5. Opera t i on

5. To adjust a different set of parameters, select a different function button – e.g. press EQ:

EQ Parameters

The function buttons are half lit if a module is available. For our source, we can select any of the five DSP
modules: INP, DYN, LIM, DEL or EQ. If a function button is not l it , then the DSP module is not c onfigured.

In the configuration, DSP is enabled and disabled using the Source -> Parm and Sum Bus -> P arm branches
of the 'Tree Definition'.

On the left (master) display are two dots - these show that there are two pages of functions for the EQ s ection.

6. Press down on the left (mast er) rotary control to st ep to t he next page - the displays update accordingly:

If you s ee an arrow, then this s hows which parameter which will be adjusted when you turn the rotary c ontrol.

7. If there are two parameters, turn to adjust t he first (e.g. Gain), and press down and t urn t o adjust the

second (e.g. Frequency).

8. When you have finished adjusting all parameters, deselect the white ACCESS k ey on the fader strip - the

Central Module rotary controls and small MF keys return to their default mode of operation.

ruby User M anual V ersion: 6.0.0/4 41/82

5. Opera t i on

5.5 Bus Assign

Bus as signments are made using the 4 small M F Key s and rotary control on each fader strip. The controls are
switched into “bus assign” mode using the BUS function button on the Central Module.

Up to 5 pages of assignments can be configured; the pages are selected using the dual engraved function
buttons: e.g. press INP 1 for page 1; DY N 2 for page 2; and so on. If all 5 pages are c onfigured, then you can
acces s up to 20 busses (4 per page), each of which may be mono, stereo or 5.1.

The name, format and signal flow of eac h summing bus is defined by the configuration. The configuration als o
determines whether each bus c an be assigned from t he control surface. For example, you c ould exclude a bus
(e.g. PGM) from the "bus assi gn" pages, s o that sources are always assigned to it, in order to s implify the
operation.

In the configura tion, use the Sum B us -> P arm branch of the 'Tree Definition' to define the summing busses in
the sy stem. Then use Syst em -> Definition -> Parameter = Aux to define how bus assignments are
presented on the control surface.

Ø

To view or change the bus assignments:

1. On the Central Module, select BUS and INP 1 - the fader s trip MF Key s and rotary control are s witched

into 'bus assign' mode globally across the console:

Bus Assign Mode - Pa ge 1

Each MF K ey i s labeled and colour-coded to show:

·

Red = source is ass igned to the bus pre-fader.

·

Yellow = source is ass i gned to the bus post-fader.

·

Green = source is not ass i gned to the bus.
Note that the available busses, assignment options (pre/post/off) and MF Key colors are all defined by the

configuration.
The display also shows the send level from the source to last adjust ed bus.

2. Use the MF Keys to change the bus ass ignments. Eac h press c y cl es through the available options - for

example, pre-fader, post-fader and off.

3. Press down on the rotary control to cycle through the available send levels, and t urn to adjust. The send

level may be adjusted from -120dB to +9dB.

WARNING: take c are when adjusting send levels to main output busses such as programme. These levels
should be set to 0dB unless operating in special c irc ums t anc es . Ot herwise you will not achieve unity gain
through the console.

You may be able to adjust send levels from the faders if an MF Key or other control trigger has been
programmed to access this function.

ruby User M anualV ersion: 6.0.0/442/82

5. Opera t i on

4. To access more busses, select a different page – for example, press DYN 2 for page 2:

Bus Assign Mode - Pa ge 2

Up to 5 pages c an be configured if required. If a page is available then its function button is half lit. In our example,
we can choose page 1 or 2; page s 3 to 5 are not c onfigured.

5. When you have completed all y our as signments, deselect the BUS function button to return t he fader

strip MF K ey s and rotary c ontrols t o t heir default functions - the BUS button remains half lit when deselected:

Default Functiona lity

ruby User M anual V ersion: 6.0.0/4 43/82

5. Opera t i on

5.6 Conference Bussing (Mix Minus/N-1)

The conference system is us ed to generate mix minus/N-1 feeds for particular sources within your configuration.
Each s ource within the s yst em receives an automatically switc hed mix minus feed. When their s ource fader is

open (on-air), they will hear programme minus t hemselves, and when their source fader is closed (off-air), t hey will
hear the conference bus minus t hemselves – t his allows members of the conference to hear each other while t hey
are off-air.

Let’s take an example where the configuration has defined conference feeds for 3 sources: DJ, GST 1 and TEL 1.

Ø

Se tting Up the M onitoring

In order for our sys tem t o operate c orrect ly the mix minus feed for each s ource must be returned to t he correct
destination. In our example, we are assuming:

1. The DJ is listening to their mix minus feed on his/her headphones.

2. The studio gue st is also listening on his/her headphones.

3. The telephone guest (TEL 1) is receiving the correct mix m inus feed.

Depending on the configuration, the conference bus may be switched automatically t o t he monitoring when ac t ive.
Alternatively, y ou may need to switch t he monitoring manually – if this is the c as e, there will need t o be a CONF
button on the monitor source selector.

Ø

Worki ng with the Confere nce System

Once you have c onfigured the correct monitoring, then the conference sys tem operates as follows:

1. Tu rn on the CONF bus assi gn buttons for all sources within t he c onference – i n our ex ample, on t he DJ,

GST 1 and TEL 1 fader strips.

This routes each source onto the conference bus; t he CONF buttons will turn red, yellow (flashing) or white
depending on the status of the faders:

For the conference system to work you mus t have at least two sources with CONF enabled. Also note that
the lamp colours may be configured differently in y our sy stem.

Each source within the conference sys tem now receives an automatically swit ched mix mi nus feed; what they
hear will depend on the status of the three source faders.

2. Close all three source faders.

The CONF buttons become red and all s ources will hear the conference bus mi nus themselves. In other words,
they c an hear each other, but not thems elves, and chat off-air.

ruby User M anualV ersion: 6.0.0/444/82

5. Opera t i on

3. Open one of the faders – e.g. t he DJ fader.

The DJ source is now assumed to be on-air, and the DJ’s monit or feed is automatically s witched to programme
minus themselves. This is reflected by the flashing (yellow) CONF button:

The CONF buttons on the studio and telephone guest fader strips remain red. This is because t heir faders remain
closed, and so t he two guests are st ill hearing the conference bus minus t hemselves and can continue their off-air
conversat ion. Also, i f you clos e the DJ fader, the DJ’s monit or feed reverts to a c onference bus mix minus, s o
they c an rejoin the off-air conversati on if required.

4. Finally, open both the DJ and studio Guest faders.

Both the DJ and studio Guest are now on-air, and so they will hear programme minus themselves (yellow flashing
CONF buttons):

In this mode, there are less than two active conference sources and s o the conference s y s tem is canc elled. The
Telephone Guest’ s monitor feed is automatically switc hed to a Programme mix minus . This s tate is reflected by
the white CONF button.

5. To cancel the conference for any of the sources, deselect the CONF button.

The CONF buttons turn green (off) and the source’s m onitor feed receives programme minus themselves at all
times.

ruby User M anual V ersion: 6.0.0/4 45/82

5. Opera t i on

5.7 VCA Grouping

VCA grouping can be used to control several sources or summing busses from a single master fader.
Up to 8 VCA masters can be defi ned in the configuration, and you can ass ign any number of fader s t rips t o eac h

VCA mast er.
Please note:

·

A fader strip can only ever be assi gned to a single VCA.

·

A VCA m as t er cannot be slaved to another VCA.

·

For your console to support VCA grouping, at least one VCA mas t er must be defined in the configuration.

In the configuration, us e the "Source VCA Group" type (in the 'Tree Defi niti on') to define the VCA masters.

5.7.1 Assigning Faders Strips to a VCA

1. On the Central Module , select BUS and VCA 1 - the fader strip MF Keys are switc hed int o “VCA ass ign”

mode globally ac ross t he c onsole.

VCA Assign Mode - VCAs 1 to 4

Each MF K ey i s labeled and colour-coded to show:

·

Red = V CA as sign on.

·

Green = V CA as sign off.
Note that the fader strip rotary controls have no function.

2. Use the MF Keys to c hange the assignments.

3. To ac ces s t he s econd page of V CA mast ers, press VCA 2 – you can now change the assi gnments t o

VCAs 5 t o 8.

4. When you have completed all y our ass ignments, deselect t he BUS function button t o return t he fader

strip MF K ey s and rotary c ontrols t o t heir default functions.

VCA assignments are shown in the metering pages of Vis Tool M K2. Or, you can i nterrogate as signments by re­entering the “VCA ass i gn” mode.

5.7.2 Assigning the VCA Master t o a Fader Stri p

VCA mast ers are available as sources when you activate source select i on from a fader strip. This means t hat you
can assign a VCA mas ter to any fader s trip in the usual manner, see Assigning a Fader St rip.

Once ass igned, t he fader s trip label display and backlight update according to the display name and colour
coding defined in the configuration.

In the configura tion, use the Display name and Source Color options (in the S ource -> Parm branch of the
'Tree Definition') to edit these options.

ruby User M anualV ersion: 6.0.0/446/82

5. Opera t i on

5.7.3 Working with VCAs

VCA groups use non-moving slave faders. This means t hat when you move t he master fader, the sl ave faders
remain stationary even though their level is c hanging. This allows you to see and update s lave fader positions
even if the VCA mast er is closed (like an analogue VCA).

As y ou move the VCA master, you will see the level adjust ment applied to the slaves in the upper display s (if this
option is enabled in the configuration). In our example, both s lave faders are at 0dB, but the m aster VCA has
been moved to +5 and therefore the combined level is +5dB:

Combined level shown in slave fader displays

If you do not see the combined level in the s lave fader displays, t hen this option is not c onfigured.

In the configura tion, use the Show Group Fader Values option (in the S ystem -> De fini ti on -> P ara m =
Fader branch of the 'Tree Definition') to enable this feature.

ruby User M anual V ersion: 6.0.0/4 47/82

5. Opera t i on

5.8 Pool & R AVENN A Sources

On specially-conf igu red matrix s ources, known as Pool or RAVE NNA Sources, operators c an change the audio
input or connect ed s t ream directly from the fader strip.

For example, if t he DSP Core is c onnected t o a l arger matrix , such as a Nova73, vi a 16 MA DI t ie lines . B y
configuring 16 pool sources, one for each MADI tie line, and a matrix source pool within the Nova73, you can
access Nova73 signals via any of the 16 pool sources. Similarly, if your system is connected to an
AES 67/RAVENNA streaming network, then by c onfiguring RAVE NNA Sources and a RAVE NNA s ource pool,
you can acc es s available AES67/RAVENNA st reams on the network.

Signal Naming & Organizatio n

For all matrix s ources, including RAVENNA s ources, signals within a pool are organized by name, following the
conventi on Group:Si gnal. When usi ng dynamic input switc hing, t his provi des a t wo-step navigation process : first
select the Group, and then browse t hrough all available Signals within that Group. Note that both the Group and
Signal labels can be up to 8 characters.

By default, displayed labels are retrieved automatically from either the AES 67/RAVENNA streaming network or
networked router (if using NetCom or Remote MNOPL protocols).

In the case of AES 67/RAVE NNA s t reams, t he names c an be obtained automati c ally IF the st ream names follow
the Group:Signal convention. Streams with the s ame Group name are combined into a s ingle Group even if t hey
are provided by different devices . The presented lis t will then be updated automatic ally so that newly disc overed
streams are added, and streams which c an no longer be detected are erased. To prevent access to certain
signals, signal name filters can be applied to limit access. In cases where the AES67/RAVENNA st reams c annot
be named using the above c onvention, it is poss ible t o map s treams to signal labels, and present t he configured
list to the operator. In this inst ance, t he list is permanent and is independent of st ream availabilit y.

In the case of a networked router, the matrix source pool Group and Signal names come from the input names
defined in the configuration of the connected router.

Assignin g a Pool (or RAV ENNA) Source to a Fa d er Strip

If Pool or RAVENNA Sources are configured in your system, then y ou will find them when y ou
perform a fader st rip ass i gnment:

1. Doub le-pre ss an ACCESS key to enter the fader strip assign mode in the usual manner.

2. Turn the fader strip's rotary c ontrol to scroll through the available options until you reach t he

required source – in our example, the pool source labeled Pool 1.

3. Select the source and press Take to assign it to t he fader st rip.

In our example, this has assigned Pool Source 1 which is the first stereo MADI t ie line from our
Nova73.

ruby User M anualV ersion: 6.0.0/448/82

5. Opera t i on

Selecting an Input Signal

1. Press down on the rotary c ontrol to s tep through the input parameters until y ou reach the Group select .

2. Wit h t he arrow pointing at the pool Group (MADI), turn the control to browse through the available Groups

and press down to make a selec t ion.

3. Then turn to browse through the available Signals.

4. Press the Take button to assign the signal (e.g. In 3).

Group & Sign al Select

Fader Label Display

The label display at the bottom of the fader strip updates to show:

·

MADI = the matrix source pool Group name.

·

In 3 = the matrix source pool Signal name.

·

POOL 1 = t he source Display name.

Selecting an AES67/RAVENNA Stream

On a RAVENNA Source with source pool functionality, an AES67/RAVE NNA stream can be select ed i n a very
simil ar manner:

1. Tap down on the rotary control until you reach the RAVENNA Group select.

2. Wit h t he arrow pointing at the st reaming Group, turn the control to browse through the available st reaming

Groups and press down to make a selecti on.

3. Th en turn to sc roll t hrough the available streams (detected on the network).

4. Press the Take button to assign the stream.

There will be a brief pause in t he audio while the s treaming connection is c onfigured; during this time, t he label
display at the bottom of the fader strip s hows t he st atus of the connection process (described below). If t he
subsc ription is succes sful, then the name of the connected stream is displayed.

Subsc rib ing to a Stream: Status Messages

Whenever you subscribe to an AES67/RAVENNA stream, the label display at the bottom of the fader strip reports
back on the st at us of the connection.

Note that this is true for RAVENNA Sources which have source pool functionality (as described above), or are
permanently li nk ed to a stream by the configuration or logical condition.

Under normal ci rcumstances, t he expect ed s equence of messages is as follows:

"Mute" -> select a stream and pre ss Take -> ("Pending") -> "Tuning" -> ("Unstable") -> "<Stream-Name>"

Note that messages shown in () may or may not appear. The table on the next page ex plains the meaning of
each message in more detail.

ruby User M anual V ersion: 6.0.0/4 49/82

5. Opera t i on

Status Message

Meaning

"Mute"

No stream is connected to the source's AES67/RAVENNA input..
ACTION: select a stream via the rotary control and press TAKE.

("Pending")

A ppears IF the connected stream is not y et available. In this instance, the console will wait f or
the stream announcement to appear on the network, and then automatically initiate the
subscription process.

Typically, this message does not appear when selecting a stream from a RA VENNA source
pool, as the list presented to the operator is constantly updated (in the background).

The message can appear if the source has been configured using a default subscription, if a
stream is connected via VSM , or following a warmstart while restoring the last known
connection.

"Tuning"

A ppears while the console measures the streaming quality , and sets its stream receiv ing
parameters to ensure correct audio playback.

During the tuning cycle the audio input is muted, and then unmuted once the task is complete.
If a stream is being received for the first time, t hen the tuning process can take a couple of

seconds. This initial tuning information is stored in a permanent memory. It is then used
whenever you select the same stream, thereby speeding up all subsequent connections.

("Unstable")

A ppears IF the stream jitter is extremely high and cannot be dealt with; I F the stream stops for
some reason; or IF t he PTP clock information is missing. You can open the RAV ENNA pages
(in the Web UI) to view additional information on specifics.

In this instance, t he console will attempt to heal itself, and mute the audio input until the stream
reaches stable conditions.

Typically, it is very rare to see this message during the subscription phase.
If an unstable stream is due to a PTP problem, then console will start a new “Tuning” cy cle

before the audio input is unmuted.

"<Stream-Name>"

Once the subscription is successful, the name of the connected stream is displayed.

On rare occas ions, t he following error messages m ay als o appear:

Status Message

Meaning

"PoolErr"

A ppears IF there is a problem connecting to the stream.
This can occur if the selected stream is not available on the network any longer, but is still

presented in the console's list of streams. Since this list is updated cyclically, t he problem
should not persist.

If you see this error, please repeat the subscription process. If t he issue persists, check your
network settings.

The audio input will be muted while the error message is displayed.

"RavErr"

A ppears IF there is an invalid combination of status flags for the RA VENNA stream.
Since the flags are updated cy clically, t he error should heal itself. If the issue persists, then

check the RA VENNA pages (in the Web UI).
The audio input will be muted while the error message is displayed.

ruby User M anualV ersion: 6.0.0/450/82

5. Opera t i on

5.9 Working with Layers

Each Fader Module supports two layers of s ource assignments: Layer 1 and Layer 2 (if Layer 2 i s not dis abled).
This means that your console can have:

·

Two Layers across all Fader Modules.

·

No Layers at all.

·

Two Layers on some Fader Modules but not on others.
The last option is particularly useful in a split-frame configuration - for ex ample, t o provide t he main operator with

two layers and a presenter with Layer 1 only (to s i mplify the operation).
If Layer 2 is disabled, then the AC CESS 2 operates as MF Key 5 allowing to be programmed for a different

function.
If Layer 2 is enabled on a Fader Module, then different sources, or summing bus masters, c an be assigned t o

each layer. Note that both layers will be contributing to the mix even if t he fader s t rip is s witc hed to the alternate
layer. This enables a c onsole of only 4 physic al fader strips to mix 8 sources s im ult aneously.

In the configura tion, use the Disable Layer 2 option (in the S urface -> Fader Module branch of the 'Tree
Definition') to disable the second layer.

Additional layers can be created by using fader mappings. See Invisible Fader Strips .

5.9.1 Interrogati ng the Layers

You can interrogate the layers by looking at the ACCESS 1 and ACCESS 2 keys on each fader strip:

·

Fully l it (gree n) = a s ource (or bus) is assi gned and the layer is active.

·

Half lit (gree n) = a s ource (or bus) is ass igned but the layer is hidden.

·

Not lit = there is no source (or bus) assigned to the layer.

5.9.2 Individual Layer Switching

1. Press ACCESS 2 to switc h a fader st rip to Layer 2 - the k ey lights fully green, and the fader label and

control positions update to reflect the settings for the Layer 2 source.

If there is nothing assigned to the second layer, then you will s witch to a blank fader strip.

2. Press ACCESS 1 to switch the fader st rip back t o Layer 1.

You can select any combination of ACCESS keys to swit c h individual fader strips between layers.

All open sources are active in the mix. This means that if you s witch to Layer 2, open a fader and then switch
back t o Layer 1, audio may st i ll be passi ng even though all visible faders are closed!

ruby User M anual V ersion: 6.0.0/4 51/82

5. Opera t i on

5.9.3 Global Layer Switching

Layers can also be switched across all fader strips using the global LAYER 1 and LAYER 2 buttons (if they are
configured).

Usually MF K eys 45 and 46 on the Central Module are defined for this purpose, but any control t riggers can be
used.

Central Module

1. Press LAYER 2 to switch all fader strips to Layer 2 - t he fader strip labels and control posit ions update

to reflect t he s ettings for all Layer 2 sources.

Note that if Layer 2 is dis abled on a Fader Module, then its fader st rips are unaffected and remain on Layer 1.

2. Press LAYER 1 to switch all fader strips back to Layer 1.

Note that the global LAYER functions override any individual ACCESS k ey s elect ions, and so will be reset all
fader strips back t o t he selec t ed layer.

In the configura tion, use the Global Switc h to Layer 1/Layer 2 options (in the System -> Defini ti on ->
Pa rameter = Fade r branch of the 'Tree Definition') to programme the LAYER 1 and LAYER 2 MF Keys.

ruby User M anualV ersion: 6.0.0/452/82

5. Opera t i on

5.10 Fader Mappings

Any fader strip can be mapped to a different control surface position usi ng fader mappings. The sy s t em works by
giving every fader strip a unique mapping ID. This i nc ludes faders on Layer 1 and Layer 2 for all Fader Modules.

MF Keys, defined by the configuration, can then reassign any fader ID to any control surface position. For
example, a fader can be cloned by ass igning the same ID to two posit ions. Move one of the cloned faders, and
the other follows; selec t a new source for the fader, and the other follows.

Fader Mapping IDs

Fader Clone Example

The mapping numbers identify both layers. Therefore Module 1 contains Faders 1 to 4 and 5 to 8; Module 2 starts
at Fader 9 and so on.

Applications

There are three main applications for fader mappings:

·

To clone a fader - as shown above.

·

To move fader strips – for example, t o rearrange the layout for different types of production.

·

To map invisible fader strips onto physi cal faders – to create additional "layers".
The first two applications are particularly useful for multi-operator l ayouts, as faders can be c loned at different

operator stati ons, or the control surface can be re-configured from single to multi-user.

In the configura tion, use the Channel Mappings tab (in the Surfa ce -> Fa d er Modul e branch of the 'Tree
Definition') to configure fader mappings.

ruby User M anual V ersion: 6.0.0/4 53/82

5. Opera t i on

5.11 Configurable Surface Functions

5.11.1 PFL & AFL

Up to 5 independent lis ten busses (PFL or AFL) can be defined by the c onfiguration. This is particularly useful
when working with multiple operating stat ions, as each s tation c an feed a different output. Eac h bus c an feed a
dedicated output, or be s witched automatic ally to y our speakers or headphones whenever a PFL (or AFL) is
active. These options are defined by the configuration.

PFL (or AFL) is usually available on one of the fader strip MF K eys - in our example, MF Key 4 has
been confi gured for PFL. The operation will vary depending on t he m ode selected i n the SYS options.
Below is a description of the default mode, PFL SUM.

Ø

PFL S UM Operation

1. On a closed fader select PFL - t he source is routed onto the stereo PFL bus.

Multiple PFLs may be s elec t ed to listen to a number of sources.

2. Now open the fade r - the PFL is automatically cancelled.

3. Th en select PFL on an open fader - the source is put into a s t at e c alled 'PFL prepare'.

4. If you now close the fader , PFL is enabled.

Ø

PFL Re set

One of the Central Module MF K eys is usually programmed for PFL Reset. This provides a handy way of
cancelling all act ive PFLs across t he c onsole.

5.11.2 Monitoring & Meteri ng

Monitoring fu nctions are usually controlled fro m the Central Module.
If you require additional metering, then VisTool MK2 can provide configurable metering pages on an external

monitor connect to the VisTool runtime PC. Please see the "V isTool MK2 User Guide" for details.

VisTool MK2 Example

ruby User M anualV ersion: 6.0.0/454/82

5. Opera t i on

5.11.3 MF Key Functions

MF Keys appear on the Fader Module and Central Module. They c an be used for a variety of applications:

·

Source-related functions – suc h as PFL, bus assign, AutoGain, Conference enable/talback and
signaling.

·

Fader Mapping

·

On-Air si g nali ng

·

Talkback – to a variety of destinations.

·

Return Ta l kback – allowing others to talk t o you!

·

Tone – send tone to programme or other destinations.

·

Clipboard Operations – to copy/ past e DSP (EQ, DYN, LIM) sett ings from/to the source in acc es s.

·

REC Mode – to switch s ources t o a record bus.

·

Ambient Sens or – to enable or disable the sensors.

·

Unlock – can protect functions such as s napshot or clipboard operations.

·

Plus m any ot her funct ions.

The functi onality and colour coding of each MF Key i s defined by t he c onfiguration.

In the configura tion, use the MF K ey and S ource-> Key s branches in the 'Tree Definition' to program MF
Key parameters.

5.11.4 GPIO Functions

The system s upports a variety of GPIO functions which allow the c onsole to respond to or action external
switching:

·

Fader Sta rts – open the fader to activate a GPI; the GPI will then action the playback device.

·

CALL Signa ling - an MF K ey (e.g. RING) lights to signal an incoming call; press the MF Key to
answer the call.

·

Emergency Mute – an external trigger mutes the programme output.

·

DSP Disable - an ex ternal trigger disables t he ACCESS butt ons across t he c onsole. This locks the
console’s DSP parameters so that t he operator cannot adjust Input, Dynamics, Limit i ng, Delay or EQ.

·

Red Light – mutes the speaker output when the red light st atus is ac tive. This could be c onfigured to
respond to c ertain sources being on-air, or be activated manually from an MF Key .

·

Plus m any ot her funct ions.

GPIO fun ctionality is defined by the configuration.

In the configura tion, use the GPI/O branch in the 'Tree Definition' to program GPIO parameters.

ruby User M anual V ersion: 6.0.0/4 55/82

5. Opera t i on

5.12 Snapshots

The system incl udes 5 internal memories which are saved, loaded and erased using t he SNAP SAVE and SNAP
LOAD buttons on the Central Module.

Unlimited snapshots may also be saved and loaded onto a PC using the optional Vis Tool MK2 s oftware. See
the "VisTool MK2 User Guide".

WARNING: It is not recommended that snapshots are loaded during a live broadcast, as to do so may result
in sources being taken off air!

5.12.1 What’s Stored in a Snapshot?

The following settings are st ored in snapshots:

·

Fader Strip Assign m ent – the assi gnment of sources and busses t o fader st rips.

·

User La bels – the two User Label text li nes for all sources and busses within t he configuration.

·

DSP settings – Input Parameters, EQ, Dynamics, Limiter, Delay and De-Esser for all sources and

busses.

·

Fade r Le vels (optional) – the configuration determines whether fader levels are stored. Saving (and

recalling) fader levels is recommended for production systems, but not for on-air to avoid accidental

recalls during a live transmis sion.

·

Bus Assignmen t – the ass ignment of sources onto the console’s s umm ing buss es and their send levels .

·

Logica l S ta tes – up to 32 logical states defined by the configuration.

·

Matrix Conne cts – up to 128 matrix connections defined by the configuration.

·

AES67/RAVENNA Stream subscriptions handled via a RAVENNA pool.

In the configuration, t he following options affect t he behaviour of snapshots :

·

Save Value (in System -> De finition -> Para m eter = Fa der) - defines whether fader levels are stored.

·

Snap Load Fader Max (in System -> Definition -> P a ra m e te r = Fa d e r) - specifies whether s napshots
load parameters for all faders of the console, or only up to a certain fader number. You c an use this
option to excl ude fader st rips from s napshot recall. Note that parameters are always reset for sources
and summing busses not as s i gned to the surface.

·

System -> Definition -> Parameter = Logic S napshot - defines which logical states are stored.

·

System -> Definition -> Parameter = Matrix Snapshot - defines which matrix c onnecti ons are st ored.

ruby User M anualV ersion: 6.0.0/456/82

5. Opera t i on

5.12.2 Saving an Internal Snapshot

1. On the Central Module, press and hold the SNAP SAVE button:

If a memory has already been used, then the numbered butt ons, 1 to 5, illuminate in red. A green button
indicates a free memory.

Note that the configuration can define an UNLOCK funct ion t o protect snapshots from being saved or erased by
accident. If this is the cas e, then you will need to activate UNLOCK (usually an MF Key) before you c an ac c ess
SNAP SAVE.

In the conf igur a tion, use Snap Unlock (in the S ystem -> Definition -> Para m eter = Snapshot branch of
the 'Tree Definition') to activate this option.

In addition, your us er rights may prevent you from saving or erasing the 5 local snapshot memories.

2. Keep holding the S NAP SAVE button and select a memory number – e.g. press 4 t o save the console’s

sett ings int o memory 4.

The SNAP SAVE button flashes magenta to indicat e a s uc c es sful operation.

WARNING: If you selec t a used memory, t hen its contents are overwritten.

5.12.3 Loading an Internal Snapshot

1. On the Central Module, press and hold the SNAP LOAD button:

You can see which snapshots contain data from the lit buttons – in our example, we can choose from
snapshots 1, 2, 4 or 5.

2. Keep pressing and holding the SNAP LOAD button while you select a m emory number – e.g. press 4 to

recall snapshot 4.

The SNAP LOAD button flashes magenta to indicat e a succ ess ful operation, and the console’s set tings update
accordingly.

WARNING: It is not recommended that snapshots are loaded during a live broadcast, as to do so may
result in sources being taken off air!

ruby User M anual V ersion: 6.0.0/4 57/82

5. Opera t i on

5.12.4 Erasing an Internal Snapshot

1. On the Central Module, press and hold both the SNAP LOAD and SNAP SAVE buttons:

You can see which memories are used from the red buttons – in our example, snapshot memories 1, 2, 4 and 5.
Note that the configuration can define an UNLOCK funct ion t o protect snapshots from being saved or erased by

accident. If this is the cas e, then you will need to activate UNLOCK (usually an MF Key) before you c an ac c ess
SNAP SAVE.

In the conf igur a tion, use Snap Unlock (in the S ystem -> Definition -> Para m eter = Snapshot branch of
the 'Tree Definition') to activate this option.

In addition, your us er rights may prevent you from saving or erasing the 5 local snapshot memories.

2. Keep pressing and holding while you s elect a memory number – e.g. press 4.

The snapshot memory is erased.

3. To check the erase has worked, press and hold SNAP LOAD.

The memory should now be clear (unlit):

ruby User M anualV ersion: 6.0.0/458/82

5. Opera t i on

5.13 The SYS Menu

The SYS button on t he Central Module provides ac cess t o a number of sy st em-wide options. These options are
stored in the warm start data, and therefore if you make c hanges they will affect all users.

Note that the SYS butt on can be disabled by the configuration. If this is the case, t hen the button has no funct ion.

In the configura tion, use the Disable Sy s Menu option (in the S ystem -> De fini ti on -> P ara m eter =

Settings branch of the 'Tree Definition') to disable the SYS menu.

1. On the Central Module, press t he SYS function butt on t o access the menus - the displays update to

show the menu options:

5.13.1 Fader O pti ons

Fader Speed

Tu rn the Fader rotary control to c hange the fader s peed. You c an s elect Slow, Medium or Fast to change the
speed at which faders will open or clos e in response to ex ternal control signals such as a fader st art, or when
loading snapshots. Only the physic al fader speed is affected, not the response time of any changes to audio
level.

Fader Notch

Enables or disables the fader notch. Wit h t he notch enabled, you will feel a notch at 0dB when you move a fader.

Fader Hot mode

Turn this option on to disable the fader motors across t he console. With t he fader motors disabled, you m ay open
a fader without automatically putting it on air. Use t his option if y ou wish to posit ion the fader (e.g. at 0dB) and
then turn on the channel instantly (by pressing channel ON or deselecting the MUTE button).

ruby User M anual V ersion: 6.0.0/4 59/82

5. Opera t i on

5.13.2 PFL Mode

Tu rn the P FL Mode rotary control to c hange the PFL mode for the main PFL bus (PF L 1). The mode affects
whether you can select multiple PFL buttons, and what happens when you open or close faders with PFL
enabled.

The available options are:

·

SUM (default m ode) – multiple PFL butt ons may be selected. W here faders are c losed, sources are

summed onto the PFL Bus; when a fader is opened, PFL is c ancelled. W here faders are open, sources

are put i nt o ‘ PFL Prepare’ and will be summed onto the PF L Bus once t he fader is closed.

·

SUM R – identical to PFL Mode SUM but PFL recurs if you open the fader (cancel t he P FL) and t hen

close t he fader. In this mode, PF L is only c ancelled by des elect i ng the PFL butt on.

·

PFL – identical to PFL SUM, but PFL buttons intercancel suc h that only one s ource m ay ever be in PFL

or PFL prepare.

·

PFL R - identic al to P FL Mode PFL but PFL recurs if y ou open the fader (canc el the PFL) and then

close t he fader. In this mode, PF L is only c ancelled by des elect i ng the PFL butt on.

·

PFL A - this mode is c alled PF L A lways and i s identic al to PFL Mode S UM with the exception that it

allows open faders to be put into PF L rather than PFL Prepare.

·

PFL AR - this mode is a combination of PF L Always and PFL Recurring which means that PFL i s never

cancelled by opening a fader .

·

PFL PUSH – PFL is momentary. This means PFL is active when you press the P FL butt on, and c ancels

on release.

·

PFL DJ - allows y ou to prepare a fader level which is applied when you put t he fader on-air. Press PF L

and adjust t he fader level. Then deselect P FL and press START to put the fader on-air - the fader jumps to

the prepared level. (Note that the prepared level is applied only once. So, if y ou t ake t he fader off-air, and

then press S TART again - the fader jumps to 0dB as normal.)

·

AFL - the channel's PFL buttons operate as A FL (After Fade Listen). The channel's after-fader signal i s

routed to the PFL bus. Multiple AFLs may be summed. A FL is only cancelled by deselecting the AFL

button.

·

AFL/PFL - as for AFL, but the channel's PFL signal is heard when the fader is clos ed; when t he fader

opens, the list en bus receives AF L.

ruby User M anualV ersion: 6.0.0/460/82

6. Maintenance

6. Maintenance

This c hapter describes t he maintenance procedures for the control surface frames and components.
Topics inc lude:

·

Checking the Hardware Status

·

Updating Firmware

·

The Special Functions M ode

·

Replacing Defect ive Parts

·

Locating the Control Surface Serial Number

·

Cleaning the Control Surface

ruby User M anual V ersion: 6.0.0/4 61/82

6. Maintenance

6.1 Checking the Hardware Status

The Web UI can be used to c heck t he hardware status of each control surface module.
To open the Web UI, connect a computer to the DSP Core control s ystem network, open a s uitable browser

application and enter the IP address of the DSP Core into the URL field - for example, type http://192.168.101.240
and press E nt er.

The Peripherals -> Surface page shows the stat us of the control surface components :

Peripherals -> Surface

·

If a component is shown in green, then it is configured and operational.

·

If a component is shown in red, then it is configured but t here is a problem - it is not fitted or connected,

or it may be faulty.

·

If a component is not lis ted, then it is not configured.
In the example above, the sys tem has detec ted four Fader Modules and one Central M odule. A further three

Fader Modules are configured, but either they are not fitted or their frame is not connected.
For more details about the W eb UI, please refer to y our DSP Core manual.

ruby User M anualV ersion: 6.0.0/462/82

6. Maintenance

6.2 Updating Firmware

It is important that all sys tem c omponents are running the correct firmware including all of the c ontrol surface
modules. This is handled by a firmware update tool, called SoP E xplorer, which is included with the ON-AIR
Designer inst aller.

The current revi sion of each sy stem c omponent (Surface, S yst em and IOs) can be check ed and, if necess ary,
updated by transferring files from a networked computer. Full details on how t o us e t he tool c an be found in your
DSP Core manual.

ruby User M anual V ersion: 6.0.0/4 63/82

6. Maintenance

6.3 The Special Functions Mode

Each of the control surface modules offers a “special functions” mode. This can be used to adjust system
sett ings and test t he module's components (lamps, butt ons, etc.)

6.3.1 Fader Module Special Functions Mode

To enter the “special funct ions” mode on a standard Fader Module:

1. Press and hold both the keys T9 and T18 during power on of the frame.

The keys on t he module can now be used t o adjust s ys tem s etti ngs (CAN speed and frame ID) and to test the
module components (Key s, LEDs, Faders and Rotary encoders).

At this stage, the keys have no function as t hey are protect ed by the Unlock key.

ruby User M anualV ersion: 6.0.0/464/82

6. Maintenance

Once you have entered the “speci al functions” mode, you can ac cess different menus using the upper row of
keys:

And adjust set t i ngs us ing the lower row of keys:

All keys are protected by the Unlock button, so you must press and hold Unlock whenever you wish to make a
selection:

2. To enter a menu or perform a test, press and hold Unlock and select the menu.

For example, pressing and holding Unlock and selecting Ca n S pee d enters t he CAN speed menu:

·

Act i ve key s are red. These s how your current s etting and selected menu.

·

Operational keys are green. These provide acces s t o alternative sett ings.
In our example, the key T11 should be red to indicate that we are inside t he CAN speed menu. One of the k eys

T4, T5 or T13 will also be red to indicate the current CAN speed:

·

T4 = 10kBit/s (for test purposes only)

·

T5 = 100kBit / s

·

T13 = 500kBit/ a

3. Press and hold Unlock and T4, T5 or T13 to select a different speed.

4. For CAN speed and frame ID s ettings, you need to c onfirm any c hanges by pressing and holding Unlock

and the menu (CAN speed or Frame ID).
The new settings are written to flash memory and the module will perform a reset.

5. Alternatively, to exit any menu without making a change, or to exit a test, press and hold Unlock and Exit.

6. Once have y ou finished working in the “special functions” mode, repower the c ontrol surface frame to return

the module to normal operation.

ruby User M anual V ersion: 6.0.0/4 65/82

6. Maintenance

6.3.2 Central Module Special Functions Mode

To enter the “special funct ions” mode on a Central Module:

1. Press and hold both the keys T57 and T58 during power on of the control surface frame.

Setti ngs and tests are performed in a simil ar manner as on a Fader Module.
When running the Key Tes t , the value of the ambient light sensor is dis played as a binary encoded value through

the colour ing of the keys T37 to T41.

ruby User M anualV ersion: 6.0.0/466/82

6. Maintenance

6.3.3 CAN Speed

The CAN Spee d m enu allows you to display and change the speed of the CAN bus:

·

T4 = 10kBit/s (for test purposes only)

·

T5 = 100kBit / s

·

T13 = 500kBit/ s
Note that the CAN speed of 10kbit/ sec is available for test purposes only, and should not be used for operation.

The CAN speed will affect the maximum dist anc e which you c an run the cables:

Transfer Speed

Maximum Distance

500 kbit/sec (recommended)

60 m

100 kbit/sec

300 m

Remember t o confirm any c hanges by pressing and holding Unlock and the CAN speed menu button. The new
settings are written to flash memory and the module will perform a reset.

All devices on the CAN bus MUST be set to t he same speed, so if you change the speed you will need to
repeat the operation on all control surface modules and any optional Key P anels.

6.3.4 Frame ID (Can Bus Address)

The Frame_ID menu allows you to dis play and change the frame ID (CAN bus address) of the module.
The Frame ID keys are additive so it is possible to set an ID from 0 to 31 using the 4-bit frame ID as follows:

·

T14 = Frame ID Bit 4 (MS B )

·

T22 = Frame ID Bit 3

·

T23 = Frame ID Bit 2

·

T31 = Frame ID Bit 1

·

T32 = Frame ID Bit 0 (LSB)

The Frame_ID (CAN bus address) should be set t o match the Frame layout defined in the configuration.

ruby User M anual V ersion: 6.0.0/4 67/82

6. Maintenance

6.3.5 Key Test

This test checks t he function of all key s, faders and rotary encoders on
the module.

Having entered the Key-Test menu, check the controls on each fader
strip as follows:

1. Press and hold a key and it will light (red).

2. Release the key and it will l ight (green).

3. Turning a rotary encoder will result in the corresponding key

changing colour in sequence: off, red, green, yellow, white, blue,
magenta, cyan. In addition all OLED displays are dimmed or inverted.

4. Moving a fader will result in the 4 keys nearest the fader

changing colour in sequence: off (fader closed), red, green and blue
(fader open).

6.3.6 Self Test

This t es t is an automated test which c hecks all t he key and LAW O dis play LEDs.
Enter the Self Test and all LAWO displays and keys, except Unlock, with flash in yellow.

6.3.7 Fader-Calibrate

This test calibrates the module’s motorised faders. This operation should be performed after replacing a fader, or
after arou nd 2 year’s opera tion.

ruby User M anualV ersion: 6.0.0/468/82

6. Maintenance

6.3.8 RGB Def

This menu can be used to change the colour of keys which are in an off state (normally unlit).

1. Enter the menu and use the encoders 2, 3 and 4 to adjust the amount of red, green and blue.

The resulting colour is shown on the Unlock key (T2).

2. Press Unlock and Exit to exit the menu and set all unlit keys to the same colour as T2.

To reset the colour so that all keys return to their default unlit state:

3. Select the menu again by pressing Unlock and RGB Def.

Th e key T2 is unlit.

4. And press Unlock and Exit.

ruby User M anual V ersion: 6.0.0/4 69/82

6. Maintenance

6.4 Replacing Defective Parts

The CAN bus is hot-pluggable which means that t he control s urface c an be connected and disconnected during
uptime. This allows fast replacement of a frame in the case of a hardware failure. P rovi ding t he replacement frame
is set to t he c orrect CAN bus addresses, it will immediately t ake over t he s ame functions as t he ex changed
frame.

ruby User M anualV ersion: 6.0.0/470/82

6. Maintenance

6.5 Locating the Control Surface Serial Number

The serial number of your control surface can be found on the product information sti c k er placed on t he underside
of the panel:

Sticker Location

The S/N field indicates t he Serial Number:

Product Information Sticker

ruby User M anual V ersion: 6.0.0/4 71/82

6. Maintenance

6.6 Cleaning the Control Surface

To clean the control surface please use a cleaning cloth with the following properties:

·

Antistatic

·

Fluff-free

·

Wit hout emery pieces

Warning

DO NOT spill liquids into any s y stem c omponents!
DO NOT clean the mixing console with sharp instruments!

ruby User M anualV ersion: 6.0.0/472/82

7. Trouble-shootin g

7. Trou b le-shootin g

This c hapter includes a series of ty pic al problems and tips t o help you fault find the sy stem.
Topics inc lude:

·

Solving Connectivity Iss ues

ruby User M anual V ersion: 6.0.0/4 73/82

7. Trouble-shootin g

7.1 Solving Connectivity Issues

7.1.1 The control surf ace is behaving oddly

This can occur if the s ame CAN bus address i s used for more than one module.

1. Check the CAN bus addresses of each module using the special functions mode.

Each address must be unique and match the one defined by t he configuration. See CAN Bus Addressi ng.

ruby User M anualV ersion: 6.0.0/474/82

8. Appendices

8. Append i ces

This chapter includes further information which you may find useful.
Topics inc lude:

·

Part Numbers

·

Dimension Drawings

·

Connector Pin-Outs

·

The 12V DC Power Supply

·

The User Labels Software

ruby User M anual V ersion: 6.0.0/4 75/82

8. Appendices

8.1 Part N umbers

System Compo n ent

Part Number

Surface Table Top

ruby 4-fader table top

RU4FTT

ruby 8-fader table top

RU8FTT

ruby 12-fader table top

RU12FTT

ruby 16-fader table top

RU16FTT

ruby 4-fader Extender table top

RU4FEXTT

ruby 8 fader Ext ender table top

RU4FEXTT

ruby 12-fader Extender table top

RU12FEXTT

ruby 16-fader Extender table top

RU16FEXTT

ruby Central Module Extender table top

RUCMEXTT

Surface Countersunk

ruby 4-fader countersunk

RU4FCS

ruby 8-fader countersunk

RU8FCS

ruby 12 fader countersunk

RU12FCS

ruby 16-fader countersunk

RU16FCS

ruby 4-fader Extender countersunk

RU4FEXCS

ruby 8-fader Extender countersunk

RU8FEXCS

ruby 12-fader Extender countersunk

RU12FEXCS

ruby 16-fader Extender countersunk

RU16FEXCS

ruby Central Module Extender countersunk

RUCMEXCS

Surface Countersunk Short

ruby 4-fader countersunk short

RU4FCSS

ruby 8-fader countersunk short

RU8FCSS

ruby 12 fader countersunk short

RU12FCSS

ruby 16-fader countersunk short

RU16FCSS

ruby 4-fader Extender countersunk short

RU4FEXCSS

ruby 8-fader Extender countersunk short

RU8FEXCSS

ruby 12-fader Extender countersunk short

RU12FEXCSS

ruby 16-fader Extender countersunk short

RU16FEXCSS

ruby Central Module Extender countersunk short

RUCMEXCSS

Accessories

12V DC power supply

955/50-80

ruby User M anualV ersion: 6.0.0/476/82

8. Appendices

8.2 Dimension Drawings

Please use the links below to open the dimension drawing as a pdf:

·

Ruby Desk Table Top Dimension Drawing

·

Ruby Desk Countersink S TD Dimension Drawing

·

Ruby Desk Countersink S hort Dimension Drawing

The drawings show an 8-fader main frame.
Drawings for other fr a me sizes are av ailab le from the Download-Center at www.lawo.com (after Login).

ruby User M anual V ersion: 6.0.0/4 77/82

8. Appendices

8.3 Connector Pin-Outs

8.3.1 CAN

8-pin RJ45 connector, f emale.

8.3.2 DC Power Input

4-pin Kycon connector, female.

ruby User M anualV ersion: 6.0.0/478/82

8. Appendices

8.4 The 12V DC Power Supply

The 12V DC power supply c an be used to connect power to the DC input on the rear of the frame.

12V DC Po wer Supply (9 55/50 -80)

DC Plug Pinning

Dimensions and Weight

Parameter

Conditions

Unit

M echanical data

Width

72mmHeight

35mmLength

175mmWeight

670gCable length

without plug

1200

mm

Electrical Specification

Parameter

Conditions

Min.

Typ.

Max.

Unit

Input Voltage

85

264

VAC

Frequency

4763Hz

Input Current

1,85A/115VAC

1A/230VAC

AAC
Inrush Current

120A/230VAC

AAC

Efficiency

89

%

Output V oltage

12±5%

VDC

Output Current

11.5

ADC

Leakage Current

0,75

mA

ruby User M anual V ersion: 6.0.0/4 79/82

8. Appendices

8.5 The U ser Labels Software

Thw User La bels Softwa re can be used to edit user labels during runtime.

8.5.1 System Requirem ents

ruby

Th e DSP Core MUST be running OS Version 3.4.0.17a software or higher.

You can check the OS version using the W eb Browser Interface (click on Supplementary Information).

If the OS-Version is lower than 3.4.0.17a, please contact your local Lawo representative or email

[e-mail].

PC Requirements

·

Windows 7, 8 or higher operating system.

·

Core-i5 processor or higher.

·

2GB RAM (minimum)

8.5.2 Install ing the Software

The userlabels.exe setup application is inc l uded with your sys tem software.

1. Co py the userlabels.exe applicat ion onto your computer.

2. Do ub le click on the userlabels.exe application icon:

This s tarts the ‘DSA User Labels Setup W izard’:

3. Follow the Wizard's instruct ions ac cepting the default options provided.

4. When you reach the 'Summary' window, check t he options and cli ck Install - the software is installed

onto your computer; this m ay t ak e a few minutes.

By default, files are installed in the location: ‘C:\Program Files\DSA’.

5. When the installati on is complete, a confirmation window appears - clic k on Finish to exit the ‘Set up

Wizard’.

ruby User M anualV ersion: 6.0.0/480/82

8. Appendices

If you have any problems with the installation, please contact your local Lawo representative or email

[e-mail].

8.5.3 Network Connection

You should connect the User La bels PC to the DSP Core's Et hernet port either directly or via a network switc h.
Do NOT use an Ethernet hub as this will interrupt the data stream. See Sys tem Connections : E thernet.

The User Labels software uses the DMS service (the first DMS Channel) specified by the VisAdmin programme,
which is automatically installed when you install Vi sTool MK2. See the "Vi s Tool User Guide" for details.

8.5.4 Editing User Labels

1. Start t he "User Labels" application either by selecting it s desk top icon or by s electing START -> All

Programs -> DSA -> User La b els:

This is the default file path created during a standard install.

The application opens with an empty window:

When online, the flag at the bottom left of t he window indicat es that the s oftware is communicat ing
correctly with the ruby system. If this flag does not appear, then check the network connection to t he syst em.

ruby User M anual V ersion: 6.0.0/4 81/82

8. Appendices

2. To transfer the current labels from the console, select Load from Desk.

The window upda tes to show the Name, Display name and User La bel Lines for all sources and buss es defined
in the configuration. The fields relate to the front panel as follows:

User Labels Software

Conso le Front Panel

Note that you will see all s ources and busses even if they are not assigned to a fader st rip.

3. Click in the User Labe l - Li ne 1, or Use r La b e l - Line 2, fields to edit or add a name. You may enter up t o

8 characters in each line:

The Name and Display fields are defined by the configuration and cannot be edited by the User Lab els software.
(Use the Reference name and Display name in S ource -> Parm to c onfigure these options. )

4. When you have finished editing, selec t Save to Des k to transfer the new User Labels to t he console. This

can be done at any ti me, even when the console is on-air.

Note that:

·

User labels for all s ource and buss es in t he c onfiguration are saved when you s ave a s napshot. This
means that you can save and recall labels for specific s hows along with other settings, see Snapshots.

ruby User M anualV ersion: 6.0.0/482/82

8. Appendices

·

The last User Labels are stored in the console's warm st art data. This means that when you power on
you will get back to wherever you were when the power was last t urned off!

8.5.5 Other Functions

The "User Labels" s oftware includes some other buttons and menu options:

·

Clear Ta ble - selec t t his butt on to c l ear the User Labels for all sources and busses in the table.

·

Data M enu:

o Load from Desk - transfers t he current us er labels from the

console.

o Save to Desk - transfers user labels from the s oftware to t he

console.

o Export... - use t his option to export the current user label

table as an .x ml file. You can use this to copy us er l abels
from one sys tem to another.

o Import... - use this option to im port user l abels from an . xm l

file.

o Exit - closes t he User Labels software application.

·

View M enu:

o Identifier - displays the internal System Number. This

number cannot be modified and is for information only.

o Font... - s elect to open the Font dialogue box. You c an use

this to adjust the on-screen font for the user labels table.