Frequently Asked Questions

A dubbed title is actually watched in a market rather than merely being technically available, which shows in completion rates and retention when a Vodlix service expands internationally.

It does, through the same mechanism. Once a title can carry multiple tracks, a described audio track is simply another one, and accessibility requirements around streaming have been tightening in a number of jurisdictions.

The track marked as the default in the title's stream, normally the original language. Mark the track most of your audience should hear as the default, because many viewers never open the audio menu at all.

Yes. The same tracks are listed wherever the title plays on the Vodlix player, and its TV interface has a Subtitles and Audio panel built for the remote. A track choice applies to that viewing; the next title starts on its own default track.

Yes. Vodlix lets you run multiple payment gateways in parallel across your platform, so different markets and payment types can be served by different providers at the same time.

Running several gateways on Vodlix lets each market pay through the provider it trusts, which raises conversion, and keeps checkout working when one provider has an outage.

Yes. Vodlix shows performance per gateway, including failed and successful transactions, so you can route volume toward the providers that settle reliably in each region.

No. Payment gateways on Vodlix can be added, enabled or removed independently, so your payment mix can evolve as your markets change without migration projects or downtime.

Viewers complete purchases far more often when checkout matches what they are used to. Offering a familiar, trusted payment method per region through Vodlix directly reduces abandoned checkouts.

Somewhat, since each is a credential and a relationship. The comparison worth making is against the revenue from a market you otherwise cannot serve, which is usually a considerably larger number than the maintenance.

Yes, test mode puts payments through your gateways without charging anybody. It is worth using properly, because a misconfigured gateway looks identical to a working one until money is supposed to move.

Ask how people in that market already pay for things rather than which providers support the currency. Those are different questions, and the second one is the one that produces a checkout nobody completes.

Vodlix nDVR, or network DVR, records live channels in the cloud so viewers can watch programmes after they have aired, giving linear channels the flexibility of on demand content.

Viewers find catch up programmes inside the Vodlix electronic programme guide by scrolling back to earlier entries, so there is no separate catch up section to learn.

Yes. Vodlix nDVR recording is enabled per channel, so you turn it on only for channels where you hold the rights to store and replay content, keeping your service compliant.

If recording is not enabled for a channel, the Vodlix programme guide simply does not offer those programmes for catch up playback, so viewers are never shown an option that cannot work.

When adding a live channel in the Vodlix CMS, enter a recording source URL alongside the channel's stream URL and EPG feed. Once saved, the channel gains a past that viewers can browse and play.

No. That is the point of recording in the network rather than on a device. There is no hardware to ship or support, no local storage to fill, and a viewer who switches from a television to a phone keeps everything.

Yes. Catch up is treated like the rest of your content, so subscription entitlements and advertising apply to a recorded programme the same way they apply to the live broadcast.

Yes. From the admin panel you can send a push notification to every app user at once or to a single device, with a title, a message and an optional link to an episode or film. The platform also sends push notifications on its own when a live event or release that a viewer asked to be reminded about is about to start.