POWER CORE
User Manual
Version: V6.0. 0/ 5
Edition: 21 May 2018
To obtain the latest documentati on and software downloads, please visit:
www.lawo.com/downloads
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 ex press ly prohibited, unless prior written consent is obtained from the Lawo AG.
All t rademarks and registered trademarks belong to their respective owners. It c annot be guaranteed that
all product names, products , trademarks, requisitions, regulations, guidelines, specifications and norms
are free from trade mark rights of third parties.
All entries in t his document have been thoroughly check ed; however no guarantee for correctness c an be
given. Lawo AG cannot be held responsible for any mis leading or incorrect information provided throughout
this m anual.
Lawo AG reserves the right to change specifications at any time without notice.
© Lawo AG, 2018
Table of Contents
Table of Contents
1. Introduction ... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... . .... .... .... .... .... .... .... .... .... .... .... .... .... . 8
2. Important Safety Instruct ions ... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... . .... .... .... .... .... .... .... 9
3. Overview ... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... . .... .... .... .... .... .... .... .... .... .... .... .... .... .... 11
4. The Hardware ..... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... . .... .... .... .... .... .... .... .... .... .. 12
4.1 Controls, Indicators & Connectors .. . . .... .... .... . .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... . 13
4.2 IO Cards .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... . .... .... .... .... .... .... .... .... .... . 16
4.3 Accessories .... . .... .... .... .... .... .... .... .... .... .... .... .... .... . .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... ... 17
5. Installation . .... .... .... .... . .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... . .... .... .... .... .... .. 18
5.1 Preparation . .... .... .... .... .... .... .... .... .... . .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... 19
5.2 Fitt ing the IO Cards .. . . .... .... .... .... .... . .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .. 20
5.3 Fitt ing the MA DI SFP Modules .. .... .... .... .... . .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... 22
5.4 Powering the Device .. . .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... . .... .... .... .... .... .... .... .... .... .. 23
5.5 Setti ng the IP Address .. .... . .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... . .... .. 24
5.6 Getting Operational ... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... . .... .... .... .... .... .... .... ... 25
5.7 Wiring ...... .... .... .... .... .... .... .... .... .... .... .... . .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... ... 26
5.8 Synchronisation .. . .... .... .... .... .... .... .... .... .... .... .... .... .... . .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... 31
6. Licensing ........ .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... . .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... . 33
6.1 Licensed Feature Sets .. . . .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... . .... .... .... .... .... .... .... .... .... .... .... . 34
6.2 Working with the License S yst em .. .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... . .... .... .... .... .... .... ... 36
7. Configuring POWE R CORE . . .... .... .... .... .... .... .... .... .... .... .... .... .... . .... .... .... .... .... .... .... .... .... .... .... .... .... .... . 46
7.1 Starting a Confi guration . . . .... .... .... .... .... .... .... .... .... .... . .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... . 47
7.2 Creating a New Configuration .... .... .... .... .... . .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... 48
7.3 Opening an Exis ting Configuration . . . .... .... .... .... .... .... .... .... .... . .... .... .... .... .... .... .... .... .... .... .... .... .... .. 50
7.4 Loading a Project from the Unit .. .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... . .... .... ... 51
7.5 Selecti ng a Different License Pac kage .. . .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... . 52
7.6 Saving the Project ... . .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... . .... .... .... .... .... .... .... .... .... 53
7.7 Transferring Configuration Data to the Unit ...... .... .... .... .... .... .... .... . .... .... .... .... .... .... .... .... .... .... .... .... 54
8. Audio IO ... .... .... .... .... .... .... .... .... .... .... .... .... .... .... . .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... 56
8.1 Setti ng Up IO Cards . . . .... .... .... .... .... . .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .. 57
8.2 Setti ng Up RAVENNA/AE S 67 .. . . .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... 64
8.3 Setti ng Up MADI .. . . .... .... .... .... .... .... .... .... .... .... .... .... .... .... . .... .... .... .... .... .... .... .... .... .... .... .... .... .... .. 71
POWER CORE User Manual V ersion: V 6.0.0/5
3/459
Table of Contents
8.4 Setti ng Up Sync hronisation .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... . .... .... .... .... .... .... .. 74
9. Audio Mix E ngine .... .... .... .... .... .... .... .... .... .... . .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .. 75
9.1 Sources .. . .... .... .... . .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... . .... .... .... .... .. 76
9.2 Summing Busses .. . . .... .... .... .... . .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... 92
9.3 DSP Parameters ...... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... . .... .... .... .... .... .... .... .... .... .... .... .... .. 102
9.4 VCA Groups . . .... .... .... .... .... .... .... .... .... .... . .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... 110
9.5 PFL Monitoring ..... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... . .... .... .... .... .... .... .... .... .... .... .... . 112
9.6 Monitoring Master Control & Talkback .. .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... . 117
9.7 Monitoring Signal Selection . .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... . .... .... .... .... .... .... .... .... 126
9.8 Tone Generator ...... .... .... .... .... .... .... .... .... . .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... 130
9.9 Signal Metering .. . .... .... .... .... .... .... .... .... .... .... . .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... ... 132
9.10 Surround Mixing ...... .... .... .... .... .... .... .... .... .... .... .... .... .... . .... .... .... .... .... .... .... .... .... .... .... .... .... .... ... 140
10. A udio Utilit i es .. . . .... .... .... .... .... .... .... .... .... .... .... .... . .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... . 142
10.1 DMS Metering & Loopback s .. .... .... .... .... .... .... .... . .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... . 143
10.2 GP Sums ... . .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... . .... .... .... .... .... .... .... .... .... .... .... .. 145
10.3 Direct Outs . . . .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... . .... .... .... .... .... .... .... . 146
11. Routing Matrix ... .... .... .... .... .... .... .... .... .... .... .... .... .... . .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... . 147
11.1 Routing Matrix Anatomy . . . .... .... .... .... .... .... .... . .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .. 148
11.2 Cross point S wit c hing .. . . .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... . .... .... .... .... .... .... .... .... .. 149
11.3 Saving Crosspoints in S napshots ...... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... . .... .... .. 157
12. Intercom .. . . .... .... .... .... .... .... .... .... .... .... .... .... .... .... . .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... . 158
12.1 InterCom Sys t em Introduction . . .... .... .... .... . .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... ... 159
12.2 InterCom Local vs InterCom Net .... . . .... .... .... .... .... .... .... .... .... .... .... .... .... . .... .... .... .... .... .... .... .... .... 160
12.3 System Configuration .. . . .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... . .... .... .... .... .... . 161
12.4 InterCom Software ..... . .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... . .... .... .... 170
13. Control Surface Configuration ...... .... .... .... .... .... .... .... .... . .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... . 183
13.1 Frame Selection .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... . .... .... .... .... 184
13.2 Panel Selection .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... . .... .... .... .... .... .... .... .... .... . 185
13.3 Virtual Fader Modules .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... . .... .... .... .... .... .... .... .... .... .... 186
13.4 Configuring the Fader Module .. . .... .... .... .... .... .... .... . .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... ... 188
13.5 Configuring the Central Module .. . .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... . .... .... . 206
13.6 System -> Definition -> Parameter = Fader . . .... .... .... .... .... .... .... .... .... .... .... .... . .... .... .... .... .... .... .... 209
13.7 System -> Definition -> Parameter = S et t i ngs . . . .... .... .... .... .... .... .... .... .... .... .... .... .... . .... .... .... .... .... 212
4/459 V ersion: V 6.0.0/5
POWER CORE User Manual
Table of Contents
13.8 System -> Definition -> Parameter = Central Menu .. . .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... . 213
13.9 System -> Definition -> Parameter = A ux B us M enu .... .... .... .... .... .... .... .... .... .... .... . .... .... .... .... .... . 214
13.10 Connect i ng a Control Surface . . . .... .... .... . .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... ... 215
14. S napshots S y stem .. .... .... .... .... .... .... .... .... .... .... .... .... . .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... 219
14.1 Introduction .... . . .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... . .... .... .... .... .... .... .... .... .... .... .... .... .... . 220
14.2 Local Snapshot Memories .... . . .... .... .... .... .... .... . .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... 221
14.3 Isolating Fader Strips ... .... .... . .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... . . 223
14.4 Snapshot Sett ings .. . . .... .... .... .... .... .... . .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... . 224
14.5 Vis Tool Snapshots ... .... .... .... .... .... .... .... .... .... .... .... . .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .. 229
14.6 User Acc es s Rights . . .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... . .... .... .... .... .... .... .... .... .... . 232
15. Connecting a Vis Tool MK2 PC . . .... .... .... .... .... .... .... .... .... .... .... . .... .... .... .... .... .... .... .... .... .... .... .... .... .... ... 246
15.1 Vis Tool Button Control ...... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... . .... .... .... .... .... .... .... .... .... .... .. 247
15.2 Access t o Control Surface Parameters .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... . .... .... .... .... .... .... 249
15.3 Fader St rip As signment . .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... . .... .... .... .... .... .... .... .... .... . 250
15.4 DSP Parameter Control ... . . .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... . .... .... .... .... .... . 253
15.5 Fader St rip ACCESS K ey s .... . . .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... . .... .... ... 254
15.6 Monitoring Signal Switcher .. .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... . .... .... .... .... 255
15.7 Talkback Controller ...... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... . .... .... .... .... .... .... .... .... .... .... .. 257
15.8 Routing Matrix Control .. . . .... .... . .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... 259
15.9 Advanced VisTool Integration ..... .... .... .... .... .... .... .... .... .... .... .... .... . .... .... .... .... .... .... .... .... .... .... .... . 265
15.10 Timers ..... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... . .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... . 272
15.11 General Settings ... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... . .... .... .... .... .... .... . 273
16. K ey P anel Control .. . .... .... .... .... .... .... . .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... 274
16.1 Key P anel Options .. .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... . .... .... .... .... .... .... .... .... .... .... .... ... 275
16.2 Adding Key Panels ... . . .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... . .... .... .... .... .... .... ... 276
16.3 Configuring Key Panels ... . .... .... .... .... .... .... .... .... .... .... .... .... .... . .... .... .... .... .... .... .... .... .... .... .... .... .. 278
17. GPIO ... . .... .... .... .... .... .... .... .... .... .... .... .... .... .... . .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... . 281
17.1 Configuring Physi c al GP IOs ..... .... .... . .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... ... 282
17.2 Virtual GPIO Networking .... .... .... .... .... .... .... .... .... . .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... . 283
17.3 Preparing the TCP/IP Connecti ons . . .... .... .... .... .... .... .... .... .... .... . .... .... .... .... .... .... .... .... .... .... .... .... . 284
17.4 GNET (GPI/O Network) . . .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... . .... .... .... .... . 286
17.5 Ember+ ... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... . .... .... .... .... .... .... .... .. 288
17.6 GPIO over Audio channels (GT In/Out) ..... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... . .... .... .... 296
POWER CORE User Manual V ersion: V 6.0.0/5
5/459
Table of Contents
18. Configuring Cust om Logical B ehaviour . .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... . .... .... .... .... .... .... .. 298
18.1 Label .... . .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... . .... .... .... .... .... .... .... ... 299
18.2 Logic -> AND8 ..... .... .... .... .... .... . .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .. 300
18.3 Logic -> ASSIGN . .... .... .... .... .... . .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .. 302
18.4 Logic -> Blender .. . .... .... .... . .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... . .... 303
18.5 Logic -> Blink .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... . .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... 304
18.6 Logic -> Butt on 16 . .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... . .... .... .... .... 305
18.7 Logic -> Butt on 64 . .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... . .... .... .... .... 307
18.8 Logic -> DEL .... .... .... .... .... .... .... .... . .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... . 308
18.9 Logic -> DFF (Data Flip Flop) .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... . .... .. 309
18.10 Logic -> E nable Func ... . .... . .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... . .... 310
18.11 Logic -> Gate .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... . .... .... .... .... .... .... .... .... .... .... 312
18.12 Logic -> IMP .. .... .... .... .... .... .... .... .... .... .... .... .... . .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... 313
18.13 Logic -> LS Command . . .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... . .... .... .... .... .... .... .... .... .... .. 314
18.14 Logic -> Mac ro .... . . .... .... .... .... .... .... .... .... .... .... .... .... .... . .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... 315
18.15 Logic -> MFF (Mono Flip Flop) .. .... .... .... .... .... .... .... .... .... .... .... .... .... .... . .... .... .... .... .... .... .... .... .... .. 336
18.16 Logic -> MOM LAT (Momentary Latc h) .... . .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... 337
18.17 Logic -> Mon Desk . . .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... . .... .... .... .... .... .... .... .... .... .... ... 338
18.18 Logic -> MUX/ DEM UX 8 ..... .... .... .... .... .... .... .... .... .... .... .... . .... .... .... .... .... .... .... .... .... .... .... .... .... .... . 339
18.19 Logic -> NOT ...... .... . .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... . .... .... .... .. 340
18.20 Logic -> OR8 . .... .... .... .... .... .... .... .... .... .... .... .... . .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... 341
18.21 Logic -> OR32 . . . .... .... .... .... .... . .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... 343
18.22 Logic -> P RIO .. .... .... .... .... .... .... .... .... .... .... . .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .. 344
18.23 Logic -> TB Stat e .. . .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... . .... .... .... .... 345
18.24 Logic -> Text Prio .... . .... .... .... .... .... .... .... .... .... .... .... .... .... .... . .... .... .... .... .... .... .... .... .... .... .... .... .... . 346
18.25 Logic -> TFF (Toggle Flip Flop) .. .... .... .... .... . .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .. 348
18.26 PowerUp Control Outputs .. . . .... .... . .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... ... 349
18.27 Ember+ Logical Funct ions . . .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... . .... .... .... .... .... 350
19. Networking POWER CORE ...... .... .... .... .... .... .... .... .... .... . .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... 356
19.1 Remote Control from Playout S yst ems (RAS) .. . . .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... . ... 357
19.2 Resource S haring (Arbitration & Tielines) .. .... .... .... .... .... .... .... .... .... .... . .... .... .... .... .... .... .... .... .... ... 358
19.3 Remote Control of Sources (via Ember+) . . .... .... .... .... . .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... 366
19.4 Matrix Control . .... .... .... . .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... . .... .. 369
19.5 DAW Control . .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... . .... .... .... .... .... .... .... .... .... .... 377
6/459 V ersion: V 6.0.0/5
POWER CORE User Manual
Table of Contents
19.6 UDP Matrix .... . .... .... .... .... .... .... .... .... .... .... .... .... .... . .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .. 380
20. Maintenance .. . . .... .... .... .... .... .... .... .... .... .... .... .... . .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... ... 382
20.1 Restarting the System .. . . .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... . .... .... .... .... .... .... .... .... .... .... 383
20.2 The Web UI ...... .... .... .... .... .... .... .... .... .... .... .... .... .... .... . .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... . 384
20.3 Using the Firmware Update Tool (SoP Ex plorer) .. . . .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... . .... 406
20.4 Replacing Defect ive Parts . .... .... .... .... .... .... . .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .. 423
20.5 Alarm Management .. . .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... . .... .... .... .... .... . 424
21. Trouble-shooting .. . .... .... .... .... .... .... .... .... .... .... .... . .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... ... 427
21.1 Boot-up Iss ues ...... .... .... .... .... .... . .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... 428
21.2 Hardware & Power Iss ues .... .... .... . .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... ... 429
21.3 IP Networking Issues .. .... .... .... .... .... . .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... 430
21.4 Configuration Issues .. . . .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... . .... .... .... .... .... .... .... ... 431
22. Appendices ... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... . .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... . 432
22.1 Part Numbers ..... .... .... .... .... .... .... .... .... .... .... .... . .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... ... 433
22.2 Dimension Drawing ... .... .... .... .... .... .... .... . .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... . 434
22.3 Connector Pin-Outs . . . .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... . .... .... .... .... .... .... .... .... .... .... .... .... . 435
22.4 The 12V DC Power Supply . .... .... .... .... .... .... .... . .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... . 438
22.5 Default TCP/IP Settings .... .... .... .... .... .... .... .... .... . .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .. 439
22.6 Matrix Numbers .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... . .... .... .... .... .... . 440
22.7 Mack ie HUI Parameters .. . . .... .... .... .... .... .... .... .... .... .... .... .... .... . .... .... .... .... .... .... .... .... .... .... .... .... .. 441
22.8 Ember+ Tree ..... .... .... . .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... . .... .... ... 444
23. Glossary .... . .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... . .... .... .... .... .... .... .... .... .... .... .... .... ... 456
POWER CORE User Manual V ersion: V 6.0.0/5
7/459
1. Introduction
Notes - points of clarificat ion.
Tips - useful tips and short cuts.
WARNINGS: Alert you whe n an action should always be observed!
1. In troduction
Welc ome t o P OWER CORE.
About this M anual
This document describes all aspects of POWER CORE, including its hardware, installation, licensing,
configuration, remote control, networking and maintenance. The specification is valid for Version 6.0.0.x .
POWER CORE c an be installed as a st and-alone device, or as the integrated DSP Core for a Lawo c ontrol
surface. If installing with a control surface, you will find more information on the surface components in the
relevant manual.
All Lawo manuals are av ailab le from the Download-Center at www.lawo.com (after Login).
Look out for the followi ng which indicate:
Lawo User Registration
For access to the Download-Center and to receive regular product updates, please register at:
www.lawo.com/user-registration.
POWER CORE User ManualV ersion: V 6.0.0/58/459
2. Important Safety Instruction s
Exposure to excessive sound pressure levels c an 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 devic es 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 imm ediately by pulling out the
power lead.
·
All devices MUST be grounded. Grounding connectors are provided on all devices. In addition, all lowvoltage devic es ex t ernal to the syst em mus t also be grounded before operation.
·
For Sc andinavian countries, ALW AYS us e a grounded mains connecti on, t o prevent t he device from
being grounded through Ethernet or other signal connections.
·
Do NOT use the system 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 servi ce staff may replace batteries.
·
CAUTION: Danger of explosion if battery is incorrec tly replaced - Replace only with the same or
equivalent type.
Servic ing of components ins ide a device MUST only be carried out by qualified servic e personnel acc ording to
the followi ng guidelines:
·
Before removing parts of the casing, shields, et c . t he device MUST be s witc hed off and dis c onnected
from all mains.
·
Before opening a device, t he power supply capacitor MUST be discharged with a suit able resis t or.
·
Components that c arry heavy elec trical loads, s uch as power t ransistors and resistors, s hould NOT
be touched until cool to avoid burns.
Servic ing unprotect ed powered devic es may only be c arried out by qualified servi ce personnel at their own
risk. The following instruct i ons M UST be observed:
·
NEVER touch bare wires or circ uitry .
·
Use insulated tools ONLY.
·
DO NOT touch metal semi-conductor cas ings as t hey can bear high voltages.
This equipment may use Class 1 Laser products which emit invisible laser radiation that may lead to eye
injury.
·
NEVER look directl y int o optic al components or optic al fibre cables.
·
Fit protect ion caps t o close any unused optical components.
·
Connect all opti c al fibre cables BEFORE turning on the equipment.
2. Impo rtant Safety Instructions
General Safety
Eye Safety
POWER CORE User Manual V ersion: V 6.0.0/5 9/459
Defective Parts/ Modul es
POW E R CORE contains no user-serviceable parts. Therefore DO NOT open the devic es other than to perform
the procedures described in this m anual.
In the event of a hardware defect, please s end the sy stem component to y our local s ervic e representative
together with a detailed description of the fault. W e would like to remind you to please check carefully
whether the failure is caused by erroneous configuration, operation or connection before sending parts for
repair. Please contact our servic e department before sending parts for repair.
DO NOT touch the person or his/ her c lothing before power is turned off, otherwise you risk sus taining an
electric s hoc k y ourself.
Separate the person as quickl y as poss ible from the electric power source as follows:
·
Switc h off the equipment.
·
Unplug or disconnect t he mains c able.
·
Move the person away from the power source by using dry insulating material (such as wood or
plastic).
If t he person is unconsc ious :
·
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 sustained an electric shock, A LWAYS consult a doctor.
First Aid (in the case of electric shock)
2. Important Safety Instruction s
POWER CORE User ManualV ersion: V 6.0.0/510/459
3. Overview
3. Overview
POW ER CORE is a 1RU, 19-inch DSP Core, IO interface and routing matrix. It c an be inst alled as a s t and-alone
processing engine / matrix, or as t he integrated DSP / IO Core for a Lawo control surface.
Audio Interfacin g
As standard, there are two AES67/RAVENNA streaming ports, four optical MADI ports and eight GPIOs for
contact c l os ures. Opti onally, up to eight plug-in IO cards can be fitted to the rear expansion slot s to add Mic/Line,
Line In, Line Out, St udio IO, AES 3 IO or MADI IO.
Signal Processing
All units i nc lude DSP to c reate sources and summing buses with s i gnal processing: E Q, Dynamic s, Limit ing, Deessing and Automix, available for some signal paths. The total number of resources is determined by the li c ensed
feature set. Thus, y ou can purchase a suitable package for your application.
Licensed Feature Sets
POW ER CORE must be purchased with a license to "unlock " the s ys tem resources. Three different packages
are available: "Super A udio Node", "Radio Console L" and "Radio Console XL". Note t hat t he naming is purely a
guide, as one of the Radio Console packages could als o be suit able for a st and-alone s ys t em. The license must
be installed onto a USB memory st i c k and connected to the DONGLE port.
The Configurati o n
All programmable functions are defined by the sy stem configuration. This is s tored on the control sy stem and
read during boot-up. The configuration can be edited using the ON-AIR Designer s oft ware. The possibilit ies are
extensive and include the definition of audio inputs and outputs; s ources and buses; signal processi ng; and MF
Key functions.
Power
The devic e provides dual power feeds: A C and DC. If both inputs are connected, t hen AC provides t he main and
DC the redundant power supply. To use the DC input, y ou will need an external 12V DC power s upply; t his can be
ordered separately.
Remote Control
If P OWER CORE is connected to a control surface, t hen all resources can be controlled from the c onsole (via the
CAN bus). Alt ernatively, POWE R CORE s upports a range of remote control options including VisTool MK 2 and
Ember+ (via TCP/ IP). During installation and setup, a HTML interface known as t he " W eb UI" c an be used t o set
the IP address, c heck s y stem s tat uses and manage the AES67/RAV ENNA st reaming connections. Some of this
information is als o visi ble on the front panel display.
POWER CORE User Manual V ersion: V 6.0.0/5 11/459
4. Th e Hardware
This c hapter describes t he hardware including all options and acces s ories.
Topics inc lude:
·
Controls, Indicators & Connectors
·
IO Cards
·
Accessories
4. The Ha rdware
POWER CORE User ManualV ersion: V 6.0.0/512/459
4. The Ha rdware
WARNING: A warm start will reboo t the device. Do NOT perform a warm start while live on air!
4.1 Controls, Indicators & Connectors
1 SYSTEM Display & Rotary Control
The display s hows loc al device parameters such as the IP address. Turn the rotary control to st ep through the
available pages.
2 STATUS LED
This LE D indicates t he health of the devic e and sync st atus. If the LED is blinking at regular intervals , t hen the
device is working properly; the LED color reflects t he sync s t at us .
3 RESET button - warm start
Press this button to perform a warm s t art. The button is recessed to prevent accidental operation.
4 DONGLE
Use this port to c onnect t he USB memory s t ick c ontaining your sys t em's WIBU license. A safety c ap is available
to prevent acci dental removal of the dongle. If fitted, y ou will need a T10 st ar tool to remove the c ap.
5 CAN - CAN bus
Connects to the control s urface frames. If there are no surface c omponents, t hen the connector is unused.
6 RS 422 - Serial
This port can be used for remote control of POWER CORE, MACKIE HUI interfacing to a Digital Audio
Works tation, and for debugging.
7 ETHERNET 1 - Gigabit Eth ernet Control
Connects other devic es to the POW ER CORE control sy stem. A pplications include remote control via TCP/IP;
networking to other products; updating firmware and the configuration.
8 ETHERNET 2 & 3 - AES67 / RAVENNA IP Streaming
Connects the bi-direct ional AES67/RAV ENNA streams to the IP network. E THERNET 2 = st reaming port ra0.
ETHERNET 3 = s treaming port ra1. To achieve redundant streaming, you must us e both interfaces.
9 MADI 1 to 4 - MADI (AES10) via SFP
To use these ports , you must fit a Lawo-certified SFP module. Different SFPs are available t o s upport mult i-mode
or single-mode fibre. Eac h port can connect up t o 64 bi-directional MADI channels to an external devi ce. Ports
1&2 and 3&4 can be dual-redundant (defi ned by the ON-AIR Designer).
10 WCLK IN & OUT
WCLK IN c an be used to connect a wordclock sync reference. WCLK OUT always provides an output of the
current sys tem reference. The sync reference options are PTP, WCLK IN, MA DI or internal clock.
11 GPIO
8 x GPI (optocouplers) + 8 x GPO (silent CMOS relays) for local s ignaling and switched functi ons.
POWER CORE User Manual V ersion: V 6.0.0/5 13/459
4. The Ha rdware
WARNING: POWER CORE MUST be connected to t he mains us ing t he power cable supplied with the
system.
12 Expansion Card Slots x 8 (optional)
Up to 8 plug-in IO c ards can be fitted to the expansion s lots at t he rear of the frame. A ll c ards are hot-pluggable.
Options include: MIC/LINE, LINE IN, LINE OUT, S TUDIO IO, AE S 3 IO and MADI IO.
13 CASE
The CASE grounding screw should be used to ground the frame.
14 12V DC Input & AC Mains Input
Every devic e comes with dual power feeds: A C and DC. To use the DC input, you will need an external 12V DC
power supply. The 955/50-80 power s upply c an be ordered separately.
If both inputs are connected, then AC provides the main and DC the redundant power supply.
4.1.1 The Front Panel Display
Front View
The front panel display can be used to view local device parameters.
1. Turn the rotary control to step through the available pages. Each page includes a blue title field:
Welcome, Product, etc .
Useful parameters include t he devi ce's IP address, serial number, fi rmware versions, network port IP settings,
sy stem cl oc k reference (date and time), temperatures, fan speeds and voltages.
In the current release, t he "SE L" function can be used to adjust parameters but any c hanges are not s tored by
the device. Therefore, it is recommended to use other methods, such as the Web UI or ON-AIR Designer to adjust
parameters.
POWER CORE User ManualV ersion: V 6.0.0/514/459
4. The Ha rdware
The STATUS LED indicates the health of the device and sync status:
·
LED blinking at regular intervals = the device i s working properly; the LED color reflects the sync status.
·
LED steady state and white = the device is booting.
·
LED steady s tate and not white = t he device has an internal problem.
The table below describes all possible states.
LED Co l or
Status if LED is Steady State
Status if LED is B l i nking
Blue
Sy stem failure
Sy nchronized to PTP master
Yellow
Sy stem failure
Trying to sy nc to PT P master
Red
Sy stem failure
Sy nchronized to internal clock
Green
Sy stem failure
Sy nchronized v ia Wordclock
Magenta
Sy stem failure
Sy nchronized v ia MA DI
Off
Sy stem powered off
not applicable
White
Sy stem starting
not applicable
4.1.2 The STATUS LED
POWER CORE User Manual V ersion: V 6.0.0/5 15/459
4. The Ha rdware
IO Card
Part Number
Description
Max. per Frame
M I C / LINE IN
710/20
8 x mono Mic/Line in
4 (even slots
only)
LINE IN
710/25
8 x mono (or 4 stereo) Line in
8
LINE OUT
710/30
8 x mono (or 4 stereo) Line out
8
STUDIO IO
710/35
2 x mono Mic/Line in
2 x mono (or 1 stereo) Line out
2 x stereo Phones out
8
A ES3 IO
710/40
4 x stereo AES3 in (with SRC)
4 x stereo AES3 out
8
M ADI IO
710/50
2 x MADI via SFP: 64 mono in / 64 mono out per port
8
4.2 IO Cards
Rear Pa nel Expansion Slots
The rear of the frame has 8 expansion slots that c an host a variety of IO cards. The expansion sl ots are numbered
as s hown above. You will need to know the s lot number to check the status of an IO card in the Web UI.
IO Card Options
All IO cards are hot-pluggable. And, all IO cards, except MADI, break out on DB-25 connectors that are wired
according to the AES 59 (TASCAM ) s t andard.
Due to heat emissi ons, a max imum of four MIC/LINE IN cards are allowed per POWE R CORE. These must be
fitted to even numbered expansions slots only (the t op row). There are no limitat ions when fitti ng the ot her card
types.
All IO cards are optional and must be ordered s eparately. To use your c ards, they m ust be installed into the
fr ame, see Fitting t he IO Cards. When ordering, please use the following part numbers:
POWER CORE User ManualV ersion: V 6.0.0/516/459
4. The Ha rdware
4.3 Accessories
Included
Every POW E R CORE ships with t he following additional items:
·
1 x 2m IEC power cable (country-specific) - to connect AC mains t o t he frame.
·
8 x metal cover plates for the rear expansion sl ots - these will be mounted in the frame.
·
1 x USB l icense dongle (250-5998-000).
·
4 x dust caps for the MADI SFP cages - these will be mounted in the frame.
Note that you will need to install your POWER CORE lic ense onto the USB dongle before connecti ng it t o the
device. The license code for your chosen feature set c an be found on the delivery note.
Optional
The following access ories mus t be ordered separately:
·
1 x ext ernal 12V DC power supply (955/50-80) with 2m IEC power cable (country-specific) - t o c onnect
12V DC power to the frame.
·
1 x USB l icense dongle safety c ap.
·
SFP M odule MADI 1310nm MM LC Dual Fibre (981/60-80) - to connect multi -mode fibre to a MADI port.
·
SFP M odule MADI 1310nm SM LC Dual Fibre (981/60-81) - to connect s i ngle-mode fibre to a MADI port.
Remember to order enough SFP modules for all MADI ports: 4 x front panel + rear panel (2 SFPs per IO card).
POWER CORE User Manual V ersion: V 6.0.0/5 17/459
5. In stallatio n
This c hapter describes how to install t he s y stem.
Topics inc lude:
·
Preparation
·
Fitt ing the IO Cards
·
Fitt ing the MA DI SFP Modules
·
Powering the Device
·
Getting Operational
·
Wiring
·
Synchronisation
5. Installation
POWER CORE User ManualV ersion: V 6.0.0/518/459
5. Installation
Front View
Rear View
Recessed Rack
Adapters
Width
482.6 mm (19”)
Height
44.0 mm (1 RU)
Depth (housin g o n ly)
Depth (inc front plate & connectors)
353 mm
382 mm
Weig h t without IO (cover plates fitted)
4.51 kg
WARNING: DO NOT obst ruct the side ventilation holes as t o do so will prevent efficient cooling.
5.1 Preparation
Unpacking
POW ER CORE is delivered in its own box with all included acc ess ories. If y ou have ordered IO c ards for the rear
expansion slots, SFP modules for the MADI ports or a 12V DC power supply, then these will be delivered
separately.
Please c heck t he c ontents of t he shipping boxes , and in t he event of any t ransport damage, c ontact your local
Lawo repre sentative or email support@lawo.com.
Rack-Mounting
POW ER CORE is designed t o be mounted in a 19-inch rack . P lease install supporting s lide bars t o hold the
weight of the unit, and use the lock ing devices provided. For recessed rack -mounting, us e st andard, third-party,
1RU recess ed rack adapters suc h as t he ones s hown above. When fitting the rack adapters, you must make sure
that there is s ufficient airflow around the device for cooling.
Connectors are located at t he front and rear of the unit. Therefore, when using 19-inch racks with doors please
leave enough roo m for the cables.
If you have IO cards to install, then these should be fitted BEFORE inst alling the unit into t he rack.
Dimensions and Weight
A dimensi on drawing is inc l uded in the Appendices .
Temperature and Coo l i ng
POW ER CORE is equipped with temperature-controlled fans for minimum noise emis sion. V entilation holes are
provided on the left and right. There must be sufficient airflow around the device for cooling.
The c urrent temperature of the devi ce's internal c omponents can be c hecked on the front panel display. The
recommended t olerances c an be found in the data s heet for the POWE R CORE main frame. In particular, the
temperature of the FPGA chip must NOT ex ceed 85° C.
Power Consumption & Electrical Voltage
Please see the 12V DC Power Supply appendix.
POWER CORE User Manual V ersion: V 6.0.0/5 19/459
5. Installation
Warning
The IO cards carry highly sensitive electronic components , and should be handled with care. ALWAYS
observe the following procedures:
·
Discharge yourself before touching an IO card.
·
Wear conductive safety-shoes and grounding wristbands to reduce the risk of electrostatic
discharging.
·
DO NOT bend the cards.
5.2 Fitting the IO Cards
Rear Pa nel Expansion Slots "Empty"
Example Configuration (cards fitted to slots 1, 2, 3, 4, 6 & 8 )
POW ER CORE is delivered with a metal cover plate fitted to each expansion slot. To use your IO cards, they
must be inst alled into t he frame.
Cards c an be installed in any slot posit ion as long as t he frame meets the requirements stated earlier (i.e. a
maximum of 4 MIC/LINE cards per frame, fitt ed to even slots only).
Note that the same procedure is us ed to exchange an IO c ard once the unit is operational. All cards are hotpluggable, and so the exchange can be performed while the devic e is powered.
To remove and replace the screws y ou will need a small flat-blade sc rewdriver (not supplied).
1. Start by unfastening the two diagonally opposite sc rews which hold the card, or cover plate, in place.
2. Gently pull out the c ard from the frame, or remove the cover plate:
Spare cover plates should be stored safely so that they c an be reused if a card is removed.
POWER CORE User ManualV ersion: V 6.0.0/520/459
5. Installation
CAUTION: ALWAYS secure the IO card using the screws provided. This protects t he operator from c ontact
with live parts; protect s t he card from being pulled out unintentionally; and reduces t he emis sion of electromagnetic radiation.
3. Insert t he new card into the slot, and gently s li de it i nto place:
Make sure that the card glides smoothly into the side guide-rails. When fitted correctly , it will loc k into place.
If y ou are hot plugging a card, then after a few seconds, t he c ard will boot. Y ou c an c heck t he s tatus of the new
card from the Web UI (go to the System -> States page).
4. Now fast en the two screws t o fix the card in place.
5. When you have fitted all t he IO cards for your sys tem, check that all c ards are screwed into the frame
and that any empty s l ots are closed with metal cover plates.
The installat i on is now complete, and you c an wire your audio devices to the IO card connectors.
If y ou have inst alled a MADI card, then you will need fit a Lawo-certified SFP module t o each port. see Fit ting the
MADI SFP Modules.
POWER CORE User Manual V ersion: V 6.0.0/5 21/459
5. Installation
Warning
Before removal, please unlock SFP modules to avoid mechanical damage to the slots.
If a module is removed, please refit the port's dust cap to protect the internal components.
You must use the correct fibre type for your remote devic e. Us ing the wrong fibre ty pe or exceeding the
maximum optical input power can result in malfunction of, or damage to, the optical devic e.
5.3 Fitting the MADI SFP Modules
To use the MADI ports on the front panel, or an optional rear panel IO card, you m ust fit a Lawo-certified S FP
module. Different SFPs are available to support multi-mode and single-mode fibre. These are listed in
Accessories. Note that the SFPs are NOT inc luded and mus t be ordered separately . You will need one SFP for
each port.
The SFP modules are hot-pluggable, and so t hey can be fi t t ed or exchanged while the device is powered.
1. Remove the dust caps from both the port and SFP module.
Store these carefully so that they can be replaced if a module is removed.
2. Push the SFP module into the rectangular slot:
3. Press gently and firmly until the module lock s into positi on.
POWER CORE User ManualV ersion: V 6.0.0/522/459
5. Installation
Plea se note : i f you load a new configuration, or perform a firmware update, then POWER CORE will cold
start. A cold start ignores the warm start data, and resets all internal logic s t ates and audio DSP parameters
to the default values st ored in the configuration. If this is t he first t im e y ou have powered the device "out of the
box", then there will be no configuration so see Getting Operational for the next s teps.
5.4 Powering the Device
Front View
Rear View
1. POWER CORE has no on/off switch but starts automatically when power is applied:
·
While t he device is booting you will see the boot-up progress on the front panel dis play and t he STATUS
LED lights in white (steady state).
·
As soon as boot-up is complete, the display will show the Welcome page and the STATUS LED begins
to blink at regular intervals; the LED color reflects the sync status.
·
The device is now ready for operation - this tak es approximately 20 sec onds from power on.
If the STATUS LED does not st art to blink, t hen the device has an internal problem. Please t ry a restart as a first
step.
At the end of boot-up process, POW ER CORE loads it s warm start data. This is the s tate of all s ettings at t he
last shut down. It means t hat when you turn on, you will get back to wherever you were* at the last power off.
* Note that the last known PTP Master/S lave mode may not be reinstat ed if P OWE R CORE is s et t o operate as
PTP Slave only.
2. Once POWER CORE has booted s uccess fully , y ou can c heck the current firmware version and other
statuses fr o m the front panel display or by opening a Web UI connection.
POWER CORE User Manual V ersion: V 6.0.0/5 23/459
5.5 Setting the IP A ddress
By default, POWER CORE ships with the following IP settings for the ETHERNET 1 port:
·
IP Address = 192.168.101.240
·
Subnet Mask = 255.255.255.0
·
Gateway = 0.0. 0.0
You can also c heck t he current IP Address from the front panel display by turning the rotary control until you
see the Welcome page:
Front P anel: Welcome Page
If you are inst alling POW ER CORE within a network of devices, t hen you may need to change its IP Address,
Subnet Mask and Gateway. This c an be performed using the Web UI as follows.
1. Open a Web UI connection to POWER CORE in the usual manner.
2. Select System -> Network Devices - you will see the current IP settings assigned to the three
Ethernet ports. The top entry (dwc0) corresponds to front-panel port 1 and is used for sy stem administration
and control.
Any of the fields marked with an asterisk (*) can be edited. You will need to enter the Administrator password in
order to modify the parameters.
3. T o chan ge the IP Address, click in the IP Addre ss field and ty pe in the new IP.
4. T hen click on Apply - the new setting will be applied and so you will loose y our browser connection.
5. To check that the new IP has been taken, re-open the Web UI connection (by typing the new IP address
into the URL field), or refreshing the front panel display.
The subnet mask (Network Mask) and Gateway c an be edited in a simil ar manner. Note that if y ou edit these
sett ings, then you may need to also edit t he IP set tings of your s ervic e computer's Network Interface Card in
order to re-est ablis h t he W eb UI connect ion.
5. Installation
POWER CORE User ManualV ersion: V 6.0.0/524/459
5. Installation
5.6 Getting Operational
To complete the inst allation, please work through the following s t eps. In t he first ins tance, you should c heck and
update the device firmware. The rest of the steps can be performed in any order. For more details on each
procedure, please clic k on the relevant links.
1. Update the device firmware.
T he latest firmware is av ailab le from the Download-Center at www.lawo.com (after Login).
Download the release onto a servic e computer, and then use t he firmware update tool (SoP Ex plorer) t o check
and update all sy s tem components.
2. Transfer a configuration onto the device.
To get the s y st em working, you will need to transfer a suit able configuration using the ON-AIR Desi gne r. Start
the software and open the project . Then t ransfer the configuration to the devi ce. Y ou will find full details on t hese
procedures in the separate "ON-AIR DESIGNER User Guide".
Once the transfer is c omplete, P OWER CORE will cold st art and load the configuration at t he end of boot-up.
3. Co mplete the system wiring.
4. Co nn ect and configure the sync reference.
5. Install the licens e for your feature set using the online Lawo licensing Web Portal.
6. Check and, if necessary, change the IP address of the POWER CORE control syst em using the W eb UI.
7. If your sy st em has been in transit or st orage for more t han 3 days, then reset t he Date and Tim e using
Sop Explorer.
POWER CORE User Manual V ersion: V 6.0.0/5 25/459
5. Installation
WARNING: POWER CORE MUST be connected to t he mains us ing t he power cable supplied with the
system.
5.7 Wiring
The topics in this sect ion describe all possible c onnect ions to and from the P OWER CORE. Depending on the
application, y ou m ay need only s ome of t hese. Please refer t o Controls, Indicators & Connectors for connector
locations. To boot the s y stem, t he only es s ential connection is power.
5.7.1 Power
Every device c omes wit h dual power feeds: A C and DC.
Redundant Power
If both power inputs are connected, then AC provides the main and DC the redundant power supply.
AC Input
The frame includes an integrated wide-ranging AC power supply, and is delivered with a 2m IEC power cable
(country-specific).
Using the IEC cable provided:
1. Conn e ct your mains to the 100-240V AC input on the rear panel.
DC Input
To use the DC input, you will need the ext ernal 12V DC power supply; this is optional and must be ordered
separately.
12V DC Po wer Supply (9 55/50 -80)
For dimensions, weig ht and electrical specification, see the 12V DC Power Supply appendix.
T he PSU is deliv ered with its own IEC power cable (country-s pecific).
To connect DC power to the frame:
1. Connect the 12V DC power supp ly to the DC IN connect or on the rear panel.
2. Using the IEC cable provided, connect your AC mains to the PSU.
POWER CORE User ManualV ersion: V 6.0.0/526/459
5. Installation
Although operator protection is guaranteed, it is best to establish an additional ground for EMC reasons. A
grou n d in g screw is provided below the DC IN connector on the rear of t he frame.
1. Using a M4x8 screw, fasten the grounding cable to the CASE bolt.
2. If installing POWER CORE with a control surface, then establish a direct connection to the control
surfa ce modules using the CAN bus.
WARNING: POWER CORE must be on the same potential as all other system devices.
For Scandinavian countries, ALWAYS us e a grounded mains connection, to prevent t he device from being
grounded through Ethernet or other signal connections.
The CAN bus uses only one of four available pairs of wires in the CAT-5 cable. See the Connector Pin-Out.
5.7.2 Grounding
Grounding of Audio Interfaces
For compliance with AES 3, digit al int erfaces should be connected to a field ground.
For microphones, the ground from POWER CORE should connect directly to the microphone via the cable
shielding, otherwise phantom power cannot be t ransferred. Take care that the shielding does not connect t o the
field ground, to prevent interference and loss of signal quality.
5.7.3 CAN Bus
If P OWER CORE is inst alled with a control surface, then the CAN bus is us ed to c onnect the control s urfac e
frames. If there are no control surfac e c omponents, t hen this connect or is unused.
All c ontrol surface components should be connected to t he CAN bus in a daisy -chain fashion, s tarting from t he
POW E R CORE. For specific ins t ructions, please refer to your control surface manual.
Connections mus t be made using a st andard (straight 1:1) network cable: STP-CAT 5 c able with RJ45 connectors
on both ends. Note t hat all connections MUST be point-to-point; a s witch or hub is not allowed. The control
surface c an be hot-plugged via CAN, and so the cabling can be connected while the frames are powered.
5.7.4 RS-422
The RS-422 serial port can connect remote dev ices which do not supp o r t TCP/IP Ethern e t.
For example, to allow a legacy Radio Automation Sy st em or DAW running the Mack ie HUI protocol t o remotely
control POW E R CORE (via a Serial-to-MIDI connection).
T he remote device must connect to the RS 422 port using a RS-422 9-pin D-type cable with RJ45 connector. See
the Connect or Pin-Out for details. The maximum cable length is 10m.
POWER CORE User Manual V ersion: V 6.0.0/5 27/459
5.7.5 ETHERNET 1
The ETHERNET 1 port can be used to connect devic es to the P OWE R CORE c ontrol sy st em. For example, to
remotely control POWER CORE via TCP/IP; connect other networked products ; or update the sy stem's firmware
or configuration.
The connection can be made either directly from a single devic e, or via a network switc h to allow mult iple device
connections. For example, you could connect one or more VisTool PCs or Ember+ devices.
Netw ork Re qui rements
If c onnecti ng vi a a network, then this can be shared with other devic es , s uc h as i n the regular "house network" of
a ty pical broadcast facility. Routers are permitted as long as t he minimum requirements below are met. By
using routers, or sim ilar devices, the lat ency of the communic ation will increase. The network MUST meet or
exceed the following requirements:
·
At l east 100MBit/s
·
Full Duplex
Cable Type
For a direct connection, you will need a crossed network c able. For connection via a network switch, use a
straight (1:1) network cable. The cable should be STP-CAT 5 with RJ45 connectors.
When using a c rossed network cable (direct connection), the “Use of a Proxy S erver” browser option m ust be
deactivat ed. Ot herwise acces s is prevented by looking for a “Proxy”.
Ma king the Connection
1. Connect your remote device, either directly or via a network switch, to the ETHERNET 1 port of P OW ER
CORE.
2. To establish communication, configure the TCP/IP settings on your remote device - for example, if
connecting a Vis Tool PC, open the network sett ings for its Network Interface Card.
·
The IP Addre ss must be unique, and set within the same range as that of the Lawo control sys t em. The
def au lt IP addr ess of POWER COR E = 192.168.101.240
·
The Subnet Mask should be identic al to that of the system. The default Subnet Mask is 255.255.255.0
For example, if your sys t em is using the factory-default IP sett ings , t hen you could s et your devic e's IP address
to 192.168.101.241
If c onnect ing via a larger network, y ou may need to consult y our network administrator t o gain ac cess t o the
Lawo network from your device.
3. The simplest way to test the network communication is to open the W eb UI.
If you are having problems establishing a network c onnection please see the trouble-shooting tips.
5. Installation
POWER CORE User ManualV ersion: V 6.0.0/528/459
5. Installation
The ETHERNET 2 and ETH ER NET 3 ports can be used to st ream audio to and from an IP network us ing AE S 67
or RAVENNA.
The total Audio over IP c apacity of one P OWER CORE is up to 256 IO c hannels depending on t he lic ense
purchased. This c an be s plit into up to 128 streams, where each s tream c an be mono, s t ereo or multi-channel.
For each stream you can decide whether it will be transmitted or received via the ETHERNET 2 or ETHERNET 3
port. To achieve redundant st reaming, you must use both interfaces.
Netw ork Re qui rements
T he IP networ k must meet the qualifying requirements of an AE S 67/RAVENNA network. For details, please refer
to the separate "RAVENNA Networking Guide".
Ma king the Connection
Using a straight (1:1) STP-CAT 5 network cable with RJ45 connectors:
1. Connect your A ES 67/RAVE NNA network t o t he ETHERNET 2 and/or ETHERNET 3 ports of POW ER
CORE.
Configuring the AES67/RAVENNA Ne twork & Strea ms
See Sett i ng Up RAVENNA/AE S 67 for more details.
T he fou r MADI ports on t he front panel, and any optional MADI on rear IO cards, can be used t o c onnect m ultichannel digital audio to an external device.
Each port provides 64 bi-directional MADI (AES10) channels. Dual-redundant ports, and the number of
transmitt ed c hannels (56 or 64), can be defined by t he ON-AIR Designer.
T o use the MADI ports, you must fit a Lawo-certified SFP module. The SFP determines t he c onnector and fibre
type: options include multi-mode and single-mode fibre . See Accessories for details.
In the configuration, the following settings are defined by the Sy stem -> Definition -> Parm = MADI branch of
the 'Tree Defi nit ion':
·
Odd/even MADI ports may be configured as independent ports , or as redundant pairs (1/2, 3/4).
·
Each MA DI port c an be set to transmit 56 or 64 slots.
WCLK IN
POW E R CORE can sync t o external wordcloc k by c onnecting the clock si gnal t o W CLK IN and defining "sy nc
to wordcloc k" in the s ystem c onfiguration.
WCLK OUT
Wordclock out always provides an output of the current sy stem reference: P TP, WCLK IN, MADI or internal
clock.
In both c ases, connections are made using standard 75 ohm BNC connectors. The maximum cable length
depends on the equipment y ou are connecting to.
See Synchronisation for more details.
5.7.6 ETHERNET 2 & 3 (AES67/RAVENNA)
5.7.7 MADI
5.7.8 WCLK IN & OUT
POWER CORE User Manual V ersion: V 6.0.0/5 29/459
5. Installation
5.7.9 GPIO
The GPIO connect or provides remote control of POWER CORE from c ontac t c l os ures:
·
GPI = 8 x optoc ouplers (3-36 VDC / 8mA @ 36V)
·
GPO = 8 x silent CMOS relays (50V AD/DC / 0.5A A C; 1. 0A DC).
T h e connector is a 37-pin D-type. See the Connector Pin-Out for details.
5.7.10 IO Cards
All rear panel IO cards, except MADI, break out on DB-25 connectors that are wired acc ording to the AE S59
(T ASCAM) standar d . See the Connector Pin-Outs for details .
POWER CORE User ManualV ersion: V 6.0.0/530/459
5. Installation
Plea se note : i f POW E R CORE has been synchronized once to a PTP master, then it will NOT automatic ally
switc h t o another sync source but try to re-establish it s c onnecti on to t he ext ernal PTP master. W hile doing
this, it becomes P TP mast er itself, and uses t he pre-aligned internal cloc k as t he reference.
In the configuration, the external sync options are enabled (or disabled) in the “Sys tem -> Definition ->
Parameter = Sync ” branch of the ‘Tree Definit ion’. From here you can also set the internal sync generator to
run at eit her 48kHz or 44.1kHz.
The sync status can be checked from the front panel by looking at the STATUS LED:
Front View
T he LED should be blinki ng at regular intervals ; t he color then indicates:
·
Blue, blinking = s ynchronized to PTP master.
·
Yellow, blink ing = attempting to sy nc to PTP master.
·
Green, blink ing = s ynchronized to Wordclock .
·
Magenta, blinking = synchronized to MADI.
·
Red, blink ing = sync hronized to internal clock .
If the LED is not blinking, then there could be a problem with the system. See the STATUS LED for full details.
5.8 Synchronisation
Sync Reference Options
The sync reference options are:
·
PTP - from the AES67/RAV E NNA streaming network.
·
Wordclock – connected to WCLK IN on the front panel.
·
MADI – incoming MADI from front panel port 1 (or port 2 if redundancy is c onfigured and port 2 is act ive).
Note that other MADI ports c annot be used for sync hronisation.
·
Internal Clo ck – 48kHz or 44.1kHz.
Each of the external sync options li sted above can be independently enabled or disabled. If dis abled, POW ER
CORE will ignore the s ync source even if it receives a valid s ignal. It is possi ble to enable one or multiple s ync
options f or the device.
If m ult iple ext ernal sync options are enabled, then it is possible to choose a priority order for PTP, Wordcloc k and
MADI. The device will then always use t he highest prioritized s y nc s ource. If none are present, t hen the device will
default back to internal c lock . The s wi tching between the enabled sy nc options and internal cloc k is handled
automatically.
By dis abling all ext ernal sync options, POW E R CORE can act as a s y nc mast er and dis t ribute it s internal c lock
via PTP, Wordclock or MADI to other devices.
Checking the Sync Status
POWER CORE User Manual V ersion: V 6.0.0/5 31/459
5. Installation
Alternativ e ly, you can open a W eb UI connection and select the System -> States page:
On the right, you will see each of the Sync sources and whether they are Enabled (in the confi guration), P resent
(a valid signal has been detect ed), and Act i ve. The color coding indicates:
·
Blue = sync s ource is enabled, present and act ive.
·
Green = sync source is enabled and present, but not currently ac tive.
·
Red = sync source is enabled but not present.
The Prio S eque nce box shows the priori ty of the ext ernal sync s ources as defined by the c onfiguration - in our
example, PTP, Wordclock and then MADI.
Sync Output
The front panel W CLK OUT connector always provides an output of the current s y stem referenc e.
POWER CORE User ManualV ersion: V 6.0.0/532/459
6. Licensing
6. Li censing
This c hapter describes t he lic ensed feature sets and how t o work with the lic ensing s ystem.
Topics inc lude:
·
Licensed Feature Sets
·
Working with the License S yst em
POWER CORE User Manual V ersion: V 6.0.0/5 33/459
6. Licensing
6.1 Licensed Feature Sets
POW ER CORE must be purchased with a license to "unlock " the s ys tem resources. Three different packages
are available: "Super Audio Node", "Radio Console L" and "Radio Console XL".
Note that the naming is purely a guide, as one of the Radio Console packages could be suitable for a s t and-alone
sy stem (if a large DSP engine with remote control is required).
The available pack ages are s ummarised below. Please see the POWER CORE License Chart for specific
details.
Super Audio Node (SAN)
This is the smalles t pack age and is designed for POWER COREs running as a s t and-alone devi c e - for example,
as an intelligent AES67 IO node (with low latency monitoring); a mid-size signal router; or a small intercom
matrix.
Radio Console L (RCL)
This package is larger than "Super Audio Node" and is designed for a standard mid-size radio studio console.
If us ed st and-alone, it is s uited to a mid-siz e networkable DSP, s ignal supervisor and router; or mi d-siz e i ntercom
matrix.
Radio Console XL (XL)
This is the largest pack age and is designed for a large multi -operator radio st udio c onsole. In addition, it provides
5.1 mixi ng and processing suitable for a TV production console.
If used stand-alone, it offers ex tensive c apabilities as large-s c ale networkable DSP, s ignal s upervisor and router;
or intercom matrix.
6.1.1 Signal Processing Resources
Use the following as a guide to the "Audio Processing" entries i n the POWE R CORE License Chart.
·
Pa rall el I nput source s - are fully-featured input c hannels with input gain, s ignal presence indicator,
direct out, ins ert, fader, aux send (with pre/post) swit c hing, pan/balance, Aut oGain for each mic i nput.
·
Summ ing busse s - configurable as P rogram, Record, A ux, Group, M ix-Minus (clean feed) or General
Purpose. A full DSP channel with EQ, Dynamics and Delay funct ions may be applied to a number of
buses (specified under Bus DSP).
·
Equali zer (EQ) - with three fully-parametric bands plus two semi-parametric bands that can also be shelf,
high-pass, or low-pass filters.
·
Dynami cs suite - with gate, expander, compressor and limiter.
·
AutoMix and/or De-Essing - a number of AutoMix and/or De-Essing instances are available for
application to any input source.
·
AutoMix grou ps - a number of individual AutoMix groups available allow creation of mult iple i ndependent
mixes.
·
Loudne ss Meteri ng - c onforming to EB U R128 may be metered on-screen for sources and all buses.
Note that resource numbers are given as the mono equivalent. In all packages, sources and buses can be
grouped into stereo bundles. To group sources or busses in 5.1 bundles, y ou will need "Radio Console XL".
POWER CORE User ManualV ersion: V 6.0.0/534/459
6. Licensing
Category
Description
SUPER
A UDIO NODE
RADIO
CONSOLE L
RADIO
CONSOLE XL
A ll listed numbers below are mono equivalent
AUDIO
INTERFACING
FRONT MADI channels *
4x64/64
4x64/64
4x64/64
A ES67/RA VENNA IO channels *
128/128
128/128
256/256
A ES67/RA VENNA streams
64
64
128
A ES67/RA VENNA redundancy
(SM T PE 2022-7 and LACP)
YES
YES
YES
Physical GPIO support
NO
YES
YES
M aximum number of expansion
cards
888
AUDIO
PROCESSING
Configurable fader assignable
resources
32
96
254
Parallel Mix Inputs with DSP
(EQ+DY N+LIM+LOUDNESS) *
164896
A utoMix /DeEsser units *
81632
A utoMix Groups
124
Busses (no processing) *
204080
Bus processing DSP blocks
(EQ / DYN / LIM) *
01632
PFL Busses12
5
V CA Groups01
8
5.1 Mixing and Processing
NO
NO
YES
Utility Tool MiniMix er
646464
Patchable Meters (PPM &
LOUDNESS) / Silence Detects *
128
128
256
CONTROL
KSC PANEL support
YES
YES
YES
V isTool control
YES
YES
YES
NETWORKING
GPIO Tunnel over audio channels
646464
GPIO NET elements
404040
Ex ternal M atrix Remote Control
(KPF/ EMBER+ / NTP-DOT)
YES
YES
YES
A utomation System Control Interface
(RAS)
NO
YES
YES
M ACKIE HUI Support
NO
NO
YES
Ember+ Provider
115
Ember+ Consumer
0415
Routing Matrix *
1728 x 1728
1728 x 1728
1920 x 1920
A UDIO SIGNA L
DISTRIBUTION
Intercom M atrix – Number of clients
163878
6.1.2 Power Core License Chart
POWER CORE User Manual V ersion: V 6.0.0/5 35/459
6. Licensing
The dongle is a specially-configured USB memory stick which can be purchased from either Lawo or WIBU
systems. If you lose it , then please order another!
T hese instructions describe CodeM eter Runtime Version 6.40b.
A useful FAQ section (from WIBU systems) is available from: www.wibu.com/faq-codemeter
2. Ch e ck the installation by looking in t he W i ndows tas k bar where you should see the followi ng ic on.
CodeMeter Runtime Cm container
This s hows that a Cm container (for local license st orage) has been installed. Note that this c ontainer will not be
used for POWER CORE, but c an be used to st ore the licenses for other Lawo software products.
6.2 W orking with the License System
Lawo software licenses are managed by the CodeMeter licensing system from WIBU systems.
Your license must be installed onto a USB memory s tick which is c onnected to the front panel DONGLE port.
Note that you can upgrade or downgrade the DS P resources available to your sys t em, by ins talli ng a new l ic ense
and loading a suitable system c onfiguration.
6.2.1 Preparing the USB License Dongle
POW ER CORE ships with a USB memory s tic k which can be used as t he dongle once y ou have ac tivated y our
license. Note that t he memory st ick is delivered without any lic enses inst alled, and so y ou will need to redeem
your license c ode (using one of the activation methods) before fitting the dongle.
To perform the act i vation, y ou will need:
·
A PC with an internet connection and USB port. If your PC does not have an internet connection, t hen t he
offline act i vation method can be used.
·
The USB memory stick supplied with y our sy s tem.
·
The license code for your feature set. This c an be found on the delivery note s hipped with t he sy s tem. It
takes t he form of a 25-digit tic k et number such as the one shown below.
License Code Example
Once activated, it is s trongly recommended t hat y ou back up y our licenses (using the CodeMeter WebAdmin
portal). This will allow you to rest ore a license if the original dongle is lost or damaged.
6.2.2 Installing CodeMeter Runtime
In order to act ivate a lic ense, y our PC mus t be inst alled with Code Me ter Runtim e (a software tool from WIBU
systems).
You can download the latest rele a se from: https://www.wibu.com/uk/downloads-user-software.html.
1. Run the installer following the on-screen instructions.
POWER CORE User ManualV ersion: V 6.0.0/536/459
6. Licensing
To use this m ethod, y our PC must have an internet connection and be running the latest release of CodeMeter
Runtime. If inst alling onto a dongle, t hen this should also be connected to t he PC's USB port.
1. Open the Lawo licensing web portal by copying the following URL into your web browser:
https://licenseportal.lawo.com
2. Copy y our lic ense tick et number - this is the 25-digit number code - i nto t he Ticket field and select
Next:
3. The WebDepot searches f or and displays your licenses - select Activate Li censes to continue:
4. At t he next page, select t he storage method for your license - note that this c annot be altered later. For
POWER CORE, choose the CmDongle option.
6.2.3 Acti vat i ng a License Online
POWER CORE User Manual V ersion: V 6.0.0/5 37/459
6. Licensing
5. At t he next page, select the licenses you wish to act ivate and the CmContainer t o be us ed for the
license s torage:
You c an s t ore multi ple l ic enses in t he s ame c ontainer. If no Cm containers are available, then you will see an
option to "Ge t CmContai ner a u tomatica l l y".
6. Click on Activate S elected Li ce n ses Now and wait for a few s econds - a confirmation pop-up appears
once the activation is s uc cessful:
7. After selecting OK, a s ummary appears:
8. You can now clos e y our web browser and install y our USB license dongle.
POWER CORE User ManualV ersion: V 6.0.0/538/459
6. Licensing
1. Connect y our WIBU sy stems USB m emory s tick t o t he DONGLE port on the front panel:
Note that an optional safety cap can be fitted to prevent accidental removal of the dongle. If fitt ed, you will need a
T10 star tool to remove or fit the cap.
All lic ensed features should now be available. If a valid lic ense is not found, then t he alarm will sound every few
seconds!
6.2.4 Installing the License Dongle
POWER CORE User Manual V ersion: V 6.0.0/5 39/459
6. Licensing
6.2.5 Acti vat i ng a License Of f l i ne
If y our PC has no internet acc ess, t hen you can activate a s oft ware lic ense offline. This method i nvolves three
stages:
·
Crea te a l ice nse re q ue st file - for the Cm st orage container, and copy the file onto a c omputer with
internet access.
·
Activa te the li ce nse - using the 'Lawo License' web portal, and copy t he lic ense update file back t o t he
original computer.
·
Import the licens e update file - to the Cm storage container.
Creatin g the License Request File
On the computer you wish to lic ense:
1. Ope n the 'CodeMeter Control Center' (by cli ck ing on the Cm t ask bar icon), and selec t the c ontainer y ou
wish to use for the license stora ge.
2. If the container is empty , s elect Activate Lice nse. Or, if the container already holds an active licens e,
select Lice n se Update. This starts the 'CodeMeter Field Activation Service (CmFAS ) assist ant':
3. Select Next: and then Create l icense re quest:
POWER CORE User ManualV ersion: V 6.0.0/540/459
6. Licensing
Select Add license of a new producer
Enter the Lawo FirmCode = 102037
At this stage, there are two additional steps (to add the correct firmcode) if you have selected a CmStick
container. Enter the following Lawo FirmCode to create the lic ense request file:
4. Select Next, and using Windows Explorer, enter a file path for the license request file. Choose
somewhere easy to find, such as the Desktop. Then select Commit to c reate the request file:
5. Select Finish and copy t he request file onto a c omputer with internet acces s. Y ou will need both the
license request file and the 25-digit ticket number (received with your license purchase).
POWER CORE User Manual V ersion: V 6.0.0/5 41/459
6. Licensing
Activating the License
1. On a computer with internet access, follow the first four steps from the online activation method:
·
Open the 'Lawo License' web br owser page at https://licenseportal.lawo.com.
·
Copy your license ticket number - this is the 25 number code - into the Ticket field and select Next.
·
When your license is displayed, select Activa te Lice nses to c ontinue.
·
Select t he s t orage method for your licens e - either USB dongle or single computer.
2. At the Ava i l able Licenses page, s elect Offline l i cense tra nsfer to continue:
POWER CORE User ManualV ersion: V 6.0.0/542/459
6. Licensing
3. On the next page, select the license(s) y ou wish to act ivate, s elect Browse... and, using Windows
Explorer, choose the request file (created earlier):
4. T hen select Uploa d Requ e st And Continue Now - t he license request is process ed and, if suc c ess ful,
you will have the option to Download the update:
5. Select Download License Upda te Fil e Now and, when prompted, choose t he Save file option - the file
is downloaded:
6. Copy the Lic ense Update file back t o t he original PC.
POWER CORE User Manual V ersion: V 6.0.0/5 43/459
6. Licensing
Importing the License Update
1. On the original computer re-open the 'CodeMeter Control Center' and select the Cm container for the
license update. Note t hat t his must be the same c ontainer as the one selected earlier (during the License
Request).
2. Select L icense Update and follow the instructions given by the 'CmFAS Ass istant' - when prompted,
select Import License update and choose the update file (downloaded from the License portal):
3. Select Commit to acti on the update - the license is act ivated and you can c los e t he 'CodeMeter Control
Center'.
4. You can now inst all your USB l icense dongle.
POWER CORE User ManualV ersion: V 6.0.0/544/459
6. Licensing
Local Computer Container (LAWO AG)
USB Dongle Container (CmStick)
A single Cm container can contain multiple licenses - simply select the same container during the activation
process.
WebAdmin Content Cm Container
WebAdmin Backup/Restore
6.2.6 The CodeMeter Control Center
This topic briefly des cribes t he 'CodeMeter Control Center' which c an be used t o manage the license containers
and perform a backup or rest ore.
1. Click on the W indows t askbar Cm i con t o open the 'CodeMeter Control Center' - note that t he icon may
be hidden from view (depending on your task bar configuration), and may vary in c olour:
The 'CodeMeter Control Center' shows all the Cm containers which can be used for license storage.
Note that a new local c omputer container is c reated each t ime y ou run t he Code Me ter Runtim e install wizard.
Therefore, i f you have installed multiple Lawo products or soft ware versions, you will see several LAWO AG
containers. In addition, i f a USB dongle is connected, y ou will s ee a container labelled CmStick.
The Serial numbers identify each container. The icon colours indicate: green = license activated; grey =
container is empty ; red = license deactivated.
2. Select WebAdmin (bottom right) to open the W ebAdmin portal in your default browser. The portal has
many functi ons including li cense interrogation, and back up/restore functions for licenses st ored on a CmStick
(USB Dongle):
For further information, you should refer to the CodeM eter Runtim e documentation from W IBU systems.
POWER CORE User Manual V ersion: V 6.0.0/5 45/459
7. Configur i ng POWER CORE
7. Confi guring POWER CORE
This chapter desc ribes how to c onfigure POW ER CORE. You should be famil iar with the ON-AIR Designer
configuration tool. If not, please refer to the separate "ON-AIR Designer User Guide".
Topics inc lude:
·
Starting a Confi guration
·
Creating a New Configuration
·
Opening an Exis ting Configuration
·
Loading a Project from the Unit
·
Selecti ng a Different License Pac kage
·
Saving the Project
·
Transferring Configuration Data to the Unit
POWER CORE User ManualV ersion: V 6.0.0/546/459
7. Configur i ng POWER CORE
7.1 Starting a Configuration
The simples t way to cus tomis e a sy st em is to m odify the exis ting configuration or a st andard template. To do
this, y ou will need a copy of the latest c onfiguration or template as a .db3 project file. You can then use the ON-
AIR Designer software to open, edit and save the file; and transfer the modified configuration back t o t he syst em.
Note that a copy of the project file can be stored on the POWER CORE device. In this instance, you can
download a copy to your computer using 'Load Project from unit'.
If y ou do not have acc es s t o an exis ting project, then use 'File -> New' to create a new configuration project.
If you plan to install VisTool(s), it is a good idea t o c reate the V isTool and sys t em c onfigurations in parallel, and
check the results st ep-by-step. Please refer to the separate " Vis Tool MK2 User Guide" for more details on usi ng
Vis Tool Edit to edit t he VisTool project .
POWER CORE User Manual V ersion: V 6.0.0/5 47/459
7. Configur i ng POWER CORE
7.2 Creating a N ew Configuration
To create a new project:
1. Select File -> New from the top menu bar, or click on the Toolbar icon, or use the k eyboard shortc ut
(CTRL + N) - the 'New Project W i z ard' opens:
2. Select the prod uct ruby and click on Next - the 'Frame select ion' window opens:
ruby/POWER CORE - Frame selection
The four 'Frame' areas define the Sys tem Core, Surface, Panels and Screen:
·
System Core = the DSP Core, available in three lic ensed pack ages t hat affect t he number of resources.
·
Surface = the maxi mum control s urface siz e, where t he numbers in brackets indicate t he number of
Fader Modules + Central Module + Central Modules running in monitor mode.
·
Panels = the maximum number of Key Panels c onnected to t he s y stem.
·
Screen is always set to Screen functions to support VisTool funct ions.
For the Syste m Core , please s elect the licensed pack age which has been purchased.
For the Surface, s elect t he max imum c onfiguration required. For ex ample, t he ruby 16 Fader (4+1) opti on can
be used for a 4-, 8-, 12- or 16-fader surfac e with a single Central Module. If more faders are fitt ed, or you have
more than one Central Module (running in monitor mode), then a larger Surface option must be used.
Note that t he s pecificat ion c an be c hanged later (via Frame -> Change Frame). S o, for example, i f you upgrade
the lic ensed package for your DSP Core, you can change the Syste m Core frame to unlock the additional
resources.
POWER CORE User ManualV ersion: V 6.0.0/548/459
7. Configur i ng POWER CORE
5. Once you have specified the 'Frame' , click on Finish.
The soft ware c reates the new configuration and a number of windows will open. In our example, we can s ee the
'Project' window (on the left), plus the 'Sys t em Core' (in the central working area):
Note that it may tak e a few seconds to build the new project. During this time the status is shown in the
"progr ess" bar (be low Console in the 'Project' window).
POWER CORE User Manual V ersion: V 6.0.0/5 49/459
7. Configur i ng POWER CORE
If y ou s ee an error stati ng that t he project is already open then navigate to the project folder (using Windows
Explorer) and delete any .txt files. Then try opening the project again.
On POWE R CORE and Nova17, a copy of the project file can be stored on the DSP Core. To download it to
your computer, use Load Project from unit.
7.3 Opening an Existing Confi guration
To open an existing project s tored on your computer:
1. Select File -> Open from t he t op menu bar, or clic k on the Toolbar icon, or use the keyboard
shortcut (CTRL + O).
2. Select your project file and click on Open.
If y ou c annot s ee t he file, check the File s of type option at the bottom of the dialog box; you may need to
change this to s ee the c orrect file ty pe (.db3 or .mdb).
The project opens, wit h the s ame workspace layout and docking options as at the last file save:
If the configuration was created us ing a different definition version, then y ou may be ask ed if y ou wish t o c onvert
the project. Note that it may tak e a few s econds to open t he project. During this ti me t he status is s hown in the
"progr ess" bar (be low Console in the 'Project' window).
POWER CORE User ManualV ersion: V 6.0.0/550/459
7. Configur i ng POWER CORE
7.4 Loading a Project from the Unit
This function is available on POW ER CORE and Nova17 only. It allows you to transfer a c opy of the ON-AIR
Designer project file to the DSP Core, so that it m ay be loaded to another computer at a later date.
The Sa ve Proje ct to Unit option appears in the Transfer -> Config to unit confirmation box (if supported by your
sy stem). If you ti c k the option, then a compress ed version of the project file (.db3 or .mdb) will be transferred to
the unit.
To download a project which has been previous ly transferred:
1. Select File -> Load Proj ect from unit:
If t his option is greyed out, t hen there is no network c ommunic at ion between your PC and the control system.
2. A pop-up appears - enter t he IP Address of the c ontrol sy st em, and press t he TAB k ey t o est ablish the
connection.
3. T hen select OK - the project file is downloaded from the unit.
4. To save the project, use Save As and enter an appropriate filename in the usual manner.
POWER CORE User Manual V ersion: V 6.0.0/5 51/459
7. Configur i ng POWER CORE
7.5 Selecting a Different License Package
The Frame selection can be used to change the maximum speci ficati on of the sys tem.
1. Select Frame -> change fra me to open the dialogue box:
Frame selection wind ow
Here you c an specify each of the system components: S ystem Core, Surface, Panels or Screen as desc ribed
earlier.
2. If you c hange an option, c lic k on OK - the s oft ware now loads the hardware configuration for the new
frames.
Note that it may take a few sec onds t o load t he data. During this time the status is shown in t he "progress " bar
(below Console i n t he 'Project' window).
POWER CORE User ManualV ersion: V 6.0.0/552/459
7. Configur i ng POWER CORE
7.6 Saving the Project
At regular intervals you should s ave the project, and also use " save as " to keep a copy of the project at different
revision stages. This will allow you to test t he configuration and revert t o an earlier versi on if necessary.
Ø
Fil e -> Save
Select File -> Save from the top menu bar, or click on the Toolbar icon, or use the keyboard s hortcut (CTRL
+ S).
This overwrites t he existing project (as spec ified in the "File" field in ‘Project’ window):
Ø
Fil e -> Save As
1. Select File -> Save As from the top menu bar, or use the keyboard shortcut (CTRL + SHIFT + S) - the
"Save" dialogue box opens:
2. Choose a new folder locati on, enter a different file name, or s elect a different file t y pe (using the Fi le s of
type option at the bottom of the dialog box).
3. T he n click on Save t o s ave the project:
The default file ty pe is .db3 unless you specify otherwise. See Backwards Compatibility.
Note that a project containing substitutions cannot be saved as a .mdb file.
POWER CORE User Manual V ersion: V 6.0.0/5 53/459
7. Configur i ng POWER CORE
7.7 Transferring Configuration Data to the U nit
This function transfers the configuration parameters to the selec t ed unit.
1. Open the project you wish to t ransfer.
2. In the 'Project' window, select the unit from the Units field (if configuring multiple units).
3. T he n tick the Online checkbox and make sure that you have a valid network connection to the syst em.
If not, then edit the IP-Address field to matc h that of the Lawo c ontrol s ys tem - t he t raffic li ght s hould turn green
(as shown below).
If you need to change t he unit's IP address, then us e Transfer -> S etup t o unit (all products except POWER
CORE) or the Web UI (POWER CORE).
4. If you have made any changes to the c onfiguration, then t hese must be s aved before t he c onfiguration is
transferred.
Use either File -> Save or File -> Sa ve As to save the project . You can use any file name and l ocation, as long
as the file type (.db3) remains unchanged.
4. Select Transfer -> Config to unit from the top menu bar, or click on the Toolbar icon:
If t he option is greyed out, then this is because there is no network communicati on between y our PC and t he
control sy stem.
5. At the confirmation box, select Yes to s t art t he t ransfer:
Note that for POWER CORE and Nova17, the c onfirmation box i ncludes an option c alled S ave P roje ct to Unit.
You can use this to include a copy of the ON-AIR Designer project file in the transfer.
POWER CORE User ManualV ersion: V 6.0.0/554/459
7. Configur i ng POWER CORE
Project Save + Binary Files Creation
Files Transferred to Unit
The software now c reates t he necess ary binary configuration files, and transfers them to the Lawo c ontrol s y stem
via t he Et hernet network.
The progress of the transfer is shown in the Console s tatus area at the bottom of the 'Project' window. Once the
transfer i s c omplete y ou will see t he li nes Fil e loa de d to uni t and S endi ng Re sta rt. The sy stem may t ake a
few s ec onds t o rest art. Onc e boot-up is complete, t he new configuration parameters should be valid.
If y our computer’s firewall prevents t he transfer, then change your firewall sett ings and retry.
POWER CORE User Manual V ersion: V 6.0.0/5 55/459
8. Audi o IO
This c hapter describes how to configure the audio IO.
Topics inc lude:
·
Setti ng Up IO Cards
·
Setti ng Up RAVENNA/AE S 67
·
Setti ng Up MADI
·
Setti ng Up Sync hronisation
8. Audio IO
POWER CORE User ManualV ersion: V 6.0.0/556/459
8. Audio IO
The Sys tem Core configurat ion defines t he plug-in cards and IO parameters for the DSP Core.
1. Click on the To olb ar icon, or select Frame -> System Core , to open the window:
System Core Configuration Window
Note that the licensed package supported by the System Core is defined by the 'Frame Selection'. Therefore, if
the Core does not look as ex pect ed, please c heck the current specification.
You can zoom in (or out) on by pressing and holding CTRL while scrolling your mouse-wheel.
If you double-click on the text GT or DMS, you will open parameter windows for:
·
GT - used to send GPIO-over-audio.
·
DMS - used for VisTool metering or to create audio loopbacks .
2. To add or change a plug-in card, right-clic k on a slot and choose an option from t he drop-down menu:
Expansion IO Card Options (POWER CORE)
When you have completed the assignments, t he on-screen ‘Frame’ should look identic al t o your DSP Core.
8.1 Setting Up IO Cards
8.1.1 Selecting IO Cards
POWER CORE User Manual V ersion: V 6.0.0/5 57/459
8. Audio IO
3. Double-click on an IO card or connector to open the parameter window for its inputs and outputs.
MADI Port 1 Input Parameters (PO WER CORE)
MIC/LINE IO Card Input Parameters (POWER CORE)
Note that the same parameters can be acc ess ed by opening the " Audio Input" and " Audio Output" branches of
the 'Tree Definition' , and selecting the appropriate IO card.
Ign o re C ard
If enabled, the IO card is ignored by the system alarm (monitored via the Web UI or alarm bus).
This can be useful if a card is missing.
8.1.2 Audio Card Parameters
For each audio signal, the available parameters depend on the IO card type.
Use the tabs to switch between the different parameter sets: Input, Output, etc .
Module Para m eters
Every IO card includes a Module tab with the following option.
POWER CORE User ManualV ersion: V 6.0.0/558/459
8. Audio IO
Input Parameters
Inp u t N
Use this field to name the input.
For mono inputs, you can enter up to 16 characters.
For stereo or surround inputs, a two character suff ix is automatically added (e.g. “.L”).
Therefore, names should be limited to 14 characters.
Ty p e / Stereo
Use the Type drop-down menu (on Input 1) to select:
·
Mono.
·
Stereo – links inputs 1-2 for stereo operation.
·
5.1 – links inputs 1-6 for L, R, C, LFE, Ls, Rs surround.
·
5.1+2 - links inputs 1-6 for L, R, C, LFE, Ls, Rs surround + inputs 7-8 for stereo.
On odd numbered inputs, select the Stereo checkbox t o link the odd/even pair for stereo
operation.
Offset G ain
Here you can enter a fixed analogue offset gain for the input.
For M ic inputs, this is separate from the operator-controlled "mic" gain on the surface.
Matrix Enabl e
This option enables matrix control of the input. There are three options in the drop-down
menu:
·
ON – sets the input for “Matrix Connect” or “M atrix Query” functions, or ext ernal matrix control
such as the MtxCon (NovaConnect) software.
·
LS - sets the input for control from the optional Line Scheduler (LS) product. Please contact
y our local Lawo representativ e f or details.
·
OFF – the input is not enabled for ext ernal matrix control.
A fter a cold start, any inputs set to M atrix Enable ON or LS may need to be connected to a
matrix output.
Line
Use this checkbox to choose M ic or Line lev el operation.
The mode changes the input impedance and also determines which controls become
available when the source is assigned to a control surface:
·
For M ic inputs, operators can adjust mic gain, 48V and a high-pass "rumble" filter.
·
For Line inputs, these parameters are not available.
48V
Select t his checkbox to enable 48V phantom power permanently. F or ex ample, to apply 48V t o
a talkback microphone.
Fixed Mi c Gain
Here you can choose a fixed microphone input gain that cannot be changed by the operator.
For example, to enter a fixed input gain for a talkback mic.
MIC/LINE IN
POWER CORE User Manual V ersion: V 6.0.0/5 59/459
LINE IN
Input Parameters
Inp u t N
Use this field to name the input (as described earlier).
Ty p e / Stereo
Use the Type and Stereo fields to set the format of the input (as described earlier).
Offset G ain
Here you can enter a fixed analogue offset gain for the input.
Matrix Enabl e
This option enables matrix control of the input (as described earlier).
8. Audio IO
POWER CORE User ManualV ersion: V 6.0.0/560/459
8. Audio IO
Output Parameters
Outp u t N
Use this field to name the output (as described earlier).
Ty p e / Stereo
Use the Type and Stereo fields to set the format of the output (as described earlier).
Offset G ain
Here you can enter a fixed analogue offset gain for the output.
Matrix Enabl e
This option enables matrix control of the output (as described earlier).
If t he option is enabled, you cannot use the Default Audio function.
Default Audio
Double-click in the Default Au dio box to assign a default audio source for the output.
Default Audio assignments are automatically re-instated after a sy stem cold start. This
means that you can force a cold start to return to the Default Audio assignments if they are
overridden during operation of the system.
A D efault Aud io source cannot be assigned if Matrix Enabl e is active.
LINE OUT
POWER CORE User Manual V ersion: V 6.0.0/5 61/459
STUDIO IO
Input Parameters
Inp u t N
Use this field to name the input (as described earlier).
Stereo
On odd numbered inputs, select the Stereo checkbox t o link the odd/even pair for
stereo operation.
Offset G ain
Here you can enter a fixed analogue offset gain for the input.
For M ic inputs, this is separate from the operator-controlled "mic" gain on the
surface.
Matrix Enabl e
This option enables matrix control of the input (as described earlier).
Line
Use this checkbox to choose M ic or Line lev el operation (as described earlier).
48V
Select t his checkbox to enable 48V phantom power.
Fixed Mi c Gain
Here you can choose a fixed microphone input gain that cannot be changed by the
operator.
Output Parameters
Outp u t N
Use this field to name the output (as described earlier).
Stereo
On odd numbered outputs, select the Stereo checkbox to link the odd/even pair for
stereo operation.
Offset G ain
Here you can enter a fixed analogue offset gain for the output.
Matrix Enabl e
This option enables matrix control of the output (as described earlier).
If t he option is enabled, you cannot use the Default Audio function.
Default Audio
Double-click in the Default Au dio box to assign a default audio source for the output
(as described earlier).
Phones P ara m eters
These parameters are identical to the Output parameters described above.
8. Audio IO
POWER CORE User ManualV ersion: V 6.0.0/562/459
8. Audio IO
Input Parameters
Inp u t N
Use this field to name the input (as described earlier).
Ty p e / Stereo
Use the Type and Stereo fields to set the format of the input (as described earlier).
Offset G ain
Here you can enter a fixed digital offset gain for the input.
Matrix Enabl e
This option enables matrix control of the input (as described earlier).
Output Parameters
Outp u t N
Use this field to name the output (as described earlier).
Ty p e / Stereo
Use the Type and Stereo fields to set the format of the output (as described earlier).
Offset G ain
Here you can enter a fixed digital offset gain for the output.
Matrix Enabl e
This option enables matrix control of the output (as described earlier).
If t he option is enabled, you cannot use the Default Audio function.
Default Audio
Double-click in the Default Au dio box to assign a default audio source for the output
(as described earlier).
The Input, Output and MADI Settings paramet ers are identical to those available for the front MADI ports. S ee
MADI Signal Parameters and MADI Port Parameters.
The Module tab is the same as for other IO cards.
AES3 IO
MADI IO
POWER CORE User Manual V ersion: V 6.0.0/5 63/459
8. Audio IO
1. Network Topolog y and I nfrastructu re – What is the topolo g y and size of the network?
Simple si ngle switch running on Layer 2 (Basic IGMP)?
Spine and Leaf Data Center topology on Layer 3 (PIM, IGMP)?
WA N infrastructure with remote locat ions?
Quality of Service?
2. Timing and PT P and related redundancies – Pre cision Time Protocol (IEEE-1588) and
GrandMaster.
Single GrandMaster?
Multiple possi ble GM’s with B es t M as t er?
3. Stream Structure and Setup – Channel cou n t, stream d i scovery, redundancy.
What size s hould the st reams be and how many ?
What naming convention t o use? [group]:[name].
Effici ency and scale of quantities , sys t em load and frame size?
Stream redundancy incl uding hitless merge (SPS) and redundant s t reams?
Stream disc overy and announcement rings?
Multic as t address s chema, default or predefined?
Stream routing control, internal or external controller such as V S M ?
4. Configuration and License Requirements – POWERCORE licensing, stream configuratio n.
POW E RCORE License: SAN, L or XL?
POW E RCORE io matrix, s tereo, s urround etc?
Default streams?
8.2 Setting Up RAVENNA/A ES67
8.2.1 Introduction
This t opic is intended as an introduction to c onfiguring and setting up RAVE NNA s treams. It covers the typic al
configuration process and is in no way exhaustive or prescribing of how a customer should configure their sys tem.
Some questions one should ask oneself are: how redundant the network needs t o be; s hould t he audio network
be standalone; how are the st reams t o be routed and controlled; where do all the audio streams need to be routed
to; etc.
Please note that RAVE NNA requires a properl y c onfigured external network infrastructure t o funct ion correctly
and defining such is beyond the scope of this manual. Pleas e refer to and consult your network administ rator and
architect for network speci fic quest ions and sett i ngs.
Some Typi cal Questions
The table below s uggests some typical questions t o ask when setting up the system for networked audio.
POWER CORE User ManualV ersion: V 6.0.0/564/459
8. Audio IO
Group
Giv e each POWER CORE a descriptive and recognizable Group name, such as CORE1..4. The group
shall start with an alpha character and not numeral.
Name
Each outgoing stream for the Group shall also be given a descriptive name, e.g. SatRx01..08,
Codec01..06, etc. Remember to keep to the 8 character limit.
Default Audio
In this example the “baseband” inputs are being converted to AoIP streams and each should ideally
receive a default audio route from the corresponding input card. Double click on the pink cell and
select the relevant input.
Stream Size
In this example we are going to be using stereo streams. To optimize the packetiz ing process, 8
channels streams could be selected or even larger to reduce overhead.
Codec
L24 = linear 24 bits, is a good standard to use.
Samples per
Frame
32 or 48 is typical for stereo streams. Do not ex ceed the MTU of 1500 bytes otherwise the packets will
most likely get fragmented by t he switches (jumbo packets). 24 bit stereo samples with 48 samples
per frame = 288 byt es. For example an 8 channel stream would have 1152 bytes.
Devices
The requirement f or Hitless M erge means ra0and ra1 will be selected. The stream will be transmitted
on both NIC’s and the SDP will let t he receiver know that it’s a redundant stream.
Multicast
Address
The default range of multicast addresses will be used. The octets take a portion of their address from
the Ravenna NIC’s, namely t he 3rd and 4th and are arranged as follows: 239.3rdoctet. 4thoctet.x, where
x increments for each output stream starting from the first.
Discovery
The design called for two announcement rings. As this is a L2 network, mDNS Channels 1 and 2 shall
be used. Obtain (from network admin) and configure the multicast addresses in the System / Definition
/ Stream Announcement section according to the design. In CORE1..4 enable the Channel 1 and in
CORE1..2 enable Channel 2.
Return to Audio Output / Rav enna and tab RAVENNA O ut 1-64 and for the streams associated with
SatRx01..08 tick the check box mDNS 1 and 2 and for Codec01..08 tick mDNS 2 only.
Enable
Enter a True in the logic Enable field to ensure the streams get broadcast after startup.
Group
Giv e each POWER CORE a descriptive and recognizable Group name, such as CORE1..4. The group
shall start with an alpha character and not numeral.
Name
Each input will receiv e a stream off t he network and the question is whether to tie them permanently to
the input or give the input a generic name. In t his ex ample the input will be giv en a generic name, e.g.
In001.. 032 and be made stereo to correspond to the streams on the network.
Stream Size
In this example we are going to be using stereo streams. To optimize the packetiz ing process, 8
channels streams could be selected or even larger to reduce overhead.
Default Stream
Include the stream name in the event that these inputs will always be connected to the relev ant
network stream, e.g. CORE1:SatRx01
RAVENNA
Co n nect /
Stream Co n trol
Instead of using the Default Stream position to enter a default stream, the RAVENNA Connect element
could be used for triggered subscription to streams, or the RAVENNA Stream Control element could
be used should there be Primary and Backup streams associated with the input.
Configurati on Example
In t he example desc ribed below, t he network topology shall be a single Layer 2 s witc h using hitl ess merge with
an external PTP GrandMaster clock , and four connecting POW ER COREs on two announcement rings. For the
first POWE R CORE the Sat Receiver inputs will be available t o all other s y st ems , whereas t he Codec inputs will
be available to the first t wo syst ems only. There are four parts to the configuration:
Ø
Step 1 - Configure the Output Strea ms for each P OWER CORE
Open the "Audio Output -> RAVENNA" branch of t he 'Tree Definition', selec t the RAVENNA Out 1-64 tab, and
edit the parameters as follows:
Ø
Step 2 - Configure the Input Stre ams for ea ch P OWER CORE
Open the "Audio Input -> RAVENNA" branch of t he 'Tree Definition', select the RAVENNA In 1-64 tab, and edit
the parameters as follows:
POWER CORE User Manual V ersion: V 6.0.0/5 65/459
8. Audio IO
PTP Setting s
M ake sure that the PTP GM and POWER CORE have the same PTP settings so as to sync
successfully.
Slave On ly
M ake sure this is ticked so that t he POWER CORE will always look for a GM in the network.
Syn c Prio
In System -> Definition -> Parameter = Sy nc, make sure that Enabl e Sync from PTP is ticked, and that
the Syn c Prio is set to PTP as the first option.
Ø
Step 3 - Set up a nd Check the PTP S ync
Open the "S ys tem -> Definition -> P arameter = S tream A nnouncement" branch of the 'Tree Definition', and edit
the parameters as follows:
Ø
Step 4 - Check and Tune the S tre ams via the We b UI
1. Open a Web UI connection to POWER CORE in the usual manner, and enter the Administrator
password.
2. Navigate ov er to the Streams page and check t hat all the streams are being broadcast on the network.
Note the stream names, Dev ID’s, mDNS channels, and Flags. Note especially the flag status as to t he c ondition
of the stream.
3. Navigate ov er to the Outputs (Devices -> Core) page to check that t he s ubsc ribed st reams are appearing
and connected to the relevant inputs.
Use the Connect button to s earch the network for announced streams and connect them to relevant inputs.
4. Select the Stream Destinations page to view the statistics associated with the subscribed streams
(connected to Destinations).
The lower sect ion provides st atist ics t hat report on the health of the received P rimary and S econdary streams.
Data such as P ac k et Count, E arly, Late and Misordered Packets, B uffer Margins and especially Jitter.
Depending on the Jitter value the streams will be placed in a particular Class which will define the Time Offset
(shown in the upper sect ion). Each time a stream connects it will go through a Tuning process t o define its Time
Offset, however it may be necessary to manually perform this task should there have been changes to the
networ k infr astructure.
Use the Retune button t o i ndividually retune a s t ream, or Re tune All t o retune all streams. The process goes
through three phases as can be observed under the F. Once 8 has been reached the stream has been retuned.
POWER CORE User ManualV ersion: V 6.0.0/566/459
8. Audio IO
8.2.2 Setting up Streams
Audio is streamed from POWER CORE to the network acc ording to the RAVE NNA audio output s ett ings defined
in the sy s tem configuration. This means that once a s uitable c onfiguration is loaded to the sy s tem, audio will be
streamed automatically whenever POWE R CORE is c onnected to t he network and powered.
To prepare some output streams, edit the sys t em c onfiguration as follows:
1. Open the "Audio Output" branch of the 'Tree Definition', and select one of the RA VENN A Out tabs.
Note that the number of channels available is dependent on the POW ER CORE license. At max imum c apacity ,
up to 256 channels of audio can be broadcast on 128 streams.
Note that streams can be transmitted from either or both front panel ports (ra0 and ra1).
'Tree Definition': A udio Output -> RAVENNA 1-64
2. All outputs t hat have a name entered into the Name field will be transmi tted automatic ally as s treams,
while the other parameters configure the output's audio options and stream setup.
T he first few fields: Name, Type, Dig Offset Ga in, M atrix ena b l e, Transparent and Defa ult Audio are handled
in an identical manner to other outpu ts. See MADI Signal Parameters for details.
T he RAVENN A parameter s: Stream Size, Codec, SampPerFrm, Devices, I P Addre sse s, mDNS, SAP, TTL,
etc. define the stream setup.
The important fields are:
·
Name - a name must be entered in order t o publish the output stream t o the network. The maxim um
length is 8 characters. If the stream is to be displayed on another ruby surface in a c hannel lis t, t hen t he
stream name must use the format [GroupName]:[ Si gnalName], where each label field is a max imum of 8
characters. See RAVE NNA Pool Sources for details.
·
Type - defines the format of the output: mono, st ereo, etc. This s hould match the Stre am S i ze.
·
Ma trix e nable - by turning ON the Matrix Ena bl e option, t he output can be controlled by a matrix.
·
Defaul t Audio - altern a tively, if Ma trix Enable is OFF, a permanent audio source can be ass igned to
the output. Note that the Defa ul t Audio setting is ignore d when Matrix Ena bl e is ON.
·
Stream Size - defines t he number of audio channels used by t he stream. This s hould match t he audio
output form at (Type).
·
Codec - select the type of codec to use for t he stream: Linear, 16, 24 or 32 bits; or AM824 (a
packetized AES signal that includes all user and status bit s ).
·
Sa mpP erFrm - set s the number of samples included in each Et hernet Frame. A frame is t he payload
being carried over the Ethernet link. This is typically set t o 32.
·
Device s - select which port to send the stream out on: ra0, ra1 or both ra0 + ra1 (Hitless Merge SMTPE
2022-7).
POWER CORE User Manual V ersion: V 6.0.0/5 67/459
8. Audio IO
·
IP Address 0, 1 - enter the multicast address for the streams being transmitted on ra0 and r1. Note that if
this field is left blank, then a default multicas t address is as signed. These fields provide y our network
architect with t he ability t o im plement a spec ific IP mult i c as t sc hema for your facility .
·
UDP Port No. - reserved for Unicast .
·
mDNS - multi cast DNS is a way to enable st ream dis covery on a Layer 2 network. Up to four mDNS
"Announcement Rings” can be establis hed per POWER CORE. These can be us ed to s hape the s t ream
availability between POWER CORE and other RAVENNA devic es .
·
SAP - Session A nnouncement Protocol, is a variant on mDNS and expands t he Announcement Ring
capability t o eight.
·
TTL - Time To Live defines how many hops the stream may navigate. Each time a st ream traverses a
switch, the TTL is redu ced by one.
·
Enable / Disable - ability via Logic to c ontrol whether a st ream is t o be transmit t ed or not.
In our example above, the network will receive 10 s tereo st reams (named R1601s, R1603s, etc): the first 8 are
controlled by an external matrix , while t he last t wo have been ass igned s ome De fault Audi o (from the P rogram
and Record sums).
3. Repeat these s teps to configure the remaining RAVENNA output s t reams as needed.
Once the configuration has been transferred to the sy stem, you can use the Web UI RAVENNA -> Inputs page to
check the streaming setup.
POWER CORE User ManualV ersion: V 6.0.0/568/459
8. Audio IO
Audio from streams on the network can be connected to POWER CORE either statically (by assigning a source
from a RAVENNA streaming input) or dynamic ally (by configuring RAVENNA Pool Sources).
In both cas es , you will need to define the st reaming inputs as follows:
1. Open the "Audio Input" branch of t he 'Tree Definition', and select one of the RAVENNA In tabs.
Note that the number of channels available is dependent on the P OW E R CORE lic ense. At m axim um c apacity ,
up to 256 channels of audio can be received via 128 streams.
Note that streams are received on either or both front panel ports (ra0 and ra1) depending on the external
network t opology.
'Tree Definition': A udio Input -> RAVENNA 1-64
2. All inputs which are named can be used by other elements within the c onfiguration; for example, as t he
audio input to a source. The other parameters configure the input's audio options and stream setup.
T he first few fields: Name, Type, Dig Offset Ga in, Matrix enable and Transparent are handled in an identical
manner to other audio inputs. See M A DI Signal Parameters for details.
T he RAVENN A par ameters: Stream S ize, UDP Port No, etc. define the stream setup.
The important fields are:
·
Name - a name must be entered in order to use the input.
·
Type - defines the format of the input: mono, stereo, etc. This should match the Stre am S ize.
·
Ma trix e nable - by turning ON the Matrix Ena bl e option, t he input can be controlled by a matrix.
·
Stream Size - defines the number of audio channels used from the stream. This should matc h the
audio i nput format (Type) to maintain conformity. However, this is not a requirement. If t he st ream siz e
does not matc h the type, t hen the audio inputs will s till be assigned when a s tream is subs cribed to,
with consecut ive channels being allocated on a one-to-one basis.
·
UDP Port No. - reserved for Unicast operation.
·
Defaul t Stre am (optional) - defines t he name of the stream you wish subsc ribe to. It can be us ed t o
permanently link the receiver to a stream. You can enter a stream name of up to 28 characters. The
console will then search the network using mDNS or SAP announcement protocols. If a matching
stream name is found, the receiver will automatically s ubscribe t o it. If a Default Stream name is not
entered, t hen an automatic s ubscription will not occur. In this i nstance, a stream subsc ription c an be
established by selecting a pool source on the surface, with internal logic or with VSM v ia Ember+.
·
Matrix No. - when the system is used in conjunct ion with an external routing c ontroller, s uch as Matrix
Server, t his number corresponds t o the entry in the Matrix Server configuration.
3. Repeat these s teps to configure the inputs for each RAVE NNA s t ream.
8.2.3 Subscri bing to Str eams
POWER CORE User Manual V ersion: V 6.0.0/5 69/459
8. Audio IO
8.2.4 Losing a Streaming Connection
If a st reaming connection is lost - for example, the sending device goes offline or y ou remove t he network cable then audio stops pass ing. However, the c onnect ion is st ill prepared. This means that as soon as the st ream reappears on the network - for ex ample, the sending devic e comes back online or is reconnected - audio will be reestablished.
8.2.5 Confi guri ng Redundant Streami ng
POWER CORE supports two redundancy mechanisms: hitless switching (SMTPE 2022-7) and LACP (Link
Aggregation Control Protocol).
Hitless Merge / Seam l ess Protection Switching (SMPTE 2022-7)
Hitless Merge (or SPS) is a method of redundancy which employs t wo different networks (i. e. routes) t o transport
data. If one "route" fails, then the other can be used to recover the mis sing data.
The standard is defined by SMPTE 2022-7.
SPS has been implemented into the POW ER CORE configuration and the goal has been to m ake t his as sim ple
as possible. SPS adds st ream redundancy on the phy sic al l evel i n that t wo st reams c arrying the s ame data are
transmitt ed independently on the 2 RAVE NNA NIC’s. The degree of redundancy can be up to the level of t wo
physic ally independent networks with their own PTP down to si mply two ethernet cables plugging into the s ame
switch. Each stream is given its own multicast address and even though transmitted via different paths this
information is captured in the SDP that acc ompanies both st reams. The receiver or s ubsc riber thus k nows of the
existence of the other stream and internally rebuilds any missing data.
To create a Hitles s M erge enabled s tream, s et t he Devices field to ra0+ra1 in the RAVENNA Output branch of
the 'Tree Defi nit ion':
These are referenced in s everal of the W eb UI pages relating to RAV ENNA and are ty pically c alled Device ID’s.
The Statistic s pages refers t o t he devic es as P rimary and Secondary.
LACP (Link Aggregation Control Protocol )
LACP is a networking protocol supported by some network switches and routers.
It can provide redundancy by "bonding" or “teaming” physical ports together to form a single logical channel.
Enabling LACP not only provides redundancy but c an also increase throughput, although the usage here is the
former. A s ingle IP address is c onfigured and LACP enabled via t he W eb UI Sy st em -> Network Devices page.
Note that the connecting network infrastruct ure needs t o support LACP for this to function properly.
POWER CORE User ManualV ersion: V 6.0.0/570/459
8. Audio IO
Input Parameters
Inp u t N
Use this field to name the input (as described earlier).
Ty p e / Stereo
Use the Type and Stereo fields to set the format of the input (as described earlier).
Di g Offset G ain
Here you can enter a fixed digital offset gain for the input.
Matrix Enabl e
This option enables matrix control of the input (as described earlier).
Transparent
Select t his checkbox to set t he input to be “transparent”. T he option should be enabled if y ou
are using the input to route a Dolby E signal.
8.3 Setting Up MADI
8.3.1 MADI Signal Paramet ers
Open the Sy s t em Core c onfiguration (as des c ribed earlier), and double-click on each of the front MA DI ports to
configure its i nput and output parameters.
POWER CORE User Manual V ersion: V 6.0.0/5 71/459
8. Audio IO
Output Parameters
Outp u t N
Use this field to name the output (as described earlier).
Ty p e / Stereo
Use the Type and Stereo fields to set the format of the output (as described earlier).
Offset G ain
Here you can enter a fixed digital offset gain for the output.
Matrix Enabl e
This option enables matrix control of the output (as described earlier).
If t he option is enabled, you cannot use the Default Audio function.
Transparent
Select t his checkbox to set t he output to be “transparent”. T he option should be enabled if y ou
are using the output to route a Dolby E signal.
Default Audio
Double-click in the Default Au dio box to assign a default audio source for the output (as
described earlier).
POWER CORE User ManualV ersion: V 6.0.0/572/459
8. Audio IO
"System -> Definition -> Pa ra meter = Madi"
Open this branch of the 'Tree Definition' to c onfigure parameters for the MADI ports.
Parameter
M adi – reference name for the element.
P1, 2, 3, 4 E xternal
Matrix Port
This is a project-specific feature.
Server 1 active
Server 2 active
These options support a redundant matrix server.
A ssign a control signal to switch to server 1 or server 2.
P1 En able 64 Tx Slots
etc.
When this checkbox is selected, the MA DI port transmits 64 slots as opposed to 56.
Note that t he receiver automatically detects whether 56 or 64 slots are supplied. If t he port is
configured to transmit 64 slots and only 56 are received, then the last 8 slots are muted.
The option can be selected for each individual M ADI port.
P1 Select Input 2
etc.
Click to assign a control signal to switch the MADI port from P1 to P2.
Note that if Sync f rom MADI is enabled, then this will also switch the MADI sy nc source.
The option can be selected for each odd/even pair of MADI ports.
P2 Tx = P1 Tx
etc.
When this checkbox is selected, MADI port P2 transmits the same data as port P1. The option
can be used to configure redundant M ADI outputs.
The option exists for each odd/even pair of M ADI ports.
8.3.2 MADI Port Paramet ers
8.3.3 Creating Redundant MADI Ports
To create redundant MADI links with automatic switching from say MA DI Port 1 to Port 2:
1. I nv ert the P1 Inpu t pre sent control output using a NOT logic element.
2. Then feed the output of the NOT ga te to the P 1 S elect Input 2 control input.
Now if the signal input to MADI P1 fails , the sys tem will automatically switch to MA DI P2.
3. To configure redundant MADI outputs, check the P2 Tx= P 1 Tx option.
Now MADI port P 2 t ransmit s the same data as port P1.
You can use this procedure to configure each odd/even pair of M A DI ports .
POWER CORE User Manual V ersion: V 6.0.0/5 73/459
8.4 Setting Up Synchronisation
"System -> Definition -> Pa ra meter = Sync"
Open this branch of the 'Tree Definition' to configure the system's sync reference parameters. See
Synchronisation for more about the sy nc reference options and how to use t he Web UI t o check the sync
status.
The configuration paramet ers are defined as follows:
Parameter
Sy nc – reference name for the element.
E n able Sync from
PTP, MADI, etc.
When no boxes are ticked, the system is synchronised to internal system clock (either 48kHz
or 44.1kHz, see Enable Samplerate Switch below.)
To sync to an external reference, select the relevant tick boxes.
Syn c Prio
If more than one sync source is enabled, then this menu sets the prioritization order.
E n able Samplerate
Switch
Select t his tick box t o enable the 44.1kHz sample rate switch (described below).
Samplerate 44.1kH z
Selects a logic control signal to switch the system sample rate from 48kHz (default) to
44.1kHz . To switch the sample rate you must check the En able Samplerate Switch box AND
apply a logic control signal.
8.4.1 Sync Reference Parameters
8. Audio IO
POWER CORE User ManualV ersion: V 6.0.0/574/459
9. Audio Mix Engine
9. Audi o M i x En g i ne
This c hapter describes t he audio mix engine.
Topics inc lude:
·
Sources
·
Summing Busses
·
DSP Parameters
·
VCA Groups
·
PFL Monitoring
·
Monitoring Master Control & Talkback
·
Monitoring Signal Selection
·
Tone Generator
·
Signal Metering
·
Surround Mixing
POWER CORE User Manual V ersion: V 6.0.0/5 75/459
9. Audio Mix Engine
9.1 Sources
9.1.1 Source Anatomy
Each input channel is called a ‘source’. Sources c an be mono, stereo, 5.1 or 5.1/stereo.
All s ources assi gned to fader strips are act ive in the mix . This includes s ources as signed t o “hidden” layers or
virtual bays. The naming of s ources, assignment of signal process ing and other att ributes are all made by the
sy stem c onfiguration. Phy sical inputs are normally ‘hard wi red’ to sources. This allows s ource-specific c hannel
features suc h as fader st art or mic live si gnaling to follow the source when it i s assi gned to a different fader strip.
The maximum number of s ources which c an be added to the configuration, and summed together simultaneously,
is determined by the license package for the System Core. Note that a stereo source uses two summing
resources; a 5.1 source uses 6 s umm ing resources, and so on.
Every source includes:
·
Analog ue Input section – available for sources fed from microphone inputs; inc ludes mic gain, 48V and
high pass rumble filter.
·
Digital I nput section – available for every s ource; includes digital gain, phase reverse, pan or balance,
surround parameters.
·
Metering – meter points for input, pre and post processing.
·
Fader – a motorised fader for level control.
·
Bus Assign – bus s ends with pre/post fader selection and variable level control.
In addition, the following DSP modules can be enabled (or disabled) by the configuration:
·
EQ – 3-band parametric E Q plus High and Low P as s Fil t ers.
·
Dynamics – Gate, E xpander, Compress or and De-Ess er/A utoMi x s ec tions.
·
Limiter – independent limit er.
·
Delay – adjustable in ms, met res or frames.
·
Insert – external insert point which c an be Pre EQ; P os t E Q; or Post Dynamics .
Each fader (not source) can also be assigned a Direct Out. This can be:
·
Pre fader, pre processing.
·
Pre fader, post processi ng.
·
Post fader, pre processing.
·
Post fader, post processing.
POWER CORE User ManualV ersion: V 6.0.0/576/459
9. Audio Mix Engine
9.1.2 Creating Sources
The "Source" branch of the ‘Tree Definition’ allows you to insert and configure sources.
Each source can support several sets of parameters. Switc h between them using the menu t abs at t he top of t he
parameter area.
The most im portant fields are the source Name and Type (def ined in the Parm tab):
A source must be named before it c an be referenced to other elements vi a t he 'Tree Selection'.
The Type defines whether this is a normal audio source (mono, s t ereo or surround) or a special source such as a
VCA Group, Minimix, R3LAY or Protools. This sec tion c overs normal audio sources. The other s ource ty pes will
be described later.
POWER CORE User Manual V ersion: V 6.0.0/5 77/459
9. Audio Mix Engine
Source Name
Reference name for the source element.
Type
This field defines the type of source.
Display
Display name for the source. This is the name which appears in the fader label when the
source is assigned to the control surface. Enter 6 characters or less so that t he name can
appear in full on the control surface displays.
If a Source is published to the Ember+ network, then its Display name must be unique.
Alias
This name must be used if y ou need to distinguish between sources which have t he same
‘Display’ name. For example, if you hav e t wo sources named CD, you will need to enter
different Alias names in order to save and load snapshots.
If an A lias name is not entered then snapshot data is referenced to the ‘Display’ name.
It is strongly recommended that you use unique Display names wherever possible!
Class
This field can be used to permit Src snapshots sav ed on one source to be recalled on another,
see V isTool Snapshots.
If the Class field is left empty , then Src snapshots stored from the source can only be recalled
to itself.
If the Class field is set to the same tex t string as other sources (e.g. default), then Src
snapshots stored from another default source may be recalled. This is useful if, for example,
y ou wish to able to recall microphone parameters stored on one input t o another.
E mber+ Local
Provi d er N r
This field is used to publish all source parameters to an Ember+ provider - enter the provider
number from 1 to 5, or select None if you do not wish to publish the source.
9.1.3 Source Parameters
Select the source y ou wish to edit in the 'Tree Defi nition' and open the Parm tab to acc es s its main parameters:
POWER CORE User ManualV ersion: V 6.0.0/578/459
9. Audio Mix Engine
Src Repl Element N r
Src Repl Name
These fields are used to couple the source to an ext ernal source in an Ember+ consumer. The
Src Repl Element N r should match that defined in the Ember+ SrcRepl element. The Src Repl
Name should match the display name configured in the Ember+ consumer.
List Enable
Select t his checkbox if you wish the source to be added to the source selection list when
assigning sources from the control surface.
Au d io In put
Selects the audio input f or t he source.
Limiter
Compressor
Equaliser
Delay
Tick these checkboxes to assign signal processing to the source. Note that:
Compressor represents the Dynamics (Gate, Ex pander and Compressor) section.
DSP is not available for surround sources.
Lim Op Disable
Co mp Op D isable
E q O p Disable
Dl y Op Disable
On sapphi re MK2 systems, all 96 Sources are configured with Limiter, Dynamics, EQ and
Delay. Tick these check box es to prevent the operator adjustment of DSP parameters for certain
sources. Note that:
Compressor represents the Dynamics (Gate, Ex pander and Compressor) section.
De-Esser/AutoMix
A vailable on mono and stereo sources only . Select this checkbox t o assign one of the 32 De-
Esser/AutoMix processors to the source. Note that each function (De-Esser and AutoM ix) can
be enabled by the operator independently.
No va17/MTx Server
A vailable on stereo sources only. If the audio input to the source is assigned from a remote
matrix , then this option selects the method of communication:
·
Turn the option On if t he remote matrix is a Nov a17, Nova29 or Matrix Server.
·
Turn the option Off if t he remote matrix is a Nova73 (for communication via Remote MNOPL).
Once communication is established, you can use the Matrix Out 1 field to support the transfer
of labels from the remote matrix (to the fader label display on the console).
A nd/or use the Class/Pool f ield (and Mt x Src Pool element) t o provide operator-controlled
selection of audio inputs from the remote matrix. See Configuring a Matrix Source Pool.
Matrix Out 1
A vailable on stereo sources only. This option allows the labels from a remote matrix (as
described abov e) to appear in the fader strip display s and source's Kpf label.
Enter the matrix number of the remote matrix output which is connected to the source's audio
input.
Class/Pool
A vailable on stereo sources only. This option will allow an operator to select audio inputs from
a remote matrix directly from the fader strip. See Configuring a Matrix Source Pool.
When using a Nov a17, Nova29 or Matrix Server, enter the Pool ID defined in the corresponding
M TX Src Pool element.
When using a Nov a73, enter the class configured in the Nova73 map (as described in the
"ext_router_control_en.pdf" available from the Download-Center at www.lawo.com (after
Login).
RAVENNA
OFF / O N. W hen set to ON, the source becomes a RAVENNA source that can subscribe to
streams available on the network.
RAVEN NA Pool No.
Up to 6 pools can be defined to shape the availability of streams, and whether a particular
stream can be selected by this source. Note that a RAVENNA Src Pool element must be
defined to support this setting. See Configuring RAVENNA Pool Sources.
Fader Open
Tick this box if you wish the lev el of the source to be set to 0dB rather than - infinity. This is
particularly useful for sources which are not to be assigned to the control surface.
Inp u t Mu te
Selects an input control signal to mute the audio input.
This mute occurs at the point before the signal is distributed in the matrix, therefore will affect
routes to other destinations as well as to the selected source. (To mute the source within the
‘channel’, see Channel Mute.)
The mute is active until the input control signal = Logical “1”.
Fader Up
Opens the source fader (see also Ho ld Mod e below).
POWER CORE User Manual V ersion: V 6.0.0/5 79/459
9. Audio Mix Engine
Fader Do wn
Fader Tog g l e
Fader Up to L ast
Value
Fader Tog g l e to L ast
Value
Closes the source fader (see also Hol d Mode below).
Changes the state of the source fader: open to closed, or v ice v ersa (see also Ho ld Mod e
below).
Opens the source fader to its last known position.
Toggles the source fader to its last known state.
These 5 functions can be used to programme a fader start and are triggered by t he rising edge
of the input control signal.
Ho l d Mode
When this input is activ e, t he last position is stored when the fader is closed by Fader
Down/Toggle. Opening the fader using logic sets the fader to the last stored position. If Hold
Mode is activated while the fader is closed, then the Default Positi o n set below is used.
Default Po s (d B)
Used in conjunction with Ho l d Mode. Sets the default level, in dB, t o which the fader will open if
Ho l d Mode is activated while the fader is closed.
DMS Color
The value entered here selects the colour for DM S meters within VisTool (see VisTool Editor:
PPM). The v alue shown is represented by 0x RRGGBB where RRGGBB denote the amounts of
Red, G reen and Blue respectively. Click on the colour selector box to choose from the colour
palette.
Source Col or
Selects the colour used to illuminate the fader strip backlight when the Mode is set to either:
·
Source Col or Enabled
·
Mix Mode
If you select Black, then the backlight is unlit.
Source Col or Mode
Select t he mode of operation for the fader strip backlight:
·
Source Col or Enabled - always indicates the type of source.
·
Source Col or Disabled - always indicates signal present.
·
Mix Mode - combines the options above; signal present takes priority.
Signal present parameters are defined under "System -> Definition -> Parameter = Signal
Present"..
Ch ann el O n Edge
Ch ann el O ff
Edge
Ch On/O ff Toggle
Ch ann el Mu te
When a positive edge is supplied to this input, the source is unmuted.
When a positive edge is supplied to this input, t he source is muted.
This input toggles the status of the channel mute on each rising edge of the control signal.
This input mutes the source as long as it is supplied with an active control signal.
These 4 control inputs allow the audio signal of a source to be switched on and off.
Access U ser Off
This input locks out the Access Key so that the source cannot be assigned to the centre
section. You may use this to limit operator access to source parameters.
Parm Page User Off
This input locks out all DSP modules for the source. You may use this to prev ent parameters
such as a presenter’s mic EQ and Compression from being altered by the operator.
Ch ann el Parm off
This input locks parameter control from the channel fader strip. Y ou may use this to prev ent
parameters such as mic gain and pan from being altered by the operator.
Ref Src
Selects the reference source. When a source is assigned to the control surface, a reference
source can be assigned at t he same time. For example, on a console with two lay ers – on-air
and record – you could assign the TEL source to both layers automatically . In this parameter
box, assign the reference source (e.g. TEL).
To determine where the reference source appears on the control surface, use the Ref Src
F ader Offset option set within the “System -> Definition -> Param = Fader”.
Note that changing DSP parameters on one of the sources will aff ect the other.
Matrix Mic Nr
Matrix Gn et Po rt
These two fields are used if the audio input to the source is a microphone which requires
arbitration. See Mic Arbitration.
Use the Matrix Mic Nr field to enter the Mic Input Nr referenced within the server's
configuration.
In the Matrix Gnet Port field, enter the GPI/O Network port number which connects to the serv er.
POWER CORE User ManualV ersion: V 6.0.0/580/459
9. Audio Mix Engine
disable Surr. Pan
This control input disables the Surround Pan parameters on the Channel and Central M odules
– LCR, front-rear, Centre slope and LFE level. This can be used to simplify operation for a
stereo installation. Note that 5.1 panning is only av ailable if 5.1 or 5.1+2 Sums are configured.
Access
This control input will action the fader access key f or t he source. For example, to action an
access key f rom a GPI.
Mono
A vailable on stereo sources only. This control input monos the source.
ms -> xy
A vailable on stereo sources only. This control input converts an ms input to xy.
Stereo
A vailable on stereo sources only. This control input resets the source to stereo.
Left -> Both
A vailable on stereo sources only. This control input routes the Left audio input to both sides of
the source.
Ri g ht -> Both
A vailable on stereo sources only. This control input routes the Right audio input to both sides of
the source.
Side Swap
A vailable on stereo sources only. This control input rev erses the Left and Right audio inputs at
the input to the source.
Phase
A vailable on mono and stereo sources only T his control input reverses the phase of t he source.
Start Mic AutoGain
Cycle
A vailable on microphone input sources only . This control input starts the AutoGain
measurement process.
POWER CORE User Manual V ersion: V 6.0.0/5 81/459
9.1.4 Changing Audio I nputs
1. Select the source you wish to edit in t he 'Tree Definition' and open the Parm tab.
2. Do ub le- click inside the pink Audio Input box for the source you wish to edit.
3. Open the branches of the 'Tree Select ion' to choose an input:
9. Audio Mix Engine
4. Select OK to c onfirm and close the 'Tree Select ion' window - the parameter box updates to show y our
assignment.
5. T o remove an entry, click anywhere inside the entry box and press DEL on your PC keyboard.
POWER CORE User ManualV ersion: V 6.0.0/582/459
9. Audio Mix Engine
These options allow operators to dynamic ally subsc ribe to st reams from t he control surface (via the fader s trip
rotary control and TAKE button).
1. Select the first source you wish to c onfigure in the 'Tree Definition' and open the Parm tab.
2. Check that the Audio Input is as s i gned from a RAVENNA st reaming input.
3. T urn the RAVENNA option ON to enable the RAVENNA Pool stream selector.
4. T hen assign a RAVENNA Pool No. from 1 to 6.
Up to s ix different pools can be defined, and each c an be as signed t o m ultiple s ourc es. This allows you to
create s ources which can ac ces s the same subset of st reams i f you wish (by assi gning the s ame RAVENNA
Pool No).
5. Repeat these s teps to configure each of your RAVENNA s ources.
Signal Na ming & Organization
For all matrix s ources, including RAVENNA sources, s ignals within a pool are organized by name, following t he
convention Group:Signal. W hen using dynamic input switc hing, this provides a t wo-step navigation process : first
select the Group, and then brows e through all available Signals within that Group. Note t hat both t he Group and
Signal labels can be up to 8 characters.
By default, displayed labels are retrieved automatic ally from eit her the AE S67/RAVE NNA st reaming network or
networked router (if using NetCom or Remote MNOPL protocols).
In the case of AES67/RAVENNA streams, the names can be obtained automatically IF the st ream names follow
the Group:Signal convention. St reams with the same Group name are combined into a s ingle Group even if they
are provided by different devices . The presented list will t hen be updated automatic ally so t hat newly dis c overed
streams are added, and st reams which can no longer be detected are erased. To prevent access to c ertain
signals, signal name fi lters c an be applied to limit access . In cases where the AES67/RAVENNA streams
cannot be named using t he above convention, it is poss ible t o map s treams to s ignal labels, and present t he
configured list t o t he operator. In this ins tance, the lis t is permanent and is independent of st ream availabilit y .
In t he case of a network ed router, t he matrix source pool Group and Signal names come from the input names
defined in the configuration of t he c onnected router.
9.1.5 Confi guri ng RAVENNA Pool Sources
POWER CORE User Manual V ersion: V 6.0.0/5 83/459
9. Audio Mix Engine
Selecting an AES67/ RAVENNA Stream from the Control Surface
Once you have transferred the configuration, assign the RAVENNA Source to a fader st rip. Then:
1. Tap down on the rotary control until you reach the RAVENNA Group select.
2. With the arrow pointing at the streaming Group, turn the control to browse through the available
streaming Groups and press down to make a selecti on.
3. T hen turn to sc roll t hrough the available streams (detected on the network).
4. Press the Take butt on to assign the stream.
There will be a brief pause in the audio while the s treaming c onnection is c onfigured; during this tim e, the label
display at the bottom of the fader strip shows the status of the connection process. If the subscription is
successful, t hen the name of t he c onnected st ream is dis play ed.
POWER CORE User ManualV ersion: V 6.0.0/584/459
9. Audio Mix Engine
RAVEN NA Src Pool
Reference name for the element.
Pool No.
None, 1 to 6.
Pool Typ e
Static or Dynamic:
·
Dynamic is the more ty pical choice. It allows the pool to adjust dynamically t o a
changing stream structure.
·
When Static is selected, two additional tabs open where you can enter up to 64 static
streams, each with a Source Label.
No d e Name Filter
Enter a name to filter the streams according to the node name. Node names can be seen
in the Web UI. A wildcard is given as *.
Stream Group/Name Fi l ter
Enter a name to filter the streams according to the Group and Name using the wildcard *.
Stream Size Filter
A pply a stream size filter. The options are None, 1, 2 or 8.
Relo ad Pool
Enter a control signal to reload (refresh) the source pool. This allows the stream list to be
refreshed should any new streams be made av ailable on the network.
9.1.6 RAVENNA Src Pool Parameters
The RAVENNA Src Pool element defines the functionality of the RAVENNA Source Pools, whether they be
Stati c or Dynamic and the application of Filt ers to build subset s for easier navigation. Up to 6 independent pools
can be defi ned. The element is defined under the "Logic" branch of the 'Tree Definition':
POWER CORE User Manual V ersion: V 6.0.0/5 85/459
If the P ool Type is set to Static, t hen the "Static Source List" t abs appear:
Static RA VENN A Src Pool
Reference name for the element.
Local Group
Enter the name of the Group to which the stream belongs.
Local N ame
Enter the name of the stream itself. G roup and Name are separated by a colon “:”.
RAVEN NA Source Label
Enter the label to be used for the selected stream.
9. Audio Mix Engine
POWER CORE User ManualV ersion: V 6.0.0/586/459
9. Audio Mix Engine
9.1.7 Editing Display Names
The Display field is us ed t o name the fader label for a source. This is different to the Reference name which
identifies the source within the configuration.
1. Select the source you wish to edit in t he 'Tree Definition' and open the Parm tab.
2. I n the Display field, enter the name for the source as you want it t o appear on the control surface.
Enter six characters or less so that the name can appear in full on the control surface displays .
You can use copy (F5) + paste (F6) or incremental past e (F7) to quickly edit a series of source names.
POWER CORE User Manual V ersion: V 6.0.0/5 87/459
9. Audio Mix Engine
You can keep track of how many resources are available by opening the "Command -> Resources" window.
9.1.8 Assigning DSP to Sources
On POWER CORE, all sources added to the configuration come with full process ing: Lim it er, Dynamic s , EQ and
Delay. If you wish to allocate a de-ess er or automixing (to a mono source), t hen this must be enabled on a
source-by-source basis.
1. Select the source you wish to edit in t he 'Tree Definition' and open the Parm tab.
2. Use the Op Disa ble checkboxes to disable operator control of a process ing module from the c ontrol
surface.
3. To assign a de-esser or automixing, enable the DeEsser / AutoMix box. This option is available on m ono
sources only.
The signal processing is described in more detail later, see DSP Parameters.
POWER CORE User ManualV ersion: V 6.0.0/588/459
9. Audio Mix Engine
9.1.9 Source Fader Behaviour
The fader status outputs are active depending on the status of the s ource fader.
Note that each control s urface will behave differently depending on whether or not it supports m oving faders. For
surfaces with moving faders, there is a choice of two modes: Normal or Hot Fader (described below). For
surfaces with non-moving faders, there is no c hoice as t he faders always operate in the equivalent of Hot Fader
Mode.
The two modes are shown in the diagram below.
·
Normal Mode – the surface fader posit ion always represents t he fader level. This means that i f a source
is c ontrolled by RAS or Fader Up/Down/Toggle logic signals, then the surface fader will move i n response
to the automation.
·
Hot fa der Mode – the surfac e fader pos ition is independent of any automation (RAS or fader l ogic). This
allows an operator t o preset a fader value (e.g. 0dB), before an RAS controller or Fader Up/Down/Toggle
fader start opens or closes the Backgrou nd fader level.
Note that in Norm al Mode , the Back ground level is always 0dB and has no act ion; in Hot Fade r Mode , the
operator sets t he Surface level, while RAS or fader logic signals c ontrol the Bac kground level.
POWER CORE User Manual V ersion: V 6.0.0/5 89/459
9. Audio Mix Engine
F ader Start
For moving fader systems:
·
In N o rmal mode the output indicates the status of the RAS/Logic controlled surface fader
position.
·
In H o t Fader mod e, t he output indicates the status of the RAS/ Logic controlled background
fader position.
For non-moving fader systems, the output is active when the “Background” fader (RAS/ Logic)
v alue is open.
nF ader Start
The negative result of Fader Start.
F ad. -20dB
Becomes active when the “Background” fader value moves above -20dB.
Becomes inactive when the “Background” fader value is off.
Fader Man. Start
For mov ing fader systems:
·
In N o rmal Mod e the status is true by default.
·
In H o t Fader Mode, the output reflects the surface fader position.
For non-moving fader systems, the output reflects the status of the physical fader position. I t is
active when the “Surface” fader value is open.
Fader Man. nStart
The negative result of Fader Man. Start.
F ader Man.
-20dB
Becomes active when the “Surface” fader v alue moves above -20dB.
Becomes inactive when the “Surface” fader value is off.
Fader Result Start
A ctive if Fader Start AND F ader Man. Start are both active. If a VCA master is assigned, then
this also needs to be activ e.
In N o rmal mode this output is identical to Fader Start.
In H o t Fader mod e, t his output flags the status of the combined phy sical fader and RAS/ logic
controlled fader position. In other words, both the physical fader and the automation/logic need
to be open for this output to be true.
Fader Result n Start
The negative result of Fader Result Start.
Fader prepared
A ctive if Fader Start is activ e AND Fader Man Start is NOT activ e.
Use this output in Ho t Fader mod e, or on non-moving fader sy stems, t o f lag when the RAS or
logic has opened a fader position, but the phy sical surface fader is closed.
Fader Tou ch activ e
A ct ive if the fader sense is active (the fader is touched).
The following fader status outputs are available for each source. You can use these to trigger other logical
funct ions via the 'Tree Selection' window.
Selecting Hot F ader Mode
For moving fader systems, t he operator can enable (or disable) Hot Fader Mode from the SYS menu.
The initial value, which is act ive following a cold st art, is defined in the “Sys tem -> Definition -> Parameter =
Fader” branch of the ‘Tree Definition'.
POWER CORE User ManualV ersion: V 6.0.0/590/459
9. Audio Mix Engine
In addition to onboard signal processing, each s ource supports an insert send and return. The devices which are
available for insertion are defined in the configuration. Note that:
·
Mono devices c an only be assigned to a mono source.
·
Stereo devices can be assigned to a mono or stereo source. If a st ereo devic e is inserted on a mono
source, then only the left chan nel is used.
·
Inserts are not supported by summing busses.
Parameter
Insert – reference name for the element.
Insert N
Enter a name for the insert. This is both the reference name and the name which will be
displayed on the control surface, so use 6 characters or less.
Ty p e: Stereo
When checked the insert device is treated as a stereo device, and when unchecked a mono
device – see the notes above.
Outp u t L
Outp u t R
A ssign the outputs (sends) to the insert device.
Inp u t L
Inp u t R
A ssign the inputs (returns) from the insert device.
9.1.10 Inserts
Configuring I n sert Devices
Open the "System -> Definition -> Parameter = Insert" branch of the 'Tree Definition' to configure the insert
devices . You can us e any audio inputs and outputs for the connections to a mono or stereo insert devic e.
POWER CORE User Manual V ersion: V 6.0.0/5 91/459
9. Audio Mix Engine
If s umm ing buss es cannot be ass i gned to the control surface, then they are output from the console at unity
gain (0dB).
A s t ereo bus uses t wo and a 5.1 bus us es 6 s umm ing bus resources.
9.2 Summing Busses
9.2.1 Bus Anatomy
Each bus is called a ‘summi ng bus’, and can be mono, stereo or 5.1.
The naming, assignment of signal processing and bus att ributes are all made by the sy stem c onfiguration.
The first pair of busses i s always pre-defined as s tereo PFL 1. The remaining buss es can be "user" defined as
any of the following:
·
Sum Bus – normal summing busses can be allocated DSP and ass igned to a fader strip. Typically,
these are used to create aux sends, groups or extra main outputs.
·
GP S ums – cannot be allocated DSP or fader st rip c ontrol. They are ideal for applicat ions such as a
talkback bus.
·
Conf Busses – these busses have special facilities for generating a mix minus (N-1).
·
PFL – additional PFL buss es (up to 5). For example, in a mult i-operator s urface, each s tat ion m ight feed
a different PFL bus/output.
The signal flow for each summing bus i s the same as for a source, see S ource Anatomy .
The maximum number of busses which can be added to the configuration, and their DSP resources, is
determined by t he lic ense pack age for the Syst em Core.
The configuration also defines whether you can re-assign busses from the control surface, or whether s ources are
‘hard wired’ to each bus. F or example, you may choose to 'hard wire' sources to the programme bus for sim plic it y
and security.
9.2.2 Creating Sum Busses
Use the "Sum Bus" branch of the ‘Tree Defi niti on’ to ins ert and configure summing busses .
Each bus c an support s everal sets of parameters. Switch between them using the menu tabs at the top of the
parameter area.
The most im portant fields are the Name and Type (def ine d in the Parm tab):
A sum bus must be named before it can be referenced to other elements via the 'Tree Selection'.
The Type defines whether this is a normal summing bus (mono, stereo or surround) or a special bus such as
R3LAY.
POWER CORE User ManualV ersion: V 6.0.0/592/459
9. Audio Mix Engine
9.2.3 Sum Bus Parameters
Select the Sum Bus you wish to edit in the 'Tree Definition' and open the Parm tab to access its main
parameters:
T h e r e are identical to the correspond ing Source parameters, with the following exc eptions/ additions:
·
DSP mus t be allocated t o each summing bus by t ick ing the Limiter, Compressor, Equalizer and/or
Delay boxes.
·
Post Only – s elect this check box t o limit bus as signments to post fader only (e.g. for a Main or Group
bus).
Note that you cannot assign a sum bus to another s um bus or conf bus. To achieve, y ou will need to ass ign t he
sum bus t o a loopback output, and then assign the loopback return as the input t o a source. The source m ay
then be assigned to t he sum bus in t he us ual m anner. Audio loopbacks will be described later.
POWER CORE User Manual V ersion: V 6.0.0/5 93/459
9. Audio Mix Engine
You can keep track of how many resources are available by opening the "Command -> Resources" window.
9.2.4 Assigning DSP to Sum Busses
On POWER CORE, all summing busses are added to the configuration without signal process ing. Therefore, if
you wish to apply DSP, t he modules must be enabled on a bus-by-bus basis.
1. Select t he s umming bus you wish to edit from t he Sum Bus branch of the sy stem tree, and select the
Parm menu tab.
2. Use the Limiter, Compressor, Equalizer and/or Delay c heckboxes t o enable each process i ng module.
The signal processing is described in more detail later, see DSP Parameters.
POWER CORE User ManualV ersion: V 6.0.0/594/459
9. Audio Mix Engine
Parameter
A ux – reference name for the element.
Au x Mode Sequence
Defines the order in which bus assignments are made; you can select between:
·
Pre - post -off
·
Post - pre - off
"Off", "Pre", "Post"
Colors
Defines the MF Key colors used for aux assignments.
The default colors are Aux Off = green; A ux Pre = red; Aux Post = Yellow.
Au x 1 to 20
A ssigns the summing bus defined as “Aux n”.
Hide
Tick this box if you do not want the bus to be displayed on the Fader Module OLEDs when in
‘Bus Assign’ mode.
Use this option to prevent operators from adjusting assignments onto a bus (e.g. PGM).
Fader E n abl e
A ssigns the control trigger which will switch the aux send levels onto the faders (globally
across the console).
9.2.5 Setting Up PGM / A UX Busses
Open the "Sy stem -> Definition -> Parameter = Aux" branch of the 'Tree Defi nition' t o define t he 20 summing
busses which can be assigned from the control surface. Note that the bus l oc at ions are called Aux 1 to Aux 20.,
although they may be used for any ty pe of bus: programme, groups, auxes , etc.
Once a bus is ass igned to an "Aux n" l ocation, it will become available to the operator via the BUS assign buttons
on the Central Module (unless the Hide option is act ive). Up to five pages c an be configured, where Aux 1 to 4 will
appear on page one; A ux 5 t o 8 on page two; and so on. The available parameters are as follows.
POWER CORE User Manual V ersion: V 6.0.0/5 95/459
9. Audio Mix Engine
Au x n Pre
This control input will switch the send to Aux n to pre fader.
Au x n Po st
This control input will switch the send to Aux n to post fader.
Au x n O ff
This control input will switch the send to Aux n Of f .
Select Aux n
This control input will assign the source to Aux n. T he first press assigns the source pre-fader;
the second press is post fader; and the third press is off.
Post Onl y
If t his box is checked, then there is no pre-fader option.
9.2.6 Managing Bus A ssignments
Having defined Aux 1 to Aux 20, there are two ways to manage the as signments from each source. Ei ther a
particular state c an be forced or the states can be toggled. The former is ideal for static bus ass ignments. The
latter is ideal for operator-controlled bus as s i gnments from a fader st rip MF K ey .
Forced State Bus Assig n
Use the Aux S witch s ource parameters t o force a partic ular st at e for each bus s end.
Toggled State Bus Assign
Use the Aux source parameters to t oggle the stat e for each bus send.
POWER CORE User ManualV ersion: V 6.0.0/596/459
9. Audio Mix Engine
ConfBus
Reference name for the conference bus.
Display
Display name for the conference bus used on the control surface. Enter 6 characters or less.
Source Col or
Selects the colour used to illuminate the LAWO backlight on the control surface when this
source is assigned to a fader strip.
Tick the enabled checkbox to enable colour coding.
List Enable
Select t his checkbox if you wish the conf bus to be added to the source selection list when
assigning sources from the control surface.
Co n f 2
Select t his checkbox if you wish the bus to be part of t he second Conference sy stem.
Unchecked, the bus will automatically default to Conference 1.
9.2.7 Conf / Mix Minus Busses
The conference system i s used to generate mix minus/N-1 feeds for particular sources within your configuration.
Each s ource within the s yst em receives an automatic ally s witched mix minus feed. W hen their source fader is
open (on-air), they will hear programme minus thems elves, and when their source fader is closed (off-air), t hey will
hear the conference bus minus thems elves – this allows m embers of the conference t o hear each other while they
are off-air.
9.2.8 Creating Conf Busses
The "Conf Bus" branch of the ‘Tree Definit i on’ allows you t o insert and configure conferenc e bus parameters.
POWER CORE User Manual V ersion: V 6.0.0/5 97/459
9. Audio Mix Engine
When working with Conf 1 and Conf 2 conference groups, note t hat:
Sources c onfigured to different conference groups c annot communic ate while a conference is ac t ive.
When a source is configured to both conference groups it i s required to configure the switching or summing of
the Conf buses separately.
Conf buses wit h t he attribute “Conf 2" (see below) must only be set as a Conf 2 bus within the sources. The
same applies to Conf 1.
Co n f 1 B us
A ssigns a Conf Bus to the source. T his sets the relationship between the source and the bus
in order to generate the N-1 mix.
Co n f 1 On
Turns on the Conference sy stem with a rising edge.
Co n f 1 Off
Turns off the Conference system with a rising edge.
Co n f 1 To ggle
Changes the state of the Conference system with a rising edge.
Co n f 1 In d i sable
A rising edge removes the source from all conference busses that are assigned to the
Conference 1 system. A f alling edge reassigns the source. For example, this might be linked to
the presenter’s cough switch.
Co n f 1n
If a source is assigned to a Conf Bus 1, then you can use the control input Conf 1n to assign its
own signal to the conference bus. With a rising edge source is added and with a falling edge it
is taken away.
9.2.9 Conf Bus Assi gnments
For each source you can assign a conference bus to be used as it s mix mi nus feed.
All options are repeated for the two separate conference s ys t ems – Conf 1 and Conf 2. This offers t he poss ibilit y
to form a second mix -minus/c onference group where all sources are automatically assigned to all mix-minus
sums but its own. By usi ng t he c ommand “Conf 1 In d isable” or “Conf 2 In di sable” (see below), y ou can form
different mix-minus/conference groups; sources working on Conf 1 need not be included in Conf 2 and vice versa.
The source parameters from the 'Tree Definition' are as follows. A ll options are repeated for both Conf 1 and Conf
2.
POWER CORE User ManualV ersion: V 6.0.0/598/459
9. Audio Mix Engine
There are two completely s eparate conference sys tems (Conf 1 and Conf 2), each of which may be used to
gene rate multiple mix minus or N-n feed s.
9.2.10 Conf Bus Confi g Example
To generat e a mix minus/N-1 or N-n feed, there are three parts t o t he c onfiguration:
·
First, a c onference bus must be created for each mix minus feed (from the "Conf Bus" branch of the 'Tree
Definition').
·
Second, the sources must be defined to feed the conference system (using the "Source -> Conf"
parameters).
·
Third, some MF Key s should be programmed so t hat the operator can enable or disable t he conference
for each source.
Each c onference source receives an automatic ally switched mix m inus feed. When their source fader is open (on-
air), they will hear programme minus t hemselves, and when their source fader is clos ed (off-air), t hey will hear the
conference bus minus thems elves – this allows members of the conferenc e t o hear each other while t hey are offair.
Defining the Conference Busses
1. Righ t-click on the Conf Bus branch of the 'Tree Defin ition', and Insert a new element. Use the repetition
field to insert multiple busses in one operation:
2. Edit the parameters for each conference bus:
Most important is the Reference name - in our example, CB_DJ. Tick Conf 2 if the bus is t o be part of t he second
conference sy s tem, or leave it blank t o use Conf 1.
See Conf B us for details on the remaining parameters.
POWER CORE User Manual V ersion: V 6.0.0/5 99/459
9. Audio Mix Engine
To create an N-many, as sign the same conference bus to multi ple sources.
To use the second conference system, assign the bus to Conf 2 Bus. (The Conference bus should also have
its Conf 2 parameter enabled, see step 1.)
Defining the Conference Sources
1. Select t he first s ource - for example, “Source -> Microphones -> MI C DJ”.
2. Assign the confere nce bus output to the Conf 1 Bus parameter (f r om the Conf menu tab):
3. Repeat to ass ign each conference bus to it s source.
POWER CORE User ManualV ersion: V 6.0.0/5100/459
Loading...