What Are The Differences Between Flavors Set V1 and Flavors Set V2

Printer-friendly version

In the Falcon version, Kaltura introduced a new transcoding flavors (entry transcoding renditions) set dubbed V2. This FAQ describes the differences between the first version and the new version introduced in Falcon (dubbed V2).

Comparison of the flavors sets

Flavors Set V2 (Introduced in Falcon) Flavors Set V1 (Pre-Falcon)
Main codec utilized: H.264
Main codec utilized: VP6
Consolidated single flavors set that is optimized for both desktop and mobile.
V2 is a set of 6 flavors that is used for Web (Progressive Download, HDS and RTMP) and mobile (Progressive Download and HLS).
Two seperate sets: desktop and mobile specific flavors.
Optimized ffmpeg settings
Inclusion of the WEBM flavor
Removal of the 'Edit' flavor (As part of the move to deprecate the Flash based editors)
Redundent 'Edit' flavor (A low-res densed key-frame flavor for Flash app editing)
The default playback mode is HDS (Requires server/CDN support on self hosted editions)
The default playback mode was Progressive Download


V1 to V2 constraints and complications

V1 and V2 assets are not compliant.

As flavors define the playback sets (assets that will be used by the media player during playback), accounts should not include assets from both V1 and V2 sets.
Having assets from both sets available per entry -

  • May cause faulty adaptive bitrate playback behaviors.
  • Does not comply with the Akamai requirements and may cause incosistent adaptive playback behaviours.
  • Does not comply with the Apple requirements and will render such entries to be incompatible with the AppStore.

Therefore, the following guidelines should be applied when considering an upgrade:

  • Publishers should have either V1 or V2 sets configured in their account (Admin Console > Configure Action > check either "V1 flavor set" or "V2 flavor set"), but never both together.
  • Video Entries should never contain assets from both sets. An existing entry (with V1 set) might be transcoded to V2 assets after the switch to V2, therefor:
  • A switch to V2 should be followed by:
    • Disable of the V1 set.
    • Re-convertion of all the account entries to a V2 set
    • Publishers should understand and approve the consequences of the switch from V1 to V2 as it may affect entries availability during transcoding.
FAQ Type: 
(44022 reads)