yes this should go away if you don’t build quake.
this one here is fatal. no idea about windows… maybe it needs installation, maybe it’s called glslc? if it comes by a different name, you can overwrite it in bin/config.mk as GLSLC=glslangValidator (replace by actual name here).
Thanks! I think I might wait and see how @priort gets on… although I’ll probably have a go tomorrow sometime. 
Thanks a lot, I’ll try this ASAP and of course I’ll give feedback 
It’s working now.
With this config.
intgui/lod:1
fltgui/dpiscale:1
strsnd/alsa/pcm:default
intgui/export/wd:6000
intgui/export/ht:4000
intgui/export/format:0
fltgui/export/quality:90
strgui/export/basename:/home/franklin/Pictures/export/test/
strqvk/device_name:NVIDIA GeForce GTX 1080 Ti
intgui/ruc_num:2
strgui/ruc_entry00:/run/media/franklin/My Book/PHOTOGRAPHIC_DB/2022-05-01
strgui/ruc_entry01:/run/media/franklin/My Book/PHOTOGRAPHIC/TEST IMAGE
intqvk/device_id:-1
strgui/metadata/command:/usr/bin/exiftool -l -createdate -aperture -shutterspeed -iso
great. is that a cr3 with old exiv2 or did you compile completely without exiv2? wondering why it doesn’t show exif information under the histogram.
Could we maybe create a pool where people can upload their raw samples for creating noise profiles? In theory I can create a directory in my Nextcloud. But maybe there is a better solution (I can delete the raws if I or someone else has created the profiles but storage is not unlimited there and I guess there are lots of cameras)?
Btw, it would be handy if noise-profile.sh could process several raws in a directory at once. Right now it’s a lot of copying and pasting… or is that already possible?
hm, for i in $(ls -1 *.CR2); do ./noise-profile.sh $i; done ?
not sure we’d need the raw input samples? once the fit is good we’ll only need the values, maybe the rawhistogram as proof that it’s good. but as mentioned before, you can pretty much recompute the raw histogram and fit for any image of that camera and iso combination… in most cases fitting should be possible, and in almost every image you should be able to judge whether the fit is good or not.
i think i should refactor the file layout soon though… all those individual files are unwieldy. would be good to download just one or two files for all support for a specific camera model.
In this case, do the raws have to be in the same directory as noise-profile.sh or can I just put the directory path before *.CR2?
I meant maybe people would provide raw samples even though they don’t want to use vkdt or are too lazy to execute noise-profile.sh themselves.
ah. that makes sense, yes.
A little problem: I have created noise profiles for the Samsung A52 smartphone, which has several cameras. So far I have created profiles for the main camera and the ultrawide camera. The other cameras I cannot access with OpenCamera, respectively it’s a bit complicated for the selfie camera. But the problem is that vkdt/noise-profile.sh gives the profiles from those two cameras the same filenames. How can this be solved? I mean I have copied the profiles into two different folders now but how can vkdt use them if they have the same names? Btw, vkdt also overwrites profiles with the same names apparently (I had to create some profiles twice).
meh, telephones. does the raw/dng contain any hint which camera was used? does rawspeed know about this? i can’t find it in cameras.xml, how is this file even loaded…
Well in the exif data I only see SM-A528B for both cameras as “model”, and interestingly 5mm as focal length.
So apparently this is a rawspeed “bug” and we have to skip this for now. But I think this is important because a lot of people only take photos with their smartphones.
Apparently something is wrong here. Even the image resolution is exactly the same with both cameras, I only see one hint, but only sometimes: apparently the two cameras sometimes don’t use the same iso values, with camera 1 there is an iso 40, with camera 2 there is an iso 55. The other data is exactly the same, focal length, f-value, even the image resolution…
i would have expected some more esoteric exif tag with a cryptic name to tell the cameras apart. did you look at some full exiftool output maybe?
Ok, exiftool does show some differences, e.g. focal length and resolution are different:
anna@anna-ms7c96:~/Bilder/nprof/samsunga52$ exiftool IMG_20230106_114236.dng
ExifTool Version Number : 12.16
File Name : IMG_20230106_114236.dng
Directory : .
File Size : 31 MiB
File Modification Date/Time : 2023:01:06 11:42:36+01:00
File Access Date/Time : 2023:01:06 11:42:36+01:00
File Inode Change Date/Time : 2023:01:06 11:48:39+01:00
File Permissions : rwxr-----
File Type : DNG
File Type Extension : dng
MIME Type : image/x-adobe-dng
Exif Byte Order : Little-endian (Intel, II)
Subfile Type : Full-resolution image
Image Width : 4624
Image Height : 3468
Bits Per Sample : 16
Compression : Uncompressed
Photometric Interpretation : Color Filter Array
Image Description :
Make : samsung
Camera Model Name : SM-A528B
Strip Offsets : (Binary data 30020 bytes, use -b option to extract)
Orientation : Horizontal (normal)
Samples Per Pixel : 1
Rows Per Strip : 1
Strip Byte Counts : (Binary data 17339 bytes, use -b option to extract)
X Resolution : 72
Y Resolution : 72
Planar Configuration : Chunky
Resolution Unit : inches
Software : samsung/a52sxqeea/a52sxq:12/SP1A.210812.016/A528BXXS1CVI6:user/release-keys
Modify Date : 2023:01:06 11:42:35
CFA Repeat Pattern Dim : 2 2
CFA Pattern 2 : 0 1 1 2
Copyright :
Exposure Time : 1/10
F Number : 1.8
ISO : 40
Date/Time Original : 2023:01:06 11:42:35
Focal Length : 5.2 mm
TIFF-EP Standard ID : 1 0 0 0
DNG Version : 1.4.0.0
DNG Backward Version : 1.1.0.0
Unique Camera Model : SM-A528B-samsung-samsung
CFA Plane Color : Red,Green,Blue
CFA Layout : Rectangular
Black Level Repeat Dim : 2 2
Black Level : 64 64 64 64
White Level : 1023
Default Scale : 1 1
Default Crop Origin : 8 8
Default Crop Size : 4608 3452
Color Matrix 1 : 0.5234375 -0.00390625 -0.0341796875 -0.7900390625 1.538085938 0.1953125 -0.3330078125 0.5107421875 0.4248046875
Color Matrix 2 : 1.013671875 -0.3251953125 0.1044921875 -0.453125 1.372070312 0.3525390625 -0.0283203125 0.142578125 0.693359375
Camera Calibration 1 : 1.00390625 0 0 0 1 0 0 0 0.970703125
Camera Calibration 2 : 1.00390625 0 0 0 1 0 0 0 0.970703125
As Shot Neutral : 0.662109375 1 0.4453125
Baseline Exposure : 0
Calibration Illuminant 1 : D65
Calibration Illuminant 2 : Standard Light A
Active Area : 0 0 3468 4624
Forward Matrix 1 : 0.9296875 0.0048828125 0.0302734375 0.4521484375 0.7470703125 -0.19921875 0.12890625 -0.689453125 1.385742188
Forward Matrix 2 : 0.76953125 0.1376953125 0.056640625 0.2333984375 0.90234375 -0.1357421875 -0.04296875 -0.45703125 1.32421875
Opcode List 2 : GainMap, GainMap, GainMap, GainMap
Opcode List 3 : WarpRectilinear
Noise Profile : 8.59628617251989e-05 5.02973783010207e-07 9.2644621741116e-05 2.65623060795061e-08 8.12871952032436e-05 6.20251754374834e-07
Aperture : 1.8
CFA Pattern : [Red,Green][Green,Blue]
Image Size : 4624x3468
Megapixels : 16.0
Shutter Speed : 1/10
Focal Length : 5.2 mm
Light Value : 6.3
anna@anna-ms7c96:~/Bilder/nprof/samsunga52$ cd /home/anna/Bilder/nprof/samsunga52uww
anna@anna-ms7c96:~/Bilder/nprof/samsunga52uww$ exiftool IMG_20230106_121517.dng
ExifTool Version Number : 12.16
File Name : IMG_20230106_121517.dng
Directory : .
File Size : 23 MiB
File Modification Date/Time : 2023:01:06 12:15:17+01:00
File Access Date/Time : 2023:01:06 12:15:17+01:00
File Inode Change Date/Time : 2023:01:06 12:24:50+01:00
File Permissions : rwxr-----
File Type : DNG
File Type Extension : dng
MIME Type : image/x-adobe-dng
Exif Byte Order : Little-endian (Intel, II)
Subfile Type : Full-resolution image
Image Width : 4000
Image Height : 3000
Bits Per Sample : 16
Compression : Uncompressed
Photometric Interpretation : Color Filter Array
Image Description :
Make : samsung
Camera Model Name : SM-A528B
Strip Offsets : (Binary data 25621 bytes, use -b option to extract)
Orientation : Horizontal (normal)
Samples Per Pixel : 1
Rows Per Strip : 1
Strip Byte Counts : (Binary data 14999 bytes, use -b option to extract)
X Resolution : 72
Y Resolution : 72
Planar Configuration : Chunky
Resolution Unit : inches
Software : samsung/a52sxqeea/a52sxq:12/SP1A.210812.016/A528BXXS1CVI6:user/release-keys
Modify Date : 2023:01:06 12:15:17
CFA Repeat Pattern Dim : 2 2
CFA Pattern 2 : 1 0 2 1
Copyright :
Exposure Time : 1/10
F Number : 2.2
ISO : 55
Date/Time Original : 2023:01:06 12:15:17
Focal Length : 1.7 mm
TIFF-EP Standard ID : 1 0 0 0
DNG Version : 1.4.0.0
DNG Backward Version : 1.1.0.0
Unique Camera Model : SM-A528B-samsung-samsung
CFA Plane Color : Red,Green,Blue
CFA Layout : Rectangular
Black Level Repeat Dim : 2 2
Black Level : 64 64 64 64
White Level : 1023
Default Scale : 1 1
Default Crop Origin : 8 8
Default Crop Size : 3984 2984
Color Matrix 1 : 0.5087890625 -0.0048828125 -0.0703125 -0.3779296875 1.295898438 0.05859375 -0.142578125 0.4736328125 0.328125
Color Matrix 2 : 0.84375 -0.150390625 -0.12890625 -0.6669921875 1.655273438 0.21875 -0.1357421875 0.3056640625 0.6923828125
Camera Calibration 1 : 0.986328125 0 0 0 1 0 0 0 0.97265625
Camera Calibration 2 : 0.986328125 0 0 0 1 0 0 0 0.97265625
As Shot Neutral : 0.5810546875 1 0.4755859375
Baseline Exposure : 0
Calibration Illuminant 1 : D65
Calibration Illuminant 2 : Standard Light A
Active Area : 0 0 3000 4000
Forward Matrix 1 : 0.8369140625 -0.0869140625 0.21484375 0.251953125 0.7890625 -0.041015625 0.0048828125 -0.8857421875 1.706054688
Forward Matrix 2 : 0.791015625 -0.06640625 0.2392578125 0.306640625 0.7021484375 -0.0078125 0.0576171875 -0.7294921875 1.497070312
Opcode List 2 : GainMap, GainMap, GainMap, GainMap
Opcode List 3 : WarpRectilinear
Noise Profile : 0.00057078526 0 0.00057078526 0 0.00057078526 0
Aperture : 2.2
CFA Pattern : [Green,Red][Blue,Green]
Image Size : 4000x3000
Megapixels : 12.0
Shutter Speed : 1/10
Focal Length : 1.7 mm
Light Value : 6.5
It may be that Fedora ships exiv2 compiled without ISOBMFF 
This is the .jpg OOC of the Fujifilm X-H1 camera. The exif information is not shown. But the same file in RAF does show the information.
if you install vkdt from OBS, there is an exiv2 package next to it that has isobmff
I know there is gpu acceleration in wsl2 . I actually don’t know which apis. There were special windows drivers when it released a year ago for Intel, amd and Nvidia. Not saying you need a special windows drivers , but I’m saying that it can’t be cuda only .
It might just be 3d / mesa acceleration only .
But from your error, some sort of vulkan driver seems to be loading and responding … It’s just not one vkdt is happy about . Maybe because it’s a cpu fallback or something.
I know a lot about Linux , but the cli experience . I know very little about the state of graphics and apis there . I also use wsl2 just for cli stuff , but did try a gfx 3d app just to see if something is working .
So who knows you might get further. Might also be I’m sending you in a goose chase that will end in tears :).