0
Answered

Image preview weird reaction

ltotsas 4 months ago • updated by Vlad R 2 months ago 8

When i try to open an image lets say up to 3mb the preview of the image load instantly!! Though when i try to open an image lets say 10mb the image takes time to fully load. 

The weird think is that when i will try to download the 10mb image without previewing it, the image will be downloaded INSTANTLY! 

If the file is too large in filesize or to big in pixel dimensions, FileRun will process it to load a smaller version of it, instead of the original file, hence the wait. Resizing a large image is not instant.

It's the expected behavior.

Is there any way to bypass this and show the whole image, or at least make the process bigger!? I mean php configuration wise!?

See "$config['app']['thumbs']['output_small_filesize']" here: http://docs.filerun.com/advanced_configuration

Having a same issue. Checked the "advanced config" section and see only "$config['thumbs']['output_small_max_filesize'] = 8388608;" which is different (?) and has no explanation. Increasing this number to 33554432 makes no difference.


Using FileRun as a personal file storage on home PC, storing large RAW and JPG image files mostly. Can you tell more about how to alter this behavior?


Some extra preview image (to, let's say, fit in 1920x1080, or custom) caching mechanism would be a pure salvation. Thank you for the best solution anyways.

The problem is that there is caching for those images and thats the flag about. BUT when an image resolution is high then the system tries to change the resolution to match a certain size lets say so it takes time. 

I still have no solution to that. 

Under review

You can use:

$config['thumbs']['output_small_max_filesize_without_size_check']

It's by default set to 2097152, which means, the pixel dimensions are not checked for files smaller than 2MB. You can increase that value as you like.

Checked the "advanced config" section and see only "$config['thumbs']['output_small_max_filesize'] = 8388608;" which is different (?) and has no explanation. Increasing this number to 33554432 makes no difference.

33554432 is 35 megabytes. Setting this value would mean FileRun  would not generate thumbnails for files lower than that, but instead just output the files if they are web-safe (PNG, JPG, etc). The exception to this make the files that are very large in pixel size, regardless of byte size, as we wouldn't want to output a 1080p image for a thumbnail.