|
| Greg's diary |
| recent entries |
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Friday, 4 July 2025 | Dereel | |
| Top of page | ||
| next day | ||
| last day |
|
More photo insights
|
Topic: photography, technology, opinion | Link here |
I hadn't planned to do much photo stuff today, since there's clearly a lot to do to process yesterday's photos. But one was easy, the Skyhawk:
That's in dire need of cropping. How hard can it be? With various excursions, it took me several hours. The simple thing is just to crop it:
|
|
||||||||||
But that's messy, with lots of artefacts. How about cropping it in DxO PhotoLab and then put it through “Perfectly Clear“?
|
|
||||||||||
That's much better, but too dark. In fact, the output of DxO looks the best:
|
|
||||||||||
And as I said yesterday, that's really quite impressive for a hand-held image corresponding to 6120 mm “full frame” focal length.
But why should that take much time? The Exif data. I still couldn't get ExifTool to play nice with the OM System OM-1 Mark II. OK, time to post a question on the ExifTool forum. Prepare an example:
Oh. I've been trying to write to the JPEG output of DxO PhotoLab. That's not ideal for blaming ExifTool. Try again with the raw image.
Oh. The problem doesn't occur with the raw image! What happens if I try to copy the Exif from raw to the JPEG image?
That works, but it causes more non-reproducible problems. But it seems that I can update the Exif data on the raw file and then copy it. I still don't understand what's going on, and why it sometimes works and sometimes doesn't, but I can live with it unless it comes back to bite me again. A couple of scripts to change, and I have worked around the issue.
|
Oven insights
|
Topic: food and drink, general, opinion | Link here |
So, a new oven? Off to take a look. I wasn't expecting it to be easy, and I wasn't disappointed. Appliances Online didn't want to know about 90 cm ovens! Well, maybe it does, but it gave me no way to select them.
Back to The Good Guys. They have 90 cm ovens ranging in price from $1399 to $4190, still considerably cheaper than the $11,500 that Appliances Online want for a 60 cm oven.
What do I get for that money? Hard to say. Somehow the comparison shows things that are uninteresting to me, and I can't find out what I want to know. How much power do they use? For the (maximum) four that I “compared”, they only showed 2. The Omega OBO9011AM, the cheapest they offer, also uses the most power, an advantage for an oven. And how hot do they get? Again only two ovens divulge that information. 240° for the Haier HWO90S10EX2, 250° for the Omega. And I was hoping for a higher temperature.
Somehow this is all too much pain. Back to our current oven to try to guess which (if any) element is burnt out. It doesn't seem to be the rear (fan) element, nor the bottom element. I need to let it cool down between each attempt, and I didn't get any further. But potentially I had just forgotten how long it takes for the oven to heat to 250°. More investigation needed.
|
LG ThinQ?
|
Topic: technology, food and drink, opinion | Link here |
Our new LG XD5B14PS dishwasher comes with advertising for LG ThinQ.
What's that? Buzzwords galore, a way to increase the pain of your smart phone by communicating with the dishwasher? About the only thing I could establish is that you can select custom wash cycles, though it's not clear what. Downloaded the app from the toyshop and started it. Please log in! Create an account! Dammit, LG, will I need an account to use your appliances next? And why do you subject me to the pain of entering text on a mobile phone?
Ah, you can sign up with a Real Computer too. Maybe. And it wants to know my date of birth! Dammit, what are you playing at? Of course there's no way for it to know, which is good, because I can't even enter it (though there's a field for entering it in the wrong format, today being 7/4/2025). I have to select from a toy calendar.
For some reason (masochism?) I tried it. It hung. Tried again. It hung. Tried again with a different browser. It hung. Tried to send mail to support. What kind of device do you have? What's wrong with it? No option to complain about their appalling web site. Selected some random stuff and sent off the real report in the text attachment (at least they allow that). No reply.
LG, what are you playing at? Are you Yet Another company who just wants to annoy their customers?
| Saturday, 5 July 2025 | Dereel | Images for 5 July 2025 |
| Top of page | ||
| previous day |
|
OM-1 problems?
|
Topic: photography, technology, opinion | Link here |
One of the nice things about the OM System OM-1 Mark II is that I can charge the battery from USB. After downloading files from the camera, I simply turn it off and leave it to charge. As a result, I have never used the two spare batteries that I bought along with the camera.
But today I came into my office to find the “battery empty” indicator flashing. It was still connected to the USB cable. Disconnect. No change. Turn on and off. No change. Finally I got it to stop by removing and replacing the battery, after which it showed 100% charge.
What happened? It seemed that hydra didn't want to let go. Looking at the system log, I had:
Jul 4 17:05:19 hydra kernel: (da3:umass-sim1:1:0:1): fatal error, failed to attach to device
Jul 4 17:05:19 hydra kernel: da3 at umass-sim1 bus 1 scbus9 target 0 lun 1
Jul 4 17:05:19 hydra kernel: da3: <OMSYSTEM OM-1MarkII 1.00> s/n BJRA15001 detached
Jul 4 17:05:19 hydra kernel: (da3:umass-sim1:1:0:1): Periph destroyed
Jul 5 08:02:54 hydra kernel: ugen0.3: <OMSYSTEM OM-1MarkII> at usbus0 (disconnected)
Jul 5 08:02:54 hydra kernel: umass1: at uhub2, port 12, addr 90 (disconnected)
Jul 5 08:02:54 hydra kernel: umass1: detached
So yesterday evening, when I was finished, the system noted the event and removed the “disk” device /dev/da3. But it didn't see a disconnect until this morning. Why? I'll have to keep my eye on it.
|
Still more ExifTool pain
|
Topic: technology, photography, opinion | Link here |
Today I spent an inordinate amount of time trying to document my success in copying Exif data to images from my OM System OM-1 Mark II, with little success. Every time I think I have got a workaround, I find they don't work or are not repeatable. Today I tried geotagging:
=== grog@hydra (/dev/pts/18) ~/Photos/20250703 872 -> exifx orig/A7032091_DxO.jpg
File orig/A7032091_DxO.jpg
Date taken: Thursday, 3 July 2025, 11:23:58
Exposure: 1/1600 sec, f/6.3 (EV 16.0), 800/30 ISO
Camera: OM Digital Solutions OM-1
Lens: LEICA DG 100-400mm f/4.0-6.3
Focal length: 400.0 mm
Meter mode: Multi-segment Aperture-priority AE
Comp: +1.3 EV
Size: 5184 x 3888 pixels (20.16 megapixels)=== grog@hydra (/dev/pts/18) ~/Photos/20250703 873 -> geotag orig/A7032091_DxO.jpg
GPSLOG /src/GPS/Tracklogs/Phones/GPSLogger/albo/20250703.gpx
exiftool -geotag=/src/GPS/Tracklogs/Phones/GPSLogger/albo/20250703.gpx orig/A7032091_DxO.jpg
1 image files updated
All well and good. But then I copied the Exif data from the raw file to correct the time (the camera was running 80 s too fast):
=== grog@hydra (/dev/pts/18) ~/Photos/20250703 875 -> exiftool -overwrite_original_in_place -TagsFromFile orig/A7032091.ORF '-all>all' orig/A7032091_DxO.jpg
Warning: [minor] Writing large value for MakerNotes - orig/A7032091_DxO.jpg
1 image files updated=== grog@hydra (/dev/pts/18) ~/Photos/20250703 876 -> geotag orig/A7032091_DxO.jpg
GPSLOG /src/GPS/Tracklogs/Phones/GPSLogger/albo/20250703.gpx
exiftool -geotag=/src/GPS/Tracklogs/Phones/GPSLogger/albo/20250703.gpx orig/A7032091_DxO.jpg
Warning: [minor] File contains multi-segment EXIF - orig/A7032091_DxO.jpg
Warning: [minor] File contains multi-segment EXIF - orig/A7032091_DxO.jpg
Error: Can't write multi-segment EXIF with external pointers - orig/A7032091_DxO.jpg
0 image files updated
1 files weren't updated due to errors
Why? It already had that data. But ExifTool is trying to update the existing Exif data in A7032091_DxO.jpg. What happens if I remove it all and just copy it? First, how do I remove the Exif data? Google Gemini to my aid again:
To remove all EXIF data:exiftool -all= your_photo.jpg
OK, I can do that:
=== grog@hydra (/dev/pts/18) ~/Photos/20250703 861 -> exiftool -all= orig/A7032091_DxO.jpg
Warning: [minor] File contains multi-segment EXIF - orig/A7032091_DxO.jpg
1 image files updated=== grog@hydra (/dev/pts/18) ~/Photos/20250703 862 -> exifx orig/A7032091_DxO.jpg
File orig/A7032091_DxO.jpg
Size: 5184 x 3888 pixels (20.16 megapixels)=== grog@hydra (/dev/pts/18) ~/Photos/20250703 863 -> exiftool -overwrite_original_in_place -TagsFromFile orig/A7032091.ORF '-all>all' orig/A7032091_DxO.jpg
Warning: [minor] Writing large value for MakerNotes - orig/A7032091_DxO.jpg
1 image files updated=== grog@hydra (/dev/pts/18) ~/Photos/20250703 864 -> exifx orig/A7032091_DxO.jpg
File orig/A7032091_DxO.jpg
Date taken: Thursday, 3 July 2025, 11:22:36
Location: 38.00496 S, 144.58989 E
Exposure: 1/1600 sec, f/6.3 (EV 16.0), 800/30 ISO
Camera: OM System OM-1 Mark II, serial BJRA15001
Lens: Leica DG Vario-Elmar 100-400 mm f/4.0-6.3
Focal length: 400.0 mm (full frame equivalent: 800 mm)
Focus: MF; C-AF, MF, Imager AF 127.39 m (118.50 - 137.72 m)
Field of view: 2.5 horizontal, 1.9 vertical, 3.1 diagonal
Meter mode: ESP Aperture-priority AE
Stabilization: On, Mode 1
Comp: +1.3 EV
Size: 5184 x 3888 pixels (20.16 megapixels)=== grog@hydra (/dev/pts/18) ~/Photos/20250703 865 -> exiftool -overwrite_original_in_place -TagsFromFile orig/A7032091.ORF '-all>all' orig/A7032091_DxO.jpg
Warning: [minor] File contains multi-segment EXIF - orig/A7032091_DxO.jpg
1 image files updated
But it's not repeatable. I think there's a secondary effect in play, maybe related to the location of the data in the image file. It would be really nice to find a solution. Does it have something to do with DxO PhotoLab, maybe? After all, it seems possible to update the raw image.
|
Hat trick
|
Topic: technology, photography, opinion | Link here |
As if all that wasn't enough, while processing my house photos I got this message on stopping Hugin:
Crash Annotation GraphicsCriticalError: |[0][GFX1-]: Detect DeviceReset DeviceResetReason::NVIDIA_VIDEO DeviceResetDetectPlace::WR_POST_UPDATE in Parent process (t=314.609) |[1][GFX1-]: Detect DeviceReset DeviceResetReason::NVIDIA_VIDEO DeviceResetDetectPlace::WR_POST_UPDATE in Parent process (t=512.092) |[2][GFX1-]: Detect DeviceReset DeviceResetReason::NVIDIA_VIDEO DeviceResetDetectPlace::WR_POST_UPDATE in Parent process (t=1200) |[3][GFX1-]: Detect DeviceReset DeviceResetReason::NVIDIA_VIDEO DeviceResetDetectPlace::WR_POST_UPDATE in Parent process (t=1561.49) |[4][GFX1-]: Detect DeviceReset DeviceResetReason::NVIDIA_VIDEO DeviceResetDetectPlace::WR_POST_UPDATE in Parent process (t=2263.19) |[5][GFX1-]: Detect DeviceReset DeviceResetReason::NVIDIA_VIDEO DeviceResetDetectPlace::WR_POST_UPDATE in Parent process (t=81123.4) |[6][GFX1-]: Detect DeviceReset DeviceResetReason::NVIDIA_VIDEO DeviceResetDetectPlace::WR_POST_UPDATE in Parent process (t=81163.4) [GFX1-]: Detect DeviceReset DeviceResetReason::NVIDIA_VIDEO DeviceResetDetectPlace::WR_POST_UPDATE in Parent process
What a mess! Is that an indication of problems with the display hardware, or just a Heisenbug?
| This page contains (roughly) yesterday's and today's entries. I have a horror of reverse chronological documents, so all my diary entries are chronological. This page normally contains the last two days, but if I fall behind it may contain more. You can find older entries in the archive. Note that I often update a diary entry a day or two after I write it. | Do you have a comment about something I have written? This is a diary, not a “blog”, and there is deliberately no provision for directly adding comments. It's also not a vehicle for third-party content. But I welcome feedback and try to reply to all messages I receive. See the diary overview for more details. If you do send me a message relating to something I have written, please indicate whether you'd prefer me not to mention your name. Otherwise I'll assume that it's OK to do so. |
| Greg's home page | This month | Greg's photos | Greg's links |
| RSS 2.0 |
|
