Video refuses to play when default quality is not set to auto

[st-am]

Official Instance

• [X] The bug is reproducible on the official hosted instance, or is API-related.

Describe the bug

When setting the default quality to anything other than auto, videos refuse to play and either infinitely load or the video progress bar goes fully or partially red, as if i've watched the video.

To Reproduce

1. Set default quality to anything other than auto
2. Attempt to watch a video

Expected behavior

Video plays

Logs/Errors

No response

Browser, and OS with Version.

LibreWolf 128.0-2 on Arch Linux

Additional context

No response

[kovdan01]

I actually have an opposite behavior: videos refuse to play when quality is auto, but setting quality to anything except auto resolves the issue. But I'm running my own instance.

[trubeck]

I actually have an opposite behavior: videos refuse to play when quality is auto, but setting quality to anything except auto resolves the issue. But I'm running my own instance.

I have the same behavior on Adminforge. I'm accessing with Firefox 128.0 on Win 11.

[ChocolatePie698]

I'm having the same issue I think. But I receive an error when refreshing the page. Error 3015.

[bonswouar]

Same behavior here, Librewolf/Linux and Firefox/Windows, it seems it appeared in a quite recent update. By the way setting it to auto by default and change it manually for each video works

[st-am]

Same behavior here, Librewolf/Linux and Firefox/Windows, it seems it appeared in a quite recent update. By the way setting it to auto by default and change it manually for each video works

I tested it on Brave Browser and had the same issue, I prefer not to use the qualities on the video player because it has slightly compressed audio, while using the default qualities in Preferences, I didn't have this issue, and side note, when I go into the quality options on the video player and select what quality I want to use, while using a quality from the preferences tab, the quality says auto and selecting it shows none of the qualities are selected.

[ac615223s5]

The problem seems to only happen in docker, not in the development version edit: nvm

[ACR-Jeff]

Thank you for bringing this up. I was pulling my hair out trying to figure this out, I can confirm this is an issue and it solved my loss of hair issue.

Void Linux using Librewolf

[Kostrol]

Auto does not work properly either, it does not change/scale with bandwidth or buffering and for me is just stuck playing at 240p for most of the instances I've tried, exception is official kavin libre.

[bonswouar]

I prefer not to use the qualities on the video player because it has slightly compressed audio, while using the default qualities in Preferences, I didn't have this issue, and side note, when I go into the quality options on the video player and select what quality I want to use, while using a quality from the preferences tab, the quality says auto and selecting it shows none of the qualities are selected.

For me (using latest version) changing the quality manually on the video player does change the audio quality too, and it does show as selected in the player

[Atemu]

This happens on basically every video now for me.

Has anyone identified a root cause yet?

[opusforlife2]

This seems to be fixed as of right now. I've opened 4-5 videos on the main instance and the bug is gone.

[st-am]

This seems to be fixed as of right now. I've opened 4-5 videos on the main instance and the bug is gone.

You're right, it's fixed

[st-am]

nvm

[Kostrol]

CDN version?

The issue still persists for me for me for libre and a few other private instances, one returned 3015 error. These video not playing issues are very nuanced and conflicting I find, a few videos will be stuck no matter how many refreshes or instance changes you do, and then you open a few recommended ones and they will start playing, I don't understand it. No errors most of the time, I don't know if there is a page where you can view what they mean when they do show up.

[Atemu]

This happens on a private self-hosted instance for me, so it's certainly not a CDN issue. Though I do have a reverse proxy (nginx) in front of course.

[ChocolatePie698]

This is currently still happening. Not sure how to fix this.