6.5.0.B1.1250
When two or more clients are connected to a channel, there is now additional spacing between the two status icons in the “Connections” multi-viewer inspector tab.
6.5.0.B1.1249
Disabled unsupported timecode sources and batch recording for SRT and UDP channels.
6.5.0.B1.1248
Updated Blackmagic DeckLink drivers to 14.0 for improved stability, performance and compatibility. If you are using a DeckLink device, please update your system to this version.
Fixed an issue when using an external audio device that could result in a delay between audio and video if there was no input available when the channel was started.
6.5.0.B1.1247
The “Cache Options” channel setting has been replaced with “Dropped Frames Strategy” with the options “Duplicate last valid frame” and “Add black frame”. When frames are dropped from the input (resulting in a gap between two frames), the former will “fill” the gap with duplicates of the last frame before the gap, the latter will “fill” the gap with black frames, making the gap easier to find in post production. In both cases, audio for the inserted frames will be silence.
6.5.0.B1.1246
Updated Blackmagic ATEM drivers to 9.4 for improved stability, performance and compatibility. If you are using an ATEM device, please update your system to this version.
Updated Blackmagic DeckLink drivers to 12.9 for improved stability, performance and compatibility. If you are using a DeckLink device, please update your system to this version.
Fixed an issue that could cause connection and performance issues with NDI channels.
It is no longer possible to activate (start) a SRT or UDP channel if the “host” or “port” fields in the channel configuration tab are empty. These fields are required to connect to the input source.
When using a metadata set with date, time or date/time fields, changes made for a given channel are now correctly restored after changing the selection. For example, previously if one channel was selected and the date and/or time changed, then a different channel was selected and then the first one again, the changes made to the date/time fields were lost (the values reverted back to the current date/time).
Fixed a bug that caused unexpected behaviour selecting multiple channels with a metadata set that contained date, time or date/time fields.