Built-In Quest Video Link Resolver not working right
tracked
Juno Tanuki
VRChat Build: 2023.3.1p1-1333-439938a540-Release
When Inputting a direct YouTube URL to a video player, doesn't matter what type, results in the video player coming up with an error on the Quest platform.
I dug deeper in to the logs to see if the link was resolving as the most recent update was saying. And while the link DOES resolve, it resolves to an "access denied" dead link thus the video player cant pull the video to play it on Quest. Direct mp4 and 3rd party reslovers do work and the video players themselves function properly but the built-in link resolver does not.
Pictures linked in the report show a direct link VS a 3rd party resolved link showing the video players working.
Log In
fundale
This issue is partially fixed,
but still an issue for users who's account is not the owner account of a headset...
∗StarKnight∗
fundale: My Quest 2 standalone seems to be working fine with YT and Twitch URL resolver but my girlfriend's Quest 2 standalone always has loading errors with the same URL. They only difference is that she is using her account as a secondary account while the device's owner account is still my account (to share bought games). So is this a known issue with multiple accounts and is there a way to solve it (without making her account the owner, of course)?
B
BeserkerLoona
Im A Quest2 User And Putting YouTube Video Links Keeps Giving Me (Video Error) Unable To Load Video Tried Restarting Loading It Pressing The Go Button Doesn't Work Re Entering It Multiple Times And Even Rejoining The World Doesn't Do Shxt
VoxUmbra
Also confirming this issue. This was working completely fine last week on the live build and during the open beta.
VoxUmbra
The video player on quest seems to be working again now with no 3rd party link resolver.
syncpulse
I tested today and it is now working for me across multiple videos and livestreams. Looking good for everyone else too?
MrDummy_NL
I can confirm the promised resolver is not working. Something went possible wrong at end. All youtube links are not working.
Only direct mp4 and external resolver works.
Oh, Stream mode give it upside-down video, also not good.
So you're back at the begin. Need fix the problem quickly, many are waiting for it.
Lush
tracked
syncpulse
I've also been able to replicate this issue over the last few days. I believe this worked reliably when the feature was still in Open Beta but I can't be sure.
Not sure what exactly is wrong, but logs reveal the video URLs are being resolved to their direct links, but for some reason those direct links are not working. (Some info in the following snippets is redacted due to the resolved URLs containing personal info)
2023.08.16 12:50:24 Log - [USharpVideo] Started video load for URL: https://youtu.be/Ne18ZQ7LLI0, requested by YM2612
2023.08.16 12:50:24 Log - [Video Playback] Attempting to resolve URL 'https://youtu.be/Ne18ZQ7LLI0'
2023.08.16 12:50:25 Log - [Video Playback] URL 'https://youtu.be/Ne18ZQ7LLI0' resolved to 'https://redacted.googlevideo.com/videoplayback?expire=1692226225&redacted'
2023.08.16 12:50:28 Warning - AndroidVideoMedia: Error opening extractor: -10000
The same also happens with the AVPro player:
2023.08.16 12:49:32 Log - [AVProVideo] Opening https://redacted.googlevideo.com/videoplayback?expire=1692226171&redacted (offset 0) with API ExoPlayer
2023.08.16 12:49:39 Error - [AVProVideo] Error: Loading failed. File not found, codec not supported, video resolution too high or insufficient system resources.
FWIW the resolved URL returns HTTP 403.
Strangely, manually resolving the URL (using the same yt-dlp command line as the VRC PC client) works fine, so I actually have no clue what the underlying issue is.
Full unredacted logs available to VRC staff upon request, but I imagine this isn't hard to repro yourselves :p
camegone
syncpulse: In my log, There are a few "Curl error 23" which means "failed to write". I think it's prettey sus.
camegone
I found a more strange fact.
While resolving normal video failed, YouTube Shorts can be played.
(This is a phone screen shot, but Quest behaved the same.)