-
Notifications
You must be signed in to change notification settings - Fork 54
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
disable previous / next video preloading #2284
Comments
Agree, I have lots of videos on a 100Mbps server with Nextcloud, and I observed very poor performance when previewing these videos. However, there is no problem when using the sharing link to view a single video file. PS. I use this Nextcloud instance which only have 1 user |
Preload metadata should only load a few KB of video, I'm surprised that has such a big effect on your servers.
Well, that would epxlain it, 100mbps is really low for a server serving videos :/ |
it does not load only metadata but the whole video
it's not a slow host if you have only one user. |
Is any of you in Nextcloud 29 ? |
@olaulau what is the total size downloaded by your browser on the preloaded videos? |
migrated to nextcloud hub 8 (29.0.3). |
100MB from videos other than the current one you mean? |
yes, filtering with current file shows only a third of total media transferred. |
Is your feature request related to a problem? Please describe.
when playing some high rate video (from a gopro for example), with many in the same folder, the viewer preloads simultaneously the previous and the next video, which can be very laggy.
Describe the solution you'd like
we could :
viewer/src/components/Videos.vue
Line 39 in aee0712
Describe alternatives you've considered
I don't really know how to develop with vue.js and compile this sources, but I figured out this workaround :
we can see in FF network debugger that only one video file is requested (before we could see 3 different videos requested)
Additional context
it is not a cpu problem, my hosting server is ok, it's really a bandwidth problem, which is felt more from internet than locally.
The text was updated successfully, but these errors were encountered: