That’s for the metadata other than ratings and colour labels (e.g.iptc info, image description/copyright, …)
Hi,
that’s ok, but be aware that you are essentially overwriting the built-in presets for all the cameras in this way. If you add a different wbpresets.json in your user folder (which is something like %LOCALAPPDATA%/ART on whidows) you can overwrite only the cameras you care about, and leave the others at their defaults.
On any case, if you manage to get the presets for some cameras that are missing, you might consider sharing those so that other users might benefit 
Hi,
Thanks for the info, noted for next time (in the folder with the file “options”)
Here are the presets I added :
[
{
“make_model” : “PANASONIC DMC-GX80”,
“presets” : [
{“name” : “Fine Weather”, “multipliers” : [2.46875, 1.0, 1.56640625]},
{“name” : “Cloudy”, “multipliers” : [2.6640625, 1.0, 1.45703125]},
{“name” : “Shade”, “multipliers” : [2.859375, 1.0, 1.3828125]},
{“name” : “Tungsten (Incandescent)”, “multipliers” : [1.63671875, 1.0, 2.29296875]},
{“name” : “Flash”, “multipliers” : [2.5703125, 1.0, 1.4609375]},
{“name” : “D55”, “multipliers” : [2.3125, 1.0, 1.5703125]},
{“name” : “ISO Studio Tungsten”, “multipliers” : [1.63671875, 1.0, 2.29296875]}
]
},
{
“make_model” : “PANASONIC DC-GX800”,
“presets” : [
{“name” : “Fine Weather”, “multipliers” : [2.37890625, 1.0, 1.56640625]},
{“name” : “Cloudy”, “multipliers” : [2.5546875, 1.0, 1.4609375]},
{“name” : “Shade”, “multipliers” : [2.734375, 1.0, 1.38671875]},
{“name” : “Tungsten (Incandescent)”, “multipliers” : [1.625, 1.0, 2.2734375]},
{“name” : “Flash”, “multipliers” : [2.45703125, 1.0, 1.4296875]},
{“name” : “D55”, “multipliers” : [2.23828125, 1.0, 1.5703125]},
{“name” : “ISO Studio Tungsten”, “multipliers” : [1.625, 1.0, 2.2734375]}
]
},
{
“make_model” : “PANASONIC DC-GX880”,
“presets” : [
{“name” : “Fine Weather”, “multipliers” : [2.3671875, 1.0, 1.5703125]},
{“name” : “Cloudy”, “multipliers” : [2.546875, 1.0, 1.46484375]},
{“name” : “Shade”, “multipliers” : [2.7265625, 1.0, 1.39453125]},
{“name” : “Tungsten (Incandescent)”, “multipliers” : [1.61328125, 1.0, 2.2578125]},
{“name” : “Flash”, “multipliers” : [2.44921875, 1.0, 1.4375]},
{“name” : “D55”, “multipliers” : [2.2265625, 1.0, 1.57421875]},
{“name” : “ISO Studio Tungsten”, “multipliers” : [1.61328125, 1.0, 2.2578125]}
]
}
]
I noticed that the latest development version of ART has a dcp profile for the Panasonic lx100 which is a great bonus for me as that is the camera I use.
I just wondered where the camera matched profiles come from? It is different from the Adobe dcp profile and the basic standard profile.
Typically I generate them from color target shots that are kindly made available by a popular website 
In principle I could do this systematically, but I’m too lazy so I add them when I bump into a raw file of a missing camera.
They are not of the highest quality probably, but usually they are better than a simple matrix imho
You can also get all the adobe ones by installing DNG converter (free) and then there is another free program adobe profile editor where you can add a second tone curve tweak colors and if you have a color checker modify using that information to create custom profiles (say stronger reds or something) as well…its great that ART and RT support these so that there are so many options
@agriggio It’s great as a starting point, spot on, thanks.
@priort I was using the dcp from Adobe dng convertor but have realised that it was giving everything a slight magenta hue.
I haven’t tried the profile editor but can imagine that is a worm hole of tweaking that could suck away a lot of hours…
You can select parts of your image and shift colors so you might be able to correct that in the profile editor…interesting I always heard DCP files from Adobe had issues with blues
OK thanks for your help…
Hi,
@agriggio I would have two requests to add, would it be possible to:
1 / change the color of the black frame around the photo in the editor, to select a neutral gray for example
2 / limit the zoom of the mouse in the editor to 100% with an option
and again well done for all the work done.
Hi,
That’s already there, there’s even a shortcut in fact… Just hit 9
I’ll see what I can do, but this is not high priority for me, so you might have to wait…
great, I had to pass by, thank you !
No worries I understand, there are the keyboard shortcuts, but I’m not too comfortable with that. It will be when you have the time. Thanks again.
@agriggio
Having a look at Having trouble with my sky blueness . . . ., I uploaded ER6_4832.DNG and ER6_4832.CR3
There is a black strip on the left and bottom. Is it due to a bad raw crop?
Opening the two files, I remark that the Camera WB is different for the two files. Do you know where it comes from? I was not able to find the value in the exif data.
Thanks to have a look.
Should be fixed now
Hi @agriggio
In the Rotate tool, click and drag shows a dotted line with the number of degrees of the line being drawn. In the Perspective Correction tool, when adding control lines, no dotted line is shown when the tool is being used to draw lines - only when you let go of the end of the line does the line become visible.
Is it possible to make the control line visible before you let go?
Many thanks
Barry
It seems that there is still a discrepancy between DNG and CR3 WB.
Profile is neutral.
For CR3 I find those information
WB RGGB Levels As Shot : 1849 1024 1024 1633
Color Temp As Shot : 4877
For the DNG, I suppose WB is stored here :
As Shot Neutral : 0.553813 1 0.627067
I have not the understanding of how we go from WB_RGGBLevelsAsshot to AsShotNeutral and to ART WB multipliers.
Thanks
They actually represent the same information. Both represent the proportional adjustment of R and B using G as the anchor. The DNG is rather straightforward in that regard, as those numbers can be directly applied to the image as a multiplication. The CR3 numbers are for the raw bayer pattern (RGGB), and if you divide the R into either G you get 0.553813, and B into either G gives you 0.627067.
Goofy, no? 
Edit: Oh and to provide some insight into the behavior you depicted, I’d surmise that ART isn’t decoding the CR3 numbers well, although libraw delivers them as multipliers…
Do you have the latest version of exiftool? Can you try clearing your cache as well? Thanks!
I should have the last version of exiftool and I should have deleted the cache.
Rechecking and retesting.