Skip to content

YTLiveRecorder 1.2.10

Choose a tag to compare

@liquidcryptid liquidcryptid released this 01 Aug 22:19
· 21 commits to main since this release

YTLiveRecorder 1.2.10

Automatic YouTube livestream recorder (yt-dlp + ffmpeg).

Not affiliated with YouTube or Google.


Which file do I download?

Your computer Download this
Windows YTLiveRecorder-Windows-Setup.exe
Linux (recommended, auto-update) YTLiveRecorder-Linux.AppImage
Linux (.deb package) YTLiveRecorder-Linux.deb

Other files on this page (latest.yml, latest-linux.yml, *.blockmap, checksums) are for automatic updates — you can ignore them for a first install.


Usage

Windows

  1. Download YTLiveRecorder-Windows-Setup.exe and run it.
  2. If Windows protected your PC (SmartScreen): More infoRun anyway.
  3. Allow admin install when asked.
  4. Open YTLiveRecorder.
  5. Browse → pick a folder for finished recordings.
  6. Add channel — handle only (e.g. liquid_cryptid; @ optional).
  7. Start Monitoring. When a channel is live, recording starts.
  8. While Recording, click Stop next to that channel to save the current segment (monitoring continues; a new segment starts if the stream is still live).
  9. Stop Monitoring when done watching entirely — the app saves any active files as normal .mp4/.mkv under your folder.

Updates later: green badge next to the title, or Help → Check for Updates…

Linux (AppImage)

chmod +x YTLiveRecorder-Linux.AppImage
./YTLiveRecorder-Linux.AppImage

Same steps as Windows inside the app. AppImage supports in-app updates.

Linux (.deb)

sudo dpkg -i YTLiveRecorder-Linux.deb

Update by installing a newer .deb, or use the AppImage for auto-update.


Patch notes (1.2.10)

Bug fixes

  • Long-run Chromium FD / shared-memory leak while monitoring — live probes and yt-dlp status checks no longer run inside the UI renderer. Multi-MB YouTube page fetches used Chromium Mojo shared memory and left deleted /dev/shm FDs growing for hours (often ~1k+ FDs after a day of 20s polls). Probes now use Node fetch + a queued yt-dlp status print in the main process (lib/live-check.js); the renderer only receives yes/no via IPC. Recording spawn is unchanged for this release (still nodeIntegration in the UI process).

Reliability

  • Probe HTML body capped at 3 MiB in main (markers appear earlier; less peak memory)
  • Live-check helper processes are killed from main on Stop Monitoring and quit

Notes

  • After upgrading, multi-hour monitoring should keep the UI process open file-descriptor count roughly flat (dozens), not climbing into the thousands
  • Concurrent recordings still use ~100 MB RAM each (yt-dlp + ffmpeg); that is expected, not this leak

Full history: see CHANGELOG.md in the project repository.


Notes

  • 64-bit only (no macOS build)
  • First-time Windows installs may need SmartScreen “Run anyway”
  • Release version 1.2.10 (filenames do not include the version number)