[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

Fri Nov 22 2019

Bitmovin Encoder Lifecycle

Fri Nov 22 2019

OverviewLink Icon

The feature set of the Bitmovin Encoder naturally evolves over time, including additional features, fixes and performance improvements in newer releases to increase efficiency. Upgrading to new releases is however possible as soon as a new release is available, and Bitmovin recommends the use of the Encoder version currently in Stable stage for production environments.

When the version you are currently using gets deprecated, you will need to update to a newer version, as we will make versions unavailable when reaching their end of life date. Thus, users must ensure that they use a newer version of the Bitmovin Encoder before the end of life date, in order to guarantee uninterrupted functionality.

Please note that this document is referring to the Bitmovin Encoder and not the Bitmovin REST API. Release processes and cycles are different for Bitmovin’s REST API.

Encoder Version LifecycleLink Icon

A release of the Bitmovin Encoder will follow lifecycle stages as described in this table. Note that all releases will not necessarily go through each stage.

Version StatusScheduleDescription
BETAEvery new releaseNew releases of the Bitmovin Encoder will be in status BETA by default. BETA versions will contain the newest features and updates. Features in Beta versions might be subject to change.
STABLE
(Recommended)
4 weeks after BETA status or earlierA BETA version eventually becomes a Stable version. A STABLE version offers the most complete, up-to-date, tested, and stable codebase. STABLE versions are intended to be used in production environments.
SUPPORTEDWhenever a new release is promoted to STABLEA SUPPORTED version was STABLE once but got replaced by a newer release of the Bitmovin Encoder. It doesn't contain the latest feature set, and may hold functionality that is outdated.
Furthermore, SUPPORTED versions might not offer the most efficient encoding capabilities. If you're using a SUPPORTED version, we recommend that you upgrade to the STABLE version, as SUPPORTED versions will ultimately be deprecated.
DEPRECATED4 months after release dateA DEPRECATED version is outdated and should not run in production environments. If you're using a DEPRECATED version, update to the STABLE version at your earliest convenience but anytime before the end of life date.
END OF LIFE6 months after release dateA END OF LIFE version is no longer available (this includes all relevant documentation).

Which Encoder Version should I use?Link Icon

The Bitmovin Team recommends to use the STABLE version in most cases. Using this version tag ensures that your video encoding workflows are always benefiting from our latest patches, security fixes, and performance improvements. Furthermore, you won't have to care about upgrading encoder versions by yourself on a regular basis.

What happens if I use an "End Of Life" encoder version in my configuration?Link Icon

Encodings setup with an encoder version that is no longer available as it reached its End Of Life, it will be overwritten with STABLE instead.

Give us feedback