Bugfix Release Notes - Schedule - 9.0.7 – LTN help center

Resolved Defects List / Improvements

[Bugfix] Properly remove unused nodes internally
[Bugfix] Automatic respawn of SRT outputs, in case the automatic restart did not start streaming properly
[Bugfix] Pasting elements before gaps did not work properly
[Bugfix] Moving elements before gaps did not work properly
[Bugfix] Standard users could not create rerun elements
[Bugfix] Runmode could not be changed from Delay to Primary while playback was running
[Bugfix] Skipping the last element in a rundown when rundown was set to loop could cause issues
[Bugfix] All items inside a sub-rundown showed the same start-time
[Bugfix] Fix in internal VideoEngine that could cause 100% CPU utilisation for about one second, causing subsequent issues

Documentation

For a detailed product documentation, please refer to the following location:

System Characteristics

Known Issues and/or Limitations

MPEG-TS Muxing Overhead	Because of vbv-buffer compatibility the muxer overhead is set to 80%. This result of this is an overall increased bitrate of 80%, in regards to the configured video bitrate within LTN-Schedule transcoding settings. For example: 10MBit configured within the Schedule UI will result in 18MBit MPEG-TS muxed stream output on the actual MPEG-TS Output (SRT). RTMP and HLS Targets are not affected by that. LTN continues improving this component to reduce the overhead in upcoming updates.
Deletion of rundown elements	Deleting more than 2000 assets in the rundown at once does not work.
Missing meta-data	Inspector for rundown elements does not show all meta-data infos.
Library bulk delete problems	Deleting more than 500 Assets of the Library can slow down the system.
Starting Playback during an ad-break issue	Starting Playback during an ad-break can cause the current video element to skip to the next one too early when the backup video is overall shorter than the ad-break itself.
Drag&Drop to set backup video on re-run element doesn't work	When dropping a video from the library on a re-run element in the rundown it does not set the dropped video as backup video. It only lets the user drop the video before or behind the re-run element.