Wishes for future versions

classic Classic list List threaded Threaded
8 messages Options
Reply | Threaded
Open this post in threaded view
|

Wishes for future versions

Remco Viëtor
Hi,

I have been using Digikam for a while now, and I find it the best suited to my
needs.

There's still a number of things I'd liek to see added, so I decided to drop
the list here to see if others are interested in those features, and if some
are already planned (in that case, no need to clutter the bugzilla wishlist).

So, what I'm missing is:

- a 'levels' tool
- a tool in batch queue to write metadata from the database to the image files
- a way to save and restore a list of batch queue commands
- a way to save a slideshow (in dvd-slideshow format?)
- possibility to select a point/area in a raw image to determine white balance

Please comment :)

I'm quite willing to start coding on some parts of this, after discussion with
the maintainers (to avoid me starting on something that's about to be
overhauled).

Remco
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users
Reply | Threaded
Open this post in threaded view
|

Re: Wishes for future versions

tosca
I'm afraid I'm not very interested in all the image editing tools as I use Darktable to post process my RAW files. I don't make slideshow very often, by I use a specific program for that, too.

But I agree for any addition/improvment in the batch queue commands. Save/restore would be very nice; and would also be for the printing assistant tool.

Marie-Noëlle


2012/1/14 Remco Viëtor <[hidden email]>
Hi,

I have been using Digikam for a while now, and I find it the best suited to my
needs.

There's still a number of things I'd liek to see added, so I decided to drop
the list here to see if others are interested in those features, and if some
are already planned (in that case, no need to clutter the bugzilla wishlist).

So, what I'm missing is:

- a 'levels' tool
- a tool in batch queue to write metadata from the database to the image files
- a way to save and restore a list of batch queue commands
- a way to save a slideshow (in dvd-slideshow format?)
- possibility to select a point/area in a raw image to determine white balance

Please comment :)

I'm quite willing to start coding on some parts of this, after discussion with
the maintainers (to avoid me starting on something that's about to be
overhauled).

Remco
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users



--
Mes dernières photos sont dans ma galerie.
Retrouvez-moi aussi sur mon blog.
Et parcourez les Cévennes à ma façon avec Cévennes Plurielles,


_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users
Reply | Threaded
Open this post in threaded view
|

Re: Wishes for future versions

Andrew Goodbody
In reply to this post by Remco Viëtor
On 14/01/12 10:08, Remco Viëtor wrote:
> There's still a number of things I'd liek to see added, so I decided to drop
> the list here to see if others are interested in those features, and if some
> are already planned (in that case, no need to clutter the bugzilla wishlist).
>
> So, what I'm missing is:
>
> - a 'levels' tool
Yes, possibly although I do not actually edit photos in Digikam (yet).
> - a tool in batch queue to write metadata from the database to the image files
Yes, possibly, but I find it better to always store the metadata in the
files.
> - a way to save and restore a list of batch queue commands
Yes definitely. I think I read that this is in the queue already.
> - a way to save a slideshow (in dvd-slideshow format?)
Yes.
> - possibility to select a point/area in a raw image to determine white balance
Yes. May have been requested already, not sure.
>
> Please comment :)

The big one that I would like to see is to be able to copy a set of tags
from one image and copy them to one or more other images.
Next I would like the xmp sidecar file support to be knocked into shape.
You should be able to better control where metadata is read from (ie
allow from image and sidecar), merging it if necessary, and where it is
written to. This could need to be different for raw vs. 'developed'
image formats.
There are also sporadic reports of issues with tagging CR2 raw files and
then propagating those tags to the 'developed' files. This is not
something I have tried, but I would like it to work. Not sure if getting
xmp sidecar files working properly would help here.

Andrew
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users
Reply | Threaded
Open this post in threaded view
|

Re: Wishes for future versions

Remco Viëtor
In reply to this post by Remco Viëtor
On Saturday 14 January 2012 11:08:47 Remco Viëtor wrote:

>
> So, what I'm missing is:
>
> - a 'levels' tool

Stupid me...

There is a levels tool in the editor, what is missing is the same tool in the
batch treatment.

