4 ms·
Yeah that’s completely nuts to me, I’ll continue to recommend yt-dlp for the significant future.
by Operyl 5y ago
Yeah that’s completely nuts to me, I’ll continue to recommend yt-dlp for the significant future.
- TowerTall 5y agoIs there any GUIs for yt-dlp?
- Operyl 5y agoI tried https://github.com/axcore/tartube https://github.com/axcore/tartube some time ago and it worked. I mostly use the command line though, it’s really simple.
- llacb47 5y agohttps://github.com/oleksis/youtube-dl-gui https://github.com/oleksis/youtube-dl-gui
- prox 5y agoCommand is insanely simple (and I don’t use a lot of shells normally) Copy your youtube url Go to your command shell yt-dlp -v pasted url Watch the download. Done.
- Cyberdog 5y agoYou'll want to surround the pasted URL with quotes, or else the question mark in all non-shortened YouTube video URLs will confuse the shell. Also, I suggest adding `-f mp4` to avoid getting a video in Google's proprietary video format. (Yes, I know, but basically…) yt-dlp -f mp4 'https://www.youtube.com/watch?v=dQw4w9WgXcQ https://www.youtube.com/watch?v=dQw4w9WgXcQ'
- Operyl 5y agoThis is one of my favorite things I don’t have to worry about with zsh + oh-my-zsh, pasted URLs being auto quoted.
- kevin_thibedeau 5y agoUnquoted URLs with '?' work fine in bash. It's not like it's common to have files named with a URL that could confuse a glob expansion.
- derimagia 5y agoIt's mainly the "&" which does it, which is pretty common.
- deleted 5y ago[deleted]
- btdmaster 5y agoWebm is quite a nice format actually, it's a subset of MKV that gave a good target for browser developers. The fact that patent-encumbered h264 is the only codec that is hardware-accelerated across devices is an entirely different issue.
- solarkraft 5y agoMP4 (H.264/H.265) is the proprietary one. WebM (VP8/VP9) is open and royalty free (as is the upcoming AV1). Less commonly supported though, most notably by Apple and some TVs (quite import for that use case).
- kmeisthax 5y agoDepends on who you ask. ISO and ITU would insist that VPx are the proprietary (read: non-standard) ones, which is a different sense of proprietary from what you're using (read: costs money to use). The whole video codec industry was predicated upon a particular licensing structure where everyone was paid to participate in ISO/ITU codec development in exchange for patent ownership over the final standard. That's why Apple never touched VP8/9 - decode blocks for ISO-standard codecs were very plentiful and very good, compared to those you could get for royalty-free Google ones. Of course, nowadays the ISO/ITU business model is broken[0], so maybe the actual standards will move towards "royalty-free by default". Or AOM codecs will outcompete ISO ones and they become the de-facto standard[1]. But I don't see that happening until and unless Apple actually ships AV1 hardware codec blocks. [0] Specifically, a good chunk of HEVC patents are only available from a company called Access Advance, a patent pool that has overlapping membership with MPEG-LA's pool. Since there's an overlap, you have to pay for certain parts of HEVC twice, and Access Advance won't reimburse you for the duplicate license. They say you should ask MPEG-LA for a reimbursement, despite the fact that said reimbursement would be more than you actually pay for MPEG-LA's half of HEVC. [1] One of the founders of MPEG, Leonardo Chiariglione, is very outspoken that royalty-free codecs outcompeting FRAND codecs would mean the end of innovation in video coding. I personally find this a mistaken view (AOM's members were going to be doing the R&D anyway) but that's how the ISO/ITU people think.
- ncmncm 5y agoYou understand that "proprietary" has an actual definition? And, that definition is not, in fact, "non-standard", nor is it "costs money to use"? "Proprietary" means "owned by somebody who restricts access". Access, in this case, refers to rights to run encoders, and to deliver decoders. VP8, VP9, and AV1 are also defined by published and recognized standards, but are additionally not subject to restrictions on use. This has nothing to do with money, and suggesting it does is disingenuous. Also, do you get that Apple's reasons for anything they choose are at best obscure, where not actually fraudulent? We all can only guess at Apple's reasons for anything, even where they seem to say what their reasons are, because Apple is under no obligation to reveal the whole truth about their reasons. That Apple does not support VPx and AV1 is more reasonably guessed, from observation of historical behavior, to be a consequence of their preference for proprietary, exclusionary business models, most probably because they better limit competition.
- iqanq 5y agomp4 files returned by youtube are of a lower quality than webm files.
- Groxx 5y agoyou'll also want to cd to the correct folder because you probably don't want it to go in ~ or some other random location depending on what terminal you launched and how you launched it. CLIs are terrible for people not familiar with CLIs. I love 'em, but GUIs exist (and persist) for good reasons.
- nyuszika7h 5y agoWith yt-dlp, you can use something like `-P /home/username/Downloads`, and you can even put that in your config so you don't need to manually specify it every time.
- deleted 5y ago[deleted]
- agumonkey 5y agoyoutube-dl gui allows to queue urls though, convenient
- arvigeus 5y agoSearch for yt-dlp on flathub. There was a GUI for it, but it is too generic to remember it now. VideoDownloader?
- cercatrova 5y agohttps://www.svp-team.com/wiki/Manual:SVPtube https://www.svp-team.com/wiki/Manual:SVPtube Paid generally but there's a legacy free version for YouTube and Vimeo it says.
- database64128 5y agoA small project of mine: https://github.com/database64128/youtube-dl-wpf https://github.com/database64128/youtube-dl-wpf It uses WPF so it can only run on Windows though.