Reply To: Nitro’s thumbails far from futureproof?


Home Forums Nitro for Mac Nitro’s thumbails far from futureproof? Reply To: Nitro’s thumbails far from futureproof?

#134067
Joachim Jundt
Participant

Are you sure you understood what I wrote?

“You are right. You are asking for trouble. Please do not manipulate the Nitro Previews folder.”

For the third and last time: I DO NOT MANIPULATE THE NITRO PREVIEWS FOLDER!!! Neither am I generating subfolders nor deleting or adding files to it. I’m fully aware to not mess up a given Nitro folder structure. And the one asking for trouble imo is Nitro’s programmer by throwing all thumbnails (in their respective size) into single folders one for each thumbnail size, but only because in other apps I experience longer and longer response times the more content one single folder has.

All I do – and this is long term practice, which you are maybe not aware of – is shrinking the big JPGs generated by Nitro using Apple’s raw-conversion machinery with a standalone app to an acceptable size, but without fiddling with their quality or compression settings. My experiments with JPEGmini Pro from Beamr Imaging ltd a couple of years (!) ago did show no quality loss, no hickups and so far it saved me 196 GB of disk space and – more important – my images in the web load faster. JPEGmini Pro appears to have better algorithms.

Once again, I have to do this process because your application sits on a sometime crowded library on the main drive and stores large thumbnails there without giving me the option of using an external SSD for the growing database and number of thumbnails. Using JPEGmini Pro is the only way to postpone the moment of ‘no more storage space available’ a little further into the future.

“The app avoids creating large previews when they aren’t needed.” If I tell the app to create (better) thumbnail views of a selection of images, I expect the app to do so and to do it with all selected images, not only ⅓ of them!

At first, I was pleasantly surprised that Nitro can deal with large Hasselblad files. Downsides are Nitro’s forced residence on the main drive which will not expand. Also, the poor quality of the JPG previews inside the RAW as Hasselblad opts for “fff” (sort of TIF, I guess) previews in their genuine raw converter Phocus. And now this weird behaviour.

Suggestion: I’ll prepare a screenvideo and send a link to it by mail as I’m afraid, me being no native speaker would possibly create more misunderstandable text