You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Current implementation functionally pulls the track info twice (once at queue time, the other at runtime). Chances are nonzero for a YouTube ratelimit if requests happen too often. Also, this introduces ~1-2 extra seconds of latency that should be unnecessary
YouTube API is the obvious choice but I think we could also get away with streaming the URLs returned by the info JSON directly with a little finagling
The text was updated successfully, but these errors were encountered:
Current implementation functionally pulls the track info twice (once at queue time, the other at runtime). Chances are nonzero for a YouTube ratelimit if requests happen too often. Also, this introduces ~1-2 extra seconds of latency that should be unnecessary
YouTube API is the obvious choice but I think we could also get away with streaming the URLs returned by the info JSON directly with a little finagling
The text was updated successfully, but these errors were encountered: