[Bug] The media playback was aborted due to a corruption problem or because the media used features your browser did not support. #98

Open
opened 2025-03-08 02:10:42 -03:00 by SarhaSarha · 9 comments

Describe the bug

This error ekeeps appearing on every single video I watch and I can't even watch ghem all the way through this bug is so annoying?! It's worse than the media cound not be kloaded error! And t keeps loading for long periods of time too.

Steps to Reproduce

Logs

Screenshots

Additional context

<!-- BEFORE TRYING TO REPORT A BUG: * Read the FAQ: https://docs.invidious.io/faq/! * Use the search function to check if there is already an issue open for your problem: https://github.com/search?q=repo%3Aiv-org%2Finvidious+replace+me+with+your+bug&type=issues! MAKE SURE TO FOLLOW THE TWO STEPS ABOVE BEFORE REPORTING A BUG. A BUG THAT ALREADY EXIST WILL IMMEDIATELY CLOSED. If you want to suggest a new feature please use "Feature request" instead If you want to suggest an enhancement to an existing feature please use "Enhancement" instead --> **Describe the bug** <!-- A clear and concise description of what the bug is. --> This error ekeeps appearing on every single video I watch and I can't even watch ghem all the way through this bug is so annoying?! It's worse than the media cound not be kloaded error! And t keeps loading for long periods of time too. **Steps to Reproduce** <!-- Steps to reproduce the behavior: 1. Go to 'inv.nadeko.net' 2. Click on 'a video, for exampe https://inv.nadeko.net/watch?v=8POqpsnq-OY' 3. Watch the video entirely 4. See error --> **Logs** <!-- If applicable, copy the log that appear in the browser page where the error is reported. --> **Screenshots** <!-- If applicable, add screenshots to help explain your problem. --> **Additional context** <!-- Add any other context about the problem here. - Browser (if applicable): - OS (if applicable): -->
Owner

which browser do you use? Os? There is a lot of people using the instance with no problems right now so it's a problem on your end

which browser do you use? Os? There is a lot of people using the instance with no problems right now so it's a problem on your end
Author

Windows 11 on edge,

Windows 11 on edge,
Owner

Then read https://docs.invidious.io/devtools/ and tell me if you see any errors. Try another browser like firefox too.

Then read https://docs.invidious.io/devtools/ and tell me if you see any errors. Try another browser like firefox too.

Using LibreWolf on Linux. I got NS_ERROR_NET_PARTIAL_TRANSFER for a request of type mp4:

image

Using LibreWolf on Linux. I got NS_ERROR_NET_PARTIAL_TRANSFER for a request of type mp4: ![image](/attachments/b00da3b4-8ea7-4034-88f3-94e2256c2cf5)
Owner

@four_two_eight wrote in #98 (comment):

Using LibreWolf on Linux. I got NS_ERROR_NET_PARTIAL_TRANSFER:

image

That's normal, youtube servers seem to drop the connection a request takes too long (like that one). It may also be that the IP of the videoplayback proxy changed. If you are listening to music, I recommend you to watch it as a video instead with the minimum resolution, in that way, you only request small parts of the video and audio, unlike when you set the listen only mode.

@four_two_eight wrote in https://git.nadeko.net/Fijxu/invidious/issues/98#issuecomment-8017: > Using LibreWolf on Linux. I got NS_ERROR_NET_PARTIAL_TRANSFER: > > ![image](/Fijxu/invidious/attachments/b00da3b4-8ea7-4034-88f3-94e2256c2cf5) That's normal, youtube servers seem to drop the connection a request takes too long (like that one). It may also be that the IP of the videoplayback proxy changed. If you are listening to music, I recommend you to watch it as a video instead with the minimum resolution, in that way, you only request small parts of the video and audio, unlike when you set the listen only mode.

The media playback was aborted due to a corruption problem or because the media used features your browser did not support.

yeah, happens to me too. the whole point of invidious to be so ugly is to be backward compatible with a variety of older setups. its not like we want to play video on win95 with ie5 browser.

what kind of "features" are shipped with the media (video) that the (fairly modern) browser is not able to support it... I can think of only on HLS/DASH playback feature, but then again, it works just fine on yt and non-invidious sources that use this tech, so something must be off with invidious itself

> The media playback was aborted due to a corruption problem or because the media used features your browser did not support. yeah, happens to me too. the whole point of invidious to be so ugly is to be backward compatible with a variety of older setups. its not like we want to play video on win95 with [ie5](https://en.wikipedia.org/wiki/Internet_Explorer_5) browser. what kind of "features" are shipped with the media (video) that the (fairly modern) browser is not able to support it... I can think of only on HLS/DASH playback feature, but then again, it works just fine on yt and non-invidious sources that use this tech, so something must be off with invidious itself
Author

It may be the corruptin problem pthough

It may be the corruptin problem pthough

This seems to happen all the time to me since a week or so, nothing weird shows up in the dev tools (at least with regards to videoplayback requests) but the error pops up.

Steps to reproduce without waiting:

  1. select medium as preferred video quality
  2. start playing the video
  3. seek to a place that's not yet buffered
  4. BOOM

Also, leaving the video unattended for a few minutes and resuming playback usually triggers the error, too.

Workaround:

Change the video quality to DASH and accept the video will stutter even at 240p if played at 1.5x or more :-(

Tested on:

ungoogled-chromium 134.0.6998.35

This seems to happen all the time to me since a week or so, nothing weird shows up in the dev tools (at least with regards to videoplayback requests) but the error pops up. **Steps to reproduce without waiting:** 1. select `medium` as preferred video quality 2. start playing the video 3. seek to a place that's not yet buffered 4. *BOOM* Also, leaving the video unattended for a few minutes and resuming playback usually triggers the error, too. **Workaround:** Change the video quality to DASH and accept the video will stutter even at 240p if played at 1.5x or more :-( **Tested on:** ungoogled-chromium 134.0.6998.35
Owner

@talia1561 wrote in #98 (comment):

  • select medium as preferred video quality

  • start playing the video

  • seek to a place that's not yet buffered

  • BOOM

Yep indeed that is a shit "bug". I don't know how to fix that because that is more in the VideoJS side of things. I'll see what I can do tho.

@talia1561 wrote in https://git.nadeko.net/Fijxu/invidious/issues/98#issuecomment-8049: > * select `medium` as preferred video quality > > * start playing the video > > * seek to a place that's not yet buffered > > * _BOOM_ Yep indeed that is a shit "bug". I don't know how to fix that because that is more in the VideoJS side of things. I'll see what I can do tho.
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
5 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: Fijxu/invidious#98
No description provided.