fuck you riaa
GUI for youtube-dl (and forks) + FFmpeg (ffmpeg.exe & ffprobe.exe) which is used for converting.
The goal of youtube-dl-gui is to make it as accessible to as many people as possible, with as many arguments added as options as I use them... or get requested to add them. If at all.
Powerusers can use the custom arguments option to have almost absolute control of the input arguments, excepting the URL and the output.
The forks that are supported are youtube-dl, yt-dlc, and yt-dlp. Additional forks can be added, by request.
A Windows computer (or any computer) that has support for .NET Framework 4.7.
Youtube-dl (or any fork) may require ffmpeg to be present along side it.
On first start, be sure to read the dialogs.
This program won't run without youtube-dl being in either the same directory as youtube-dl-gui, or in the system's PATH. It's designed to download youtube-dl for you if it does not find one.
If you want to use a schema, feel free to build your own using the following useable replacement flags (perhaps i'll add a friendly way of building your own), or just stick to one of the default ones.
Downloading with custom formats and converting in any way will require FFmpeg, which you can download and put the files in "ffmpeg/bin/*.exe" in with the same directory as youtube-dl-gui or extract it anywhere and put the bin directory into your windows PATH.
The static paths for youtube-dl and ffmpeg may be set, which will allow you to select the executable, for youtube-dl, and/or the directory, for ffmpeg.
When using custom arguments, the url and save directory are automatically passed, url being the first thing passed, followed by custom arguments, and the save-to directory being the final one passed.
Examples:
youtube-dl.exe https://awebsite.tld/video.html \<custom arguments> -o "C:\Users\User\Downloads\"
ffmpeg.exe -i "C:\Users\User\Downloads\VideoToConvert.ext" \<custom arguments> "C:\Users\User\Downloads\FileOutput.ext"
Each fork may have differences in compatible sites. It's recommended to do your own research. Or just try it, and see if it works. The worst that can happen is you blow up.
For anyone looking to translate, feel free to open a pull request with the new language file in the Language
folder. Check if a language you're translating exists already, and you can edit it off of that.
For anyone looking to contribute to the code, make a pull request with the changed code.
things and stuff