Using digiKam in Windows and Linux
Locked
Using digiKam in Windows and Linux
 
|
Sure, I've done it experimentally.
Just have the images and database on an NTFS partition. IIRC, the only problem was related to "locale." UTF-8 and all that stuff. The first time I'd open digiKam in the "new" OS, I got a warning about locale, should I change it? Yes. And that was it until I switched OS again. Best as I can recall, anyway. Paul _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
|
|
All,
When I start the up image editor for an image settings I used from the previous editing session persist for the current session. I do not want this to happen. Even if I click on the Use Defaults button in the bottom right, there are settings that still persist. For example, I just check to confirm--the last time I edited an image, I used the Saturation slider to desaturate an image to black-and-white. When I open a new image and select Hue/Saturation/Brightness, the Saturation slider is at -100. So my present workflow is to open an image in the editor, then systematically select my frequently used settings and click on the Reset button for each to "zero-out" every thing, I know I must be missing something or doing something wrong because this surely can't be how it supposed to work. Any advice is appreciated. Guy -- "There is only love, and then oblivion. Love is all we have to set against hatred." (paraphrased) Ian McEwan Guy Stalnaker [hidden email] _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
|
|
I agree with you 100% that it is really annoying that the editor
remembers, especially when it remembers CPU-intensive things like sharpening. But I never found a way to make it not remember, except to delete the configuration file before starting the editor. Which means everything is reset (including stuff you don't want reset), unless you make a backup copy that you can paste over the real config file - not user friendly at all. On 4/7/12, Guy Stalnaker <[hidden email]> wrote: > I know I must be missing something or doing something wrong because this > surely can't be how it supposed to work. _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
|
|
I have the same behaviour of the program and always thought it is made in this manner, that is I figured out it is not possible to get the editor forget previous settings of the last image used. This is annoying to me of course, specially when RAW workflows start. Although in this last case I have to say that some of the things in the initial parameters should be remembered such as the system used to develop the raw images (bilinear...etc.). Things such as those found in Post-elaboration should be forgot as in the normal editor of jpeg images (contrast, gamma, etc.).
happy easter to all Antonio
Il giorno 08 aprile 2012 01:55, Elle Stone <[hidden email]> ha scritto: I agree with you 100% that it is really annoying that the editor -- Antonio Trincone http://publicationslist.org/antonio.trincone http://www.icb.cnr.it/antonio.trincone/ http://sites.google.com/site/phototrincone/ http://sites.google.com/site/cvtrincone/home http://imaginesvolantscriptamanent.blogspot.com/ _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
|
|
On Sunday 08 April 2012 09:11:51 Antonio Trincone wrote:
> I have the same behaviour of the program and always thought it is made in > this manner, that is I figured out it is not possible to get the editor > forget previous settings of the last image used. This is annoying to me of > course, specially when RAW workflows start. Although in this last case I > have to say that some of the things in the initial parameters should be > remembered such as the system used to develop the raw images > (bilinear...etc.). Things such as those found in Post-elaboration should be > forgot as in the normal editor of jpeg images (contrast, gamma, etc.). > happy easter to all > Antonio > > Il giorno 08 aprile 2012 01:55, Elle Stone <[hidden email]> ha > scritto: > > > I agree with you 100% that it is really annoying that the editor > > remembers, especially when it remembers CPU-intensive things like > > sharpening. ... I don't find it annoying at all that previous settings are remembered. What is annoying is the generation of the preview as soon as the tool is opened, especially for longer operations (refocusing, inpainting...). Why do I like to keep previous settings? I often work with several images taken under closely similar conditions. That means that most require the same settings for the tools used, or settings very close to those. So digikam remembering those settings is a good thing for me. That is valid for both RAW development and post-treatment, btw. But, I often use two sharpening steps: for capture sharpening, and unsharp mask for creative and output sharpening. The settings for each step are rather constant between images. It is rather annoying that when I want to use USM after refocusing, Digikam starts preparing the refocusing preview again... Something similar for the inpainting tool, it's rather annoying to see Digikam start to generate a preview w/o having a chance to change settings. So, please, keep the settings between uses, but remove the automatic preview generation (or make it optional). And many thanks for the great work that's being done on Digikam :) It covers 90+% of my editing needs (the other 10% is pixel-level editing, requiring masks etc, so outside Digikam's domain) Remco P.S. I noticed something strange in the preview generation: 'sometimes' there's no automatic generation of sharpening previews, other times there is. It seems related to what I have done to the right sidebar panels: I usually can stop the preview generation by setting them to the minimum width. Is preview generation triggered by a change in the on-screen size of the edited image, by any chance? R. _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
|
|
Remco, you are right. It isn't the "remembering" per se, it's the
automatic generation of the preview that is annoying, because it takes so very long and there's nothing you can do until it's done. If there were a way to tell the editor to remember settings, but to not generate the preview until a button is pushed, that would be great. Elle On 4/8/12, Remco Viëtor <[hidden email]> wrote: > On Sunday 08 April 2012 09:11:51 Antonio Trincone wrote: >> I have the same behaviour of the program and always thought it is made in >> this manner, that is I figured out it is not possible to get the editor >> forget previous settings of the last image used. This is annoying to me of >> course, specially when RAW workflows start. Although in this last case I >> have to say that some of the things in the initial parameters should be >> remembered such as the system used to develop the raw images >> (bilinear...etc.). Things such as those found in Post-elaboration should >> be >> forgot as in the normal editor of jpeg images (contrast, gamma, etc.). >> happy easter to all >> Antonio >> >> Il giorno 08 aprile 2012 01:55, Elle Stone <[hidden email]> ha >> scritto: >> >> > I agree with you 100% that it is really annoying that the editor >> > remembers, especially when it remembers CPU-intensive things like >> > sharpening. ... > > I don't find it annoying at all that previous settings are remembered. What > is > annoying is the generation of the preview as soon as the tool is opened, > especially for longer operations (refocusing, inpainting...). > > Why do I like to keep previous settings? I often work with several images > taken under closely similar conditions. That means that most require the > same > settings for the tools used, or settings very close to those. So digikam > remembering those settings is a good thing for me. That is valid for both > RAW > development and post-treatment, btw. > > But, I often use two sharpening steps: for capture sharpening, and unsharp > mask for creative and output sharpening. The settings for each step are > rather > constant between images. It is rather annoying that when I want to use USM > after refocusing, Digikam starts preparing the refocusing preview again... > Something similar for the inpainting tool, it's rather annoying to see > Digikam > start to generate a preview w/o having a chance to change settings. > > So, please, keep the settings between uses, but remove the automatic preview > generation (or make it optional). > > And many thanks for the great work that's being done on Digikam :) > It covers 90+% of my editing needs (the other 10% is pixel-level editing, > requiring masks etc, so outside Digikam's domain) > > Remco > > P.S. I noticed something strange in the preview generation: 'sometimes' > there's no automatic generation of sharpening previews, other times there > is. > It seems related to what I have done to the right sidebar panels: I usually > can stop the preview generation by setting them to the minimum width. Is > preview generation triggered by a change in the on-screen size of the edited > image, by any chance? > > R. > _______________________________________________ > Digikam-users mailing list > [hidden email] > https://mail.kde.org/mailman/listinfo/digikam-users > Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
|
|
I want to join the group:
Rember: yes Preview: no ;) When I use "Enhance -> Sharpen -> Refocus", I keep the same settings in 99%, since they work pretty well for me. But everytime, I open the dialog, digiKam starts to generate a preview, which takes about 15 seconds on my machine with my fotos. Contrary to Elle's post, in my situation (digikam 2.5.0) I can cancel this preview-generation. So my workflow is: Open sharpen-dialog, cancel preview-generation, click OK to sharpen image, be happy with the result. ;) To sum up: I my case, it would be helpful, if digiKam would not automatically generate a preview at dialog start. But I can live with the current situation, too, of course. ;) Peter On 08.04.2012 23:09, Elle Stone wrote: > Remco, you are right. It isn't the "remembering" per se, it's the > automatic generation of the preview that is annoying, because it takes > so very long and there's nothing you can do until it's done. If there > were a way to tell the editor to remember settings, but to not > generate the preview until a button is pushed, that would be great. > > Elle > > On 4/8/12, Remco Viëtor <[hidden email]> wrote: >> On Sunday 08 April 2012 09:11:51 Antonio Trincone wrote: >>> I have the same behaviour of the program and always thought it is made in >>> this manner, that is I figured out it is not possible to get the editor >>> forget previous settings of the last image used. This is annoying to me of >>> course, specially when RAW workflows start. Although in this last case I >>> have to say that some of the things in the initial parameters should be >>> remembered such as the system used to develop the raw images >>> (bilinear...etc.). Things such as those found in Post-elaboration should >>> be >>> forgot as in the normal editor of jpeg images (contrast, gamma, etc.). >>> happy easter to all >>> Antonio >>> >>> Il giorno 08 aprile 2012 01:55, Elle Stone <[hidden email]> ha >>> scritto: >>> >>>> I agree with you 100% that it is really annoying that the editor >>>> remembers, especially when it remembers CPU-intensive things like >>>> sharpening. ... >> >> I don't find it annoying at all that previous settings are remembered. What >> is >> annoying is the generation of the preview as soon as the tool is opened, >> especially for longer operations (refocusing, inpainting...). >> >> Why do I like to keep previous settings? I often work with several images >> taken under closely similar conditions. That means that most require the >> same >> settings for the tools used, or settings very close to those. So digikam >> remembering those settings is a good thing for me. That is valid for both >> RAW >> development and post-treatment, btw. >> >> But, I often use two sharpening steps: for capture sharpening, and unsharp >> mask for creative and output sharpening. The settings for each step are >> rather >> constant between images. It is rather annoying that when I want to use USM >> after refocusing, Digikam starts preparing the refocusing preview again... >> Something similar for the inpainting tool, it's rather annoying to see >> Digikam >> start to generate a preview w/o having a chance to change settings. >> >> So, please, keep the settings between uses, but remove the automatic preview >> generation (or make it optional). >> >> And many thanks for the great work that's being done on Digikam :) >> It covers 90+% of my editing needs (the other 10% is pixel-level editing, >> requiring masks etc, so outside Digikam's domain) >> >> Remco >> >> P.S. I noticed something strange in the preview generation: 'sometimes' >> there's no automatic generation of sharpening previews, other times there >> is. >> It seems related to what I have done to the right sidebar panels: I usually >> can stop the preview generation by setting them to the minimum width. Is >> preview generation triggered by a change in the on-screen size of the edited >> image, by any chance? >> >> R. >> _______________________________________________ >> Digikam-users mailing list >> [hidden email] >> https://mail.kde.org/mailman/listinfo/digikam-users >> > _______________________________________________ > Digikam-users mailing list > [hidden email] > https://mail.kde.org/mailman/listinfo/digikam-users > Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
«
Return to digikam-users
|
1 view|%1 views
| Free forum by Nabble | Edit this page |