Brio's comprehensive broadcast feature set supports a wider breadth of broadcasters while retaining the same market-leading levels of quality and customer support which Calrec is renowned for.
The smallest in Calrec's Bluefin2 family, Brio's control surface is unlike any other console. Available in two sizes; Brio 36 with a 36 fader dual-layer surface and the Brio 12 with a 12 fader dual-layer surface at only 498mm wide, both provide more faders in a given footprint than any other comparable audio console.
Based on Calrec's 20 years of digital development, Brio's uncluttered, compact and configurable surface gives instant access to a large number of audio paths, whilst an intuitive 15.6" HD touchscreen UI provides quick access to more in-depth control. A bank of illuminating hardware rotary controls give fast and precise control over parameters displayed in the touchscreen UI.
Brio is a mixing console completely focused on the needs of broadcasters. This level of scalable and managed I/O, comprehensive monitoring, surround sound and high bus quantities provides a level of dedicated broadcast functionality that has never been available at this level.
As the market calls for more and more audio mixes to support online content, smaller consoles that possess pure live broadcast features are increasingly desirable. Products in this sector have traditionally had basic capabilities and are not ideally suited to broadcast environments. Brio is the first application-specific alternative.
Brio's compact size means it is extremely portable and quick to install, making it ideal as a general purpose workhorse that can be used as and when needed, and its connectivity with other Hydra2-compatible equipment makes it even more versatile.
Brio is entirely self-contained. Brio 36 even provides analogue and digital I/O, and GPIO, built into the surface. Additional expansion I/O slots are also fitted to allow for further I/O to be connected. A Hydra2 module can also be fitted to connect to and share audio over Calrec's Hydra2 network.
This means Hydra2's sophisticated management facilities can be utilised for network-wide control, including interfacing with multiple IP networks. This protects the system against any future formats that may emerge and allows the console to sit on multiple networks simultaneously if desired.
HIGHLIGHTS:
- 36 x dual layer faders - 100mm, motorised, with PFL overpress
- DSP - Freely configurable on the fly, operates at 44.1, 48, 88.2 and 96kHz
- Full dynamics on every input channel and group path
- 6 band EQ available on every Input Channel, Group, Aux and Main path
- Calrec Hydra 2 Card allows for connection to any Calrec Hydra 2 audio network
PRICE ON APPLICATION
Surface
- 36 x dual layer faders - 100mm, motorised, with PFL overpress
- 1 x assignable user rotary control per strip
- 2 x assignable user buttons per strip
- 12 x assignable global user buttons
- Compact 892mm x 892mm control surface
Dimensions
- Height: 270 mm
- Width: 892 mm (830 mm with slim trim option - available on request)
- Depth: 892 mm
DSP/Multiple Sample Rates
- Freely configurable on the fly, operates at 44.1, 48, 88.2 and 96kHz Path Processing
- Stereo and 5.1 path spill leg access and independence for Routing, Input, EQ, Dynamics , Inserts and Pan settings via the ‘Full Path’ button
- Second compressor:-Multi-band Compressor/Limiter with single or three band operation
- Ducker mode added to the Expander/Gate module for Channels and Groups
- Selectable sidechain source (“key input”) for dynamics processors. The Expander/Gate/Ducker & Comp/Lim1 processors of all Input Channel and Group paths can be keyed by mono audio from other paths on the surface
- Path delay: up to 5.4 s available per path from a pool of 64 mono legs, as above.
Networking
- Support for Hydra2 connection to Apollo/Artemis/Summa/Router cores that are running V8.0.1 software and above for multi-console networking.
- Changeable System ID:-Brio consoles ship with a factory set ID of 192.1. If connecting them to a multi-console Hydra2 network, their system ID should first be changed, to be a unique ID amongst all the consoles on the network. Networked consoles should not use IDs starting with 192*. Note: the second part of the system ID is used to determine the internal I/O’s HID. The second part therefore needs to be unique amongst Brio36s, regardless of whether they have a unique first part in order to differentiate their I/O. Any existing internal I/O patching will need to be re-made after changing I/O ID.
- H2Hubs connected to a standalone Brio should be given an ID greater than 1* (using the DIP switches on the rear of the hub).
- I/O connected via H2Hubs will not update software – when upgrading software, each I/O box requires connecting directly to the Brio console one at a time, in order to upgrade them.
- H2Hubs also need a direct connection to a Brio in order to update their software, and require both primary and secondary to be connected in order to reprogram both primary and secondary modules within the H2Hub.
*Console IDs of 192.X can be used, however there will be conflict if any H2Hubs are connected that have an ID that matches X. It is therefore recommended not to give Hubs an ID of 1 as this will conflict with a factory default Brio on 192.1. It is also recommended not to use 192 if connecting to a larger, multi-console network, to avoid such potential for ID conflicts.