CRESASTREAM AUTOMATION
All updates →
ANNOUNCEMENT
Private Testing is planned VERY SOON

Selected candidates will soon be able to give the suite a real world test run and provide their feedback and opinions!

← Back to all updates

DEVELOPMENT UPDATE

CRESA's Music Visualizer Goes Global

UPDATEPUBLISHED

CRESA begins moving music visualization out of individual scenes and onto a shared audio source, allowing the visualizer to follow the broadcast's music rather than a single presentation.

Music had already been part of CRESA for a while. Spotify integration, playback information and browser presentation had all started taking shape much earlier in development. By 21 August, attention turned to something else:

Why should music visualization belong to a particular scene?

Moving Beyond A Scene-Specific Visualizer

Earlier visualizer work was tied more closely to individual broadcast presentations, including BRB. That worked, but it meant the visualizer was being treated as part of a scene rather than part of the music system itself. The next step was to begin sharing that visualization across the broadcast.

Instead of each presentation needing to understand the music independently, CRESA could work towards one common visualizer driven by a shared audio source.

MusicAudio Becomes The Source

The visualizer was moved onto MusicAudio as its global source. That was an important architectural change. The presentation no longer needed to care whether it happened to be sitting inside the scene that originally owned the visualization. If CRESA could observe the shared music audio, other presentations could consume the same underlying signal.

That made the visualizer much easier to reuse across different parts of the broadcast.

Making The Meter More Reliable

Moving to a shared source also meant the audio tracking itself needed more attention. Meter tracking and diagnostics were hardened so CRESA had a more dependable picture of the audio signal it was trying to represent. Work also kept the visualizer provider independent rather than tightly coupling it to one particular music integration.

That separation mattered. Spotify might provide track information and playback state, but the visualizer's job was increasingly about the audio actually moving through the broadcast. Those were related problems, but they did not need to be the same system.

One Signal, Multiple Presentations

This was another small architectural shift with much bigger implications later. CRESA was gradually replacing scene-specific implementations with shared services and common sources of truth. Music visualization was now heading in the same direction. Instead of asking each scene to build its own version of the music experience, CRESA could begin treating music as something the entire broadcast could understand.

The visualizer was no longer watching a scene. It was starting to listen to the broadcast.

Back to all updates