Faqs

DynTube Video Player

The DynTube player connects adaptive playback with the project's protection, captions, audio, branding, and analytics configuration. Use a supported embed for the simplest integration, then test the published page on the devices your audience uses.

How should I test casting?

Casting availability depends on the browser, sender device, receiver, network, media output, and protection configuration. Confirm that casting is enabled for the player and supported by the intended environment. The sender and receiver may make different requests, so origin-restricted or encrypted playback needs an integration that preserves the required authorization.

Do not enable encryption keys on all origins as a routine casting fix. That setting widens key delivery and can weaken an intended domain boundary. First test the supported player configuration and collect the sender, receiver, browser, and error details. Ask support to validate a protected casting use case before changing the account-level exemption.

How do I add player branding?

Open Settings → Global (/settings/global) for account-wide player branding controls, or use the project's player settings when the feature is included in your plan. Upload a clear asset with suitable dimensions and transparency, save the configuration, and verify it on a published video. Project-level settings let different libraries use appropriate branding when supported.

How do subtitles and alternate audio appear?

Publish the subtitle or audio track for the correct video and language, then select it from the player's controls. DynTube supports uploaded subtitle files as well as supported automatic-generation workflows. Uploaded SRT can be converted to WebVTT for delivery. Test timing, labels, default selection, and mobile controls before launch.

Will analytics work with a custom player?

DynTube's supported player and embeds emit the playback events used by the platform's analytics workflow. A third-party player does not automatically produce the same accepted events. If you need a custom player, verify the current integration contract and implement the required event and identity inputs rather than assuming analytics parity.

For Plus and other entitled workflows, your application can provide a supported customer identifier or email so reporting can connect viewing activity to the customer. Only send identifiers you are permitted to process, keep the integration consistent across sessions, and verify the resulting report before relying on it for business decisions.

Player troubleshooting checklist

  1. Confirm the video is processed and published.
  2. Generate a fresh supported embed from the intended project.
  3. Check allowed origins, signed-link expiry, and the project's protection mode.
  4. Test captions, audio, branding, analytics, and casting separately.
  5. Capture the player error, browser, device, page origin, and time for support.
  • Video Playback Issues
  • Video Options
  • Screen Recording & Download Prevention

Something missing or wrong here? Tell us and we will correct it. New to DynTube? Start with uploading and embedding.