QMPlay2 plays a great deal more than the files on your drive. Any stream that FFmpeg can open, the player can open too.
That encompasses direct HTTP links, HLS playlists and many radio stations.
Opening a URL
- Choose Add → Address in the playlist menu.
- Paste the stream link.
- Confirm to add it, or use Paste and play to begin at once.
HTTPS links require FFmpeg built with OpenSSL or GnuTLS, which packaged builds ordinarily include.
HLS and M3U links
HLS streams end in .m3u8 and load like any other address. Release 25.09.11 corrected playback for certain HLS sources.
Some servers require a particular Referer or User-Agent. Place EXTVLCOPT lines within an M3U file and QMPlay2 will send those headers.
Internet radio
The Extensions module includes a radio browser. Search for a station, add it to the playlist and save your favourites as a PLS or M3U list.
Recording a stream
The Recording action in the playback menu saves the current stream to disk. Since 25.01.19 it also works for local playback.
Custom user agent
To alter the user agent for every request, open QMPlay2.ini and add a CustomUserAgent value within the General section.
Using Streamlink
Streamlink retrieves live streams from many sites and hands them to a player. Direct it to QMPlay2 in one of two ways:
streamlink -p QMPlay2 --player-http "URL" beststreamlink -p QMPlay2 -a /dev/stdin "URL" bestThe first serves the stream over a local HTTP address; the second pipes it through standard input on Linux and BSD.
Advice for smooth playback
- Select a lower quality in Streamlink if your connection drops frames.
- Enable hardware decoding for high-bitrate live video.
- Use a wired connection for long sessions where possible.
Know what kind of address you are opening
QMPlay2 network playback begins with a media source the player can resolve. A direct media address, a streaming playlist and a normal web page are different things. Copying the address of a page containing a video does not necessarily provide the address of the video stream itself. Identify what the source supplies before treating an unsuccessful open operation as a decoder problem.
Start with a legitimate stream you are allowed to access and whose availability you can confirm. Avoid testing an unfamiliar address containing private account tokens in shared screenshots or public troubleshooting notes. Some stream addresses are temporary, so an address that worked earlier may expire. Keep the exact failure stage in mind: whether the address is rejected immediately, waits without starting, begins with audio only or plays and then pauses. Those distinctions guide the next useful check.
Separate connection problems from playback problems
Test an ordinary local file before investigating a network stream. If the local file plays correctly, the basic audio and video outputs are available. Next, check whether another network source works. One unavailable station can indicate a source problem, while several unrelated sources failing together may point to connection settings, network restrictions or a shared application component.
A working web browser does not prove every application has identical network access. A proxy, firewall or managed network can treat applications differently. Check the relevant settings and read any error message rather than changing graphics options first. Likewise, smooth local playback does not prove the network can deliver a high-bitrate stream continuously. Keep delivery, extraction and decoding as separate stages so that each test answers one question instead of creating several new uncertainties.
Understand live streams and seeking limits
A live stream is not the same as a complete file stored on your drive. The source may offer only the current programme, a limited time window or no seeking at all. If the timeline behaves differently from a local film, that can be a property of the source rather than a player error. Test the available controls without assuming that every moment of the broadcast remains accessible.
Pausing also depends on the way the stream is delivered and buffered. A long pause can exceed what the source or application retains. When you resume, the result may differ from a short pause in a local file. For important live viewing, test the stream before the event begins and keep the connection stable. If the source changes its programme or ends transmission, no local playback setting can restore data that is no longer being supplied.
Treat playlists as directions to media
Network playlist formats describe where media can be found and sometimes how a sequence is organised. They are not necessarily the media itself. A playlist can lead to several addresses, variants or segments, and some of those locations may change over time. If a saved playlist stops working, check whether the underlying source is still available before assuming that the playlist file has become corrupt.
Keep saved station names clear and distinguish alternative versions if you maintain several entries. A station may offer different bitrates or formats, which can be useful when one version is too demanding for the connection. Test each saved entry after adding it. If a source requires particular request headers, use only values supplied for legitimate access by the source provider and keep private information out of public playlists. Do not expect an old saved address to remain valid indefinitely.
Reduce buffering with a controlled comparison
Buffering means the player is waiting for enough data to continue, but the cause can be upstream, local or both. Compare the same stream at a lower offered quality if that option exists. Check whether large downloads or other devices are using the connection. A wired connection can be a useful comparison when wireless conditions vary, but it cannot repair a source server that is unavailable.
Avoid changing the video decoder immediately when playback repeatedly waits for data. First compare local playback and another network source. If the picture continues smoothly once enough data arrives, network delivery deserves attention. If a demanding local file also stutters, decoding workload may be involved as well. Record the pattern and time of the problem, because a busy source may behave differently later. A repeatable test is more useful than a single speed measurement taken under unrelated conditions.
Record only after checking the source and storage
Before recording, confirm that you have permission to save the stream and that the destination has enough free space. A long broadcast can create a much larger file than a short test suggests. Choose a folder you can write to and recognise later. Make a brief trial recording, stop it normally and reopen the result to check what was actually captured.
A recording is not guaranteed simply because live playback looked correct. Interruptions, source changes or a full drive can affect the saved output. Check both picture and sound in the trial file, and note whether recording includes the part of the programme you expected. Keep the original stream entry separate from recorded files in your library. That helps you distinguish a currently available network source from a local copy that should play without an internet connection.
Use external stream tools with clear boundaries
An external stream tool can obtain a playable source and pass it to QMPlay2, but it introduces another stage to diagnose. Verify that the tool recognises the source and can locate the player executable. A command that fails before launching the player is different from one that launches the application but delivers no usable media. Read the terminal output and identify which stage actually failed.
Quoted paths matter when an executable location contains spaces. Keep a command simple while testing and use a source you are entitled to access. If you change how media is handed to the player, test the same stream again so the comparison remains useful. Remember that external tools may need their own updates and dependencies. A working local player does not automatically prove the external stream tool is installed correctly or supports a particular service.
Keep a small, maintainable station collection
Save only streams you expect to use and label them clearly. A huge list of untested addresses can make an ordinary source outage difficult to identify. Review favourites periodically, remove entries that no longer work and keep alternatives only when their purpose is clear. For a planned session, open the relevant stream shortly beforehand rather than relying on a test from weeks earlier.
When asking for help, describe whether the issue affects one source or several, whether local media works and whether an external tool is involved. Do not publish passwords or token-bearing addresses as part of the report. Include a harmless public test source where possible. Keeping your checks focused on address validity, source availability, connection behaviour and local playback gives you a practical sequence for resolving most streaming failures without random configuration changes.
FAQs
Can I open any web page as a stream? A page address is not always a direct media source. Some services need a supported extraction workflow, and others do not provide an accessible stream for this use. Confirm the source type before changing playback settings. Use only content and access methods you are entitled to use.
Why does a saved station stop working? The source may have changed its address, stopped broadcasting or restricted access. Some addresses also expire. Test another station and confirm that local media still works. Replace an unavailable entry with a verified source rather than assuming the saved list itself is the cause.
Why can I not seek through a live stream? The source may provide only current data or a limited playback window. A live timeline does not necessarily contain the complete programme. Check the source behaviour before expecting local-file controls. No player setting can seek to material that the service is no longer supplying.
Will a faster processor prevent buffering? It will not repair a connection that cannot deliver data consistently. Compare a lower offered quality, another source and local media. These tests help distinguish network waits from decoding delays. Background downloads and source congestion can matter even when the computer itself is fast.
How can I check that recording worked? Make a short trial, stop it normally and reopen the saved file. Verify picture, sound and duration before relying on a longer recording. Check storage space and write access in advance. Live playback alone does not prove that every part of the broadcast was saved successfully.
Why does an external tool fail before QMPlay2 starts? Check the tool installation, supported source and configured player path. Read its output to identify whether it obtained media information or failed earlier. A command-line error before launch belongs to a different stage from a decoding error after the player opens.
Conclusion
QMPlay2 streaming is more predictable when you identify the address type and test each stage independently. Confirm local playback, check that the source is available and compare another stream before changing output settings. Respect the limits of live timelines, keep saved stations current and verify trial recordings before depending on them. If an external stream tool is involved, check its work separately from the player's rendering. A small set of verified sources and clear troubleshooting notes makes network playback easier to maintain.