Home » Rane Manuals » Audio Components » Rane HAL1x » Manual Viewer

Rane HAL1x Design Guide - Page 120

Inactive Link, Link Master

Add to My Manuals
Save this manual to your list of manuals

Page 120 highlights

HAL SYSTEM DESIGN GUIDE example, if you plan to be deactivating and re-activating control links, you definitely need to understand the Link Master! To fully explain the Link Master function, let's begin with a scenario. Suppose that you have two Level controls in your system (LevelA and LevelB). In most situations, these two Level controls work independently, but in a few cases they must track one another. Therefore, you create a control link (Link1) that links LevelA and LevelB. Link1 remains inactive most of the time. While inactive, LevelA and LevelB operate independently and are, therefore, typically set to a different value. So what happens when you activate Link1? Should LevelA snap to LevelB's value or should LevelB snap to LevelA's value? This is where the Link Master comes into play. In any control link, one participant is designated as the Link Master. You can accept the default designation or configure it yourself. In this scenario, if LevelA is the Link Master, LevelB and the control link value take on the value of LevelA. If LevelB is the Link Master, Level A and the control link value take on the value of LevelB. As long as Link1 remains active, LevelA and LevelB track the control link value. The following images help illustrate this example: Inactive Link: 116

Section	Page
CHAPTER 1: Welcome to the World of HAL	5
About This Document	5
System Requirements	7
Minimum Requirements for Running Halogen	7
Recommendations for Best Performance	7
Administrative Rights Requirements	8
Using the HAL System Documentation	8
Getting Started	10
CHAPTER 2: Introduction to the HAL System	12
Overview of HAL Devices	15
Available HAL Models	15
HAL Front and Rear Panels	16
Discontinued HAL Models	22
Remote Audio Devices	25
How the shielded CAT 5e Cabling is Utilized	25
RAD Grounding	26
The Parts of a RAD	28
PAGER1 RAD	30
RAD16z	31
AM1 and AM2 RADs	34
RAD26 - One Room RAD	35
RAD27 - USB Audio	41
Using a RAD as a Portable Device	45
Discontinued RAD Models	47
Digital Remote Devices	47
DR Grounding	48
Available Digital Remote Models	48
Infrared Remote Devices	65
IR2 Device	65
Expansion Units	67
HAL1x Expansion Units	68
Discontinued EXP Models	89
Momentary and Latching Toggle Configuration	89
Introduction to the Halogen Software	92
Basic Structure	93
Workspace Layout	94
HAL System Connectivity	95
Required Ports	95
Required Processes	96
CHAPTER 3: Key Audio Design Features	98
About the Distributed Program Bus	98
About Zone Processing	100
About Paging	103
About Control Links	110
Basics of Control Linking	110
Advanced Topics	118
Best Practices	124
About Room Combine	126
About Presets	140
About Events	153
About Control Pages	158
Basics of Control Pages	158
Advanced Topics	165
Best Practices	166
CHAPTER 4: Designing and Installing Your HAL System	169
Recommended Workflow for Creating a HAL System	169
A Few Design and Installation Tips	172
Installing and Starting the Halogen Software	172
About Halogen Configuration Files	174
Creating, Viewing, and Modifying Notes about a HAL System Configuration	177
Generating Device Labels	178
Generating Hardware Lists	180
Upgrading Halogen Software and HAL Firmware	180
Uninstalling the Halogen Software	182
APPENDIX A: Transitioning from Drag Net	183
Index	186

Match case Limit results 1 per page

example, if you plan to be deactivating and re-activating control links, you definitely need to understand the

Link Master!

To fully explain the Link Master function, let’s begin with a scenario. Suppose that you have two Level con-

trols in your system (LevelA and LevelB). In most situations, these two Level controls work independently,

but in a few cases they must track one another. Therefore, you create a control link (Link1) that links LevelA

and LevelB. Link1 remains inactive most of the time. While inactive, LevelA and LevelB operate inde-

pendently and are, therefore, typically set to a different value. So what happens when you activate Link1?

Should LevelA snap to LevelB’s value or should LevelB snap to LevelA’s value? This is where the Link

Master comes into play. In any control link, one participant is designated as the Link Master. You can accept

the default designation or configure it yourself. In this scenario, if LevelA is the Link Master, LevelB and the

control link value take on the value of LevelA. If LevelB is the Link Master, Level A and the control link

value take on the value of LevelB. As long as Link1 remains active, LevelA and LevelB track the control

link value. The following images help illustrate this example:

Inactive Link:

HAL SYSTEM DESIGN GUIDE

116