Top 7 RTMPDumpHelper Commands You Should KnowRTMPDumpHelper is a utility that simplifies working with rtmpdump and other streaming-download tools by extracting stream URLs and generating ready-to-run command lines. Whether you’re saving live streams for later viewing, debugging playback issues, or automating downloads, knowing a handful of key RTMPDumpHelper commands will save time and headaches. This article covers the seven most useful commands and options, shows examples, and offers practical tips for reliable downloads.
What RTMPDumpHelper does (brief)
RTMPDumpHelper sits between your browser and streaming tools. It captures the parameters (server, playpath, swfUrl, pageUrl, and other connection data) required to construct an rtmpdump/streamlink/ffmpeg command so you don’t have to manually extract them from network traces. It supports different backends and can output commands tailored to the tool you prefer.
1) –capture / -c — capture stream parameters
Why it’s useful:
- Captures the connection parameters from an open page or traffic so you can reproduce the stream download later.
Typical usage:
- Run RTMPDumpHelper and open the target stream in your browser. Use the capture option to record the handshake and connection details.
Example:
RTMPDumpHelper --capture Notes:
- After capture, the helper will show a set of parameters (rtmp URL, playpath, app, swfUrl, pageUrl, etc.) that you can copy into a generated rtmpdump/ffmpeg command.
2) –backend / -b — choose output tool (rtmpdump, ffmpeg, streamlink)
Why it’s useful:
- Allows you to generate command lines for the tool you prefer. rtmpdump is traditional, ffmpeg is flexible and widely available, streamlink handles many protocols and stream types.
Typical usage:
RTMPDumpHelper --capture --backend ffmpeg Result:
- The output will include a ready-to-run ffmpeg command (including proper headers and input options) instead of rtmpdump syntax.
3) –output / -o — specify output filename or path
Why it’s useful:
- Controls where the downloaded stream will be saved and under what name.
Typical usage:
RTMPDumpHelper --capture --backend ffmpeg --output "my_stream.mp4" Notes:
- Use full path to save to a specific folder.
- When generating commands for ffmpeg, ensure the extension matches desired container/codec behavior (e.g., .mp4, .flv, .mkv).
4) –live / –no-live — treat stream as live or VOD
Why it’s useful:
- Live streams often require different handling (segments, indefinite length) than video-on-demand. Specifying live ensures the generated command uses appropriate options (e.g., no seek, segmenting behavior).
Typical usage:
RTMPDumpHelper --capture --backend ffmpeg --live Notes:
- For VOD, the helper may add options to download the full file and finalize container metadata correctly.
5) –swfurl / –pageurl — override or supply SWF URL and page URL
Why it’s useful:
- Some streams require the correct swfVfy or referrer to accept the connection. Manually providing these can fix authentication and handshake errors.
Typical usage:
RTMPDumpHelper --capture --swfurl "https://example.com/player.swf" --pageurl "https://example.com/watch/123" Notes:
- These options are commonly translated into rtmpdump’s –swfUrl and –pageUrl or ffmpeg input headers. If capture fails because the helper missed the swf or referrer, supply them manually.
6) –auth / –token — include authentication tokens or cookies
Why it’s useful:
- Many streaming services rely on tokens, cookies, or signed parameters. Supplying them allows authenticated access.
Typical usage:
RTMPDumpHelper --capture --backend rtmpdump --auth "cookie=SESSIONID=abc123" --token "auth_token=xyz" Notes:
- For cookies, you may supply a cookie string or path to a cookie file. For tokens, provide the exact query/header parameter the server expects.
- Keep credentials secure; avoid sharing generated commands that contain tokens.
7) –script / –batch — generate scripts or batch commands
Why it’s useful:
- Save time by exporting the generated command lines into a shell script, batch file, or a file per stream for automated running later.
Typical usage:
RTMPDumpHelper --capture --backend ffmpeg --output "my_stream.mp4" --script "download_my_stream.sh" Result:
- You get a script containing the ffmpeg or rtmpdump command that you can run directly or schedule via cron/task scheduler.
Practical examples
-
Capture and generate an ffmpeg command saved to a script:
RTMPDumpHelper --capture --backend ffmpeg --output "event_live.mp4" --script "grab_event.sh" --live -
Capture and run rtmpdump immediately (example may prompt you to confirm):
RTMPDumpHelper --capture --backend rtmpdump --output "vod.flv" -
Manually supply SWF and page URL when capture misses them:
RTMPDumpHelper --capture --backend ffmpeg --swfurl "https://site.com/player.swf" --pageurl "https://site.com/watch/456"
Tips for reliable downloads
- Use ffmpeg backend when you want container flexibility and easier conversion to MP4.
- If capture fails, refresh the browser while RTMPDumpHelper is running or try an incognito window to avoid extension interference.
- Keep an eye on tokens; many expire quickly so capture and download close in time.
- When automating, rotate or refresh authentication tokens programmatically to avoid failed downloads.
Legal and ethical reminder
Downloading streams may violate terms of service or copyright law. Always ensure you have permission to record or save the content before using these tools.
Leave a Reply