Encoder 2.200.0 - 2.208.1
2.208.1 (BETA)
Released 2024-08-28
Fixed
- In cases of complex inputs like JPEG2000 (J2K) and ProRes, when the output resolution is configured to be smaller than the input content resolution, crop filter was not working as expected. This has been fixed now.
2.208.0
Released 2024-08-27
Changed
- Dolby Vision encodings would benefit from increased machines per encode (100 instances for EncodingMode
SINGLE_PASS
,TWO_PASS
and 200 instances forTHREE_PASS
), resulting in improved execution time.
Fixed
- Improved rate-control of VP9 encoder.
- In cases of complex inputs like JPEG2000 (J2K) and ProRes, the crop filter was incorrectly applied twice due to internal processing of complex inputs. This has been fixed.
Known Issues
- S3 role-based output for segmented muxings: No upload verification available.
2.207.0
Released 2024-08-13
Added
- For RTMP input including the stream-key directly in the URL instead of in a separate field is now supported. So both
rtmp://[server-domain-or-ip]:[port]/[application]/[stream-key]
orrtmp://[server-domain-or-ip]:[port]/[application]/+ [stream-key]
as a separate field are now accepted.
Changed
- Various improvements for HEVC under the hood which positively influence quality and turnaround speed.
Fixed
- Fixed potential stalling encodings with HEVC slices greater 1.
Known Issues
- S3 role-based output for segmented muxings: No upload verification available.
2.206.0
Released 2024-08-06
Fixed
- Fixed an issue where encodings would sometimes fail in case more than 10 output streams where configured with at least one of them being subtitles.
- Fixed failing per-title encodings having duplicate configured output paths in different outputs.
- Fixed an issue where ignored progressiveWavMuxings lead to an error.
Known Issues
- S3 role-based output for segmented muxings: No upload verification available.
2.205.0
Released 2024-07-23
Added
- Support for muxing Webvtt into FMP4 container has been added.
Fixed
- Fixed an issue that caused delays for triggering the LIVE_INPUT_STATUS_CHANGED webhook for the status CONNECTED.
Known Issues
- S3 role-based output for segmented muxings: No upload verification available.
2.204.0
Released 2024-07-16
Fixed
- Fixed a bug, where inserting a custom keyframe exactly on an audio segment boundary and using the associated keyframe ID for defining a Dash period resulted in a wrong start segment for the audio dash representations.
Known Issues
- S3 role-based output for segmented muxings: No upload verification available.
2.203.0 (STABLE)
Released 2024-07-09
Added
- Support added for Google Cloud region:
me-central2
- Progressive MP4 muxings are now supported for live encodings.
- PCM Codec Configuration can now be used for creating custom PCM streams from any input audio stream (previously, it's usage was restricted to xdcamhd workflow).
- Support for
S32LE
sampleFormat andSTEREO
channelLayout has been added to PCM Codec Configuration.
Fixed
- Fixed potential out-of-memory issues for encodings having multiple high-resolution Dolby Vision renditions.
- An issue where custom keyframes were not correctly propagated into mp4Muxing with fragmentDuration was fixed. Custom keyframes are now correctly applied.
- Fixed a bug that caused Live HLS manifest to stall. This bug was triggered when single segments would take longer to process than expected.
Known Issues
- S3 role-based output for segmented muxings: No upload verification available.
2.202.0
Released 2024-06-25
Added
- Introduced a new Muxing - ProgressiveWavMuxing. It is now supported to use PassthroughAudioConfiguration for PCM input streams with ProgressiveWavMuxing.
- Added support for Live Heartbeat Webhooks. It is now possible to configure global Webhooks that periodically send updates about the Live Encoding status.
- Note: This feature is available with
encoderVersion
=> 2.201.0 and above. Encodings started with older encoder versions than2.201.0
will not trigger heartbeat notifications. Only the live encodings that are created after the webhook was configured will send heartbeats. Encodings that are already running will not send heartbeats. When a webhook is deleted, Live encodings created afterward will not send heartbeats. The existing running live encodings will keep sending the heartbeats.
- Note: This feature is available with
Changed
- Speed improvement of internal preprocessing to prevent gateway timeout in case many streams with stream conditions are used.
Known Issues
- S3 role-based output for segmented muxings: No upload verification available.
2.201.0
Released 2024-06-18
Added
- Audio Passthrough of AAC audio streams into ProgressiveMovMuxing is now supported.
Changed
- When using the endKeyframeId of fmp4 Representation or Chunked Text Representation the segment containing the end keyframe is not included in the segment list of the representation anymore by default. This means, that the last frame included in the period is the frame before the keyframe having the endKeyframeId.
Fixed
- When using Per-Title with many fixed resolutions, it was possible that the highest bitrate was not assigned to the highest fixed resolution. This is fixed.
- Fixed bug in the Dolby E extraction where the extraction of the stream would not happen correctly in case the Dolby E ingest stream is not selected as the first stream
Known Issues
- S3 role-based output for segmented muxings: No upload verification available.
2.200.0
Released 2024-06-11
Added
- It is now supported to configure audio passthrough with AudioPassthroughConfiguration for AAC input streams into MP4Muxing and PCM input streams into ProgressiveMovMuxing.
- Added new filter AzureSpeechToCaptionsFilter (for LIVE Encoder). This can be used to generate subtitles by transcribing an audio Stream by using Azure's Speech To Text Cognitive services.
- Added support for Dolby E in a single stereo stream as input.
Fixed
- Progressive text muxings, with audio only workflows, would not generate any subtitles. This has been fixed.
- Timescale associated to subtitle representations in dash manifests (either just-in-time or post-encoding) would not always be consistent when multiple periods were configured. The timescale is now always set to 1000 and is consistent with the presentation time offset.
- A bug where rate change could drop all frames in the last segment of the video processing was leading to stall and later to error. This has been fixed.
Known Issues
- S3 role-based output for segmented muxings: No upload verification available.
Updated 10 days ago