Sangiin (the House of Councillors) publishes a steady stream of plenary sessions, committee hearings, and official press briefings through its mainstream video platform. That archive is genuinely valuable — floor debates, budget committee testimony, and policy announcements are all part of the public record. But the platform is built for streaming, not for keeping, and streams are inherently fragile: sessions get re-encoded, moved behind new player versions, or quietly rotated out of a legacy catalog. If you want a copy that survives those changes, you have to capture it yourself, deliberately and on your own hardware.
The technical obstacle is that almost nothing modern is served as a single downloadable file. Delivery happens over DASH or HLS, which splits a broadcast into hundreds of short chunks, each with its own URL and its own byte range. Video and audio usually travel as separate adaptive streams at different resolutions and bitrates, and the player only stitches them together in memory. On top of that, servers apply rate limits and throttling to discourage bulk retrieval, so a naive download is slow, or stalls halfway through a 90-minute session. Subtitles, where present, are yet another track — often packaged separately as WebVTT or TTML rather than burned into the picture.
This is exactly the problem yt-dlp was engineered to solve. It reads the manifest, discovers every available rendition, negotiates the highest quality your connection can sustain, and pulls fragments in parallel instead of one at a time. FFmpeg then muxes the separate video and audio streams into a single container without any quality loss from re-encoding. For multi-hour committee footage, parallel fragment fetching is the difference between a four-minute job and a forty-five-minute one.
On the legal side, this guide assumes Fair Use archiving: personal research, accessibility, journalism, and preservation of public proceedings. Sangiin content is largely public-interest material, but that does not make every downstream use permissible. Redistribution, commercial reuse, and monetized re-uploading may fall outside fair use, and platform terms of service still apply. Keep your archive local, attribute properly, and check the governing license before you publish anything you capture.
Below we compare three practical methods. Method one is the yt-dlp app — a desktop GUI that wraps the same engine in a native window, so you get the raw power without ever opening a terminal. Method two is the upstream yt-dlp command-line interface: the same capability, scripted and scriptable, but demanding fluency with flags. Method three is web-based online converters: nothing to install, and correspondingly the weakest option for quality, privacy, and reliability. If you want the short answer, it is the desktop app for anything you intend to keep.
yt-dlp app (Recommended Desktop GUI)
The yt-dlp app is a native desktop application built on Tauri v2 and Rust, wrapping the upstream yt-dlp engine, FFmpeg, and aria2c behind a clean graphical interface. It is proprietary software built upon those open-source utilities, not an open-source project itself — but the download engine underneath is the same battle-tested one used by experts, so nothing is lost in translation. You paste a Sangiin URL, the app enumerates every available format, and you pick your resolution from a dropdown instead of typing a format string.
Under the hood, the multi-connection fragment engine accelerates DASH and HLS retrieval by fetching many chunks simultaneously, which is what makes 4K and 60fps renditions practical rather than painful. FFmpeg then automatically muxes the best video track with the best audio track into a single playable file, and can embed subtitle tracks and metadata at the same time. Everything runs locally: settings and job history live in a plain JSON file on your own filesystem, and there is no telemetry, no account, and no server round-trip.
Step-by-Step Instructions
Step 1: Download & Launch yt-dlp app
Install the desktop build for your operating system and open it. No terminal, Python runtime, or manual dependency setup is required.
Step 2: Paste the Sangiin video or playlist URL
Copy the page address from your browser and drop it into the app's URL field. Playlist links are expanded automatically into a selectable list of sessions.
Step 3: Choose resolution, frame rate, and subtitles
Open the format list and select the highest available rendition — up to 4K or 8K at 60fps where the source provides it. Tick the subtitle track if you want captions preserved.
Step 4: Select an output folder and start the download
Pick a destination on disk, then begin. The fragment engine fetches chunks in parallel while a progress readout tracks each stream.
Step 5: Let FFmpeg mux the final file
When the transfer completes, FFmpeg merges the video and audio streams into one container. The finished file is ready to play or archive.
Advantages
- ✓ Graphical format picker exposes 4K, 8K, and 60fps renditions without command syntax
- ✓ aria2c multi-connection engine plus automatic FFmpeg muxing and subtitle embedding
- ✓ Zero telemetry with local JSON storage — your archive and history never leave your machine
Drawbacks
- ✗ Requires desktop installation
Ready to download yt-dlp app? 🚀
Experience native speed, 4K/8K stream extraction, and zero telemetry video archiving on Windows, macOS, and Linux. ✨
Get yt-dlp appyt-dlp (Command Line Interface)
Upstream yt-dlp is an open-source command-line program maintained by a large volunteer community. It is the reference implementation: everything the desktop app does ultimately routes through this engine. For automation, headless servers, cron jobs, and batch pipelines, the CLI is unmatched — a single command can archive an entire Sangiin session playlist, name each file with a template, and write a metadata sidecar for every entry.
The tradeoff is that it assumes terminal literacy. You must install Python or a standalone binary, place FFmpeg on your system path, and understand format selector syntax like bestvideo+bestaudio to get 4K instead of a default merged stream. Nothing is discoverable through menus, error messages are terse, and updating dependencies is your own responsibility.
Advantages
- ✓ Full upstream feature set with no interface abstraction in the way
- ✓ Scriptable and automatable for batch playlist archiving on servers or cron jobs
- ✓ Excellent documentation and a large community troubleshooting knowledge base
Drawbacks
- ✗ Steep learning curve for format selectors, paths, and configuration flags
- ✗ Manual dependency management for FFmpeg, aria2c, and Python updates
Web-Based Online Converters
Browser-based converter sites ask only for a URL and a click, and they do technically work for short clips. There is no install, no configuration, and no knowledge barrier, which explains their persistent popularity. For a two-minute statement you may never watch again, that convenience is real.
The costs, however, are substantial. Most such sites cap resolution well below source quality, silently re-compress the result, and throttle server-side transfers unless you pay. They are typically funded by intrusive pop-ups and redirect ads, and they log the URLs you submit along with your IP address and browser fingerprint. Anything gated behind a login or a cookie session usually fails outright, and long committee sessions frequently time out mid-transfer.
Advantages
- ✓ No installation and no technical knowledge required to start
- ✓ Occasionally adequate for very short, low-stakes clips
Drawbacks
- ✗ Intrusive ads, pop-ups, and redirect chains on nearly every page
- ✗ Privacy tracking — submitted URLs, IP addresses, and fingerprints are logged
- ✗ Strict resolution caps and server-side re-compression that degrade 4K and 60fps sources