darktable: Issues

Bug #9289 (Triaged): lighttable: strange behaviour when rejecting images with the mouse / fluxbox...

2013-03-07T09:40:35Z

When an image is rated lower than the filer, or rejected, using the mouse and it disappears of the collection, the behaviour of the selection is strange. The normal behaviour would be to keep the selected range if the image being modified is out of the selection, or not selecting any new image if the image being modified is the image selected.

The problem comes because the selection is not handled in the button_pressed callback. This is fixed in the following commits:
fc4c157596fdd9727d33dad5a8ec074783993f47 and 0ccab755f33a73d025643850130fa8b9d6a24bb9

But this fix raises a bug in fluxbox that makes impossible to select any image, so it was reverted in:
c101d8f3c1f369a195507342e5f17d504c959d17

Bug #9288 (New): folder selection in collect images module is cleared when switching do darkroom ...

2013-03-06T21:36:36Z

Hi,
this is very annoying for me. Frequently my scenario looks like this:
- I'm browsing through entire collection using folder selection looking for specific images
- when I find one I go to darkroom to tune them
- and when I go back to lighttable I'm on top of folders tree and I have to navigate again and again to go back where I ended

Is it because widgets are destroyed and recreated when switching to darkroom and back?

Similar annoying thing is when one selects film roll by double click and then clears the rule to select next roll. Film roll selector will be on the top of the list, which can be very long because of its flatness.

Feature #9287 (New): Export module to Piwigo web server

2013-03-04T14:32:43Z

It's will be great if darktable will be able to upload directly to a piwigo web server

a API is available for that, as another soft can already do it (exemple : shotwell)

Documentation available for that :
piwigo.org/doc/doku.php?id=dev:webapi:start
a complete & complex method :
piwigo.org/doc/doku.php?id=dev:webapi:pwg.images.add
a simple method :
piwigo.org/doc/doku.php?id=dev:webapi:pwg.images.addsimple

Bug #9286 (New): spot removal: active spot loses focus after one drag operation

2013-03-03T21:24:29Z

steps to reproduce:

draw a spot-pair
drag one endpoint a bit, stop mouse movement and release mouse button

what happens: the active spot loses its focus, repeating step two results in drawing a new spot-pair instead of moving the endpoint again
what is expected: the active spot should remain active until the mouse leaves the circle

note this also happens if you try to move the endpoint of a newly created spot-pair if the pointer has not been moved after releasing the mouse button.

using dt with a trackpoint or touchpad triggers this issue quite often.

Bug #9283 (New): Collect Images module tags list out of sync

2013-02-26T16:55:04Z

The list of "darktable|..." tags available in the Collect Images module can become out of sync. For example, I start with an empty library. I import some raw files and some JPEGs. Two available tags are "darktable|format|cr2" and "darktable|format|jpg". I remove the JPEG files from the DT library. The "darktable|format|jpg" tag remains in the list. Collecting images with it leads to the message "there are no images in this collection." I would have expected that "darktable|format|jpg" would no longer be in the list of tags.

Bug #9281 (New): Lighttable may jump to the top

2013-02-26T03:59:22Z

While scrolling through images in Lighttable mode, the view may surprisingly jump to the top (i.e., to the first images in the collection) randomly. This happens more often if you have set a bigger view on the images. For example, set the number of images per row to one and scroll to the images with the mousewheel or the arrow keys.

Bug #9280 (Confirmed): Freeze while rejecting images in preview

2013-02-26T03:20:21Z

When viewing images in full-scale "z" preview and rejecting one by clicking on the "X", darktable may freeze. On the console, it says:

[image_cache_allocate] failed to open image -1 from database: unknown error

Bug #9279 (Incomplete): Darktable corrupts geotag data

2013-02-25T16:11:21Z

After having imported a directory with geotagged images (in XMP files), the geo locations are corrupted. The image attached has N264°00,901' and E094°07,533'. They used to be correct. Since this means data loss, I set the priority to high.

