Differences of behaviour since last upgrade
Locked
Differences of behaviour since last upgrade
 
|
Apart from the undisplayed title mentioned in my previous thread, there are others things that I'm not so satisfied with:
1) at launching time, Digikam spends time to search new pictures. I don't need this as I always import pictures straight into Digikam, and never used it in the past. But I don't find the way to deactivate this function. It used to be in the configuration menu, I think, but I cannot find it now.
2) queues of the batch tool manager act somewhat strangely/inconsistently: - you can have several queues, but when you close the BTM window, elements are not removed from the queues. Consequently, any Ctrl-B will add new elements to a former queue that is not empty, and whose elements have already been treated.
- when I want to delete already treated elements from a queue, that's Ok for the current queue (the one which tab is opened). But when I want to do the same on other queues, although elements have been treated too, they are considered to not have been and I get a message saying that elements remain that have not been treated yet
- as far as I understand, the execute button work for all the queues at the same time. There is no option to run only the current queue, no way to move an element from a queue to another one... in that way, the ability to manage several queues at the same time is quite limited.
But may be I don't use these queues as they should be, but I didn't any configuration settings on the matter. Advice on the matter would be appreciated. Marie-Noëlle  De l'AIgoual à l'Aubrac, un voyage photographique en Cévennes et Lozère
Un livre à offrir ou à s'offrir, en souscription jusqu'au 31 août 2013. Cliquer sur l'image ci-dessus ou ce lien pour en savoir plus _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Re: Differences of behaviour since last upgrade
|
|
2013/8/19 Marie-Noëlle Augendre <[hidden email]>
Option have been removed. Since 2.x, this option is obsolete due to the differs analysis done in background after that digiKam is started. Typically the scan method has changed like this :
- before 2.x, scan for new albums + new items is done at startup, before to show main GUI. This scan at startup mode can be disabled in Setup/Misc. - after 2.x, scan core implementation have been changed to only register new albums in DB at startup, and to scan new items after than main GUI appears. It's done through a separated thread and scaning progress is reported to ProgressMAnager from status bar.
I work as you. My startup take few seconds only. I manage around 250Gb of photo. it's fast and do not perturb me in my workflow (as main GUI is imediatly here and usable as well)...
BQM is not a stand alone window, as Light Table in fact. If you want to clean a queue, just delete it from list.
There is a report already in Bugzilla about.
Not exactly. Queue are processed one by one. items in queue can be processedin parallel if right option is checked.
It's not yet implemented.
Do you tried to store queue settings in a workflow and apply it to a new one ?
Gilles Caulier
_______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Re: Differences of behaviour since last upgrade
|
|
2013/8/19 Gilles Caulier <[hidden email]> Marie-Noëlle
It still happens quite often that Digikam get stuck, doing I don't know what in the background, either at launch, or when I modify several pictures at a time (though I deactivate almost all the 'copy to image' option). Sometimes, I seem to have no other option than quit.
Yesterday, the launching was going forever, and I realize there was still another thread running; I had to kill it so Digikam could launch properly and give me access to the UI.
In Lightable (unless the option has been removed?), you can choose to empty the window when closing. However, the purpose is a bit different:
- Lightable is used to compare/make a selection: it makes sense to remove some pictures, add some others till your selection is final - in BQM, pictures you put in pictures a queue in order to apply a specific treatment. Once it is done, I don't see a reason to keep them in the queue, unless you want to apply another serie of tools. But when you close the window, that means the treatment is done, and that specific queue has no more reason to exist.
Good.
Sorry, this was said from a user point of view: when I click on execute, all the queues are processed, there is no option to run only the current one.
Yes. In fact, what I'm currently doing is quite simple but time consuming and need a bit or organization: in order to launch my new online gallery, I'm preparing all the JPEGs that will be then FTP-exported. For this, I cannot use the same queue as I won't apply the redimension tool in the same way for landscapes, portraits or panoramics; I'm not looking for a max dimension, but for a maximum height. So I need three different queues, with three different max sizes depending on the picture original format.
But ... - if I put pictures in the wrong queue, the resizing is not right - if I forget to remove a picture once it is treated, I get two copies of the same (in the past, it was possible to not create an additional copy, and cancel the treatment, but it seems this option has disappeared too).
Fortunately, I'm doing the selection on the past 4 shooting years "only", but that still leaves quite a lot of pictures to review, select and treat... and quite many mistakes to be made ;-)
De l'AIgoual à l'Aubrac, un voyage photographique en Cévennes et Lozère
Un livre à offrir ou à s'offrir, en souscription jusqu'au 31 août 2013. Cliquer sur l'image ci-dessus ou ce lien pour en savoir plus _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Re: Differences of behaviour since last upgrade
|
|
Re: Differences of behaviour since last upgrade
|
|
2013/8/19 Gilles Caulier <[hidden email]>
I guessed so. But it can be quite long when you modify many pictures at a time. Recently, I have been shooting about 1000 pictures (average) during 10 days in a row, and it was RAW from a 18Mpx camera.
I use to make my selection in the temporary folder before moving pictures I keep in their definitive folder; so it's not unusual I move several hundred pictures in one go. Given the volumes, I have not enough space on my laptop harddrive, so everything is on removable disks.
One thing I might do differently from you is the RAW treatment: I use Darktable instead of Digikam, to produce TIFF (even more huge, about 50Mo/picture) that are then managed in Digikam. But in most cases, Digikam is already opened (I use it to make my selection) and folders are immediately updated; if not, I only have to use the F5 key.
There is one thing that gives me regular headaches! When I want to select several pictures, I use Ctrl-click to add to a selection (easier/more precise than the click on the '+' sign that makes me deselect everything when I click on '-' instead...); and very often, I get pictures that are duplicated or, worse, moved in another folder and I don't see it at the time it's being done.
I'm not sure how Digikam 'interprets' my commands, but sure it is not what I wanted to do...
Nothing is impossible, but I don't think so. Marie-Noëlle De l'AIgoual à l'Aubrac, un voyage photographique en Cévennes et Lozère
Un livre à offrir ou à s'offrir, en souscription jusqu'au 31 août 2013. Cliquer sur l'image ci-dessus ou ce lien pour en savoir plus _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
| Free forum by Nabble | Edit this page |