redbrain

If that's the case, then perhaps this isn't a bug with ytdl but rather improper handling of a stream. Can you share what you did to fix the issue, if...

@GaryCraft Try using a stable version of Node (ie the v14 LTS) and see if that fixes it?

It would be nice if a `best/worst/reliable` filter name scheme was implemented, however you should probably think more about it since it's quite a breaking change

I actually manage a npm package called [ytdl-core-muxer](https://npmjs.com/ytdl-core-muxer) that accomplishes this all in Streams, no temp files needed.

Most of this time is waiting on requests from YouTube, afaik there's hardly anything that can be done to speed up the process. If you do find a timesave, please...

> if that's the case, how is basicInfo faster than info? iirc `getInfo()` actually makes more requests, in order to download and decipher format/streaming information. > Seems more like a...

if we can verify what you claim, using innertube could be a worthwhile time investment. I will look into it, and if any other maintainers could look into it that...

I've looked for how other scrapers do this; it seems they all download it fully and cut it later with ffmpeg or the equivalent. I couldn't find much on YouTube's...

Thanks for the information! Do you have time to draft a PR to close the issue?

Forgive me if I'm missing something, but since ytdl.getInfo()'s options extend miniget, which then extends http.request, couldn't you just pass timeout as an option directly?