Compatibility

The table below summarizes the thumbnails types supported by Bitmovin Encoding.

⚠️

Currently, thumbnail generation is supported only for VoD use case, not for live encoding.

Overview

Thumbnails are still images that enable preview of videos. Depending on the platform, protocol and thumbnails types, thumbnails images can be used for several use cases, for instance:

• Thumbnails as single images - for example for feeding CMS (Content Management Systems) with imagery.
• Thumbnails for trick play / trick mode - usually showing preview images while users scrubs through the seek bar or while doing fast-forward operation during a playback session.

Bitmovin encoding supports the generation of a wide range of thumbnails types to support those use cases, and the following sections will provide details of the different types we support with the Bitmovin Encoding solution

ℹ️

To check what thumbnails types we support with Bitmovin Player see Player - Thumbnail Preview Support.

Thumbnails as single images

The Bitmovin Encoding solution supports the generation of jpeg/png single images from the input video asset. Within the Bitmovin API, we know these single images as Thumbnails.

The Bitmovin encoding API supports several configuration options for single image thumbnails, such as setting image size, image interval generation, file name pattern, etc. For more information check out the Bitmovin API for adding Thumbnails to an Encoding.

Thumbnails for trick play

WebVTT Sprites

The Bitmovin encoding solution supports the generation of jpeg/ png Sprites and its respective WebVTT file. A Sprite is a jpeg or png file that contains smaller images stitched together into a single one that is referenced within a WebVTT file. Each WebVTT file has the proper mapping information for referencing each Sprite and its respective images within a specific time range for playback.

When creating a Sprite, the Bitmovin API allows to set the number of images per sprite, the Sprite dimensions - rows and columns, image interval, image size, etc. For more information check out the Bitmovin API for adding Sprites to an Encoding.

Some players (including the Bitmovin web player) can be configured to use such thumbnails, without need for them to be added to the manifests.

Images Adaptation Sets for DASH

The Bitmovin encoding solution supports the generation of jpeg/ png Sprites based on the DASH-IF IOP specification -section 6.2.6. According to the DASH specification, thumbnails are added as a new AdaptationSet with @contentType="image". In this way, each Image Adaptation Set provides the timing and the proper addressing mechanism just as for other audio/video AdaptationSet, allowing mapping of images (or sections in the sprite) to the specific time ranges for playback. Within the Bitmovin API, we refer to this mechanism as ImageAdaptationSet.

For more information check out the Bitmovin API for adding ImageAdaptationSet to DASH manifests, which relies on Sprites having been created first - as explained in the previous section.

I-frame only playlist for HLS

The Bitmovin encoding solution supports the generation of video I-frames as defined in the standard HLS specification - rfc8216. According to this spec, video I-frames are used to render images for operations such as trick play and seek.

For more information check out the Bitmovin API for adding I-Frames to HLS manifests.

Base Index Frames (BIF)

Bitmovin encoding supports the generation of BIF files - a Roku specification that allows trick mode support. This format is not used by other playback platforms. For more information checkout the API for creating BIF files.

⚠️

In addition to BIF, Roku specifications also allows to use HLS Image Media Playlist for trick mode playback, however HLS Image Media Playlist are not currently supported with our encoder. Please inform your account manager if this is a format you require.