ffmpeg-windows-build-helpers VS yt-dlp

$ git clone https://github.com/rdp/ffmpeg-windows-build-helpers.git $ cd ffmpeg-windows-build-helpers $ ./cross_compile_ffmpeg.sh --disable-nonfree=n --compiler-flavors=multi

ffmpeg has the option to build in quite a few dependencies / external libraries, so it's rather complex. Last time I did it I used https://github.com/rdp/ffmpeg-windows-build-helpers but there are other build scripts on GitHub that also seem like they'd be good

I recommend the ffmpeg windows build helpers and simply build your own.

If you do want to compile yourself, there's a more thorough build script here https://github.com/rdp/ffmpeg-windows-build-helpers

I've run into this situation myself, and in order to generate a version of the ffmpeg executable with the change I wanted I used VirtualBox to spin up a virtual linux machine, and then used https://github.com/rdp/ffmpeg-windows-build-helpers this script to build a new binary (adding in the diff patch at the appropriate point). It's an informative process, you learn a lot about how software is taken from source code into something usable, but if you're new to that world I wouldn't recommend taking it lightly. It took me a few solid days of work before I had a binary I could actually use.

For Windows I've used: https://github.com/rdp/ffmpeg-windows-build-helpers. (cross-compiling on Linux)

use a build script that someone else has put together. Don't try and do it yourself. Ffmpeg with all the usual libraries takes sooo many parts, that way madness lies. I had a lot of luck with https://github.com/rdp/ffmpeg-windows-build-helpers but I have no idea if that's better or worse than other options. Maybe u/_gyan has some advice there

I tried googling up the issue and came across a very outdated solution for a file which I cannot find because the wiki says is deprecated https://github.com/rdp/ffmpeg-windows-build-helpers/issues/268

You can put these options in a config file and they will become the default: https://github.com/yt-dlp/yt-dlp?tab=readme-ov-file#configur...

Yep. yt-dlp and youtube-dl

https://github.com/yt-dlp/yt-dlp

https://github.com/ytdl-org/youtube-dl

Will also start to feel the impact. My theory is that we will see a bunch of new video hosting sites as youtube itself attempts to lock down its ecosystem. They haven't paid attention in any adversarial way as far as I can tell.

When they do, it wont be great.

The points you make aren't unreasonable.

It is necessary to establish clear boundaries of what can and can be provided by the maintainers. If not done at an earlier stage of the project, the support burden becomes too much to bear at which point the maintainer transfers ownership, and the project suffers from catastrophic consequences such as the xz backdoor we're talking about here, or other cases where the project mostly stalls and serves as an ego-boosting platform for the new maintainer, as was the case with PhantomJS[6].

This can also happen in your life, where a "friend" sees that you possess a certain skill, and then gradually tries to push an inordinate amount of their personal work related to this field onto you.

Personally, I think it's best to use an approach with extremely clear communication as to what the maintainer can and cannot provide. This can be seen, for example, in yt-dlp[1], where the consumer is clearly informed upfront that not providing detailed information as requested will lead them to block said consumer; or sqlite where their position regarding contributed patches[2] and support[3] is similarly made clear.

Having a shouty BDFL like Torvalds can also help improve code quality[4] and questionable contributions[5], though it is better that the shouty BDFL makes statements that are professional and do not show as much aggression; so for example, "Mauro, shut the fuck up"[7] would become "Mauro, your response is completely unbecoming for a Linux kernel maintainer, and is not in line with the promise of not breaking userspace."

[1] https://github.com/yt-dlp/yt-dlp/issues/new?assignees=&label...

[2] https://www.sqlite.org/copyright.html

[3] https://www.sqlite.org/support.html

[4] https://www.theregister.com/2024/01/29/linux_6_8_rc2/

[5] https://cse.umn.edu/cs/linux-incident

[6] https://github.com/ariya/phantomjs/issues/14541

[7] https://lkml.org/lkml/2012/12/23/75

Or just "yt-dlp "

yt-dlp ( https://github.com/yt-dlp/yt-dlp ) still works pretty well at the current state of Twitter.

To download audio from YouTube videos, you'll utilize the widely used yt-dlp library, which can be installed using the pip command as follows:

Use: `yt-dlp with --write-comments --no-download --batch-file FILE`

- FILE is a text file with a list of YouTube id's/URL's

- https://superuser.com/a/1732443/4390

- https://github.com/yt-dlp/yt-dlp

> Then youtube-dl wasn't a thing anymore (maybe it is again?)...

yt-dlp is definitely a thing: <https://github.com/yt-dlp/yt-dlp>