immich
immich copied to clipboard
[BUG] [WEB] Video previews in Gridview keep downloading, even if they are not visible anymore (reopen)
Describe the bug If I scroll through my assets and hover over an video, it starts to download and preview it, which is a great feature.
The Prolbem is, that it does not stop to download the video, even, if I scrolled away from that video, which makes previewing images very slow, since it blocks my bandwidth.
To Reproduce Steps to reproduce the behavior:
- I installed Immich through docker-compose
- Placed an Nginx reverse proxy for ssl in front of it.
- Upload assets from my phone
- In Web: Hover over an video and scroll down. Keep an eye on networktraffic of my machine.
Expected behavior The download of the video stops, as soon as I stop hovering with my mouse over an video (or at least as soon, as it is no longer visible in the browser through scrolling.
Screenshots If applicable, add screenshots to help explain your problem.
System
- Server Version:
<1.35>
- Mobile App Version:
<1.35>
Additional context Browser is Firefox on MacOS 13
This is a reopened Ticket for #875
This might be the Firefox problem only. I've tested on Chrome and Brave, and I cannot reproduce this issue. Hmm. Can you help check the network tab of Firefox?
Sure! I'm not sure what I am looking for though.
I can see these GETs for media as soon as I scroll over them:
Maybe it's worth to mention, that they are h265 files, that can not be played in the browser..
I can also still reproduce this on Chromium and Safari.
In the video I hover over a bunch of videos and scroll down. On the right you can see, that chromium does not stop to download the videos in the background.
https://user-images.githubusercontent.com/22196236/201402669-129adaea-560d-4787-8666-892938c0f5d9.mov
Edit: The recording was made on Chromium
H.265 can now be played in Chrome. They added that feature sometime last week, I believe. It still cannot be played on Firefox, though.
I see you have a group of videos you hovered over, correct? My test was conducted on a single photo hovering action.
Yes it was a group of videos. Sorry I didn't consider this to have an impact. ^^
Yea, Firefox does not support it because of the royalty fees. Plain Chromium does not support it as well, for the same reason. I try to avoid Google as much as I can, that's why I do not use Chrome.
Paitently waiting for #203 because of this :)
Yes it was a group of videos. Sorry I didn't consider this to have an impact. ^^
Yea, Firefox does not support it because of the royalty fees. Plain Chromium does not support it as well, for the same reason. I try to avoid Google as much as I can, that's why I do not use Chrome.
Paitently waiting for #203 because of this :)
Got it! I will try to reproduce the scenario and get back to you on the fix
To help reproducing:
Chromium seems to work correctly now (1.38.2). My h265 Files (not playable in open source chromium) are not downloading anymore (only a few megs). Same goes for large and small Files (av01 tested) that are playable after hovering over.
Firefox keeps loading the h265 files for 30 seconds after it breaks up. It does not seem to download the hole file. The large av01 file behaves the same. After hovering over it, it keeps downloading the file for 30 seconds until it stops. The small 720p file behaves accordingly, as it stops loading more or less directly after stopping the hover. The large av01 file keeps loading for about 30 Seconds like the h265 files.
Internet Speed 100 Mbit/s
The av01 Videos are downloaded from Youtube.
File | Firefox download time after hover | Chromium download time after hove |
---|---|---|
h265 Video length: 4 Minutes, size: 1,4GB | 30 Seconds | ~3 Second |
av01 8k length: 14 Minutes, size: 3GB | 30 Seconds | ~3 Second |
av01 720p length: 14 Minutes, size: 93MB | ~3 Seconds | ~3 Seconds |
Conclusion: The codec does not seem to make a difference. It's more about the file size (or more probably the bitrate).
Maybe Firefox wants to buffer a specific amount of time?
What about a setting to disable video previews? Not as a fix but as a workaround since a low bandwidth mode would be nice as well.