Feature #9277 (New): WebP format support in export module

2013-02-21T07:52:59Z

Please add webp format support

Bug #9276 (In Progress): Panasonic DMC LX7 support

2013-02-20T23:39:47Z

When I import raw shots from my DMC LX7, I get weird colors I can't manage to adjust neither using different input or output profiles, base curve or white balance. The light table thumbnails looks ok just after import, but as soon as I enter the darkroom, the colors are heavily shifted. Then in the light table the thumbnail is updated with the weird colors.

Screenshot of light table thumbnails after the color shift (both jpg and raw formats versions the same shot) : ubuntuone.com/5NgVKfEmzOhMM6cUN4fyBN

Sample RAW photo to reproduce the problem : ubuntuone.com/3TP5UKlsvXkR2XUANykVrJ

Please tell me if I can provide more information.

using darktable 1.1.3+25~gba0923f from ubuntu unstable ppa.

Bug #9275 (New): Lighttable UI sluggish when using 'except' operation on tags under 'collect images'

2013-02-19T01:25:43Z

If I select a tag under 'collect images' that has quite a few matches, and then select 'exclude images' and select another tag that impacts a smaller number of images, then the UI suddenly becomes much less responsive. Scrolling around in the LightTable file manager becomes at least 3x slower - even the highlight image that follows the cursor becomes much slower.

An important use case for me is to scroll through a list of potential images I'd like to use in my art, but I'd like to be able to exclude images that are already used in my art, so being able to use the 'except' operation on tags is pretty important to me.

I've attached a short video showing the performance difference between the two scenarios...

Feature #9274 (New): Using primary key, CMD on Mac, as CTRL is used on Linux

2013-02-18T19:14:30Z

Would be great if the Mac port used CMD instead of CTRL for e.g. multi select and copy-paste actions.

I might have been led on, but someone mentioned a change from using <control> to <primary> key was an easy switch in the software that would enable this perfectly across platforms.

Feature #9273 (New): lens correction enhancement - more understandable interface

2013-02-18T15:41:37Z

The lens correction module has not very user oriented UI.

'corrections' is presented as a pull down menu of all the possible combinations of TCA/distortion/vignetting corrections, this choice make it hard, for the new users and the users who do not like reading hard, to find the correct choice. The straigh forward solution will be introduction of the checkboxes with short labels/icons with appropriate help text (now the abbreviation TCA is not explained)
all the following widgets: 'geometry', 'scale' .. 'tca blue' have no clear connection with the correction they are affecting. The solution will be to group them together with the correction they are affecting. More over, they have no effect (tca ...), when 'none' corrections is chosen, although they have the same look and feel. The use of disabled widgets can address this. One obvious 'mistake' is the mode of correction - does it affect all the corrections together, if yes why it is so?

I understand that blind introduction of more adjustable parameters in the lens correction module is not the solution. The module may be splitted, or even introduce some hierarchy to hold all the functionality.

Feature #9272 (Triaged): lens correction enhancement - amount of correction

2013-02-18T15:11:30Z

The common camera models have the option of low, medium and high correction of vignetting. The lens correction module does not have any "amount value" for vignetting and distortion correction. It may be interesting to allow user choose the magnitude of the applied corrections. As an example - the full vignetting correction can be unpleasant, albeit correct, while partial correction can have the right perceptual appearance.

Feature #9271 (New): lens correction module and lens profiles reload

2013-02-18T15:01:26Z

In the current state the lens profiles are loaded at the startup of the Darktable. For the creation of lens profiles it means that every change of a lens profile, which can be done only in the lens profile xml, can be viewed only after restart of the Darktable. In the case of fully automated generation of the lens profiles this behaviour is just OK. But for anything else it introduce an obstacle to test changed lens profile. The solution can be either ability to reload lens profiles (e.g. user lens profiles) or to introduce some sort of control over all the parameters of lens profile in the Darktable.