[JIMLN] Release Notes v.6.1
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
Stability and performance improvements..
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.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.
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.1185
Golden master.
The activate license is now synchronised with the online license every 30 instead of 7 days.
6.1.0.GM.1184
Initial Release