Forum Replies Created
-
Posts
-
Thanks for your reply. You’re sure about the path?
I found one here: /Users/JoJu/Library/Containers/com.gentlemencoders.nitro/Data/Library/HTTPStorages/com.gentlemencoders.nitroAnd the imho real library with some “fat JPG suspects” is here: ‘/Users/JoJu/Library/Containers/com.gentlemencoders.nitro/Data/Library/Caches/File System/FullSize-1’
123 files, 1.43 GB – now I let JPEGmini work on them: 934 MB, ⅓ saved, and Nitro still working. Excellent, I will treat all 3FR jpg previews in Nitro that way!File names missing:
Especially when using the comparison or multi-view and deleting the less good ones, it would be nice to see the filenames.As an addition: For now I can live with that workaround. But with growing image and preview archives, I expect an app to reside on an external drive, at least with the data folders. I cannot open the Mac Studio and plug another drive into it.
Nik, it has been 40 days now since I asked where Nitro stores it’s preview thumbnails. As Nitro improves it’s previews drastically, I’d like to create thumbnails for all of my 3FR raw files. But as long as I don’t know in which location they are hosted, I shy back to go on with this. I’d love to use my X2D (I bought one after the rental) together with Nitro and will later do a raw-converter comparison. Editing with Nitro so far was the best experience of all three converters.
Btw., how can I always see the image’s name? I tried to find a setting to do so, no success.
Your guess is right, Nik. Rebuilding thumbnails is improving the quality of the 3FR raw-file. Now I need to know where these previews are stored as I host all other raw-converter databases on an external SSD. I’d like to do the same with Nitro but so far I haven’t found a database related to Nitro. If Nitro needs the internal disk which is limited and very expensive at Apple, I can’t use it in the future to fill it up with JPG previews.
No problems here as well. It’s best in dark mode, but also in “bright mode” the blue frame is recognizable. I’ve seen worse in other apps.
Thank you very much, Nik. That are some answers to questions I have put on a mind map. But the more I think about, the more I tend to “skip the app in the middle” (=Photos). Tidying up my main lib already is plenty of work to invest. So far my images were not referenced, just inside the aplibrary container.
Disk space is no issue, there’s still 14 TB free space on a 24 TB drive.
I will try again to find an article about a way to run old apps on a new Mac OS. I know, there will be limits, too. But so far I could not find a well-working way to get library structures and image edits from Aperture into another app. Using Capture One’s “import AA lib” routine would also lead to bad results and at the end, it’s developers were straightforward too stupid or incapable of implementing a decent full text search for album/projects names. So I really don’t want to know how their idea of a DAM materialised. It’s an idea without any proper manual for dummy programmers… Can you imagine? Since the end of Aperture no image managing software calling itself a DAM comes even close to old Aperture’s abilities? It’s really sad.
“– crowdsource a wiki and let us fill it in and you can check and correct”
Sorry Pito Salas, as a technical author I’d like you to just give us at least one link to an app where that idea is working properly and with reliable content. For now, I am convinced this won’t be working. Why?
-
Anybody in that crowdsource will get Nitro after it’s released.
Then write some articles into the wiki, with some errors about functions, terminology, translations.
These errors will need more time to get fixed than the app itself.
Anybody looking into that wiki will have to spend some time to find out which article is credible and which is under construction.Nik, in my experience Word is about the worst tool for this job, but I admit to be one of the worst users as I have too many reservations against it and no experience at all on Word for Mac as I refuse to install and pay this plague. Unreliable, complicated, unpredictable are the first topics coming in my mind.
“Distracting” could also be said about the thumbnails they are also in colours. To me, it’s a completely different work: being in the library and organize it or editing images. Honestly, I never got my head around that reasoning: colours are an important factor of organizing traffic or bring people to the right airplane. Imagine all traffic signs would be grey to not distract from the landscape :D.
Anyway, in my opinion it was a very stupid design decision and so far nobody delivered some logical, comprehensive basics about that. I say “some people need the colours to navigate quicker”. And the larger the library, the more important becomes a quick navigation.
