-
Notifications
You must be signed in to change notification settings - Fork 295
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
No option to preview files larger than 8GB #1181
Comments
I strongly agree with @DominicMe - the limitation makes sense for a default user because it costs much performance to process large files. But for advanced users there should be definitely the option to set "Any size" at all - because they know what they are doing and ressources may be no problem for them. Maybe a warning or hint message can be displayed in the settings if "Any size" is selected like "Selecting any size can cause performance issues."? |
I should also mention that in Gnome files the maximum limit is 4GB in the options menu however it is not enforced and files well over 8GB have a thumbnail preview generated with no noticeable performance decrease. |
Agree with what everyone has said so for. For now, I'm forced to open up another File Manager to generate the thumbnails, which is a big hassle |
Added options of 16GB and 32GB for thumbnail creation sizes
Added options to preview thumbnails for up to 16GB and 32GB
Great to see that it has finally been fixed, can't believe how little code change it required. Still I feel that adding hard-coded options is a temporary solution. There should be "unlimited" option as even now there are already 4k movies that are well over 32GB so it is already an issue again. |
There are many files now, especially with the arrival of 4K that will exceed 8GB meraning no thumbnail is generated. This is a really annoying and I see no reason to limit to 8GB since thumbnails are generated on the host. Why isn't there "Any Size" option? It's a silly limitation to have, and I hope a no limit option is added soon.
The text was updated successfully, but these errors were encountered: