https://github.com/yt-dlp/yt-dlp/issues/6247
Issue report on yt-dlp fix on Github.
If the SF's developers would just use the standard yt-dlp rather than hiding it behind YoutubeToMP3Process.exe (and possibly YoutubeToMP3Service.exe) it would be so easy for the user to fix themselves. Out with the old, in with the new. I don't make any claim that I fully understand what they are doing or why they are doing it but with the exception of decrypting the DRMs, they are just using 'off the shelf' software to get the job done. As proof of concept I have already updated the last few versions of SF to use the latest FFMpeg, MKVMerge, and Python versions rather than the older versions found in StreamFab. Based on a previous observation I made, it looked like yt-dlp was updated automatically by YoutubeToMP3Process when a new yt-dlp came out, but now I'm not so sure that that is what happened. Renaming yt-dlp and replacing YoutubeToMP3Process within SF is accepted and doesn't produce any errors. Doing so with the latest yt-dlp doesn't fix the Youtube problem, though. Not being able to see the source code, I've gone as far as I can with my experiments. I'm sure the Developers will have this fixed in no time at all once they find out about it.