Console and Operator App
Use the Via-B desktop window to select matches, configure graphics, and send updates to MagicSoft. You can also open the same interface in your browser.
For the complete match-day sequence, see the Operator Guide.
Start, hide, reopen, and quit
- Start Via-B Operator App from the Windows Start menu.
- Watch the startup list advance through License, Update, Database, Migrations, Backend, and Console.
- Closing the window hides Via-B to the system tray; it does not stop the backend.
- Select Open Via-B from the tray to restore the desktop window.
- Select Open in browser to open the same local console in the default browser.
- Select Quit Via-B to stop the app and its automatic updates.
Starting Via-B while it is already running brings its window to the front.
Find a screen
The left navigation contains:
- Operate: the selected match, active profile, scheduled graphics, and actions that need your attention
- Metrics: operational measurements and history
- Delivery: updates being sent to MagicSoft and the results of previous sends
- Modules: module readiness, settings, dependencies, and generation actions
- Mapping: MagicSoft project scanning, source-to-target mappings, and validation
- Simulation: controlled non-live testing
- Logs: operator-visible application logs
- Support: download a support package and check license or update results
- Settings: Opta credentials, the MagicSoft connection, and other app settings
Check app status
The top bar and tray icon show the status of four parts of Via-B:
| Position in the tray icon | Component | What it describes |
|---|---|---|
| Top left | Database | The database that stores your settings and match data. |
| Top right | Backend | The part of Via-B that fetches data and generates graphics. |
| Bottom left | Destination | The connection to MagicSoft CG and its loaded project. |
| Bottom right | Delivery | Sending updates to MagicSoft. |
If Via-B reports a problem, open Operate and read Priority actions for the explanation and the available action. Use Delivery to inspect a failed send or Logs for its error details.
The tray menu also exposes the active match, profile variation, current primary action when available, Settings, application data, startup log, backend restart, and quit actions.
Desktop versus browser
Both views share the active match, profile, mappings, settings, readiness, and recent events. Use the desktop window for native file selection. A browser can accept a pasted path only when the installed Windows backend can read it.
Choose MagicSoft project files and graphic folders on the Windows computer or an accessible network drive.
Change settings
Configure Via-B through Settings. Values save after you stop typing. Wait for the save result before leaving the page. Changing the LiveManager connection in the desktop app also restarts the local backend to apply it. Wait for the app to reconnect before continuing. For other settings, use the restart action if the page says a restart is required.
Saved credentials stay hidden. Keep them private when sharing screenshots or asking for support.
Receive Windows notifications
Windows notifications start on. Updating from an older version turns the saved setting on once; if you turn it off afterward, Via-B keeps that choice. Open Settings > Windows notifications to choose which events to receive. Via-B can report scheduled preparation, generation and delivery while minimized.
Click Send test notification and check the Windows banner or Notification Center. If it does not appear, click Open Windows notification settings and allow notifications for Via-B. Windows Do Not Disturb or full-screen rules can hide banners. You can also follow the work in Operate > Scheduler.
Clean generated files
Open Settings > File cleanup to remove current and previous generated graphics and their saved copies. Imported artwork and settings are preserved. Use this after you have finished using those graphics in MagicSoft; generate them again before you need them next.
The top bar shows blue progress during cleanup. Windows notifications report the start and completion, including file counts. You can keep using Via-B: cleanup waits for publication and yields when a new Run starts.
Clean files on application exit starts off. Enable it to perform the same cleanup when you choose Quit Via-B. Closing the window only hides the app and does not perform exit cleanup.