Case Study RTBF in Belgium - LAWO
←
→
Page content transcription
If your browser does not render page correctly, please read the page content below
Case Study RTBF in Belgium FULL-IP OB TRUCK TIMES TWO Also featured: An in-depth Look at the Flexibility afforded by Lawo’s C100 Blades
Lawo Case Study: Full-IP OB Truck Times Two
Executive Summary
In early April and September 2020, RTBF,
Belgium’s public broadcaster for the
country’s French-speaking community,
took delivery of two groundbreaking, full-IP About RTBF
OB trucks. The 12m long trailers had to be RTBF is the public Belgian radio and television organization of the
configured remotely in order to be delivered Wallonia-Brussels Federation, an autonomous public enterprise
on time, due to the covid-19 lockdown. with a cultural mission. Active in television, radio, on the web and
social networks, RTBF is a 360° media player and the engine of
Perfect examples of how to leverage the
expression and fulfillment for its audiences now and in the future.
flexibility of Lawo’s C100 FPGA blade, the
As a public media service, its mission is to provide pluralist and
OB Twins come equipped with a 100Gbps
independent information to the French-speaking community of
Arista-powered network core (audio, video Belgium (approx. 4.5 million people), but also to promote the
and matrix) that revolve around Lawo’s community’s culture, heritage and talents, and as to ensure the
V__matrix platform for SDI- and IP-based transmission of memory.
video and audio input/output as well as Its mission is to entertain, educate and contribute to social
processing. cohesion as well as the development of local economies.
Lawo’s VSM talks directly to the XVS-8000 IP
vision mixer using NMOS-IS04/05 protocols. LAWO PRODUCTS DEPLOYED (in each of the two trucks):
• 21x V__matrix C100 (12x for streaming/gateway
Each truck offers 36 vm_dmv heads
functionality, processing, glue and color correction + 9x for
delivered through C100 blades for
vm_dmv multiviewers: 36 head outputs, 210 video inputs)
multiviewing purposes. Overarching control
• 2x V__pro 8 (Dolby E encoding/decoding)
and orchestration is handled by Lawo’s
• 48-fader mc2 56 audio console, Nova 73 audio router core
VSM IP control system and theWALL for
multiviewer arrangement. • 2x A__UHD Core (main + redundant)
• 1x PowerCore in truck (local MIC preamps, line inputs/
The OB Twins support all audio formats in
outputs, AES3, Dante)
two resolutions (24 and 32 bits), which are
• Audio stageboxes: 4x PowerCore + 4x LCU commentary,
mixed using an mc² 56 audio production
1x DALLIS (pristine musical preamps)
console and 512 DSP channels provided by
• Video stageboxes: 3x V__matrix Silent Frame with C100
Lawo’s A__UHD Core.
blades, 3x A__mic 8 (additional audio connectivity +
See right for a comprehensive list of Lawo 8-channel GPI/O)
products installed in and around RTBF’s • VSM via separate network: overall stream routing,
full-IP OB trucks. parameter control.
2
RTBF in Belgium
RTBF’s Twin Full-IP OB Trucks
In early April 2020, RTBF, Belgium’s public broadcaster for the and accepted remotely, with hardly anybody on site. Another is
country’s French-speaking community, took delivery of the first that social distancing and tight schedules of the most talented
of two groundbreaking, full-IP OB trucks. Due to the covid-19 operators are no longer an issue.
lockdown, the 12m long trailer had to be configured remotely using
TeamViewer, a few web cameras and microphones for confirmation Besides, thanks to ST2110 IP, distributed production scenarios
purposes as well as via VPN. The second identical OB truck was are in the process of becoming the norm. Yet another benefit is
configured by Lawo’s Jörg Mittag, Dave Leliveld and Andreas Hain the flexibility afforded by choosing the most malleable processors
in late August. available.
Top-notch broadcast facilities all over the world have relied on
Open-standards-based IP technology is taking the broadcast—
Lawo for their productions for a few years now and confirm that
and the corporate AV—world by storm. One of its benefits is
ST2110-based IP is the future, not least because it allows for
the convenience with which infrastructures can be configured
flexible tweaks to their workflows.
Both OB trucks were built by Broadcast Solutions in Germany
3
Lawo Case Study: Full-IP OB Truck Times Two
In the light of all this, RTBF’s decision to commission two identical the software-defined V__matrix units for a variety of applications,
full-IP OB trucks in 2019, when nobody even knew what including SDI–IP gateway streaming, video processing, embedding/
“lockdown” meant, appears to have been far-sighted. de-embedding, color correction, audio and video delay,
multiviewers, audio shuffling, and audio processing.
It was certainly in keeping with RTBF’s plans to equip its new
broadcast center with an IP infrastructure, and to use its new OB Despite the massive processing power they house, the four racks
trucks as additional control rooms whenever necessary. inside RTBF’s full-IP OB Twins are still fairly empty. And only
one of those racks contains Lawo’s V__matrix software-defined
Connecting the trucks to the facility’s network via IP is a simple IP-routing, processing and multiviewing units.
matter of plugging a pair of optical cables into the right wall
sockets. And turning the two trucks into one giant, mobile Just in case you were wondering: the reason for commissioning
production facility for high-profile events is also a possibility. two identical full-IP OB trucks is rumored to have been that RTBF’s
management wanted to provide the same advanced infrastructure
But there was more: the significantly reduced rack space, weight for two crews covering different events to avoid lengthy discussions
and cable runs inside the trucks are excellent news for the beforehand…
environment, while the OB truck operators are at liberty to use
Input/output panel at the back of the truck that supports all formats. Essences that
aren’t IP streams already are converted to ST2110 for “internal use”.
4
RTBF in Belgium
Vital Statistics
RTBF’s 12m long OB trailers come equipped with a 100Gbps “NEP Belgium’s and
Arista-powered network core (audio, video and matrix) that
revolves around Lawo’s V__matrix C100 platform for SDI- and Lawo’s guidance was
IP-based video and audio input/output as well as processing.
invaluable and provided the
They are based on the ST2110 suite of open standards provided
by the Lawo gear they contain. highest benefit for RTBF.
V__matrix and V__matrix Silent Frames for: We consider our two full-IP
• Video,
• SDI-derived audio,
OB trucks the first building
• Video and audio processing, blocks of our future
• Multiviewing (36 head outputs capable of displaying every Media Square facility.”
incoming signal as well as 3 tally layers).
—Cécile Gonfroid, CIO, RTBF
The audio section features:
• 48-fader Lawo mc2 56 Audio Production Console with a Nova 73
router,
• A redundant pair of A__UHD Core ultra-high-density IP DSP
engines for mc2 consoles (512 DSP channels each),
• Power Core I/O and processing nodes,
• A__mic8 audio edge devices.
Lawo’s VSM system (with support for NMOS-IS04/05 protocols)
controls the V__matrix units, the vm_dmv multiviewers, the Sony
vision mixer (in- and outgoing streams, tally information and label
transfers) as well as all other devices and stream routings.
The 10 stageboxes (five 19” flightcases per truck) assembled for
the OB Twins were designed for both outdoor and indoor use in
V__matrix units inside the OB trucks. The C100 blades they contain handle studios and venues. The Power Core edge devices in the audio
all video and audio essences. flightcases not only accept MIC/line and AES3 signals, but also
support MADI and Dante—both with SRC—for direct sourcing
from a PA system during concerts and other events.
5
Lawo Case Study: Full-IP OB Truck Times Two
The video stageboxes, finally, are each equipped with a V__matrix
Silent Frame for SDI-to-IP gateway operation and an A__mic 8
stagebox for flexible ad-hoc audio connectivity and GPI/O control.
As stated earlier, audio can also be ingested via the SDI inputs.
Example of the audio stageboxes built for RTBF’s OB Twins. Audio I/O and
processing are provided by the Power Core.
For music applications, RTBF requested one DALLIS stagebox
Example of the video stageboxes built for RTBF’s OB Twins. The A__mic 8
per OB truck because of the superior sound quality of its 48 provides ad-hoc audio I/O accommodation and GPI/O connectivity.
microphone preamps and their exceptional 128dB signal-to-noise
ratio. Each full-IP OB truck comes equipped with 180 microphone
preamps per truck.
Lawo furthermore supplied six LCU commentary units that can be
connected to the desired stagebox. All stageboxes are equipped
with an Arista network switch that delivers power over Ethernet
(PoE). Connectivity for Riedel Bolero antennas is also included. An
additional Cisco switch has been installed for the distribution of
VSM control signals.
One interesting aspect about RTBF’s OB Twins is that the audio
received via the SDI inputs is also transmitted to the mc2 56 audio
mixer after being de-embedded, and that these audio streams
are available in both the ST2110-30 and -31 formats (see also
below).
One audio stagebox with a DALLIS I/O unit for RTBF’s OB Twins
“I very much enjoyed collaborating with the Lawo team on
tailoring the solution to RTBF’s needs.”
—Geert Thoelen, Technical Director, NEP Belgium
6
RTBF in Belgium
Audio control section in RTBF’s full-IP OB trucks, with a 48-fader mc2 56 Audio Production Console.
On Your Marks…
RTBF’s full-IP OB trucks transmit SDI signals and IP streams we would have been able to insert the required data directly in the
to the outside world and can be linked to each other via a right places. But we nevertheless managed to accomplish what
network connection, which turns them into one big control room needed to be done,” comments Dirk Sykora.
compound.
This remote scenario required a dedicated computer to which all
The first truck was delivered on 4 April 2020 after having been configuration files were transmitted, allowing the team to configure
configured and commissioned remotely. Due to covid-19, traveling and test the OB truck from afar.
between Belgium, the Netherlands and Germany had suddenly
become impossible, while delivery in early April 2020 had already During this three-week stint, daily video conferences were held at
been confirmed, and was expected. 1pm where RTBF, NEP Belgium, Broadcast Solutions and Lawo
reviewed what had been completed and what needed to be done
Lawo, NEP Belgium’s Geert Thoelen and Broadcast Solutions’ next. This was necessary to ensure that everybody was moving
Matthias Hahn therefore suggested moving the acceptance in the same direction, which isn’t always obvious with teams
tests and configuration tasks to the virtual realm, using a VPN scattered across several locations.
connection to the OB truck. This approach had to be revised,
because no viable VPN connection could be established. The remote acceptance scenario was greatly facilitated by the OB
truck’s full-IP backbone. All devices and solutions were readily
As a result, Broadcast Solutions set up five computers running accessible to the configurators and RTBF operators in three
TeamViewer in Bingen (Germany). All virtual attendees had their different countries.
own TeamViewer access. “VPN would have been faster, because
7
Lawo Case Study: Full-IP OB Truck Times Two
A Look at the End-to-End IP Network
IP Network Core
STUDIO/FOP
STUDIO/FOP Arista Leaf Arista Leaf
OB TRUCK Arista Leaf Arista Leaf
Arista Leaf Arista Spine Arista Leaf
10Gb 40/100Gb 1Gb
OB TRUCK
Arista Leaf Arista Spine Arista Leaf
10Gb 40/100Gb 1Gb
IP networks are based around switches—in the case of the OB Twins switches manufactured by Arista are used. Given the network’s
relative complexity, one switch acts as “Spine”, i.e. a switch that aggregates the streams received from, and transmitted to, subordinate
switches, which are called “Leaves”. The “STUDIO/FOP” Leaf switches are located in mobiles stageboxes for flexible deployment.
STUDIO/FOP
Audio Network Riedel
Panels/Bolero
Commentary
LCU Audio Stagebox
PowerCore
Dallis
STUDIO/FOP Arista Leaf
Arista Leaf
Riedel Commentary
Panels/Bolero LCU Audio Stagebox
PowerCore
Dallis
OB TRUCK Arista Leaf
Arista Leaf
Arista Leaf Arista Spine Arista Leaf
10Gb 40/100Gb 1Gb
OB TRUCK
Arista Leaf Arista Spine Arista Leaf
10Gb 40/100Gb PowerCore Audio1Gb
Core DSP
Internal Stagebox A__UHD Core
Audio Matrix
Ext Patch Audio Nova73
PowerCore Audio Core DSP
Internal Stagebox A__UHD Core
Audio Matrix
Audio Mixer
Ext Patch Audio Nova73
mc² 56 MKIII
Audio Mixer
mc² 56 MKIII
The audio signals ingested via the audio stageboxes (and possibly an A__mic 8 in a video stagebox). The audio end devices accept
STUDIO/FOP
analog, AES3, MADI and Dante™ signals, which are converted into streams and then mixed and processed. Both ST2110-30 (24 bits)
Riedel Commentary Audio Stagebox
and ST2110-31 (32 bits) are supported—in any combination.
Video Stagebox
Panels/Bolero LCU
Cameras Sony
8 V__matrix
A__mic8
PowerCore
Dallis
STUDIO/FOP
Arista Leaf Arista Leaf
V__matrix PowerCore Audio Core DSP
Video mixer
EVS 9x C100
Sony Internal Stagebox A__UHD Core
Multiviewer
V__matrix Audio Matrix
Ext Patch Video 12x C100
Ext Patch Audio Nova73
Streaming
CCU Sony RTBF in Belgium
Audio Mixer
mc² 56 MKIII
Video and Control Networks
STUDIO/FOP
Riedel Commentary Audio Stagebox
Video Stagebox
Panels/Bolero LCU
Cameras Sony
V__matrix PowerCore
A__mic8 Dallis
Arista Leaf Arista Leaf
OB TRUCK
Arista Leaf Arista Spine Arista Leaf
10Gb 40/100Gb 1Gb
V__matrix PowerCore Audio Core DSP
Video mixer
EVS 9x C100
Sony Internal Stagebox A__UHD Core
Multiviewer
V__matrix Audio Matrix
Ext Patch Video 12x C100
Ext Patch Audio Nova73
Streaming
CCU Sony
Control Network
Cisco
Audio Mixer
VSM mc² 56 MKIII
Control System
The video network (pink devices) is based on the V__matrix platform whose C100 blades are used to generate multiviewer heads (vm_
dmv, “Multiviewer), convert the SDI signals coming from the cameras into video streams (“Streaming”), and to provide video and audio
processing. Video streams are essences that are transported and handled independently from audio essences (see left). This provides
almost endless possibilities regarding video/audio stream combinations. Nevertheless, all features required by the OB Twins fit into 12
units of rackspace.
The V__matrix units in the video stageboxes are so-called “Silent Frames”, which are almost inaudible and can therefore be placed on
the stdio floor, close to the SDI cameras.
The control network (purple) revolves around Cisco switches. All devices in the OB Twins are managed by Lawo’s VSM virtual studio
manager software that (re)configures the required devices and provides access to deep-dive editing at the press of an on-screen button.
The control network—which also manages devices manufactured by EVS and Sony—is considered the heart of the OB trucks.
9
Lawo Case Study: Full-IP OB Truck Times Two
C100: The Ace of Blades
Both future-proof OB
trucks are equipped
with 21 Lawo C100
blades. These are FPGA
processing units whose
function is defined by the
software that is uploaded
to them.
Housed in V__matrix
units, the C100 blades can
be programmed to provide
all functions requested
by RTBF. They can be
retasked at any moment
simply by uploading
different software.
The latter will come in
handy when RTBF decides
to replace the SDI cameras
currently in use with IP
models. The blades in
charge of converting
their SDI signals to IP streams will not become obsolete in the way. After all, specifying boxes is only the first step for such a big
process: operators can simply use them for other tasks. This was project.
one important reason why Geert Thoelen of NEP Belgium, who
architected the OB trucks’ infrastructure, together with Dirk Sykora, It was therefore decided to organize a one-week training/
was in favor of installing Lawo’s C100-based V__matrix units. brainstorming session at RTBF during which Lawo presented
and demonstrated the potential of the V__matrix C100 blade
(depending on the V__matrix size, two or more such blades can
Initial Brainstorm be installed). This was deemed important to ensure that the
The entire IP system of RTBF’s full-IP OB Twins evolves around the RTBF task force grasped the numerous options provided by the
power of Lawo’s C100 blades, which can be configured according C100 blades, and to keep configuration time to a minimum once
to the customer’s needs. everybody was clear on what was expected. “The C100 blade is
so flexible that there are usually several ways of achieving a given
While looking at the tender documents, NEP Belgium and Lawo result. All of us were looking for the most efficient solution for the
already had a good idea of what RTBF would need, but they project at hand,” observes Lawo’s Dirk Sykora.
wanted to be sure to address all requests in the most effective
10RTBF in Belgium
Shading stations
Overview of the C100 CONFIG RTBF – Streaming blades 1~12
PTP Configuration
three software PTP Agent 0
40Gb - 1
PTP Shifter PTP Clock
blocks inside ST2110
System Clock
RTBF’s C100
C100 CONFIG RTBF – Streaming blades 1~12
blades used for SDI inputs (00~10)
Auto detect 1.5G/3G
FramePhaser
Framesync
Video Configuration
(in 00~10)
Video Matrix 1
(out 00~09) SDI Outputs (00, 01/10~17)
Auto detect 1.5G / 3G
streaming and
Video delay (0~10)
(out 18~28) 11x TX streams for SDI inputs
Inputs : Video TX Stream (00~10)
Video RX Stream (00~14) 10x for SDI outputs (in 18~32) 2110-20, Auto detect 1.5G/3G
00~10 : SDI In
2110-20, Session 00~14 3x for Processor Insert, 2x for free tieline 18~32 : RX
38~40 : Proc Insert 3x TX streams for Proc Insert
(out 33~35) Video TX Stream (15~17)
41 : Color Bars
1x HD / 1x 3G (on different blades) (in 41) 42 : Black 2110-20, Auto detect 1.5G/3G
Video Color Bar
(Video generator 0)
processing: PTP,
Outputs: (out 36) 1x TX stream for Color Bar
Video TX Stream (18)
00~09: SDI Out 2110-20, Auto detect 1.5G/3G
18~37: TX
Video Black 1x HD / 1x 3G (on different blades) (in 42)
38~40: Proc Insert
(Color Corrector 3) (out 37) 1x TX stream for Video Black Video TX Stream (19)
2110-20, Auto detect 1.5G/3G
(out 38~40) (in 38~40)
Video and Audio.
Processor Insert
Color Corrector Framesync/
(00~02) Video delay (18~20)
See below for
C100 CONFIG RTBF – Streaming blades 1~12
details. Audio Configuration
22x TX streams for SDI inputs Audio TX stream (00~21)
Possibility to switch off SRC for Dolby E 24-bit audio 2110-30 (8-channel)
(Additional C100
Audio TX stream (50~71)
2110-31 (8-channel)
SDI Inputs (max 00-10)
Audio SRC (00~10)
(16 channels)
(16 channels)
Auto detect 1.5G/3G
Audio Gain
blades are used
Audio Generator 1kHz to create a audio ramp Mono Audio Matrix 1 Mono Audio Matrix 2
(Audio Gain 0) Mono Audio Matrix 0
for audio shuffling for audio splitting DolbyE Alligner SDI outputs (00, 01/10~17)
Audio Delay (00~10) for audio combining (Audio Delay 24~34)
(16 channels) 1 x 16ch —> 2 x 8ch (16-channel)
(in 00~21) (out 00~19) 2 x 8ch —> 1 x 16ch (10 x 16 channels)
Audio Gain Fixed routing at startup AV Matrix 1 Auto detect 1.5G / 3G
Audio Generator 440Hz to create a audio ramp Fixed routing at startup for block routing
Fixed routing at startup
(Audio Gain 1) (8 channels)
Inputs :
for vm_dmv
Audio Gain 00~21: SDI In
Audio Generator 400Hz to create a audio ramp 36~65: RX In
(Audio Gain 2) 76~81: Proc Insert
82, 83: 1kHz
Signal Generator 1kHz (in 82, 83)
Outputs :
00~35 : SDI Out
36~41 : Proc Insert
multiviewer Audio RX Stream (00~29)
2110-30 (8 channels)
Session 20~49 20x for SDI outputs
6x for Processor Insert
4x for free tieline
30x Audio RX 8-channel (in 36~65)
generation.)
in 76~81
Processor Insert
6x TX streams for Proc Insert Audio TX stream (36~41)
24-bit audio 2110-30 (8-channel)
Audio Delay (18~23)
(6x 8-channel)
6x TX streams for Proc Insert Audio TX stream (86~91)
32-bit audio (Dolby E) 2110-31 (8-channel)
2x TX, 1kHz Audio TX stream (42, 43)
24-bit audio 2110-30 (8-channel)
2x TX, 1kHz Audio TX stream (92, 93)
32-bit audio (Dolby E) 2110-31 (8-channel)
Considerations that played a part were: should RTBF use ST2110
or ST2022 streams, and would they need to accommodate I. PTP Configuration of the C100
Dolby E signals often used for satellite downlinks? This
informed the decision to support both ST2110-30 (24 bits) and Each C100 requires a synchronization path to a PTP clock
ST2110‑31 (32 bits) audio, which is rather unusual. The reasons generator. This means that a PTP Reception Agent needs to be
for this two-pronged strategy are detailed on page 14. created and assigned to a domain and a port to supply the blade’s
system clock.
Explaining that a C100 blade is initially a blank page, or a box of
Lego bricks that allow users to build what they have in mind, is
The next question is whether one or two PTP Reception Agents
always a good start.
are needed. A redundant network requires two. In RTBF’s case,
While some blocks are mandatory, others are only needed for
there is only one PTP receiver per C100 blade, because the OB
specific applications. Knowing which ones are required for the
trucks’ network is not redundant. This may change in the future,
project at hand is aways a great help.
and adding a second PTP Reception Agent at a later stage only
Additional C100 blades, with a different configuration, are used for requires inserting this software-based functionality.
vm_dmv multiviewer generation.
The PTP Agent is usually connected to a PTP
C100 CONFIG RTBF – Streaming blades 1~12 Shifter to create video timing offsets against
PTP Configuration the truck’s clock.
Next in line is the blade’s PTP clock to which
PTP Agent 0
40Gb - 1
PTP Shifter PTP Clock all video signals are synchronized. The
System Clock block inside a C100 generates
a timing reference for log entries. If no offset
System Clock
information is required, the System Clock
is connected directly to the PTP Agent.
Otherwise, it can be patched to the PTP
Shifter block.
11
C100 CONFIG RTBF – Streaming blades 1~12(out 18~28) 11x TX streams for SDI inputs
Inputs : Video TX Stream (00~10)
Video RX Stream (00~14) 10x for SDI outputs (in 18~32) 2110-20, Auto detect 1.5G/3G
00~10 : SDI In
2110-20, Session 00~14 3x for Processor Insert, 2x for free tieline 18~32 : RX
38~40 : Proc Insert 3x TX streams for Proc Insert
(out 33~35) Video TX Stream (15~17)
41 : Color Bars
1x HD / 1x 3G (on different blades) (in 41) 42 : Black 2110-20, Auto detect 1.5G/3G
Video Color Bar
(Video generator 0)
Outputs: (out 36) 1x TX stream for Color Bar
Video TX Stream (18)
Lawo Case Study: Full-IP OB Truck Times Two 00~09: SDI Out
18~37: TX
2110-20, Auto detect 1.5G/3G RTBF in Belgium
Video Black 1x HD / 1x 3G (on different blades) (in 42)
38~40: Proc Insert
(Color Corrector 3) (out 37) 1x TX stream for Video Black Video TX Stream (19)
2110-20, Auto detect 1.5G/3G
(out 38~40) (in 38~40)
Processor Insert
Color Corrector Framesync/
(00~02) Video delay (18~20)
C100 CONFIG RTBF – Streaming blades 1~12
II. Video inside the C100 Audio Configuration
Similarly detailed explanations were given for two other other projects, up to eight color correctors are possible.
important blocks inside each C100 blade: video and RTBF uses:
22x TX streams for SDI inputs Audio TX stream (00~21)
audio. • 12x C100 blades for streaming/gateway functionality, Possibility to switch off SRC for Dolby E 24-bit audio 2110-30 (8-channel)
processing, glue and color correction (for a total of
Audio TX stream (50~71)
The video “section” consists of SDI inputs, incoming 36 processing blocks), SDI Inputs (max 00-10)
Audio SRC (00~10)
2110-31 (8-channel)
(16 channels)
(16 channels)
video streams (ST2110-20), video delay as well as a • 6x external stageboxes with V__matrix Silent Frames Auto detect 1.5G/3G
Color Bar and a Video Black generator, both of which that handle streaming tasks, Audio Gain
Audio Generator 1kHz to create a audio ramp Mono Audio Matrix 1 Mono Audio Matrix 2
are created internally by the blade. (Audio Gain 0) Mono Audio Matrix 0
• 9x C100 blades running vm_dmv distributed for audio shuffling Audio Delay (00~10) for audio splitting for audio combining
DolbyE Alligner
(Audio Delay 24~34)
SDI outputs (00, 01/10~17)
(16-channel)
(16 channels) 1 x 16ch —> 2 x 8ch 2 x 8ch —> 1 x 16ch
(in 00~21) AV Matrix 1 (out 00~19) (10 x 16 channels) Auto detect 1.5G / 3G
multiviewers (36 head outputs, 210 video inputs). Audio Generator 440Hz
Audio Gain
to create a audio ramp
Fixed routing at startup
Fixed routing at startup for block routing
These inputs are connected to a matrix where any (Audio Gain 1) (8 channels)
Fixed routing at startup
signal can be routed to any destination. In RTBF’s Even though all installed C100 blades share the exact Audio Gain
Inputs :
00~21: SDI In
case, the matrix sends out SDI signals andCONFIG
C100 video RTBF – Streaming
same configuration,
blades 1~12 the VSM control system has been Audio Generator 400Hz to create a audio ramp
(Audio Gain 2)
36~65: RX In
76~81: Proc Insert
82, 83: 1kHz
streams. programmed to only access the processing blocks of
PTP Configuration
Signal Generator 1kHz (in 82, 83)
the blades inside the OB truck—not the ones in the Outputs :
00~35 : SDI Out
The first 11 streams transport the received SDI signals stageboxes. 36~41 : Proc Insert
as ST2110-20 streams to the network,
PTP Agent 0 the next three PTP Shifter PTP Clock
40Gb - 1
carry the output signals coming from the processing This was done for practical considerations: Audio RX Stream (00~29) 30x Audio RX 8-channel (in 36~65)
2110-30 (8 channels)
20x for SDI outputs
insertion blocks (color correction and video delay). disconnecting (or not connecting) a stagebox also Session 20~49
6x for Processor Insert
4x for free tieline
These blocks can be freely assigned to any incoming removes the color correctors, etc., it contains. Better
System Clock in 76~81
essence (SDI or IP). not to count on them in the first place.
Processor Insert
6x TX streams for Proc Insert Audio TX stream (36~41)
24-bit audio 2110-30 (8-channel)
Audio Delay (18~23)
For the RTBF OB truck project, each C100 blade was (6x 8-channel)
6x TX streams for Proc Insert Audio TX stream (86~91)
configured to provide three such processing blocks. In 32-bit audio (Dolby E) 2110-31 (8-channel)
2x TX, 1kHz
C100 CONFIG RTBF – Streaming blades 1~12 24-bit audio
Audio TX stream (42, 43)
2110-30 (8-channel)
Video Configuration
2x TX, 1kHz Audio TX stream (92, 93)
32-bit audio (Dolby E) 2110-31 (8-channel)
FramePhaser (in 00~10) (out 00~09)
SDI inputs (00~10) SDI Outputs (00, 01/10~17)
Framesync
Auto detect 1.5G/3G Video Matrix 1 Auto detect 1.5G / 3G
Video delay (0~10)
(out 18~28) 11x TX streams for SDI inputs
Inputs : Video TX Stream (00~10)
Video RX Stream (00~14) 10x for SDI outputs (in 18~32) 2110-20, Auto detect 1.5G/3G
00~10 : SDI In
2110-20, Session 00~14 3x for Processor Insert, 2x for free tieline 18~32 : RX
38~40 : Proc Insert 3x TX streams for Proc Insert
(out 33~35) Video TX Stream (15~17)
41 : Color Bars
1x HD / 1x 3G (on different blades) (in 41) 42 : Black 2110-20, Auto detect 1.5G/3G
Video Color Bar
(Video generator 0)
Outputs: (out 36) 1x TX stream for Color Bar
Video TX Stream (18)
00~09: SDI Out 2110-20, Auto detect 1.5G/3G
18~37: TX
Video Black 1x HD / 1x 3G (on different blades) (in 42)
38~40: Proc Insert
(Color Corrector 3) (out 37) 1x TX stream for Video Black Video TX Stream (19)
2110-20, Auto detect 1.5G/3G
(out 38~40) (in 38~40)
Processor Insert
Color Corrector Framesync/
(00~02) Video delay (18~20)
12 13
C100 CONFIG RTBF – Streaming blades 1~12Lawo Case Study: Full-IP OB Truck Times Two
III. Audio inside the C100
All audio streams inside the OB trucks had to be available in the 24-bit stream. For streams going to RTBF’s mc2 56 console, on the
ST2110-30 and ST2110-31 (for Dolby E) formats. Additionally, other hand, VSM picks the 32-bit variety.
RTBF had expressed the desire to work with 8-channel audio
streams, which made things slightly more complex. Lawo also “built” an AV matrix into RTBF’s C100 blades
that switches streams in groups of eight from any source to
ST2110-30 audio streams can be sample-rate converted any destination: SDI inputs, signal generator on a variety of
where necessary. The provided SRC blocks are bypassed for frequencies, etc. The audio contained in the SDI signals can be
Dolby E streams, because Dolby E does not support sample rate sourced from anywhere—even from the patchbay at the back
conversion. of the truck, which provides 32 SDI inputs to which any desired
output can be connected: feeds coming from a satellite vehicle,
The C100 blades furthermore contain a matrix for audio external feeds, cameras, audio signals coming from the stage
reshuffling, plus audio delay processing blocks for alignment during an event, etc.
with the video delay (in ST2110, audio and video essences lead
separate lives). The audio processor inserts programmed for RTBF’s C100 blades
handle audio delays. In addition, each SDI input has its own delay
As RTBF chose to work with 8-channel audio streams, while SDI setting.
uses 16 audio channels, an audio matrix block had to be included
to split incoming 16-channel blocks into two groups of 8, which The reason for accommodating Dolby E end-to-end is that RTBF
may require multiple signal splits and combinations. wanted to keep all options open with respect to the source signals.
One likely scenario, for instance, involves connecting a satellite
As stated above, each audio input on the network is able to handle truck to the OB truck’s external patchbay. If that satellite feed
24- and 32-bit audio. The reason why 24-bit operation needed to transports Dolby E signals, the OB truck’s inputs need to be able
be provided is that EVS and Riedel devices require ST2110-30 (24 to process them. Predicting where the RTBF crew will insert such
bit). V__matrix C100 blades as well as Lawo’s mc² consoles accept signals is difficult, however. Hence the dual ST2110-30 and -31
both ST2110-30 and ST2110-31 (32 bit). scenario.
VSM, the overarching broadcast
control system used in the OB
Twins, has been programmed to
be destination-aware: depending
on where an audio stream needs
to go, VSM automatically selects
the -30 or the -31 version. When
an SDI signal needs to be routed to
an EVS recorder, for instance, VSM
automatically selects the associated
Ample space for 16 operators.
14RTBF in Belgium
Intuitive VSM Control
VSM’s “CCU” tab on the “Video X/Y” page
(see left), for instance, allows operators
to route the desired CCUs to the required
destination (video mixer, etc.). Each CCU
input provides GAIN controls that set the
audio signal connected to the camera body.
In the blue strip to the right (see below), all
of the selected source’s parameters can be
set on-screen: Dolby E on/off, Frame Phaser
on/off, Video Delay on/off, Audio Delay on/
off, etc. Changes to the available parameters
are indicated by means of orange LED
indicators below the corresponding source
button.
All aspects and areas of RTBF’s OB Twins are managed by Lawo’s
VSM broadcast control system, on a separate Cisco-based network The “Visual Link” section provides at-a-glance information about
(a so-called out-of-band control network). the routings in effect.
VSM was chosen for reasons of tight integration, smooth support Additionally, operators can create labels for each source and
for the overall solution as well as for its proven IP track record. destination right on this page: no need to deep-dive into the
“Building panels and changing settings in VSM has become so parameter tree. Any label changes are immediately mirrored to all
easy in these OB trucks that one hardly needs to spend time on relevant sections: the Sony visual mixer, Lawo multiviewers, etc.
the server anymore,” observes NEP Belgium’s Geert Thoelen.
(Most VSM functionality was programmed
remotely, due to the covid-19 lockdown, and
completed within a mere 15 days.)
Special attention has been devoted to making
the software operations “under the hood”
as transparent as possible. All VSM display
pages shown here were custom-designed for
RTBF’s IP OB trucks.
15Lawo Case Study: Full-IP OB Truck Times Two
The “Panel Build” page (see right) allows
operators to select an area inside the
truck by pressing it, and to configure the
VSM hardware panels of that area.
This allows operators to quickly change
panel layouts without altering the truck’s
basic configuration.
On the “Audio X/Y” page, operators can set
parameters related to the mc2 56 console,
including the signal assignments to the
monitor speakers , for which separate
LEVEL controls have been prepared.
The “Status” page shows pictures of all
C100 blades and other units. It can be
used to check the status of each individual
blade or device.
VSM furthermore allows to perform color
corrections and to control the mc2 56
console as well as the Nova73 router.
Thanks to this approach, the VSM
control system in RTBF’s OB Twins is
a sophisticated, highly intuitive remote
control.
16RTBF in Belgium
Other Devices and Control “RTBF’s two new OB trucks
The Sony visual mixer in each OB truck is connected directly to are among the most advanced
the Arista-based ST2110 spine/leaf network, as are the three EVS
machines used for recording, play-out and slow motion. The latter on the planet. The ST2110-
are equipped with 10Gbps interfaces.
based approach has resulted
The tender documentation specified that vision mixer control was
to be based on NMOS. As a result, the necessary IS04 and IS05 in highly flexible tools for OB
drivers were developed by Lawo’s VSM team to avoid back-and-
forth conversions between Lawo and the Sony vision mixer. The assignments of any scale.”
EVS machines, on the other hand, are controlled via Ember+,
because EVS was more experienced with that protocol. —Geert Thoelen, Technical Director,
NEP Belgium
The baseband cameras are connected via SDI to the CCUs, and
from there to a V__matrix unit. As stated earlier, the SDI cameras
will be replaced with native IP cameras at some point.
17© 2020 Lawo AG. All rights reserved. All company and product names mentioned herein may be trademarks of their respective owners.
Product specifications are subject to change without notice. This material is provided for information purposes only. Lawo assumes no liability related to its use.
HEADQUARTERS INTERNATIONAL OFFICES RENTAL SERVICE
Lawo AG BENELUX + 31 6 54 26 39 78 + 49 7222 1002 0
Rastatt CANADA + 1 416 292 0078 rental@lawo.com
GERMANY CHINA + 86 10 6439 2518
+ 49 7222 1002 0 NORWAY + 47 22 106110
sales@lawo.com SINGAPORE + 65 9818 3328
SWITZERLAND + 41 43 38868 00
UK + 44 333 444 5296
USA + 1 888 810 4468
www.lawo.comYou can also read
