Playback

A player that looks like your product

The player is the part of a video platform your audience actually sees, so it should carry your brand rather than a vendor’s. Appearance and behaviour are configurable per project, adaptive streaming handles the connection, and nothing on the surface advertises somebody else.

Your brand on the surface your audience sees

The problem

Keep playback inside your brand experience

Embedding a public platform’s player puts their product inside your page, and it behaves like their product.

Without control

A platform player embedded on your site

Your page, their surface. The controls, the branding and the end-of-video behaviour are decided by somebody whose interests are not yours.

  • Vendor branding on the control bar and in the corner of your content.
  • Suggested videos at the end, frequently a competitor’s.
  • A control set and appearance you cannot bring in line with your design.
  • Behaviour that changes when the vendor ships a redesign you did not ask for.

On your own terms

A player configured as part of your product

The same embed, with appearance and behaviour set by you and no third-party surface competing for attention.

  • Colours and controls configured to match the page around them.
  • Your logo, on plan-entitled accounts, in place of vendor branding.
  • Nothing recommended at the end that you did not choose.
  • The same player across on-demand and live, so the experience is consistent.

The mechanism

Configure the player for each audience

Representative capabilities rather than a feature count, and the compatibility caveats stated where they belong.

Appearance optionsPer project
Colours, control visibility and layout choices, so the player can be brought in line with the page it sits on. Configured per project, which is what lets an agency or a multi-tenant product hold several brands in one account.
Behaviour optionsPer project
Playback behaviour such as default quality, default volume, sticky playback while scrolling and pause-on-scroll. These change how the player behaves in a page rather than how it looks.
Brand text and logoPlan-entitled
Plan-entitled accounts can upload a player logo, and the player supports removing or replacing brand text. Entitlement depends on your current plan and should be confirmed rather than assumed.
Adaptive HLS playbackAdaptive playback
The player selects a quality rung from the HLS ladder based on the connection it observes, and switches mid-playback. This is what keeps a poor connection watching rather than buffering.
Casting, when availableConditional
Chromecast and AirPlay are offered when enabled and when the viewer’s browser and device support them. The control appears when it can work and is absent when it cannot.
Subtitle and audio tracksPer video
Published subtitle tracks and alternate audio tracks are presented by the player, so a multi-language title is one embed rather than several.

The workflow

Setting the player up

Per project, which is the unit that matters if you are holding more than one brand.

  1. 01

    Decide your project boundaries

    Player settings live on the project, alongside protection settings. One project per brand, client or course family keeps configuration where it belongs.

  2. 02

    Configure appearance and behaviour

    Set colours and controls to match the page, then decide the behaviour questions — default quality, whether playback follows the reader down the page, what happens on scroll.

  3. 03

    Add your branding, if entitled

    Upload a logo and adjust brand text. Confirm entitlement first so you are not designing around something unavailable.

  4. 04

    Embed and check it in place

    Put the embed on a real page and look at it at phone, laptop and large-desktop widths. A control set that reads well at 1440 can crowd at 390.

  5. 05

    Test the conditional features

    Check casting on a device that supports it and one that does not, and check subtitles on a phone. These are the behaviours most likely to differ from what you expected.

Beyond the embed

Use DynTube delivery with the player workflow you prefer

Retained from the legacy source, which offered two genuinely useful escape hatches.

  • Direct HLS links

    If you already have a player you have invested in, HLS links let you keep it. Protection settings still apply — check that your player supports the mode your project uses.

  • Playback events and methods

    The player exposes events and control methods, so your page can react to playback and drive it — building a custom control surface or triggering something at a point in the video.

  • Scheduled availability

    A video can be made available from a set date and time, so a launch does not depend on somebody publishing at the right moment.

  • Aggregate playback reporting

    Plays, watch seconds and completion are reported in aggregate. See video analytics for exactly what the contracts expose — and what they deliberately do not.

Put it on a real page and look at it

Configure a project, embed one of your own videos, and open it on your phone. Player decisions are visual, and ten minutes in place beats any list of options.