6.1.0.GM.1202
Removed irrelevant “Invalid XML” errors in just:control related to running a port service scan on a channel’s port.
6.1.0.GM.1201
Improved stability in the API server at port 8080.
6.1.0.GM.1200
Resolved an problem that could cause performance issues recording H.264 or H.265 (HEVC) on certain systems.
6.1.0.GM.1199
When using a Blackmagic device in UHD (e.g. a DeckLink 8K Pro), the first 16 audio channels are now captured instead of just the first 8. Additionally fixed corrupted audio and/or crashes recording with a capture preset that specifies more audio channels than being currently captured from the input device.
6.1.0.GM.1198
The API exposed for just:in Mac now implements the Cross-Origin Resource Sharing (“CORS”) mechanism, in particular the HTTP “OPTIONS” method, thus allowing a browser-based user interface to connect to multiple channels with different IP addresses.
6.1.0.GM.1197
API requests sent with an “Origin” header field now return “Access-Control-Allow-Origin” in the response. This means that the machine’s IP address and “localhost” are both valid and can be mixed in calls from a web browser.
Calls to /ingest/startRecordingWithFilename now have additional checks for valid channel configuration and valid signal before execution, and a “400 Bad Request” is returned in the channel cannot record. These checks mirror those already in place in just:control to prevent a channel entering an invalid state.
6.1.0.GM.1196
An interactive “Swagger UI” for testing the API is now published at “/swagger-ui/index.html” on the system running Just In Engine.
Most “400 Bad Request” responses now include an “error” property in the response body to indicate the reason that the request failed.
6.1.0.GM.1195
Updated the OpenAPI specification published at “/v3/api-docs” to include the latest changes related to naming presets.
Fixed a bug that resulted in a “400 Bad Request” response to an API request with a body larger than 2KB.
All API requests are now fully type-checked against the OpenAPI specification.
Sending an “/ingest/startRecordingWithFilename” request now results in a “400 Bad Request” response if the channel is already recording. Other related calls (e.g. changing naming, capture or destination preset) also result in a “400 Bad Request” response while recording.
Sending API requests to a disabled channel now result in “400 Bad Request” responses.
Fixed naming inconsistencies between just:in Mac and just:in Linux, all requests to the just:in Mac API now match those specified in the OpenAPI documentation.
6.1.0.GM.1194
Resolved a memory leak when writing to an AVFoundation container.
6.1.0.GM.1193
Fixed a memory leak and resulting crash caused by an NDI source not matching the channel’s specified format (e.g. frame-rate, resolution, scan).
6.1.0.GM.1192
When using an AJA device with LTC attached to the card’s LTC port, it is no longer necessary to select the correct timecode source in the AJA Control Panel. Now simply selecting the timecode source in just:control will automatically configure the AJA device to use the LTC port timecode.
Golden master.
6.1.0.GM.1191
Fixed a bug that resulted in NDI channels reverting to Computer Time timecode source each time the channel was started.
Improved stability and performance receiving NDI streams.
Improved stability when using AJA devices.
Fixed a bug that could result in invalid capture presets after re-configuring an existing preset.
Golden master.
6.1.0.GM.1190
Improved performance when recording H.264.
When using LTC timecode over audio, 25, 29.97 or 30fps timecode is now automatically converted to match a channel configured for 50, 59.94 or 60fps instead of flagging the timecode as invalid. For example, a 1080p50 channel can now receive p25 LTC timecode.
Golden master.
6.1.0.GM.1189
Golden master.
6.1.0.GM.1188
Updated all copyright notices to 2024.
Golden master.
6.1.0.GM.1187
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.
6.1.0.GM.1186
Unexpected metadata values are no longer embedded when recording to a MOV container.
Golden master.
6.1.0.GM.1185
Golden master.
The active license is now synchronised with the online license every 30 instead of 7 days.
6.1.0.GM.1184
Golden master.
6.1.0.RC1.1183
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.
6.1.0.RC1.1182
All Apps now show the correct version in the “About…” panel.
6.1.0.RC1.1181
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.
6.1.0.RC1.1180
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.
6.1.0.RC1.1179
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.
6.1.0.RC1.1178
Improved logging for diagnosing issues with NDI streams.
6.1.0.RC1.1176
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).
6.1.0.B1.1173
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.
6.1.0.B1.1172
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.
6.1.0.B1.1171
Fixed a bug that resulted in unexpected results using metadata sets, event presets or custom overlays.
6.1.0.B1.1170
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.