Skip to main content
The new Core is version 4.8.0. It replaces the previous Core, the app called Server Core, and comes with the Machine Agent: one app that installs the server apps on a studio computer and keeps them running. This page lists what changed for a station, per topic: what changed, how it works now, and why. To install or move a studio computer, follow Install the Machine Agent.

Installing and looking after the server apps with the Machine Agent

  • What changed. You install one app, the Machine Agent, instead of each server app by itself.
  • How it works now. The Machine Agent installs the Core and the apps the studio needs, starts them and keeps them running. An app that is already installed is reused. An app that crashes restarts by itself. A clean computer needs nothing but the Machine Agent.
  • Why. Installing the server apps and looking after them takes less work.
The Machine Agent checks the signature of every download. It installs the Microsoft .NET runtime that the other apps need, with one Windows administrator prompt per computer, and adds the Windows firewall rule for the Core.

Moving a studio from the previous Core to the new Core

  • What changed. On Windows, the previous Core moves the computer to the new Core by itself.
  • How it works now. With automatic updates on, the move happens in the night after the release. Without automatic updates, it starts when someone updates the Core to 4.8.0 by hand. The studio, its settings and its Cloud connection are kept, so you don’t enter a connect code. During the move only the Core restarts, for about 30 seconds. Output Players keep running. The previous Audio Manager is stopped and replaced by the new Audio Manager.
  • Why. Nobody has to be at the studio computer for the move.
When the move fails. When the new Core is not running properly within 5 minutes, the Machine Agent starts the previous Core again, so the studio keeps working. The move is tried again 24 hours later, at most 3 times in total. After the move. Once the new Core runs, the previous Core is removed. The two never run next to each other. Integrations that use the local API of the previous Core keep working: the new Core answers the same routes. See Legacy routes. End of support. VRA supports the previous Core and the previous Audio Manager until 21 December 2026. The notice is on status.visualradio.cloud. Check a studio’s versions. In the Cloud, open Settings → Studio → Overview to see which version each app of the studio runs.

Changing a studio’s station without restarting the Core

  • What changed. The Core no longer restarts when a studio changes to another station.
  • How it works now. Outputs, scheduling, macros, automations, media, signals and item groups follow the new station. The connections to the video switcher, audio, cameras and GPIO stay up. The Cloud and the Rack show the progress per app.
  • Why. Stations that share a studio hand over without the switcher, audio and camera connections dropping.

Running several studios on one computer

  • What changed. Starting Cores as master and slave is replaced.
  • How it works now. One computer runs several studios, with one Core for each studio. A computer that ran several studios with the previous Core keeps them: the existing setup is imported. A studio has one Core. A second Core that connects to the same studio is refused and stops.
  • Why. Each studio has its own Core, so two Cores can never control the same studio.

Controlling the Core with the Core API v2 and Bitfocus Companion

  • What changed. The Core has a new local API, the Core API v2, for control surfaces and scripts like a Stream Deck, Bitfocus Companion or a SKAARHOJ panel.
  • How it works now. Each device gets its own token, read only or read and control. You can limit a device to certain features, pin it to one station and tie it to a fixed IP address. The API covers studio state, signals, macros, the status of automations, outputs, cameras and station variables. Access from other devices on the network is off until you turn it on.
  • Why. You decide per device what it may do, and a button built for one station cannot fire on another.
Besides HTTP, the Core API answers over TCP on port 3003 and OSC on port 3004. Both are off by default. Plain-text routes answer one value like onair, 1 or OK, for devices that cannot read JSON. There is a Bitfocus Companion module for the Core. It is a download and needs Companion 5.0 or later.

Core API

Tokens, routes and access for the Core API v2.

Bitfocus Companion module

Install the module and connect it to the Core.

Station safety

Keep a button on the station it was built for.

TCP and OSC

Call the Core API without HTTP.

Switching automation on and off with Signals

  • What changed. Audio auto switching and camera automation each have a signal per studio, Audio Director and Camera Assist, that your own systems can set.
  • How it works now. A dashboard button, a Stream Deck or a script through the Core API v2 turns automation off for an item and back on. Each signal records what set it last. With a Pro license you add your own signals and use them in automations. See Signals.
  • Why. The rest of the building can take automation out and see why the cameras stopped cutting.

Video switchers, consoles and radio automation in the new Core

  • What changed. The links with ATEM, vMix, OBS, TriCaster and Videohub are rebuilt. With a TriCaster, the Core now reaches each M/E, the DSKs and macros.
  • How it works now. From the Cloud you can set a GPIO logic on Ember+ and Livewire consoles, with a pulse of 10 to 10000 ms. Setup guides per switcher are under Video switcher configuration.
  • Why. A TriCaster studio can use more of its switcher from VRA.
Every radio automation link of the previous Core works in the new Core. See Link radio automation. The Core’s connections to the Cloud and to the local network recover by themselves. An app that starts without internet keeps trying to connect.

The improved Rack

The Rack is the Core’s window on the studio computer.
  • What changed. The Rack has 3 layouts and shows more of the studio.
  • How it works now. Choose a 2U, 4U or full height layout. The Rack shows the mics, what is playing now with its cover art, the upcoming programs and a camera wall. The camera wall keeps the last picture of each camera, with its time. Every key shows whether its action is pending, confirmed or failed. Camera and angle keys ask for a second click.
  • Why. An operator sees whether a key press arrived, and a camera does not cut by accident.

Automations page and commands while the studio is off air

  • What changed. The Automations page shows which automations are active and the last 10 runs of each. On-air and off-air changes in the schedule arrive as one transition.
  • How it works now. Scheduling runs once per studio, in the Core. Commands can run while the studio is off air. That is an optional setting and it is off by default.
  • Why. You see on one page which automations are active and what they did.

What moved or is not carried over to the new Core

  • PTZ camera control is now Camera Assist. The new Core does not move PTZ cameras. Camera Assist does. See Cameras and Migrate from legacy cameras.
  • The legacy camera setup is gone from the Core. That includes vMix virtual cameras and the pre-shot before a cut in the Core.
  • Cyanview RCP is not carried over. The new Core has no Cyanview RCP link.
  • The classic Output Player is unchanged. The new Core does not replace it, and it keeps running during and after the move.
  • Only the move rolls back. A regular update of the new Core does not roll back by itself.
  • A studio computer needs internet. The new Core does not support a studio computer without an internet connection.