recloudstream / recloudstream/cloudstream
playback on mpv doesn't save progress on Cloudstream
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 10.7k
- Forks
- 1.1k
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 15
Description
Steps to reproduce
Set mpv as default player.
Play any video for some time.
Close it and try to see if the progress is recorded in Cloudstream.
Resume the video again but it doesn't save progress and will start over again.
However when playing videos on VLC, the progress is saved on Cloudstream as well.
mpv is much faster than VLC, so i prefer using it. Can you please fix this issue in next release?
Expected behavior
Playback on mpv should record playback progress on Cloudstream so as to resume easily.
Actual behavior
Playback on mpv doesn't save playback progress and cannot resume from last position.
Cloudstream version and commit hash
3.2.4
Android version
11
Logcat
No response
Other details
No response
Acknowledgements
- I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open issue.
- I have written a short but informative title.
- I have updated the app to pre-release version Latest.
- If related to a provider, I have checked the site and it works, but not the app.
- I will fill out all of the requested information in this form.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the Android mpv playback integration and comparing it with the VLC path that records progress. Reproduce the issue with mpv, then verify that closing and resuming playback restores the last position as it does with VLC.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100