-
-
Notifications
You must be signed in to change notification settings - Fork 105
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
Corrupted Video on Quest 3 #1550
Comments
Which OS version do you have? We have seen issues related to media playback on some Meta OS versions. The same Wolvic package didn't have any issue. |
I'm currently on v69 but it was happening on v68 too, and possibly earlier though I can't remember when I first tried. I don't know if it matters but I did try playing a few different HD videos (the problem doesn't seem to happen on SD from brief testing) and the only thing I noticed (and this wasn't an exhaustive check) was that, using Mediainfo, the videos that seem to have the problem are all 25 FPS whereas ones that seem OK are 23.976 FPS. The above could just be coincidence and I don't have an awful lot of Blu-rays to test with, so take it with a pinch of salt. |
That's very good info, any particular codec? |
Configuration
Wolvic version: 1.7
Wolvic build ID: unknown
Hardware: Meta Quest 3
Steps to Reproduce
Video of issue: https://github.com/user-attachments/assets/a8d8700d-105f-4c3a-801a-e5723e1ce56c
Current Behavior
I use Plex to play a lot of my media. When trying to play some MakeMKV Blu-ray rips (notably Doctor Who in this instance) on Wolvic the bottom part of the screen is corrupted (see video clip) which makes it quite unwatchable. The same video can be played via Plex with Firefox on my Linux Mint PC and with Meta's own Chromium browser.
Expected Behavior
Ability to play the video without corruption
Possible Solution
Context
The only real effect is that I have to use a different browser for some of my media. Not a showstopper, just annoying having to jump between them and I prefer Firefox to Chromium.
Error Logs and Stack Traces
The text was updated successfully, but these errors were encountered: