I have been trying to add a profile, eos5d2_Sunlight_D50_WB.icc, to my input color profile module. I am running dt on a Windows system. I have read the manual about where to put it, but the path to my color in folder does not match the ones given in the manual. This is how the folder was installed by dt:
The file is there, and I have restarted dt several times, but when I look at what the module shows is available, I see this:
I don’t know what the Canon 50D SSF… profile is. I guessed that it was the Canon_50D.icc, but I removed both Canon iccs from the In folder and restarted dt, and the Canon 50D SSF… was still there.
This is where dt originally installed these files and folders:
The manual says:
You can also supply your own input ICC profiles and put them into $DARKTABLE/share/darktable/color/in or $HOME/.config/darktable/color/in (where $DARKTABLE is the darktable installation directory and $HOME is your home directory).
I don’t know what the $HOME directory would be on a Windows system, but I can create $DARKTABLE/share/darktable/color/in. What puzzles me is I have added numerous icc to C:\Users\Bill Martz\AppData\Local\darktable\color\out\ and they show up in my choices for softproofing file and output file. Why does it not work for input?
Edit: I forgot already. I copied color/in to a folder that already exists, C:\Program Files\darktable\share\darktable, and re-started dt. No effect.
Note profiles in DT will not be listed the same as their name in every case. Often they have a description in the ICC file and this is what you see in DT not the filename
The path is correct. If you hoger your mouse over the input profile module , it will also list the paths you can use.
The profile is either broken (but if other people got it working that doesn’t seem right ) or the space in your username is causing issues or something.
I believe the oath to the config folder can be overridden on the command line. You could move the whole localappdata\darktable folder to a location without spaces , and set your config folder to that when starting (through command line options ) and see if it works.
Just thinking out loud to test a theory , don’t know if it’s a viable solution or not.
I just played around with icc files for input profiles. A corrupt file won’t show up, and the title in the drop-down is determined by the name in the ICC file (not the filename) , just things to know.
An ICC file can contain a lot of different types of profiles , some might not be compatible with Darktable.
You seem to have thing in a few locations…One poster commented that the space in your username might be the issue?? Basically for windows you should be able to locate them in user/appdata/local/darktable/color/in… or if you run DT using --configdir then a color/in subfolder of that directory will work…
could this be it that you are running DT in a way that it is directed away from the appdata folder??
I have to apologize for being really stupid. Quite some time ago I followed some directions from, I believe, priort, on running dt with the option in the command line of --library :memory:. I also followed some directions to use --configdir C:\DT_config. Except, C:\DT_config\ doesn’t exist. When I removed that from the command line, dt reverted to using C:\Users\Bill Martz\AppData\Local\darktable\ for the config directory path, and that fixed the whole problem. Except now my custom shortcuts have stopped working. I don’t know what file and where they were stored, but I can redo them.
That’s strange are you sure that the folder you were pointing to does not exist?? If your shortcuts stopped working they had to be somewhere??? If I recall this was a suggestion to allow you to run a dev version along with your official release?? Maybe ??? I can’t recall…nevertheless you must have a data db file somewhere that you were using and the other config files…
It’s a good idea to use copies of the official shortcut and label them as a reminder.
Apparently, C:\DT_config\ only existed while dt was open. It was backed up by my online backup. Once dt closed, it must have disappeared, because dt was closed when I looked for it.
I might not be remembering correctly. I might have already removed it from the command line and started dt. Anyway, at some point it was gone, and I didn’t delete it. I only found it in the cloud backup.
