Some history. I started with Applian's Replay Media Catcher (RMC). They
gave up on trying to support their extraction engines, so they dumped
their backend, and grafted jaksta's Media Recorder (MR) to their RMC
frontend GUI. They gave up on their GUI, and became a reseller of
jaksta. Both Applian and jaksta are payware. When Applian switched
from a perpetual license to an annual license (i.e., they went from
payware to subscriptionware), I left Applian to move to jaksta who was
still selling perpetual license. Applian merged with jaksta, so now
jaksta license are only 1 year (extended to 2 years if you pay another
$10). Cost for a jaksta upgrade on MR is $24/yr. I decided to hunt
around for freeware alternatives.
yt-dlp is a fork of youtube-dl, but more supported and faster to update.
Uses the same extraction engines of youtube-dl which are focused on a
specific site on how to capture video/audio streams; see
https://github.com/ytdl-org/youtube-dl/tree/master/youtube_dl/extractor.
Scroll down to the youtube.py extractor entry (near the bottom of the
list), and notice the update was just 2 months ago. Youtube changed
something, so the youtube-dl folks, or someone assisting them, updated
their extraction engine to get stream capturing to work again at
Youtube. For example, I had not use MR for many months, and it failed
when I tried to capture a Youtube video. I started a forum thread on
the error, but realized I had disabled auto-update in MR (which updates
both the product upon permission, and the extraction engines
automatically). Did the update, and the Youtube extraction engine got
updates which again let me capture Youtube videos. When sites make
changes, the extraction engines for them may start to fail, so users
issue reports and the devs have to update the extraction engine for
capture to start working again at the site. That's why you'll see these
stream capture tools list something like working at 1400 sites, because
that's how many site-specific extraction engines they defined. The
capture tool may work at many other sites, but if not then you can
report the problem, and they come up with another site-specific
extraction engine.
When I discovered MR used yt-dlp (mentioned in their released notes) and
ffmpeg, I figured I would try a freeware setup: yt-dlp, ffmpeg, and a
GUI frontend to yt-dlp. GUI frontends for youtube-dl also work for
yt-dlp (a youtube-dl fork with additional features). While a complaint
and excuse of GUI frontends is that they cannot possible encompass all
the command-line switches (arguments) of youtube-dl/yt-dlp, that is
crap. You can always use a conflict matrix to determine when options
will conflict or have to be altered when other options are selected.
More likely the GUI authors just don't want to may their GUI so busy
that it becomes as difficult to use as the command line to run
youtube-dl/yt-dlp.
I thought
https://github.com/kannagi0303/yt-dlp-gui has a nice looking
GUI, but it was missing the SponsorBlock feature in
https://github.com/dsymbol/yt-dlp-gui which is a crude looking GUI.
Video are often offered as multiple streams: primary, ads, subtitles.
The primary stream plays for a while, gets paused, the ad stream plays,
and the primary stream resumes after the ad stream ends, and there can
be multiple interjections of ad stream pausing the primary stream. The
streams can be captured separately, so later you just watch the captured
primary stream to watch the video with no ads. I don't know when yt-dlp
added their SponsorBlock API, but both Applian and jaksta have had ad
blocking every since I started using them about 7 years ago. Both
Applian and jaksta (selling RMC and MR which are the same product) have
a ton of options more than I've seen in any of the youtube-dl/yt-dlp
GUIs, and why I just might pay for their subscriptionware license.
Another yt-dlp GUI is from
https://github.com/oleksis/youtube-dl-gui who
also makes a Windows UWP (Universal Windows Platform) app at
https://apps.microsoft.com/detail/XP9CCFSWS911F5?hl=en-us&gl=US. I
can't tell if the UWP app has dependence on some Python install.
Doesn't look like it, plus I wouldn't think Python would be doable for a
UWP app. The UWP app is also missing some later features, like
SponsorBlock (
https://sponsor.ajay.app/). Still, Applian and jaksta
provide a GUI frontend to yt-dlp that shames the freeware GUI frontends,
but Applian and jaksta are payware (and now changed to
subscriptionware).
Another difference is Applian and jaksta include Npcap (successor to
Winpcap). This allows their products to use auto detection of stream
sources just by visiting a site. No need to copy the URL of a web page
from the web browser's address bar to paste into a URL field in the GUI
frontend. I have not found any mention of Npcap/Winpcap used with the
freeware youtube-dl/yt-dlp stream capture tools. Npcap is a driver, but
apparently had a signing problem months ago that caused a conflict with
Secure Boot in UEFI. With a valid signature, the driver was flagged as
insecure, and MR bitched about having to use a different detect method
than using npcap. They touted Npcap as being better, so I aborted my
experiment with Secure Boot. I think the problem was they thought their
own EV certificate was sufficient, but found they needed it co-signed by
Microsoft Dev Portal. The conflict between Npcap and Secure Boot is
probably now a non-issue. Auto-mode of capturing streams just by
visiting a web page is nice, but it is a convenience that I might forego
when going with a freeware setup.
While Applian/jaksta rolled up a nice GUI and tool set for stream
capture with a lot of features, I dislike subscriptionware. I was
hoping something was a lot closer to Applian/jaksta's GUI feature set
than what I've found so far.
Go free, lose features, and rely on peer support. Go paid, get lots of
features missing in freeware, and get fast and intelligent support.
It's a harder choice than I first thought.