[object Object] Icon

Encoding
Learn how to create, start, manage and modify Encodings

[object Object] Icon

Player
Learn how to create, start, manage and modify Players

[object Object] Icon

Analytics
Learn how to create, start, manage and modify Analyticss

Docs Home
User shortcuts for search
Focus by pressing f
Hide results by pressing Esc
Navigate via   keys

Encoding REST API Services

1.95.0

Added

Changed

  • AV1 encodings:
    • Speed - Encodings run now 5x faster.
    • Quality - Encodings now show appr. 30% higher quality when compared to HEVC/VP9 encodings.
    • Cost - Encodings are now significantly more cost effective. See our Encoding Minute Calculation Methodology for detailed pricing information.
  • Added startOffset to TextMuxing and ChunkedTextMuxing. This is used for setting the MPEGTS value for the RFC 8216 (HLS Specification) X-TIMESTAMP-MAP for WebVtt outputs (e.g.: X-TIMESTAMP-MAP=MPEGTS:900000,LOCAL:00:00:00.000).
  • WebVttConfigurations with CueIdentifierPolicy INCLUDE_IDENTIFIERS will now generate CueIds starting from 1 instead of 0 if the FileInputStreamType is WEBVTT.
  • CueIdentifierPolicy default for WebVttConfigurations for inputs with FileInputStreamType TTML and SRT. The default is now INCLUDE_IDENTIFIERS instead of OMIT_IDENTIFIERS.

Fixed

  • Added support for adding DASH Label elements to Video-, Audio- Subtitle- and Image Adaptation Sets.
  • Fixed an issue where streams that were ignored by stream conditions are not indicated as being ignored (i.e., the ignoredBy is empty).
  • Streams with WebVttConfigurations will now be trimmed with the same offset and duration as the video stream of the same Encoding if the FileInputStreamType is WEBVTT (This works now same as TTML and SRT FileInputStreamTypes already used to).
  • Fixed an issue where output subtitle cues' timestamps were shifted by the value of the first video PTS, if FileInputStream is used for the subtitle stream
  • KeyFrames are now working for streams with WebVttConfigurations

1.94.0

Added

  • Preset configurations for setting dynamicRangeFormat:

Deprecated

  • Removed deprecated AV1 API parameters which had no effect on visual quality but lead to higher encoding times.

1.93.0

Added

  • Support for adding an AAC or Dolby Atmos audio stream along with a Dolby Vision video stream to a MP4 muxing.
  • Cloud regions AZURE_GERMANY_WESTCENTRAL, AZURE_EUROPE_NORTH and AZURE_UAE_NORTH are now supported. AZURE_UAE_CENTRAL is only accessible for UAE North customers requiring in-country disaster recovery (as per Microsoft), so it can only be used for Azure connect by those customers.

Fixed

  • Corrected the documentation for BIF distance which was not marked as required.

1.92.0

Added

  • Support DolbyVisionInputStreams together with other input stream types like IngestInputStream, AudioMixInputStream, etc.

1.91.0

Fixed

  • Invalid private keys are now reported correctly when using Cloud Connect on GCP

1.90.0

Added

With this release we've improved the encoding capabilities with regards to HDR conversions for H265 output. From now on we support

  • Dolby Vision to HDR10
  • Dolby Vision to SDR
  • HDR10 to HLG
  • HLG to HDR10
  • SDR to HDR10
  • SDR to HLG

The encoder detects the applicable conversion based on the input and the configured output color settings. To make it easier to correctly configure the output we have added preset configurations for the different dynamic range formats. These can be configured on the H265 resource via the setting dynamicRangeFormat.

Dolby Vision input can be configured with a Dolby Vision input stream


1.89.0

Added

  • Support for setting duration=null for Time-based Trimming to indicate that the whole stream should be used (considering offset). offset=null will be defaulted to zero now. We also fixed and issue when settingduration=0 which lead to different results for video and audio. Setting duration=0 will now lead to 0 frames for video and audio.
  • Manifest Generation now supports HDR10 and HLG for DASH for progressive muxings.

Fixed


1.88.0

Added

  • Dash Manifest generation for segmented HDR Output is now setting essentialProperties and supplementalProperties correctly for HDR10 and HLG compatible settings

1.87.0

Added

  • Added EXPLICIT_PS option to HeAacV2Signaling. The option EXPLICIT_SBR now signals Parametric Stereo (PS) implicitly.
  • Improved descriptions for HeAacV1Signaling and HeAacV2Signaling.
  • Automatic shutdown of a live encoding after a certain period of time, configurable via the autoShutdownConfiguration.streamTimeoutMinutes configuration when starting a Live Encoding.
  • Automatic shutdown of a live encoding if input is lost and does not reconnect within a certain time period, configurable via the autoShutdownConfiguration.bytesReadTimeoutSeconds configuration when starting a Live Encoding.
  • Fail fast if not all video streams use the same input configuration.
  • Fail fast if video streams are configured to have more than one stream input (except in the case of CEA 608/708 captions passthrough, where this is expected)

Fixed

  • Webhook for ENCODING_STATUS_CHANGED now can be provided with customData (similar to webhook ENCODING_FINISHED or ENCODING_ERROR).

1.86.0

Added

  • Added new property for DASH manifests which defines the compatibility of the manifest with the Standard DASH Edition. Setting the dash edition compatibility to V4 will support the endNumber attribute for SegmentTemplate DASH manifest, specifying the last available segment. This feature is supported when creating a new DASH manifest via the startEncoding call and configuring the V2 ManifestGenerator OR when creating the manifest via the DASH manifest creation endpoint

Fixed

  • GO API SDK
    • Endpoints with optional request bodies like the https://bitmovin.com/docs/encoding/api-reference/sections/encodings#/Encoding/PostEncodingEncodingsStartByEncodingId(Start Encoding endpoint) are now generated as two methods. One will not accept a request body, the second one does accept a request body parameter and will have the suffix WithRequestBody in the name.
  • Java API SDK
    • For endpoints with optional request bodies like the https://bitmovin.com/docs/encoding/api-reference/sections/encodings#/Encoding/PostEncodingEncodingsStartByEncodingId(Start Encoding endpoint) an additional method overload will be generated which does not accept a request body parameter.

Give us feedback