Recording, Catch-Up and Rewind — Three Different Things

2026-09-05 · Setup · 5 min read

Three features get discussed as if they were one, and they are not. They have different requirements, different failure modes, and different people to blame when they do not work.

Catch-up is your provider's archive. Recording is your own copy. Timeshift is a few minutes held in memory. Sorting out which one you actually want takes a minute and saves a lot of pointless configuration.

Catch-up — the provider's archive

Your provider records certain channels on their own servers and keeps a rolling window, typically 24 hours to seven days. You browse backwards through the guide and play from their archive.

What it needs. A provider that offers it, on the channel you want, and a connection method that can ask about it.

That second point is the one that catches people. Catch-up availability is a question the player puts to the server — is there an archive for this channel, and how far back? — and that question exists in the Xtream Codes API. It does not exist in a plain M3U playlist. Some providers encode hints into M3U attributes and support is inconsistent and silently absent when it fails.

So if you have no catch-up and want it, check your connection method first. Switching from M3U to Xtream Codes frequently turns it on with no other change. The comparison of the two covers how to convert.

How to use it. Open the guide, scroll back to a previous time or day, and select a programme. Channels with an archive are marked — usually a small clock or a circular arrow beside the logo. A programme with no marker is not available, and no setting will make it so.

Why it is not working. Almost always the provider. They advertise catch-up across the service and enable it on a fraction of channels; the archive window is shorter than stated; or the recording failed for that programme. None of that is fixable from the app. What is worth checking is that your guide is loading correctly, because catch-up is navigated through the guide — if the EPG is blank or shifted, catch-up will look broken when it is not.

Recording — your own copy

The player writes the stream to storage you control. It keeps working when your subscription ends, and it does not depend on the provider offering anything.

What it needs. A player that supports recording, and somewhere to put it.

Storage is the real constraint. An hour of HD video is roughly 3 to 4 GB; 4K is several times that. A Fire TV Stick has about 5 GB usable in total, so recording to internal storage means one film and no room for anything else. In practice a streaming stick needs a USB drive, which on a Stick means a powered OTG adapter, since the device cannot supply enough current for a spinning drive on its own.

On a phone or tablet internal storage is usually fine for occasional recording.

Format the drive correctly. Most Android devices read exFAT and FAT32. FAT32 cannot hold a file above 4 GB, which is about an hour of HD — recordings simply stop there, often with no error. Use exFAT.

Scheduling. Recording from the guide is the normal route: find the programme, choose record. Two things worth knowing. Broadcast times drift, so pad the end by ten minutes for anything live — sport especially. And recording is a second concurrent stream on your account, so if your provider allows two connections and you are watching another channel, the recording may be refused.

Timeshift — the few minutes you already have

When you have been watching a channel for ten minutes, the player has those ten minutes buffered and you can move back within them. Pause, rewind, catch the replay you missed.

What it needs. Nothing from the provider. It is entirely local.

Its limit is its nature. You can only go back as far as you have been watching, and changing channel usually discards the buffer. Switch to a match at halftime and there is no first half to rewind to — that would need catch-up.

Some players let you enlarge the buffer, at the cost of memory or disk. On a 1 GB streaming stick a large timeshift buffer competes with playback itself and can cause the stutter you were trying to avoid.

Which one do you actually want?

Missed something broadcast yesterday? Catch-up. If your provider does not offer it on that channel, nothing else will help.

Want to keep something? Recording. It is the only one that produces a file you own.

Stepped away for five minutes? Timeshift. It is already working.

Want to watch a series from the start? Neither — that is video on demand, a separate part of your provider's catalogue.

When it goes wrong

Recording stops partway. Storage full, or a FAT32 drive hitting the 4 GB file limit.

Recording fails to start. Usually the connection limit — the recording is a second stream. Check nothing else is playing.

Catch-up plays but stutters. Archive playback pulls from a different part of the provider's infrastructure than live, and it is often less well provisioned. Little to be done locally.

Recordings play with no sound. Not a recording fault — an audio format the device cannot decode, the same codec problem you would hit playing it live.

What we do in Xtiva

Xtiva supports catch-up where the provider exposes it through the Xtream Codes API, recording to internal or external storage, and a timeshift buffer on live channels. Catch-up shows a marker in the guide so you can see what is available before selecting it, rather than discovering by trial.

Xtiva ships with no channels, playlists or streams of any kind, and has no archive of its own — catch-up is your provider's, and we can only surface what they expose. You supply your own provider and are responsible for the legality of the service you connect to.

Related: Xtream Codes versus M3U, EPG problems, what an IPTV player is.