Hello ingenious digiKam programmers, hi dear users
now that cameras generate that huge files (and above all poor kde users soon must suffer from kde4's hunger for computer power), things get slower again... Now when I do some corrections using digicam (even just a crop), of course I have to save the file before I can continue with the next picture. 44MB png: I light a cigarette...24%, and wait...36% and smoke....68%... If I could just save my *actions* in a file (a "recorder") without saving the *result* of my actions to the actual files, I could easily go to the next picture, do my corrections, save the action for that picture, go to the next... and only at the end, when I go out to have a coffee in the sun, I let run the saved actions and let them be applied and saved to the files. I would save all the waiting time - and a lot of cigarettes ;-) Is this idea stupid, an old hat, very healthy, or what do you think? Would it be easy to add to digiKams functionalities? I'm looking forward to read your thoughts. Daniel -- Daniel Bauer photographer Basel Barcelona professional photography: http://www.daniel-bauer.com erotic art photos: http://www.bauer-nudes.com Madagascar special: http://www.fotograf-basel.ch/madagascar/ _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
I've heard of other photo-editors that work this way. (IMatch on
windows? ACDC?) On screen you work with a reduced resolution copy or a tile from the original. The actions are then run by a separate process running at reduced priority. I've actually submitted a bug/wish on this for a slightly different context: tagging many photos. Most applications don't take advantage of multiple cores very well. Adobe Photoshop is one of the few. Suppose that Digikam on startup snooped and found how many cores you had, then prepared n-1 background process threads, so that one core would run digikam user interface, and n-1 processes would work to keep up. (I think they would be idle a lot of the time, or blocked waiting for disk IO) But if writing a 44 MB png causes a wait long enough to light a cigarette, you are doing something wrong. It shouldn't take that long. -- Sherwood Botsford Sherwood's Forests Warburg, Alberta T0C 2T0 http://www.sherwoods-forests.com 780-848-2548 _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
On Wednesday 15 April 2009 20:49:53, Sherwood Botsford wrote:
> I've heard of other photo-editors that work this way. (IMatch on > windows? ACDC?) On screen you work with a reduced resolution copy or > a tile from the original. > The actions are then run by a separate process running at reduced priority. > > I've actually submitted a bug/wish on this for a slightly different > context: tagging many photos. > > Most applications don't take advantage of multiple cores very well. > Adobe Photoshop is one of the few. Suppose that Digikam on startup > snooped and found how many cores you had, then prepared n-1 background > process threads, so that one core would run digikam user interface, > and n-1 processes would work to keep up. (I think they would be idle > a lot of the time, or blocked waiting for disk IO) > > But if writing a 44 MB png causes a wait long enough to light a > cigarette, you are doing something wrong. It shouldn't take that > long. Well, i'd say it takes approx. a minute: a loooong time when working with computers... what could I do wrong - apart from lighting the cigarette? I crop a picture, click on the "next picture"-icon and say yes to "save changes?" and wait... My computer is about 5 yrs old, but it has a calibrated monitor and 5 huge HD's..., running openSuse 10.3, KDE 3.5, digikam 9.3. regards Daniel PS: Untill now I used digikam 10.0 only for some tests for my CR2's [it looks great, but it's kde4 and that makes it even slower] - but I am not really happy with the results from raw files, so i confess that right now and untill I find the time to do deeper tests I use Canon's software in a virtualbox with win XP to convert the raw files and then go on with digiKam. But thats another topic...) -- Daniel Bauer photographer Basel Barcelona professional photography: http://www.daniel-bauer.com erotic art photos: http://www.bauer-nudes.com Madagascar special: http://www.fotograf-basel.ch/madagascar/ _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
In reply to this post by Daniel Bauer-2
On Wednesday 15 April 2009 20:27:54 Daniel Bauer wrote:
> I'm looking forward to read your thoughts. I think that is very good idea. :) m. _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
In reply to this post by Daniel Bauer-2
> Hello ingenious digiKam programmers, hi dear users
> > now that cameras generate that huge files (and above all poor kde users > soon must suffer from kde4's hunger for computer power), things get slower > again... > > Now when I do some corrections using digicam (even just a crop), of course > I have to save the file before I can continue with the next picture. 44MB > png: I light a cigarette...24%, and wait...36% and smoke....68%... > > If I could just save my *actions* in a file (a "recorder") without saving > the *result* of my actions to the actual files, I could easily go to the > next picture, do my corrections, save the action for that picture, go to > the next... and only at the end, when I go out to have a coffee in the sun, > I let run the saved actions and let them be applied and saved to the files. > > I would save all the waiting time - and a lot of cigarettes ;-) > > Is this idea stupid, an old hat, very healthy, or what do you think? > Would it be easy to add to digiKams functionalities? And no it is not easy to add to digikam - a full blown implementation is not an afternoon's hack but a few weeks' work. But yes, we will get to this at some point in time. You are very welcome to detail your ideas and tell us your requirements! > I'm looking forward to read your thoughts. > > Daniel _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
In reply to this post by Daniel Bauer-2
2009/4/15 Daniel Bauer <[hidden email]>:
> On Wednesday 15 April 2009 20:49:53, Sherwood Botsford wrote: >> I've heard of other photo-editors that work this way. (IMatch on >> windows? ACDC?) On screen you work with a reduced resolution copy or >> a tile from the original. >> The actions are then run by a separate process running at reduced priority. >> >> I've actually submitted a bug/wish on this for a slightly different >> context: tagging many photos. >> >> Most applications don't take advantage of multiple cores very well. >> Adobe Photoshop is one of the few. Suppose that Digikam on startup >> snooped and found how many cores you had, then prepared n-1 background >> process threads, so that one core would run digikam user interface, >> and n-1 processes would work to keep up. (I think they would be idle >> a lot of the time, or blocked waiting for disk IO) >> >> But if writing a 44 MB png causes a wait long enough to light a >> cigarette, you are doing something wrong. It shouldn't take that >> long. > > Well, i'd say it takes approx. a minute: a loooong time when working with > computers... what could I do wrong - apart from lighting the cigarette? I > crop a picture, click on the "next picture"-icon and say yes to "save > changes?" and wait... > > My computer is about 5 yrs old, but it has a calibrated monitor and 5 huge > HD's..., running openSuse 10.3, KDE 3.5, digikam 9.3. > > regards > > Daniel > > PS: Untill now I used digikam 10.0 only for some tests for my CR2's [it looks > great, but it's kde4 and that makes it even slower] - but I am not really > happy with the results from raw files, so i confess that right now and untill > I find the time to do deeper tests I use Canon's software in a virtualbox > with win XP to convert the raw files and then go on with digiKam. But thats > another topic...) But RAW import topic is important for me. Do you use Raw Import tool for digiKam image editor ? With it, you can set-up a lots of adjustments during demosaicing and as post-processing. http://www.flickr.com/photos/digikam/3162004701/sizes/o/ http://www.flickr.com/photos/digikam/3246694827/sizes/o/ http://www.flickr.com/photos/digikam/3404494476/sizes/o/ Best Gilles _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
On Thursday 16 April 2009 09:53:46, Gilles Caulier wrote:
> > PS: Untill now I used digikam 10.0 only for some tests for my CR2's [it > > looks great, but it's kde4 and that makes it even slower] - but I am not > > really happy with the results from raw files, so i confess that right now > > and untill I find the time to do deeper tests I use Canon's software in a > > virtualbox with win XP to convert the raw files and then go on with > > digiKam. But thats another topic...) > > But RAW import topic is important for me. > > Do you use Raw Import tool for digiKam image editor ? With it, you can > set-up a lots of adjustments during demosaicing and as > post-processing. > > http://www.flickr.com/photos/digikam/3162004701/sizes/o/ > > http://www.flickr.com/photos/digikam/3246694827/sizes/o/ > > http://www.flickr.com/photos/digikam/3404494476/sizes/o/ > > Best > > Gilles Hi Gilles, yes I know :-) It's a question of available time. Besides of my regular work I organize photo courses/workshops in Barcelona and therefor am fully occupied... (oh: still some places open in the course of May 16/17 - see www.fotofotofoto.es :-) ) I would really love to do all my work with digikam, but in Barcelona i have only my laptop (unusable for photo work except of selecting, cropping etc. because I cannot really evaluate colors and contrasts on this screen). So when I come back to Basel for a short time I sit on the computer and do the adjustments for all the pictures taken in the meantime with Canon's programs... there's no time left for testing/setting up software. I have seen (and very very shortly testet) the Raw Import tool of digikam and it looks great - but during clicking on several options I could not achieve the same quality as with Canons own software yet. The colors I get are too "neutral" or "flat". I want the program to "automatically" decode the raw files to the same result as the jpg produced by the camera. If it helps (for the development of digiKam) I can provide some samples taken in raw+jpg mode with Canon 5D Mark II - if you don't care to do tests with a naked girl :-) However, probably the problem does not lie within digikam but in my lack of time to find the correct settings... From October I will have more time. kind regards Daniel -- Daniel Bauer photographer Basel Barcelona professional photography: http://www.daniel-bauer.com erotic art photos: http://www.bauer-nudes.com Madagascar special: http://www.fotograf-basel.ch/madagascar/ _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
In reply to this post by Marcel Wiesweg
On Wednesday 15 April 2009 22:47:05, Marcel Wiesweg wrote:
>> . . . > > If I could just save my *actions* in a file (a "recorder") without saving > > the *result* of my actions to the actual files, I could easily go to the > > next picture, do my corrections, save the action for that picture, go to > > the next... and only at the end, when I go out to have a coffee in the > > sun, I let run the saved actions and let them be applied and saved to the > > files. > > Is this idea stupid, an old hat, very healthy, or what do you think? > > Would it be easy to add to digiKams functionalities? > > The idea of recording actions is in our minds as well (at least in mine, > that's what I can speak of). good to hear. > The focus is not so much on saving time for > file compression but rather to know what you have done to an image and can > see the history. yes, of course. "My" application is only one way or example of the benefits of such a recorder. One could use it as described to "batch-run" a bunch of changes on many pictures, or also to apply several steps taken on one picture on another picture (like the recorder in photoshop). And a lot more - wishes never end ;-) > And no it is not easy to add to digikam - a full blown implementation is > not an afternoon's hack but a few weeks' work. ok, so we need 66 weeks per year... plus holydays! > But yes, we will get to this > at some point in time. > You are very welcome to detail your ideas and tell us your requirements! fine. I'll write down my ideas and then ask again here, where to send it. Later. > > Marcel have agood day! Daniel -- Daniel Bauer photographer Basel Barcelona professional photography: http://www.daniel-bauer.com erotic art photos: http://www.bauer-nudes.com Madagascar special: http://www.fotograf-basel.ch/madagascar/ _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
In reply to this post by Daniel Bauer-2
> I would save all the waiting time - and a lot of cigarettes ;-)
> Try this site instead, great for wasting time (and healthier than cigarettes): http://slashdot.org -- Dotan Cohen http://what-is-what.com http://gibberish.co.il _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
In reply to this post by Gilles Caulier-4
On Thursday 16 April 2009 09:53:46 Gilles Caulier wrote:
> > But RAW import topic is important for me. > > Do you use Raw Import tool for digiKam image editor ? With it, you can > set-up a lots of adjustments during demosaicing and as > post-processing. > Main difference between digiKam RAW import and other tools is complete lack of defaults - or to be more precise - defaults are completely neutral. It means that to properly develop most RAWs user has to make many, many adjustments. And here we hit scope of Daniels wish: every time big RAW is reprocessed which can take much time. For example Raw Therapee is able to work on previews and process in background or later in queue which makes this program much more comfortable to work with many files. Also lack of white point probe can be frustrating. m. _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
In reply to this post by Daniel Bauer-2
On Thursday 16 April 2009 10:52:37 Daniel Bauer wrote:
> > fine. I'll write down my ideas and then ask again here, where to send it. http://bugs.kde.org m. _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Free forum by Nabble | Edit this page |