[Alt text: GIF from the music video for “Love Shack” by the B-52s. The video depicts people dancing in a convertible, multiple people in suits and dresses dancing (visible from the waist down), martinis, a duck shaking its tail, and two men playing saxophones. The subtitles read:
The Crowdstrike is a kernel-space app that
has no testing process
Crowdstrike! Baby Crowdstrike!
Crowdstrike! Baby Crowdstrike!]
The correct way to get someone to move to FOSS is to show them how to do it, not tell them it exists. OP already said they can do the YouTube -> captioned gif in 10min so you need to provide a simple tutorial that identifies the tools to use, how to set them up, and how to create a workflow to achieve the goal of some format with captions in under 10min.
Notice how I explained what was wrong and how to do it? That’s what’s missing from most “you need to use FOSS” posts, including yours.
I want people like you around me!
I thought the average !programminghumor@lemmy.world user is already FOSSpilled. Of course you don’t have to use the FOSS tools but they are convenient enough to be able to make this in 10 minutes.
Anyway, the relevant commands are```bash yt-dlp -f “bv*[height<=480]+ba” --no-mtime --convert-subs srt --write-sub https://www.youtube.com/watch?v=9SOryJvTAGs
aegisub needs srt; we don’t need above 480p
aegisub “The B-52’s - Love Shack (Official Music Video) [9SOryJvTAGs].en.srt”
now go rewrite appropriate lines in gui, apply style and save as “LoveShack.ass”
ffmpeg -i “The B-52’s - Love Shack (Official Music Video) [9SOryJvTAGs].mp4” -filter_complex “[0:v]subtitles=LoveShack.ass[s];[s]crop=w=640[f]” -map [f] -map 0:a -ss 49 -t 21 -acodec aac -vcodec libx265 -crf 20 crowdstrike.mp4
crf 20 for generously high quality because file size is small anyway