Apologies for the careless editing :(


I'll use the occasion to elaborate a bit about the why of some items.
Ideally, I would like to be able to edit one image in the normal editor
(starting from a raw file or any other format) and then apply the same
treatment  for a series of other images. In order for that to work, tools need
to be present in both the editor and the batch queue manager, and the tools
need to accept the same set of parameters. (and ideally the same code, as far
as possible, of course). With the versioning system in place, a lot of the
required information is now available/stored somewhere. When we get the
missing tools in the batch queue, we could use the versioning info to replay
the used treatment on another file.

Remco
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users
Reply | Threaded
Open this post in threaded view
|

Re: Wishes for future versions

Andrew Goodbody
On 14/01/12 18:15, Remco Viëtor wrote:

> I'll use the occasion to elaborate a bit about the why of some items.
> Ideally, I would like to be able to edit one image in the normal editor
> (starting from a raw file or any other format) and then apply the same
> treatment  for a series of other images. In order for that to work, tools need
> to be present in both the editor and the batch queue manager, and the tools
> need to accept the same set of parameters. (and ideally the same code, as far
> as possible, of course). With the versioning system in place, a lot of the
> required information is now available/stored somewhere. When we get the
> missing tools in the batch queue, we could use the versioning info to replay
> the used treatment on another file.

+1

Andrew
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users
Reply | Threaded
Open this post in threaded view
|

Re : Wishes for future versions

Paulux
Not very smart, but I can make anything but :

+999999999999999999999999999

Clark


De : Andrew Goodbody <[hidden email]>
À : [hidden email]
Envoyé le : Samedi 14 Janvier 2012 19h34
Objet : Re: [Digikam-users] Wishes for future versions

On 14/01/12 18:15, Remco Viëtor wrote:

> I'll use the occasion to elaborate a bit about the why of some items.
> Ideally, I would like to be able to edit one image in the normal editor
> (starting from a raw file or any other format) and then apply the same
> treatment  for a series of other images. In order for that to work, tools need
> to be present in both the editor and the batch queue manager, and the tools
> need to accept the same set of parameters. (and ideally the same code, as far
> as possible, of course). With the versioning system in place, a lot of the
> required information is now available/stored somewhere. When we get the
> missing tools in the batch queue, we could use the versioning info to replay
> the used treatment on another file.

+1

Andrew
_______________________________________________
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
Reply | Threaded
Open this post in threaded view
|

Re: Re : Wishes for future versions

todd rme
On Thu, Jan 19, 2012 at 9:03 PM, Paulux <[hidden email]> wrote:

> Not very smart, but I can make anything but :
>
> +999999999999999999999999999
>
> Clark
>
> ________________________________
> De : Andrew Goodbody <[hidden email]>
> À : [hidden email]
> Envoyé le : Samedi 14 Janvier 2012 19h34
> Objet : Re: [Digikam-users] Wishes for future versions
>
> On 14/01/12 18:15, Remco iëtor wrote:
>> I'll use the occasion to elaborate a bit about the why of some items.
>> Ideally, I would like to be able to edit one image in the normal editor
>> (starting from a raw file or any other format) and then apply the same
>> treatment  for a series of other images. In order for that to work, tools
>> need
>> to be present in both the editor and the batch queue manager, and the
>> tools
>> need to accept the same set of parameters. (and ideally the same code, as
>> far
>> as possible, of course). With the versioning system in place, a lot of the
>> required information is now available/stored somewhere. When we get the
>> missing tools in the batch queue, we could use the versioning info to
>> replay
>> the used treatment on another file.
>
> +1
>
> Andrew

If there is a single thing I would really love, it would be a reworked
duplicate image interface.  It takes too many clicks to remove a
duplicate image, making it infeasible to use for anything other than a
very small number of pictures.

You need to click the item in the list, then figure out which pictures
you want you want to delete, then click those pictures , then click
delete, then wait for the file to delete, and only after the deleting
is done can you move onto the next picture.  It could easily take 20
or 30 seconds per set, and if you have thousands of duplicates (easy
if you are trying to merge pictures from two computers with lots of
overlap but different metadata), that could easily be ten hours of
tedious clicking.  This actually is exactly the case I am in right now

Having a single browser for all duplicate pictures, for instance with
each row being a duplicate set, and each column being a folder, would
make it easy to remove duplicates from a particular folder easily and
quickly.

-Todd
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users
Reply | Threaded
Open this post in threaded view
|

Re: Re : Wishes for future versions

ozzyprv

Being able to properly read tooltips!

On Jan 19, 2012 1:56 PM, "todd rme" <[hidden email]> wrote:
On Thu, Jan 19, 2012 at 9:03 PM, Paulux <[hidden email]> wrote:
> Not very smart, but I can make anything but :
>
> +999999999999999999999999999
>
> Clark
>
> ________________________________
> De : Andrew Goodbody <[hidden email]>
> À : [hidden email]
> Envoyé le : Samedi 14 Janvier 2012 19h34
> Objet : Re: [Digikam-users] Wishes for future versions
>
> On 14/01/12 18:15, Remco iëtor wrote:
>> I'll use the occasion to elaborate a bit about the why of some items.
>> Ideally, I would like to be able to edit one image in the normal editor
>> (starting from a raw file or any other format) and then apply the same
>> treatment  for a series of other images. In order for that to work, tools
>> need
>> to be present in both the editor and the batch queue manager, and the
>> tools
>> need to accept the same set of parameters. (and ideally the same code, as
>> far
>> as possible, of course). With the versioning system in place, a lot of the
>> required information is now available/stored somewhere. When we get the
>> missing tools in the batch queue, we could use the versioning info to
>> replay
>> the used treatment on another file.
>
> +1
>
> Andrew

If there is a single thing I would really love, it would be a reworked
duplicate image interface.  It takes too many clicks to remove a
duplicate image, making it infeasible to use for anything other than a
very small number of pictures.

You need to click the item in the list, then figure out which pictures
you want you want to delete, then click those pictures , then click
delete, then wait for the file to delete, and only after the deleting
is done can you move onto the next picture.  It could easily take 20
or 30 seconds per set, and if you have thousands of duplicates (easy
if you are trying to merge pictures from two computers with lots of
overlap but different metadata), that could easily be ten hours of
tedious clicking.  This actually is exactly the case I am in right now

Having a single browser for all duplicate pictures, for instance with
each row being a duplicate set, and each column being a folder, would
make it easy to remove duplicates from a particular folder easily and
quickly.

-Todd
_______________________________________________
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