How To Use And Understand Adaptive Video Streaming

Summary

Adaptive Bitrate Streaming, otherwise known as AVS, maximizes video performance by automatically converting uploaded files into multiple streamable formats (such as HLS for Apple devices, and MPEG-DASH for other platforms). When a user plays the video, AVS adjusts the quality and resolution in real-time based on their device and internet capability, ensuring a smooth viewing experience with virtually no buffering.

Who?

This feature/solution requires Customer Support to enable, but then individual permissions can be done by the Bynder Admin.

Don't yet have Bynder? Start Here!

Once enabled, all users with CXOC (Context Experiences for Omnichannel) will have access to AVS. Any DAM user can add subtitles or select the streaming links/ embed code for delivery. Only Bynder DAM Admins can manage portal level default settings for the Video Player controls.

Why?

Bynder's features work together to allow for seamless asset management and use. AVS allows users to stream video assets with ease, allowing the videos to automatically adjust quality to prevent buffering and deliver the best video resolution for any connection. Users can also easily embed videos with our plug and play method or with an API to embed videos into any third-party platform or CMS. Furthermore, AVS supports multilingual subtitles for a more inclusive, accessible experience, and uses predictable URLs to retrieve the correct video asset for your workflows.

How?

Enabling Links For AVS

Videos uploaded before AVS was enabled will not generate streaming links automatically, they must be processed using one of the following options:

• New Content: Upload brand new assets to the DAM. Any new videos uploaded after AVS is enabled will generate streaming links once marked as public.
• One by One: Delete the existing video asset, re-upload it, and mark it as public. This ensures the asset is optimized for streaming.
• Bulk Content: Mark all associated assets as public. Then, create a support ticket to request a bulk asset regeneration of the video assets.

Embed Using The Plug And Play Method

This is the fastest method, and is what Bynder recommends. It provides the HTML code for a player that is ready to use.

1. Navigate to the portal and select an asset.
2. From the asset detail page; open the Embed Media section.
3. Set the desired dimensions of the video, or choose Responsive.
4. Copy the Video Player HTML code and paste it into the desired destination.
   • This code defaults to the DASH link. If needed, swap the URL with the HLS link provided in the same section if that is the prefered link type.
   • AVS API: Retrieve the video player embed code via an API call.

Embed Using A Custom Video Player

If using  a custom player, users need the direct HLS or DASH manifest URL. Find this link in the following three places:

• Asset Detail Page: In the Embed Media section.
• Universal Compact View (UCV): Select the video and choose the HLS or DASH output type. If AVS is enabled for an asset, you can select it directly from the UCV derivatives menu. This recently integrated functionality allows you to pull the adaptive stream directly into your workflow.
• AVS API: Retrieve the link via an API call.

Note: AVS is an optional feature. Please contact your Customer Success Manager to have it enabled for your portal. Once active, all newly uploaded videos will be processed for AVS automatically.

Note: These are streaming manifest links, not direct video files. They must be loaded into a video player that supports HLS or DASH playback.

Adding Subtitles

1. Upload A Subtitle File: From the Asset detail view navigate to Subtitles then press Add Subtitles. From here users can upload a subtitle file. The system accepts .VTT (standard) and .SRT files. Any .SRT files uploaded will be automatically converted to .VTT.
2. Use AI Transcription: If Bynder's AI package is enabled, users can generate a transcription. After the AI transcription is complete, users must manually download the file as a .VTT file and then re-upload it to the asset's subtitle section.

Managing Subtitles

Users can manage the subtitles from the Subtitles section in the Asset Detail View. 

• Newly uploaded subtitles will be marked with a New tag.
• Use the dropdown menu to upload, download, replace, or delete subtitle files.

Note: When using the direct streamable links, captions may be disabled by default in some players. Users may need to manually turn them on.

Customizing The Video Player

Users can set default player controls for the entire portal or override them for individual videos.

Available controls include:

