Skip to main content

Release 2.0.10

VP Player - Release v.2.0.10

The new release will include the upgrades, features, and issue fixes listed below:

Release Notes for Client v2.0.10:

  • Upgrade: **Default Player Badge The default player in VP now has a badge that informs users which player is the default, as this player cannot be deleted or duplicated.
  • Upgrade: Editing Audio Link New input has been added to the audio edit page to insert the link included in the RSS of that episode under the <itunes:duration> element as <link>.
  • Upgrade: Placing tags from the video dynamically in the ad tag Technical note: Here is the documentation for more details related to this feature. https://docs.google.com/document/d/1SesrY0DrGAdU9ZyOl8ciclwUCF1Z9lfyFYXQTeQ8sZU/edit#heading=h.t13qw6rvv34m
  • Feature: Add a property based on RATIO for videos uploaded in VP These properties are automatically added from a stream endpoint, which is called to provide the width and height of the video. Then, the aspect ratio of the video is calculated based on these dimensions. The properties types are:
    • 9/16 < = RATIO => ULTRA_VERTICAL
    • 9/16 <= RATIO < 3/4 => VERTICAL
    • 3/4 <= RATIO <= 4/3 => STANDARD
    • 4/3 <= RATIO <= 16/9 => WIDE
    • 16/9 <= RATIO => ULTRA_WIDE

With these properties, you can filter and create playlists containing videos with a specific aspect ratio.

  • Upgrade: Publish date in the future With this upgrade, when the video's publish date is set in the future, a warning is displayed on the thumbnail. This warning can be customized in the localization section of the player under "UnpublishedTitle" and "UnpublishedDescription." In the case of a private video, a black screen is displayed with a warning. The warnings for private videos can be customized in the localization tab of the player under "PrivateTitle" and "PrivateDescription." If the video is both private and has a future publish date, the private setting takes priority.
  • Feature: Change player version in project level The users should use this feature the same way as they use the Self-Configured player but instead of the link used in the script, they should use the link that is generated in the project settings after the user changes the player version to their desired one. Self-Configured Player Documentation: Introduction | Let’s accelerate from here
note

These release notes provide an overview of the issue fixes and improvements in version 2.0.10. For more detailed technical information, refer to the documentation or accompanying resources.