[JIM] Release Notes v.2025.3.x
Version 2025.3.x:
2025.3.2.GM.1357 - PUBLIC RELEASE
In the “Activation” tab in the configuration panel, if there is a valid license the license key is now displayed for your reference.
Updated Blackmagic Decklink drivers to Desktop Video 15.3. If you are using a Decklink device, please update your system to this version.
Updated Blackmagic ATEM drivers to 10.1.1. If you are using an ATEM device, please install ATEM Switchers 10.1.1 update.
Fixed rare AJA frame overflow when using the API extensively.
Updated to NDI 6.2.1 for improved performance and stability when using NDI sources.
Fixed a rare issue using burnt-in timecode or a custom overlay.
Fixed a rare issue recording H.264 from a 10-bit input.
LTC timecode over audio improvements.
2025.3.1.GM.1340 - INTERNAL RELEASE
Fixed a memory leak when recording 10-bit video to H.264.
Fixed a rare issue when starting a new recording, or chunking an existing recording.
2025.3.0.GM.1339 - PUBLIC RELEASE
Improved API behavior under high load.
2025.3.0.GM.1338 - RC RELEASE
Fixed an issue in the “/ingest/recordingPaths” API end-point that would sometimes result in paths being returned with a file extension and/or the incorrect path. Now an error is returned until all writers are fully configured and the first frame of all files has been written to ensure that the full and correct paths are returned for all files.
2025.3.0.GM.1337 - RC RELEASE
Added a new “/ingest/recordingConfiguration” end-point to the API that can be used to query the current capture and destination presets configured for recording on a given channel.
2025.3.0.GM.1336 - RC RELEASE
Updated DMG background.
When recording to a QuickTime Classic or Harmonised container, if the filename is changed due to a conflict with an existing file (e.g., by adding an index like “_2” at the end), the correct filename is now passed to any events executed for the recording.
Updated, more consistent naming of frame-rates for various XDCAM capture presets.
Added a new “/ingest/recordingPaths” end-point to the API that can be used to query the paths of all files currently being recorded.
Version 2025.2.2:
2025.2.2.GM.1326 - PUBLIC RELEASE
Updated the EULA.
When writing file metadata, all fields from the current naming preset (e.g., counter, time, date) are now correctly written with the correct values.
2025.2.2.GM.1325 - INTERNAL RELEASE
The “Help > Just In Help” menu now opens the correct online user manual again.
When setting up a new device with the example metadata set selected, the default destination preset now also includes a metadata path so that metadata is written when selected in Just Control.
When setting up a new device with the example metadata set selected, the metadata set now uses the correct field for date/time.
When setting up a new device with the example metadata set selected, the metadata set now has default values set for date, time, and date/time fields, so that values are correctly written to the metadata even if not changed in the inspector.
Fixed an issue that could result in the time displayed in the metadata group in Just Control’s inspector being offset by an hour.
Version 2025.2.1:
2025.2.1.GM.1324 - PUBLIC RELEASE
It is now possible to edit values in the “Metadata” inspector group, even if the user has locked the inspector.
2025.2.1.GM.1323 - INTERNAL RELEASE
It is no longer possible to reorder the columns in the audio mapping popup window when configuring a capture preset.
2025.2.1.GM.1322 - INTERNAL RELEASE
Fixed an issue related to NDI channels with “SMPTE Timecode” selected.:
2025.2.1.GM.1321 - INTERNAL RELEASE
NDI channels now have an additional “Timecode mode” settings with the options “NDI UTC Timestamps” and “SMPTE Timecode”. The former expects frames with standard NDI UTC timestamps, as provided by the majority of NDI devices. The latter expects SMPTE timecode encoded as 100ths of a nanosecond. This may be useful in conjunction with some devices such as the AJA Bridge that take embedded SDI SMPTE timecode and converts it for use with NDI. When “SMPTE Timecode” is selected for the channel, “SDI Embedded” is additionally available as a timecode source, allowing you to see the embedded timecode sent with the stream.
2025.2.1.GM.1320 - INTERNAL RELEASE
Fixed an issue when starting a recording to a QuickTime Harmonized container.
2025.2.1.GM.1319 - INTERNAL RELEASE
Improved growing file compatibility with Blackmagic DaVinci Resolve using the QuickTime Harmonized container.
2025.2.1.GM.1318 - INTERNAL RELEASE
Updated the EULA.
Improved logging. Instead of writing a single log file every 24 hours, a file is now written each hour. This prevents missing logs on systems with heavy log loads (e.g., with other software or services installed that have excessive logging).
2025.2.1.GM.1317 - INTERNAL RELEASE
After recording using the REST API call with “tal-ingest-engine-override-naming-preset” set to true, starting a new recording with Just Control now correctly uses the naming preset specified for the channel instead of overriding the naming preset for all subsequent recordings.
Fixed a crash connecting to certain SRT or UDP streams.
Fixed a bug that resulting in an error when starting a HLS recording.
When recording to a QuickTime Classic or Harmonized container with metadata, the filename in the metadata now includes the “.mov” file extension as with other containers.
Version 2025.2.0:
2025.2.0.GM.1316 - PUBLIC RELEASE
Updated all links to the v2025.2 documentation.
Reduced log file sizes when using SRT/UDP streams
2025.2.0.GM.1315 - INTERNAL RELEASE
Fixed additional video/audio sync issues with SRT/UDP streams.
2025.2.0.GM.1314 - INTERNAL RELEASE
Fixed video/audio sync issues with SRT/UDP streams.
2025.2.0.GM.1313 - INTERNAL RELEASE
When editing a HTTP event with a payload, the editor field disabled smart quotes to prevent single and double quotes being automatically changed into invalid quotes.
When more than one instance of Just Control is connected to a just:in mac channel, the number of connections is now shown in Just Control’s “Connections” inspector tab. This has always been the case for just:in linux channels.
2025.2.0.GM.1312 - INTERNAL RELEASE
Fixed a bug that resulted in unexpected behaviour using an external audio device with a negative offset.
The /ingest/splitMovie API call returns 400 Bad Request if the channel is not currently recording.
Just Control now shows the correct “TC” button and timecode in the inspector if an /ingest/stopRecording with a stop timecode has been sent to the channel. This corrects an issue stopping the recording in Just Control when stop on timecode was active for the channel.
Removed the restriction where only a single system running Just Control could connect to a channel at the same time. Now multiple Just Controls on multiple Macs can all connect to and control the same channel.
2025.2.0.GM.1311 - INTERNAL RELEASE
Fixed an issue that resulted in unexpected behaviour using an external audio device with a negative offset.
2025.2.0.GM.1310 - INTERNAL RELEASE
This build is only supported on Apple Silicon Macs, older Intel Macs are no longer supported.
This build is only supported on macOS 13.5 and higher. Older versions are no longer supported.
Removed the “TOA System Checker” App from the DMG, please refer to the relevant “Getting Started” documentation online for detailed information related to system requirements.
Added new Growing Files container for recording within Adobe Premiere Pro and DaVinci Resolve.