-
Notifications
You must be signed in to change notification settings - Fork 8
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
[BUG] Streaming video: on iphone it is only starting after complete download #363
Comments
@orgaralf you did not play the file in the iOS app, you played it in Safari browser, in a public link share? I moved the issue to the |
You can check if your web server is properly configured to support range requests:
|
@michaelstingl
Conclusio:
NOTE |
This is the output of the curl test with nginx:
|
@mmattel this issue is about the mediaviewer app, which is a pure web player. So only issues in desktop or mobile browsers are in scope. For issues with the ownCloud iOS app, please open in iOS app repo. For issues with 3rd party apps accessing via WebDAV, please open in the server core repo. |
I have collected the tests made to have an overview. |
Here are more results from further testing. Setup
Result Conclusio @micbar after diving into that issue, files_mediaviewer is not able to stream a streamable video file. There is no webserver or client issue |
Steps to reproduce
Expected behavior
The video stream should start quickly (few seconds max on a fast network).
Actual behavior
It seems the client downloads the file completely.
Client
iOS version: 14.3
ownCloud app version: 11.4.5 build 182
Device model: iPhone 12 pro
Server configuration
Web server: Apache 2.4
Database: MariaDB 10.3
PHP version: 7.2.24
ownCloud version: 10.6
Storage backend (external storage): NFS mounted shares
Logs
Web server error log
I would expect the server to add the fast load info on the file, when I play longer movies inline (eg. qt-faststart) or make that configurable? https://stackoverflow.com/questions/50914503/fastest-way-to-add-movflags-faststart-to-an-mp4-using-ffmpeg-leaving-everythi
RPReplay_Final1611414336.MP4
The text was updated successfully, but these errors were encountered: