recloudstream / recloudstream/cloudstream

Optimize video player engine to prevent buffering

Open
#3,097 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
Kotlin
Stars
10.7k
Forks
1.1k
Avg merge
1d 23h
Merged PRs (30d)
15

Description

Describe your suggested feature
Summary

Heavy video buffering occurs on a 100 Mbps internet connection when playing files (~2GB), heavily impacting playback performance.

Current Behavior

Videos frequently buffer and stall, even when the file size is relatively small (around 2GB) and network bandwidth is high (100 Mbps). The current internal video player does not seem to utilize network speed efficiently or manage caching effectively.

Expected Behavior / Feature Request

Implement a more robust video player engine or add optimization options inspired by high-performance players (like the UC Browser video player engine) that feature:

  • Advanced Caching: Aggressive pre-loading/buffering algorithms to maximize available bandwidth.
  • Playback Boost Options: Performance optimizations/hardware acceleration to ensure smooth rendering.
  • Buffer-Free Streaming: Seamless playback for 2GB+ media files on standard high-speed connections.
Environment Details
  • Network Speed: 100 Mbps
  • Average File Size Affected: ~2GB
Other details

No response

Acknowledgements
  • My suggestion is NOT about adding a new provider
  • I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open issue.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the buffering with the current internal video player using the stated 100 Mbps connection and approximately 2GB files. Trace the existing buffering, caching, and rendering path before evaluating optimization options. Done means smooth playback with substantially fewer stalls under comparable conditions, including for 2GB+ media.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, kotlin
Domain
audio-video-rtc, mobile-dev
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.