• Autoplay
• Looping
• Subtitle visibility (on/off by default)
• Show controls (the player's play/pause/volume bar)
• Allow rewind and fast-forward

Portal-Level Settings

This sets the default behavior for all embedded videos in the portal, and requires Admin permissions.

1. Navigate to Portal Settings.
2. Scroll to Video Player Settings.
3. Enable or disable the toggles for each feature.
4. Click Save changes.

Asset-Level Settings

This allows users to override the portal defaults for a single video.

1. On the asset's detail page, open the Embed Media section.
2. Enable the Override portal settings toggle and click Override settings.
3. A pop-up will appear. Adjust the toggles for this specific video.
4. The embed code will update automatically to reflect the changes.

Technical Deep Dive

Technical Information Sheet: Adaptive Video Streaming (AVS)

This document provides technical specifications and performance expectations for our Adaptive Bitrate Streaming solution. Our approach prioritizes visual consistency and universal compatibility over fixed bitrates.

1. Quality-Centric Encoding Strategy

Unlike traditional encoding that uses a fixed bitrate (which can lead to "blocky" action scenes or wasted data on static scenes), our solution uses Constant Rate Factor (CRF).

• Variable Bitrate (VBR): The bitrate fluctuates dynamically based on the complexity of the video frames.
• Constant Quality: We utilize a CRF of 21. This ensures that a simple animation and a complex 4K action sequence maintain the same perceived visual high quality, even though their resulting file sizes will differ significantly.
• Audio Standard: All streams are encoded with a high-quality audio bitrate of 160kbit/s.

2. Output Configurations (MVP)

The system automatically generates five rungs for the adaptive ladder to ensure smooth playback across all network conditions:

4. Codecs and Compatibility

• Video Codec: H.264 / AVC (MP4).
  • Why not H.265? While H.265 is more efficient, H.264 offers near-universal compatibility across older mobile devices, browsers, and desktop hardware, ensuring your content plays for everyone without performance stuttering.
• Frame Rate (FPS): We maintain the source frame rate. If you upload at 25 FPS, we output at 25 FPS. This prevents "motion judder" or audio sync issues often caused by forced frame rate conversion.

 5. Performance & Processing Expectations

Our Adaptive Streaming solution is currently optimized for short-form high-resolution content and standard-length videos. Because our system prioritizes visual "Perceived Quality" (using Constant Rate Factor encoding), processing time is driven by the complexity of the visuals, the length and the resolution, rather than just the file size. Because our current processing is CPU-based to ensure precision, users should expect the following:

• Processing Ratio: On average, high-resolution video (4K) may take significantly longer than its runtime to process (e.g., a 5-minute 4K video may take ~90 minutes to convert).
• Rule of Thumb: Estimate roughly 15–20 minutes of processing time per 1 minute of 4K video.
• Maximum Limit: There is a current system safety limit of 4 hours for a single conversion task. If a conversion exceeds this duration, the process will automatically timeout and fail to generate streaming links.

5. Engineering Constraints (FAQ)

Why don't you offer 2-pass encoding for exact file sizes?

2-pass encoding requires the system to analyze the entire video twice. This creates a massive performance overhead that would double processing times without providing a noticeable benefit to visual quality in an adaptive streaming context.

Can I set a hard "Target Bitrate"?

Not at this time. Our solution is designed to be "content-aware." Setting hard limits often results in poor quality for complex scenes. Our CRF approach ensures a consistent experience regardless of whether the content is a talking head or a high-motion sports clip.

6. How to Configure your Video Player with CMCD

Most modern video players support CMCD out of the box. You typically just need to "toggle" it on in your player’s configuration settings.

1. General Requirement

Ensure your player is configured to send CMCD data via Query Parameters (recommended for web players to avoid complex CORS issues).

2. Configuration Examples for Popular Players

• HLS.js Set the cmcd parameter to true in your config object.
• JavaScript

var hls = new Hls({
    cmcd: true
});

• Shaka Player Enable CMCD in the player configuration.
• JavaScript

player.configure({
  cmcd: {
    enabled: true,
    useHeaders: false // Recommended to use Query Parameters instead
  }
});

• Video.js If you use the videojs-contrib-quality-levels or similar plugins, ensure CMCD is enabled in the source handler options. (Many modern versions of Video.js support this via the vhs (Video Health Score) or CMCD plugins).

Troubleshooting

If the previous steps have been completed, but the links are not appearing, users may see one of these messages:

• To generate streaming links, mark this asset as public. If links don't appear in 5 minutes, please contact support for asset regeneration.
  • Meaning: The asset is not public. Mark it as public to begin the streaming link generation. If it fails, contact support.
• Processing... If streaming links don't appear in 5 minutes, please contact support for asset regeneration.
  • Meaning: The asset is public, but the links are not yet ready. This can happen with older assets that need regeneration (see "How to Get Started" section above).

Supported File Types: 

• Fragmented MP4 type

FAQs

What is the difference between "responsive" and "fixed" sizes for adaptive streaming in Bynder?
These settings refer to the dimensions of the video player, not the video content itself.

• Responsive Size: The video player will adjust its dimensions automatically based on the size of the user's browser window. If the browser size changes, the video player will resize accordingly to maintain its aspect ratio and fit the available space.
• Fixed Size: The video player will maintain a specific, predefined width and height, regardless of changes to the browser window size. This is useful for ensuring the video player fits a particular layout, especially for vertical videos where you want to control the exact dimensions.
   

Can Bynder deliver videos in responsive sizes?
Yes, Bynder can deliver videos in responsive sizes, but it's the video player that is responsive, not the video content itself. The video asset needs to be uploaded to the DAM in the desired dimensions.
 

When should one use responsive vs. fixed size?

• Responsive Size: Use responsive sizing when you want the video player to adapt seamlessly to different screen sizes and devices, providing a flexible viewing experience. This is generally recommended for most web content.
• Fixed Size: Use fixed sizing when you need precise control over the video player's dimensions, perhaps to fit a specific design layout, or when embedding vertical videos where a set width and height are critical to the presentation.
   

How can I demonstrate the responsiveness of the video player?
You can demonstrate responsiveness by embedding a responsive video player code on a webpage (e.g., using an online HTML editor like W3Schools) and then resizing your browser window. You will observe the video player adjusting its dimensions accordingly.
 

Do responsive and fixed size settings work with HLS and DASH links, or only with the Bynder embed code?
The responsive and fixed size settings for the video player only work with the Bynder embed code. They do not directly apply to raw HLS (HTTP Live Streaming) or DASH (Dynamic Adaptive Streaming over HTTP) links, as those links provide the video manifest, not the player itself.
 

What format does the Bynder embed code usually stream in?
The Bynder embed code, by default, provides the DASH manifest URL for streaming. However, it can often be modified within the embed code to specify other streaming formats if needed.
 

If a customer has adaptive streaming enabled, will video derivatives still work?
Yes, the only change will be the embed code. 

FAQs About Improving Video Reporting Accuracy with CMCD

What is CMCD? Common Media Client Data (CMCD) is an industry-standard way for your video player to communicate with our delivery network. Think of it as a "digital ID card" that your video player shows every time it requests a piece of video.

Why is it important for you? Adaptive video streaming works by breaking a video into hundreds of small "chunks." Without CMCD, our systems see these as thousands of individual, unrelated requests. This can lead to:

• Inflated Traffic Stats: We cannot tell if 100 requests are from 100 people or just one person’s player looping a video.
• Limited Insights: We can’t accurately report on "Total Views" versus "Data Downloaded."

By enabling CMCD, your player sends a Session ID with every request. This allows us to group all technical files (audio, video, and subtitles) into a single, cohesive session, giving you the most accurate view of your actual traffic consumption.
 

Related Articles

Get public links for an asset

Updated May 15, 2026 08:40