Skip to main content

Quickstart: Create a Audio Encoding

AOD (Audio on Demand) encoding refers to the process of transforming audio content into a compatible format for efficient delivery and playback over the Internet. It involves converting source audios into various bitrates to cater to different devices and network conditions. AOD encoding ensures that listeners can access high-quality audio content with smooth playback across other platforms.

To create AOD encoding for your audio content using BlendVision One, follow these quick steps:

Prepare your source audio​

Ensure you have the audio file you want to encode in a supported format. Supported formats include .mp4,.mp3,.wav,.flac,.aac, and .m4a.

You should have some sample audios to get started with audio encoding.

Obtain your API token​

You must obtain the API token to access the upload APIs to upload the audio. There're two options to obtain the API token:

  1. Contact us directly, and we will provide you with a specific API token and organization id.
  2. Alternatively, you can log in and acquire an access token. Use the access token to generate your API token by the following API:

/bv/account/v1/accounts/api-token

For more information about authentication and getting your API token, see Authentication.

Upload your audio​

Before starting the audio encoding, you need to upload the audio by using the upload API:

/bv/cms/v1/library/files:upload

Once you complete uploading the audio, you should use this API to notify the completion:

/bv/cms/v1/library/files/{id}:complete-upload

After the audio file is uploaded successfully, the audio will be saved in the Audio Library then you can use them for encoding.

For more details on uploading audios, see Upload Your Assets.

Select the ProfileSet​

  • Profile: each profile defines the audio output bitrate, and audio output bitrate. You can define your own profiles based on your needs, while BlendVision One also provides optimal presets that you can use directly.
  • ProfileSet: ProfileSet defines the codec and streaming protocol of your encoding output. You also need to define your output resolution and bitrate by adding the predefined Profiles to our ProfileSet. BlendVision One allows you to easily produce adaptive streaming by adding multiple Profiles to your ProfileSet.

For more information about Profiles and ProfileSets, see Profile/ProfileSet Settings Reference.

Security​

To ensure proper content protection and limit access to specific audiences or regions, BlendVision One offers several features and settings that you can utilize. Here are the steps to complete the relevant settings for protecting your valuable audio content:

By utilizing these content protection features provided by BlendVision One, you can effectively safeguard your live content and minimize the risk of piracy or unauthorized access. These measures help protect the value of your audio content and maintain control over its distribution and listenership.

Start encoding​

Once you have uploaded/provided files for AOD encoding and completed all settings, you can send a  request with the necessary body to start encoding by the following API:

/bv/cms/v1/aods

See Create a AOD Encoding for more information.

Get AOD encoding status​

To determine the status of a AOD encoding, you can use the following API with the specified AOD ID:

/bv/cms/v1/aods/{id}

You will receive a response containing information about the encoding status of the specified AOD. Once the encoding process for a AOD is successfully completed, the status will become AOD_STATUS_SUCCEEDED. This status indicates that the audio has been encoded without errors and is ready for further actions, such as playback or distribution.

For more information about the encoding status, see Get AOD Encoding Status.

Ready to Play​

To enable seamless playback of AOD content, you can integrate the Web, Android, and iOS player SDKs provided by BlendVision One, allowing users to view the encoded content across multiple platforms and devices easily.

To integrate these SDKs and enable content playback, you'll need to generate a resource token and a playback token. For more information about the resource and playback token, see Generate Resource Token and Playback Token to Enable Content Playback.