[JIML] Release Notes v.6.1

Improved performance when recording HEVC/H.265. Additionally, the correct profile is automatically selected depending on whether the input source has 8 or 10-bit video.
Fixed a bug that caused memory consumed by Just In Engine to increase continually when an NDI source without audio was selected, eventually causing a crash and/or the system to run out of memory.
NDI sources that switch between sending video only without audio and then video with audio are now supported.
Golden master.

Unexpected metadata values are no longer embedded when recording to a MOV container.
Golden master.

Golden master.
The active license is now synchronised with the online license every 30 instead of 7 days.

In addition to the automatic baseline, main and high H.264 profiles, you can now select any of the currently available specific profiles. The previous profiles such as “High” have been renamed like “High Auto Level”.
Fixed a minor typo in the H.264 and H.265 option panels.
Removed legacy calls from the API, added the “tal-ingest-engine-override-naming-preset” property to the startRecordingWithFilename method’s body metadata.
When calling the startRecordingWithFilename and stopRecording API calls, the metadata keys as specified in the documentation can now be used and are correctly mapped internally.

Updated AJA drivers to version 17.0. Please update your system drivers to this version if you are using AJA hardware.
When running Just In Mac Lite for the first time on macOS 14 Sonoma, you are now asked to grant access to your calendars to enable scheduled recording.

Set the minimum deployment target to macOS 12.0 (Monterey). The Apps included with this release will no longer run on versions of macOS older than 12.

Added a new API call at /v3/api-docs that returns a JSON description of the API in the OpenAPI v3 format. This can be imported into applications or services that support this format such as Postman in order to test the API.
Fixed a bug that resulted in changes in the inspector (e.g. to edit the name of the recording) being ignored when using the keyboard shortcut to start recording. In this case, the recording was named using the previous value from the field and not the updated value.

Fixed a bug when calling a REST API method with an invalid or missing channel name that resulted in no response from the API.
Added /ingest/startChannel and /ingest/stopChannel REST API methods to start or stop a given channel. Combining stop and start results in a channel being restarted.
NDI channels may now be used in the “Schedule” mode in addition to “Crash”. This means that recording can be pre-scheduled in Calendar.
Fixed a bug editing a naming preset where sometimes changes to the preset were ignored (de-selecting and re-selecting the preset resulted in any changes being lost).

Fixed a bug that resulted in the multi-viewer audio bars showing incorrect levels for SDI inputs.
Fixed a bug that resulted in recording files having incorrect audio levels for NDI inputs.

Fixed a bug that resulted in a channel process configured to use an NDI source burning 100% CPU (a single core) whenever the source wasn’t available. This is turn could cause other unexpected behaviour such as just:control being unresponsive or very slow.

Fixed a bug that resulted in unexpected results using metadata sets, event presets or custom overlays.

Naming presets now support folder creation using the new “/” token, allowing you to create naming presets with one or more sub-folders relative to the destination preset path. The names of the folders can also use any of the naming preset features such as date, time, metadata and user variables. The date and time tokens can now be configured individually, and there are new formatting options for textual day and month formatting (e.g. “Mon”, “Monday”, “Jan”, “January”). Additionally, the naming of scheduled events has now changed. Instead of using tokens such as <Date> or <Channel> in the title of the calendar event, you should create a naming preset with the specific formatting you want, and the “Name” token in the naming preset will be set to the calendar event’s title. Please refer to the user manual for more detailed information.