Newerth
(Jan Šmucr)
April 11, 2023, 1:28pm
1
Friends,
I’ve got myself the Lumix G9 and tried out the 80 Mpx high resolution mode.
RW2 raw file (I was unable to upload it here)
DT almost got it right. Almost.
P1281992.RW2.xmp (7.8 KB)
An artifact appears on the right side of the image in both the render and the darkroom.
The GPU is Intel UHD Graphics 620. It does not matter whether I keep the OpenCL on or not.
Could you please try it out if it works for you?
Thank you.
Also: https://www.dpreview.com/forums/thread/4434494
kmilos
April 11, 2023, 1:35pm
2
It is possible that the crop as defined in cameras.xml
for the high-res mode is not 100% correct. You can adjust the crop manually by enabling the hidden and disabled option plugins/darkroom/rawprepare/allow_editing_crop=false
in your darktablerc
file, and then use the new crop sliders in the “raw black&white point” module after restart.
Btw, can you reproduce the same w/ the high-res G9 sample from https://raw.pixls.us/ ?
1 Like
Newerth
(Jan Šmucr)
April 11, 2023, 1:51pm
3
The samples render the same:
Also, does this have anything to do with the issue?
kmilos
April 11, 2023, 1:53pm
4
Yes, that shows that the image was cropped from the sensor width of 10480 to 10422, and that is not enough. You’ll see this when you enable that hidden option.
My guess is that this crop of 58px was only verified for the normal mode, not for hi-res… In cameras.xml
, only this is defined for the G9:
<Crop x="0" y="0" width="-58" height="0"/>
Which works for the normal mode (5264 sensor width). Funnily, the single 20MP shot from the hi-res mode has a width of 5280?! so cropping 74 works instead. And it looks like the same 74 also works for the hi-res mode.
Even more strangely, there is this “burst mode” on G9 where the width is ok, but there are artifacts on the top and bottom.
Go figure…
Btw, it looks like there is already an open issue about this: Panasonic DC-G9 high-res RAW: insufficient crop · Issue #170 · darktable-org/rawspeed · GitHub
1 Like
Newerth
(Jan Šmucr)
April 11, 2023, 2:15pm
5
There’s more I don’t understand. The EXIF info reveals more crop details:
https://raw.pixls.us/getfile.php/2584/exif/P1000475.RW2.exif.txt
Exif.PanasonicRaw.SensorWidth 10480
Exif.PanasonicRaw.SensorHeight 7794
Exif.PanasonicRaw.SensorTopBorder 10
Exif.PanasonicRaw.SensorLeftBorder 18
Exif.PanasonicRaw.ImageHeight 7786
Exif.PanasonicRaw.ImageWidth 10386
Ah, I missed the GitHub issue. Thank you.
kmilos
April 11, 2023, 2:18pm
6
RawSpeed doesn’t use metadata crop, it tries to extract maximum amount of raw data by manual inspection and tweaking for every camera.
Newerth
(Jan Šmucr)
April 11, 2023, 2:24pm
7
Okay, thank you very much, @kmilos . I had no idea it worked like this.
1 Like
bernyemm
(Berny Marsden)
April 11, 2023, 8:08pm
8
I get the same magenta fringe.
kofa
(István Kovács)
April 11, 2023, 8:26pm
9
This (wrong clipping) affects more Panasonic cameras, e.g. my LX7 (not related to high-res).
opened 08:52AM - 01 Apr 23 UTC
**Describe the bug/issue**
Some LX7 images have garbage pixels on the edge. The… affected files, when processed using dcraw, have no garbage data.
**To Reproduce**
1. Download the files from https://tech.kovacs-telekes.org/files/2023-04-01-lx7-garbage-pixels/
2. Import and open them in the darkroom.
3. Check for garbage on the right
**Expected behavior**
No garbage pixels.
**Screenshots**
2023-03-30_17-06-32_P1000043.RW2
No garbage pixels - size shown in _image information_: 3792 (3920) x 2536:
![image](https://user-images.githubusercontent.com/3177739/229275418-fd2baaca-a105-4185-bb61-92cd4e23b431.png)
Camera's JPG: 3776 x 2520
dcraw PPM: 3792 x 2536
2023-03-30_17-06-32_P1000044.RW2
Garbage pixels - size shown in _image information_: 3792 (3920) x 2476:
![image](https://user-images.githubusercontent.com/3177739/229275472-ed755a8a-7c42-4838-98a7-a447c3f9578e.png)
Camera's JPG: 3776 x 2520
dcraw PPM: 3704 x 2476
Images sizes from camera manual:
Aspect ratio 4:3 -> 3648 x 2736
Aspect ratio 3:2 -> 3776 x 2520
Aspect ratio 16:9 -> 3968 x 2232
Aspect ratio 1:1 -> 2736 x 2736
**Additional info**
I had optical zoom set to maximum; I may have accidentally slipped into the digital zoom range with the corrupted image. I've tried taking images with digital zoom to verify, but have been unable to reproduce the issue.
**Platform**
_Please fill as much information as possible in the list given below. Please state "unknown" where you do not know the answer and remove any sections that are not applicable _
* darktable version : 4.3.0+1501~gf103dd65ab
* OS : Linux 5.19.0-38
* Linux - Distro : Ubuntu 22.10
* Memory : 64 GB
* Graphics card : NVidia 1060/6GB
* Graphics driver : 470.161.03
* OpenCL installed : yes
* OpenCL activated : yes/no (tested both)
* Xorg : 7.7+23ubuntu2
* Desktop : KDE Plasma 5.25.5-0ubuntu1
* GTK+ : 3.24.34-3ubuntu2
* gcc : 12.2.0-3ubuntu1
* cflags : N/A
* CMAKE_BUILD_TYPE : Release
3 Likes
bernyemm
(Berny Marsden)
April 19, 2023, 11:01am
10
Three instances of exposure module with drawn & parametric masks gave this result.
2 Likes