The general workflow is as follows: Your input videos can be encoded with Bitmovin into MPEG-DASH and HLS formats used for streaming. Bitmovin transfers the encoded asset back to your storage. From this storage you can directly deliver your videos to your customers.
Create an Account
If you haven’t done this already, go to the signup page of our portal and create a new account to try our services for free! Once you signed up, you will receive an activation link via email. Just click on it, and get ready to login with your credentials 🙂
You can start to use our services right away, as your account comes with an included encoding volume of 2.5 GB as well as 5000 player impressions available for 30 days.
Choose your API client
In addition to the API client, we provide you with a clean and functional Backend UI to monitor everything what is happening in your account, as well as create all resources available in our REST API. Let’s start to create an encoding.
Create an Encoding
Our encoding wizard guides you through the 3 steps it takes to start an encoding. The first step is to provide an Input by clicking on “+Create”.
Create/Select an Input File
We already support a vast amount of input sources. Besides basic input sources like HTTP(s) and (S)FTP, we support many cloud storages like Google Cloud Storage, Amazon Simple Storage S3, Azure Blob Storage, as well as other cloud storage vendors, which offer an S3 compatible interface.
An “Input” represents a set of information, which is needed to access a specific type of storage. In this example we will create an “HTTPS Input” by clicking on “+Create” in the top right corner.
Select “HTTPS/HTTPS” in the slider menu. If your input file is available at “https://inputs.example.com/path/to/your/inputfile.mp4”, enter its URL into the “URL” field. In order to easily identify this Input later on, you have to provide it with a meaningful name as well. Then, click on “Create” in the bottom right corner.
You have created an “HTTPS Input”. This “Input” holds all the information our service needs, to access input files, which are hosted on this storage. Now, our service needs to know, which input file has to be encoded. Therefore, enter the path to the input file into the field “Path”, and click on “Next Step” afterwards.
Select a Preset
Our encoding wizard provides you with 4 predefined presets for typical use cases. Select one, which fits to with your use case and click on “Next Step”.
Create/Select an Output
Like an Input, an “Output” represents a set of information, which is needed to access a specific type of storage in order to make the encoded content accessible for playback. For this example we will create an “GCS Output”, so click on “+Create”.
Select “Google Cloud Storage” in the slider menu. In order to easily identify this Output later on, you have to provide it with a meaningful name. Once you entered its bucketname, an Access Key, and a Secret Key, click on “Create” in the bottom right corner.
You have created an “Google Cloud Storage Output”. Now, our service needs to know, at which location on your storage it should store the encoded content. Therefore, enter the path where you want your files to be stored at, and click on “Next Step” afterwards.
That’s it, and the encoding is ready to go! Click on “Start” to start the encoding process.