I just installed dark table on w10. I had initially the error reported earlier on (does not work if installed in program file folder). Uninstalled and re installed at the root of my C disk.
It worked fine, no crash and I was happy to see that my Canon 80D raw files were recognized.
I tested the program on some raw + xmp files previously edited under Lightroom 6 and I was happy to see that my history was recognized.
Just two bugs to report : the star notes are recognized as well as the color labels. However one file with a rejejected status was not detected as such by the filter.
All my files do have GPS coordinates and I was happy to see that my pictures were placed on the map.
There seems to be a bug here also : pictiures coded within France seem ok. However pictures out of France are not. One picture taken at Lisbon showed up on the map at Corsica. Another picture taken at Cap Vert was placed on Egypt.The bug seems to affect the longitude, latitude seems ok.
Best regards and thanks for having made dark table available to windows users
Actually there are some cameras that have a GPS sensor and capture the
geolicalisation data in the file. My Canon 80D does not have this feature
so the gps data have been added after by a software and must be in the xmp
file. The Raw file is not modified after the shot. But I can send you the
raw as well, it is heavy, about 25 MB.
No I did not breake anything ;-), I am doing my tests on a copy of the raw
files
Can I change the langage settings after the installaltion or do I need to un install and install an english language copy ?
If the issue is with the langage settings there is a bug in Darktable with the French version.
I don’t think the raw file is the problem as other files present the issue too… Cap Vert longitude becomes Egyptian longitude…
I tried to uploaded the raw file but got an error… the file must be to big.
I tried with a French dt and couldn’t reproduce either. You can change the language by starting darktable with --conf ui_last/gui_language=C from a cmd.exe or by appending it to the command in a shortcut link thing from your desktop.
If the raw is just 25 MB you can probably just upload it here.
I believe it has nothing to do with dt’s language setting, I have another suspect: Windows regional settings. @csierra02 & @houz: what is your regional setting in Windows?
You can find them on Windows 10: Windows Settings/Time & Language/Region & Language, or at the Control Panel/Clock, Language, and Region/Region/Change date, time or number format/Additional Settings and check which setting is used, especially interesting would be the “Decimal symbol” and “Digit Grouping symbol”. I have a feeling that this influences how a decimal number found in an XMP text file is being interpreted by glib
I am using the standard German settings on Windows 7. However, I don’t expect those to be related. If you look at the code you will see that all we do is either working on strings or using functions which explicitly don’t take the locale settings into account:
Unless of course exiv2 is doing something stupid, like translating the direction characters.
Hi peterbud, thanks for your suggestion. I could not find these settings
under Windows10. I do have settings relative to
the date format, calendar… I know that these settings were defined in some
application programs such as Excel but I
don’t remember having seen them also in the OS
I guess you are right. Actually if I see the screen capture from @csierra02, the numerical values are correct. The only problem that 9,12.372W has been “converted” to 9,12.372E
Click on the left “Region et langue” and there should be something in French for “Related settings”. But if you start a Control Panel it might be easier
What build od dt are your using ? I have 2.3.0+866 ~gc23bd4a5a
Rather than trying to upload again the raw file (yesterday the upload progressed regularly up to 100 %). At this point the command reply become available and I got the message : there has been an error. I supect that the forum has some size limit put on the files and these are checked only when you try to finalize the post…
Rather than trying again on a raw file, I had the idea to test dt on a jpg file taken at Newark. There is no xmp file along with the jpg, the GPS cordinates were put by LR afterwards the shot.
I first thought, aha, there is no longer a bug… But actually there is.
There is no longer a simple W / E change but there is a shift of the cordinates and the localisation in dt is several hundred of km away from the original location…
