Release Notes
Release Notes
Breadcrumbs

ROAD Web Clients


Component

Version

ROAD Web Clients

1.4.50

With R2024.3.0 ROAD backend is released as version 1.8.574.0. See release notes in the section “Shared Modules“. It is recommended to use those versions (or higher) in combination.

Dependencies

  • Minimum ROAD backend version 1.8.574.0

  • Minimum supported DPE Services 2.12.51.4

ROAD Scheduling: Formerly the audio formats, which you can select in the “Job Settings” section of the ROAD Scheduling client, could be configured in the “settings.json” file. This has changed in an earlier version.
Now the backward compatibility was removed. Please do the configuration inside the DigaSystem parameters (…\ROAD_Scheduling\AudioFormats).

Known Issues

  • InstaRecorder: Automatic stop level trigger doesn’t work after a manual start

  • Auto Trigger Limits cannot be set to a value below -48dB

Changes

All Clients

New Features

  • Unify login behavior and improve login screen

  • Simplify Help and About dialog

Fixed Issues

  • Changing selection of connected backend host must refresh data

  • If 1st service in “ROADServiceList” is not available, clients cannot be opened

  • Fallback to legacy DPE token fails

  • Unified configuration: Now settings.json contains only the DPE URL, all other settings are in the DigaSystem parameters - see ROAD Clients documentation

Admin client

New Features

  • Improved divider dragging mechanics

Fixed Issues

  • "Log Refresh" button doesn't work

InstaRecorder

New Features

  • Implement stop trigger popup options

  • Ensure “No Job Action” while disconnected

  • Add "No Service" indicator to inform the user when current service host is unavailable

  • Show the table alias name instead of the table’s real name

  • L+R mono recordings

Scheduling Client

New Features

  • “Ember+ Start Delay” feature for external control

  • Support filtering for table and template dropdown dialogs

  • “Auto Trigger Limits” now configurable in parameters

Fixed Issues

  • Deleting occurrence then selecting "Standby" results in error message

  • JSON Verification expects camelCase (PascalCase now also accepted)

  • Creates invalid “Ember+” config

  • Level trigger must observe only the used channels