PotPlayer live TV: IPTV playlists, channel zapping and instant recording
PotPlayer was not built as a television application, but an m3u8 playlist opened in the player behaves like one. Channels appear in the playlist panel, arrow keys change station, and the record button writes the transport stream to disk without touching the picture. We spent two weeks using it as the only way to watch live television, and measured what it costs.
Setting up a playlist that survives a week
The setup is three steps and about four minutes. Save the playlist your provider gives you as a file with an .m3u or .m3u8 extension, open it once in PotPlayer, and the channels populate the playlist panel on the right. Right-click any channel and choose to add the whole list to favourites if you want a shorter list than the 400 channels most providers ship.
The part nobody mentions is that a live playlist needs a bigger read-ahead buffer than a file. In Settings, under Network, raising the buffer to 6 MB and setting the reconnect attempts to three turned a stream that dropped once an hour into one that dropped once a day. The cost is 0.7 seconds of extra latency on channel change, which matters for sport and not at all for news.
Recording is the other setting worth changing. The default writes to the system temp folder; point it at a drive with space, because one hour of 1080p HLS lands at roughly 3.4 GB and a 4K channel at 11 GB. Recording runs in the player process, not a separate one, which is why it adds only 3 percent CPU on our test machine.
“People expect a television to remember where they were,” said Nils Andersen, who maintains the IPTV test playlist used in our lab. “A player does not. Once I stopped treating the playlist as a file and started using favourites, it stopped feeling like a workaround.”
Zapping, memory and the two-hour test
Channel change on a 200 Mbit line averaged 1.28 seconds between two 1080p HLS channels, measured across 50 switches. The fastest was 0.94 seconds, the slowest 2.1 seconds on a channel whose manifest listed eight variants. A 4K DASH channel took 2.4 seconds on average, mostly because the player waits for a full segment before it paints.
Memory held at 312 MB across a two-hour session with 40 channel changes, which is the number to watch: an unbounded buffer is what makes IPTV players die after an evening. The previous build crept to 480 MB before flushing. CPU averaged 6 percent on a 1080p HLS channel with hardware decoding and 11 percent on 4K DASH.
Recording overhead measured 3 percent CPU and 18 MB additional memory during a 30-minute capture, with no dropped frames in the recording and none in the display. The output is a plain transport stream, which means it can be remuxed later without re-encoding.
“The playlist panel is the feature people miss,” said Aya Nakamura, playback support for the build team. “They look for an EPG grid, do not find one, and assume live TV is not supported. It is supported. It just looks like a media player, because it is one.”
What it does not do
There is no programme guide. EPG data embedded in a stream is parsed for the current programme name in the title bar, but there is no seven-day grid, no reminders and no series recording. If you need those, a dedicated PVR front end is the right tool; PotPlayer is the player you point at its output.
Timeshift is limited to whatever sits in the buffer. Pausing live television works for the length of the read-ahead — 40 to 90 seconds depending on bitrate — and then the picture resumes at the live edge. It is enough to answer the door, not enough to build a habit.
What it does well is play. A 1080p channel with hardware decoding uses less power than a browser tab running the same stream, and the picture controls — brightness, contrast, deinterlacing mode, audio delay in milliseconds — are the same ones you already use for files. For a second screen in a study, that is the whole argument.
The 6 MB buffer tip fixed my evening dropouts. My provider's playlist has 600 channels and the default settings were not happy with it.
Recording to a different drive is obvious in hindsight. I filled my C drive with 40 GB of football before I thought about it.
1.28 seconds is about right on my connection. My provider's own app is slower, and it shows ads before the channel appears.
No EPG is the honest limitation. I use it for one channel and a schedule I already know, so it does not bother me.
Memory staying flat over two hours is the part that matters. Every other player I tried crept up until it stuttered.
Audio delay control saved a broadcast with a badly synced commentary track. Two hundred milliseconds and it was perfect.
