CRESA's Control Centre Starts Taking Its Modern Shape

The idea behind CRESA's Control Centre had been around for a while. Bring the controls needed during a broadcast into one place and reduce the amount of jumping between separate tools. By 28 August, that idea was beginning to look much more like the Control Centre CRESA would continue building around.

Reworking The Dock

The first part of the work was a broader Dock rework. CRESA had accumulated considerably more functionality since its original controls were created, and the operator interface needed to catch up. Features were no longer isolated actions. They had state, health, presentation behaviour, diagnostics and increasingly complex relationships with OBS. The interface needed to represent more than a collection of buttons.

Control Centre Phase 2

The next step was the beginning of Control Centre Phase 2. Dedicated areas for Health and Simulation were introduced alongside the operator controls. Health could begin surfacing information about the state of the suite rather than leaving problems buried inside individual services.

That included work around:

• Overall system health
• Presentation health
• Browser diagnostics
• Problem reporting
• Safe-state controls

The Control Centre was starting to answer an increasingly important question:

Is the broadcast actually doing what CRESA thinks it is doing?

Bringing Simulation Lab Closer

Simulation Lab also began moving closer to the operator interface. The new Control Centre shell gained support for Lab capabilities, feature selection, current state, preview access and simulation availability. This didn't mean every development tool had suddenly been replaced. Instead, the boundary between operating CRESA and testing CRESA was beginning to shrink. The same interface could increasingly expose both.

Expected Versus Actual

As CRESA gained more automation, simply knowing what a feature had been told to do wasn't enough. The suite also needed visibility into what was really happening. A feature might expect a scene to be active. A browser presentation might expect itself to be visible.

OBS might disagree. Health and diagnostic surfaces created somewhere for those differences to become visible. That would become increasingly important as the suite moved towards more formal validation later in development.

From Dock To Control Centre

This was one of the clearer changes in how CRESA itself was being presented. The original Dock had been useful as a collection of broadcast controls. The Control Centre was becoming something broader.

A place to operate the broadcast.

A place to inspect it.

A place to test it.

And eventually, a place to understand when something had gone wrong.

CRESA wasn't just gaining more controls. It was starting to build the cockpit around them.