Forum Replies Created
-
Posts
-
Inserting GPS data is always cumbersome in my experience.
Separate GPS-trackers like Solmeta drain their battery empty and the switch to the camera’s battery draining. Also, the tracker can write directly into the RAW (at least the Nikon version), but that means dedicated cables – and the Solmeta spiral cables were of questionable quality. Falling apart after 3 or 4 years.
Maintaining a WLAN connection between phone app and camera is also draining both device’s batteries.
Inside a building GPS often doesn’t work. Then it’s the phone’s capability to use known WLAN addresses as location tags.
Transferring iPhone or other cellphone’s GPS entries lateron is extra work and so far I haven’t found an easy way to do so, like copy & paste.Sometimes it would be just enough if the camera registers one place and transfer this metadata to all following images until it’s moved 20 or more meters away (like a birdwatching stand), but apparently it’s more interesting for the manufacturers to put in 5 dozen different video modes instead of one useful GPS feature.
Personally I’d like the GPS stored in the RAW file, its’ a feature like storing the focuspoint/s, orientation of the frame, type of exposure meter and belongs to that image. When I transferred my Aperture libraries to Crapture One, I benefitted a lot of the way Aperture’s designers implemented “places”.
Just as additional information: Excire and Peakto are doing this kind of analysis thing like “how many images I took with which camera / lens(es) in a specific time frame” or simply answering the question “how many images did I really take with that heavy, expensive lens I needed so badly?”. There’s also another little app called Photo Statistica from Bristol coding (or something along that name line) in the app store.
However, two things do make that approach less usesful:
Not every body (although with the same mount) is reading lens data the same way. Especially the “maker” tag comes up with surprises. Now, wether Sigma changed the lens description between firmware updates or several bodies of the L-mount “alliance” got different ideas implemented how to write the lens description into the meta tag section. Various lens entries appear twice, although it’s the same lens.
Nitro’s approach to not work with a database of it’s own (correct me if I’m wrong) will make this filtering a bit more time consuming, I believe, but images on several external drives will increase the duration of that query, too, no?Take care @David Brewster when it comes to keywords in C1. Exporting a keyword catalog from C1 will result in a non-alphabetical mess in my experience. And correcting typos in keywords is a nightmare if some images already got the keywords with typo: First I need to find these images (in all catalogs…), then create an album and put them in, then delete the wrong one and apply the corrected one, else I’d get images with “buirch” and “birch”. Next annoying thing are capitals. For C1 a TREE is something else than a tree and something else than a Tree. At first glance this could be helpful to build hierarchies, in reality it’s a nightmare finding keywords. If you just starting with keywords you might be better off using Nitro for keywording.
C1’s ability to use catalogs instead of only sessions was introduced long ago and since then, not much happened to improve usability.
@HansKG, just to mention: a decade is 10 years, not 5. As “everything is neatly sorted” for you, I don’t dare to ask how you get an overview over 6 levels of folders. To me that would be a constant nightmare. And a partition is not a folder, but anyway, as you say it’s working for you – great. So, you basically use the finder’s search if you need images of a castle you made during some vacancies?
Tried to put a screen video together: https://sojujo.smugmug.com/Other/DxO-Forum/n-Cr7pHp/i-kZCxcfd/A The facade in the video also shows a part, which is not vertical (will of architect), so I had to use lines for the outside of the image. It’s not the average use case. But using the sliders sometimes just shows the problem that my camera was not exactly vertical in that moment which the needs my mouse to travel long distances between straightening and perspective tool. And the 4 point tool is simply unforeseeable for me.
I’m using the last version without subscription (16.2.6.7), so I can’t say anything about 16.6. But I see the main differences:
Vertical, horizontal or both at once can be corrected by two or four lines, each with two handles. The handles could be even more helpful, if Crapture One devs would have considered to let them become a loupe, when the cursor is on them, but maybe the newer versions are improved.
This makes the process easy to understand, compared to the sliders of Nitro. I simply adjust to line to an object which needs to be upright or horizontally Also, I don’t need to level the image before I can try to correct the perspective. And thanks to the lines, I can use small portions of the image and still get a good result. Of course, I’m used to it and maybe need more time to get used to Nitro’s way. But if I have to adjust more than one image, I have to scroll down quite a bit to get to the tools, still need more time and get less convincing results.
The 4 point adjustment of C1 (and Nitro, too) is good to quickly get a frame of a painting, a window or a monitor screen in an image rectangular. But an image of houses in an alley is different, here I only need verticals.
As @JillJam stated, the auto-correction is a very good starting point and thanks to the guiding lines (?) adjustment of facades with old houses with not much straight or upright lines still can be done.
Thank you very much. I don’t know of any other camera now with a RAW format that requires conversion to another RAW format. When I shoot tethered, the files go to the drive as .fff. The difference in size is between 20 and 30 MB per RAW. Strange.
There was an update of Phocus in October 2024 and the last version was released end of March 2025. Can’t see a connection.
It’s not coming from JPGmini. I just checked a file which I put into JPGmini just half an hour ago. Result:
File modification happended more than two months after the image was taken, but not tonight. Nonetheless, Nitro is not showing Date created / Date/time Original.Could that have something to do with my reprocessing the big previews in JPEGmini? In other pictures from other cameras the “File modification date/time” is the same as the “Date created Date/time Original“. But not with the X2D RAWs.
On second thought: Maybe not. My workflow with this camera is
-
Open Hasselblad Phocus
Connect the camera to the Mac
Import the .3FR RAWs
Then they become .fff RAWs and are smaller than before, so something is changed by Phocus
After that I navigate to ‘/Users/myName/Library/Containers/com.gentlemencoders.nitro/Data/Library/Caches/File System’
Select all folders and drag them over JPGmini’s app window (files remain in place, of course, no harm is done)James, auto-correction is always a bit of a gamble, but I believe, instead of trying to autocorrect in other photo editors you might be just as quick remaining inside Nitro… no, I just tried, sorry. Phew.
The problem with 4 point perspective corrector is that you really need to know how the new perspective should look like before your start it. In most other apps I align two construction-lines along two lines in the image which should be straight, either upright or horizontally. This is a lot of try & error in Nitro and the fact, that a portion of the image is enlarged massively and I first need to correct “enlargement” makes it less useful than most other competitors.
It’s not always about rectangularity in the image, depending on my perspective towards a facade. And cropping away huge chunks of the image which are outside the field of the perspective corrector makes the result (too often) useless. This looks like a lot of work needed.
I have completed the list. Impressive work you have done! I emailed it to you, please feel free to ask if my changes and comments are unclear.
Btw. I’m absolutely blown away by what Nitro can do in the first release version of this keyword feature! Great work, Capture Oje (my translation for the Danish DAM attempt) will never eben dare to think about something like this.
I also made a brief comparison bewteen Nitro AI keywording and Excire for a friend of mine. I think it went well, so I forwarded it to the author of some photo app tests in German computer magazine c’t. I’d like Nitro to be featured a bit more by them.
Yeah, I like to help. How would it be the easiest way for you? Your German keyword-list in a Numbers-table and mine topo, to check and compare my changes?
