-
Notifications
You must be signed in to change notification settings - Fork 30
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] Youtube issues caused by nsig changes #192
Comments
Investigating potential fix LuanRT/YouTube.js#698 |
Fixed in V1.3.15 |
Youtube has changed things again on Jul 30 2024. Investigating fix: LuanRT/YouTube.js#712 |
Fixed in V1.3.16 |
I am still getting the "falied to load fragments" issue as of v1.3.16 Here is a fragment of the log:
|
Hopefully fixed for good in 1.3.17. Using the fix from LuanRT/YouTube.js#713 |
doesnt work for me, displays an error, gave up, uninstalled.. i dont get buffering on youtube or any other site anyways, so introducing an error where there wasnt one seemed counterproductive... maybe it worked once, doesnt work now as of testing |
@adrianmmiller what version were you on? |
Still getting same error. Console output(it continues):
|
Hopefully fixed in 1.3.18 |
Nope.... Had to manually paste link, and then this: Please send this error to the developer at https://github.com/Andrews54757/FastStream/issues |
That means you are blocking access to WebAudio APIs. Are you in private browsing mode? |
@adrianmmiller I've just pushed a commit that makes webaudio optional. It will disable the audio config feature if the browser doesn't support it. |
no not in private mode, but do have some hardened media settings enabled in firefox, i.e. no autoplay, because im not insane :) |
Confirmed working with latest push, thanks |
The Issue
As of July 24 2024, Youtube videos are no longer loading with FastStream. This is caused by Youtube changing the way tokens are generated.
The Fix
A fix will require updates in the underlying Youtube.js library. Please stay tuned for more information.
The text was updated successfully, but these errors were encountered: