A live channel is a feed arriving in real time from a source nobody at your end controls. A 24/7 channel is scheduled playback: a server reads a playlist of stored files and pushes it out as a continuous stream, which your player receives exactly the way it receives anything else. Both arrive as short segments of roughly six seconds, so the player always sits a few seconds behind the server. The practical difference is recovery. When a live feed drops, the source is gone. When a 24/7 loop drops, the schedule usually keeps running on the server and you rejoin it mid-episode, which is why these channels feel more forgiving than live sport does.

1. 1Segments arrive in roughly six-second chunks, so a stall longer than the buffer shows as a freeze
2. 2You join the loop wherever it currently is, not at the start of an episode
3. 3Picture quality is fixed when the files are encoded, not by your player

Because the loop is a process, and processes restart. When the playout server for a group is restarted or re-encoded, the playlist pointer usually returns to position one, so every channel in that group jumps back to its opening episode at the same moment. Community threads about always-on groups describe this pattern repeatedly: channels stuck repeating early episodes, or a short scene looping for minutes. The tell is scope. If one channel resets, its own source was replaced. If the whole group resets together, the fault is server-side and no setting on your device changes it. Switching away and back confirms it, because playback that resumes cleanly was never a bandwidth problem.

1. 1One channel resets: that channel's source file changed
2. 2A whole group resets at once: the playout server restarted
3. 3Recovery on switch-back rules out your connection entirely

Enough to matter if you treat these channels as background. A 1080p stream runs roughly 5-8 Mbps and uses about 3 GB per hour. A 4K stream runs roughly 15-25 Mbps and about 7 GB per hour. Left running eight hours a day, one 1080p loop is around 24 GB daily, which is the number to weigh against a capped home plan before you decide to keep one on all evening. HEVC encoding cuts the bitrate to roughly half of H.264 at similar quality, so the same channel can cost half the data when the source is encoded that way. Nothing in the player changes this; it is set where the stream is made.

1. 11080p: ~5-8 Mbps, ~3 GB per hour
2. 24K: ~15-25 Mbps, ~7 GB per hour
3. 3HEVC uses roughly half the bitrate of H.264 for similar quality

Open the group and let one channel run for twenty minutes rather than clicking through twenty channels for ten seconds each. Short sampling hides the two faults that matter: a mid-episode stall and a loop reset. Then check that same channel three hours later to see whether it advanced or went back to the beginning. Do this during your normal evening viewing window rather than at 10 a.m., because capacity problems appear when servers are busy. A $5 24-hour trial covers one full evening and one morning recheck, which is enough to see both behaviors. Plans carry a 7-day money-back window, and the trial itself is excluded from it.

Ask for a published uptime figure and a stated connection limit, because those two numbers explain most of what you will experience. IP4KTV publishes 99.99% uptime, about 53 minutes of downtime across a whole year, and allows 1 to 5 simultaneous connections depending on plan. The connection limit matters more than people expect: player forums document that exceeding concurrent streams can make a provider drop and re-serve a connection, after which the client replays buffered data and the viewer sees looping. A service that will not state either number is asking you to trust an adjective. The 12-month plan is $10 per month, $120 total, and nothing auto-renews.