Skip to content
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

Videojs error "The media playback was aborted due to a corruption problem..." #3471

Open
SpectreZ64 opened this issue Dec 7, 2023 · 8 comments
Labels

Comments

@SpectreZ64
Copy link

SpectreZ64 commented Dec 7, 2023

Sometimes my viewers has an error VIDEOJS: ERROR: (CODE:3 MEDIA_ERR_DECODE) The media playback was aborted due to a corruption problem or because the media used features your browser did not support. In Owncast log time="2023-12-07T07:52:52Z" level=error msg="exit status 1". My viewers can only restart stream page and connect to stream again. This error occured about every half hour.
My server quite powerful and configured for using S3 Storage (Backblaze). Owncast ran via Docker container with autorestart on fail feature. I tryed to modify video configuration, but it's not help me with this trouble.
How I can inspect this error more informative? Maybe I can configufe log for writing some detail information?

@rmens
Copy link

rmens commented Dec 7, 2023

Are you using passthrough mode?

@SpectreZ64
Copy link
Author

No, I have 4 output settings without passthrough mode.

@gabek
Copy link
Member

gabek commented Dec 8, 2023

Sounds like this is a new case I hadn't added to the Troubleshooting page.

Would you mind putting your stream through HLS Analyzer to see what it's reporting back?

@SpectreZ64
Copy link
Author

@gabek thank you for your response.
HLS Analyzer has found two errors with my low quality stream settings:

1702393783: ERROR EC-2001: The ratio of measured peak bitrate (462.23 kbps) to specified bitrate (369.60 kbps) is 125.06%, which exceeds recommended 125% maximum. (29 seconds ago)

1702393783: ERROR EC-2001: The ratio of measured peak bitrate (1599.75 kbps) to specified bitrate (1249.60 kbps) is 128.02%, which exceeds recommended 125% maximum. (1 minute, 2 seconds ago)

@gabek
Copy link
Member

gabek commented Dec 13, 2023

That wouldn't be connected.

One thought, are you sure you have the video codec installed on your playback device? Have you tried other browsers?

@SpectreZ64
Copy link
Author

This errors fired in some different devices randomly with different browsers and OS.

I have try some other tests in HLS Analyzer and collected this errors with similar contents:

1702901948: ERROR EC-2002: Could not download segment https://s3.eu-central-003.backblazeb2.com/ambdoc/hls/3/stream-EZHazzdIg-1572.ts (1 minute, 8 seconds ago)
1702901948: Timeout condition: (28, 'Operation timed out after 4502 milliseconds with 0 bytes received')

1702903071: ERROR EC-2002: Could not download segment https://s3.eu-central-003.backblazeb2.com/ambdoc/hls/1/stream-EZHazzdIg-1947.ts (51 seconds ago)
1702903071: Timeout condition: (28, 'Operation timed out after 4500 milliseconds with 0 bytes received')

1702910300: ERROR EC-2002: Could not download segment https://s3.eu-central-003.backblazeb2.com/ambdoc/hls/2/stream-EZHazzdIg-4358.ts (4 minutes, 33 seconds ago)
1702910300: Timeout condition: (28, 'Operation timed out after 4501 milliseconds with 0 bytes received')

I suspect it's may be because my server location in Russia and cloud storage in Europe. I will try to use another cloud storage (Yandex Object Storage), if I can configure integration.

@gabek
Copy link
Member

gabek commented Dec 19, 2023

I would test not using object storage at all, to make sure things are working without additional settings.

Copy link

stale bot commented Mar 17, 2024

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If this was a feature request that others have shown no interest in then it's likely to not get implemented due to lack of interest. If others also want to see this feature then now is the time to say something! Thank you for your contributions.

@stale stale bot added the stale label Mar 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants