Skip to main content

Release v1.2.0

v1.2.0 overview

Via-B v1.2.0 makes a clean Windows installation ready for the normal Opta-to-MagicSoft workflow without support editing a database or rebuilding mappings by hand.

Highlights

  • Adds an editable Default Thai League profile with independent English and Thai mappings for every production graphics output.
  • Installs the matching MagicSoft reference projects in the configured graphics folder automatically.
  • Explains every setup problem on the module card, module page, and Operate screen.

Changes

Added

  • Added twelve English and Thai MagicSoft reference projects and their default mappings.
  • Added automatic project installation at startup and after a MagicSoft destination change.
  • Added protected Opta credential setup on first licensed startup and a manual Refresh managed credentials action.

Changed

  • Fresh installations use the normal same-workstation MagicSoft connection defaults.
  • Pasted Windows project paths now accept and remove one matching pair of outer quotation marks.
  • Project XML location and generated-image output location are shown and validated separately.

Fixed

  • Fixed clean installations leaving production modules unmapped and unable to run.
  • Fixed module screens hiding the controls needed to correct a destination or mapping.
  • Fixed unclear blocked-module, MagicSoft path, and Opta credential messages.
  • Fixed custom player, club, and on-air values using inconsistent status colors.
  • Fixed managed credential refresh rejecting normal release-version labels.

Operator impact

After installation, configure the Opta and LiveManager connections, open the supplied English or Thai projects in MagicSoft, select a match, and run or switch the match as normal. Via-B prepares the project files and default mappings without a separate download-and-scan step.

Validation

  • The complete Windows and Linux release pipeline passed for the released source.
  • Signed English and Thai Windows installers passed installed-package startup checks.
  • Package checksums, updater signatures, platform signatures, SBOMs, and verification reports passed.
  • Clean first-run setup and English and Thai MagicSoft playback were tested with the production workflow.

Artifacts

  • Windows MSI and setup packages, including the Thai installer.
  • Linux AppImage and DEB packages.
  • Versioned checksums, signatures, public signing material, SBOMs, verification reports, and startup-smoke evidence.