[digiKam-users] Album refresh

[Mark Miller-2]

I recently update from version 5.9xx to 6.4 and I have noticed an
interesting issue. Were as in 5.9 Digikam would update the contents of
the album I am viewing every few seconds. I noticed that 6.4 does not do
this. I noticed behavior as I am scanning new photos in to a album.

I can not find anything in the Digikam documents that references this
behavior of automatically updating  the albums contents....


Can some explain the why this difference? I like automatic updating
while I am scanning photos....

[Maik Qualmann]

You are probably looking for the option to monitor the albums for external
changes. You can find these in the digiKam Setup under collections. Monitoring
for external changes is now deactivated by default, since it can also cause
various problems.

Maik

Am Dienstag, 14. Januar 2020, 04:08:43 CET schrieb Mark Miller:

> I recently update from version 5.9xx to 6.4 and I have noticed an
> interesting issue. Were as in 5.9 Digikam would update the contents of
> the album I am viewing every few seconds. I noticed that 6.4 does not do
> this. I noticed behavior as I am scanning new photos in to a album.
>
> I can not find anything in the Digikam documents that references this
> behavior of automatically updating  the albums contents....
>
>
> Can some explain the why this difference? I like automatic updating
> while I am scanning photos....

[leoutation]

On 1/15/20 6:48 AM, Maik Qualmann wrote:
> You are probably looking for the option to monitor the albums for external
> changes. You can find these in the digiKam Setup under collections. Monitoring
> for external changes is now deactivated by default, since it can also cause
> various problems.

Hi
Which kind of "various problem"?

--
Maderios

[Maik Qualmann]

Under MacOS it slows down the start of digiKam network collections (around 20
minutes was reported). Adding a watch uses kernel resources. Some systems end
with 256 albums, but with a modern Linux kernel the end is reached above 10-30
thousand albums. A monitored folder is locked under Windows, cannot be deleted
or moved, and removable disks cannot be unmounted. So it is not really useful
/ possible to monitor all albums in large collections. Maybe we make it
configurable to set a few albums, digiKam no longer needs the album monitoring
internally. If you add files with drag & drop or via copy / paste, digiKam
will of course update the view.

Maik

Am Mittwoch, 15. Januar 2020, 07:54:01 CET schrieb [hidden email]:

> On 1/15/20 6:48 AM, Maik Qualmann wrote:
> > You are probably looking for the option to monitor the albums for external
> > changes. You can find these in the digiKam Setup under collections.
> > Monitoring for external changes is now deactivated by default, since it
> > can also cause various problems.
>
> Hi
> Which kind of "various problem"?
>
> --
> Maderios

[Martin Burnicki-2]

[hidden email] wrote:

> On 1/15/20 6:48 AM, Maik Qualmann wrote:
>> You are probably looking for the option to monitor the albums for
>> external
>> changes. You can find these in the digiKam Setup under collections.
>> Monitoring
>> for external changes is now deactivated by default, since it can also
>> cause
>> various problems.
>
> Hi
> Which kind of "various problem"?

I've just recently run into one on Linux.

While DK 6.1 was running, I used a file manager (Dolphin) to create a
new folder inside DK's album tree, and then copied some photos from my
smartphone via a USB connection into that folder.

All those images were corrupted, i.e. an upper part of each image looked
OK, but the lower part of each image was just shown with an empty, gray
background. Also some other photo viewer applications were unable to
display those images.

However, after I had stopped DK, copied the images once more, and then
restarted DK, DK automatically detected the new photos and displayed
them correctly, and also other applications could properly show those
images.

My assumption is that as soon as a download of a photo starts and a
target file is created, DK gets notified and tries to add the new image
to its database. If the download / copying is not complete when this
happens, the remaining part of the file can't be saved because the file
has been opened by DK, resulting in incomplete and thus corrupted image
files.

I don't know if there is a safe way to avoid this problem. A possible
workaround could be to let DK not open the files to make sure the file
is complete before it is opened by DK.

But of course, also disabling automatic detection of new photos should
avoid this.

Martin

[Stuart T Rogers]

I have done this loads of times with no adverse effect on Linux and V6
of Digikam. I suspect what happened was Digikam was looking for changes
while you were copying. I've always had to refresh Digikam after
creating a new directory and/or copying images.

Stuart

On 15/01/2020 10:47, Martin Burnicki wrote:

> [hidden email] wrote:
>> On 1/15/20 6:48 AM, Maik Qualmann wrote:
>>> You are probably looking for the option to monitor the albums for
>>> external
>>> changes. You can find these in the digiKam Setup under collections.
>>> Monitoring
>>> for external changes is now deactivated by default, since it can also
>>> cause
>>> various problems.
>>
>> Hi
>> Which kind of "various problem"?
>
> I've just recently run into one on Linux.
>
> While DK 6.1 was running, I used a file manager (Dolphin) to create a
> new folder inside DK's album tree, and then copied some photos from my
> smartphone via a USB connection into that folder.
>
> All those images were corrupted, i.e. an upper part of each image looked
> OK, but the lower part of each image was just shown with an empty, gray
> background. Also some other photo viewer applications were unable to
> display those images.
>
> However, after I had stopped DK, copied the images once more, and then
> restarted DK, DK automatically detected the new photos and displayed
> them correctly, and also other applications could properly show those
> images.
>
> My assumption is that as soon as a download of a photo starts and a
> target file is created, DK gets notified and tries to add the new image
> to its database. If the download / copying is not complete when this
> happens, the remaining part of the file can't be saved because the file
> has been opened by DK, resulting in incomplete and thus corrupted image
> files.
>
> I don't know if there is a safe way to avoid this problem. A possible
> workaround could be to let DK not open the files to make sure the file
> is complete before it is opened by DK.
>
> But of course, also disabling automatic detection of new photos should
> avoid this.
>
> Martin
>

--
Website: https://www.stella-maris.org.uk
or:      https//www.broadstairs.org

[Martin Burnicki-2]

Stuart T Rogers wrote:
> I have done this loads of times with no adverse effect on Linux and V6
> of Digikam.

So did I, without problems.

It was the first time I observed it, with a smartphone connection over
USB which was pretty slow.

> I suspect what happened was Digikam was looking for changes
> while you were copying.

Yes, that's what I tried to says in my assumption. Looks like it started
doing so before copying was complete.

> I've always had to refresh Digikam after
> creating a new directory and/or copying images.

Then maybe you have disabled the automatic update in the DK settings?

This used to work fine for me, too. E.g., if I just moved an existing
folder into the DK album tree then DK detected the folder and images
automatically, without problems.

Martin

[Ian McCarthy-2]

On 15/01/2020 05:48, Maik Qualmann wrote:
> You are probably looking for the option to monitor the albums for external
> changes. You can find these in the digiKam Setup under collections. Monitoring
> for external changes is now deactivated by default, since it can also cause
> various problems.

To save problems and performance, I have this feature turned off. What I
would really like is a button which says "scan albums now" for change,
because I know when I have changed things. At the moment I have to stop
digiKam and restart it, which is also a pain.

--
Cheers Ian Mac - Ian D McCarthy
 
  Cronkshaw Fold
  Off Alden Rd
  Helmshore                       Tel     [phone]
  Rossendale BB4 4AQ              Mobile  [phone]
  United Kingdom                 Email   [hidden email]

[Maik Qualmann]

In principle, F5 does this task, but also generates new thumbnails. But we
could still change that.

Maik

Am Donnerstag, 16. Januar 2020, 23:04:17 CET schrieb Ian McCarthy:

> On 15/01/2020 05:48, Maik Qualmann wrote:
> > You are probably looking for the option to monitor the albums for external
> > changes. You can find these in the digiKam Setup under collections.
> > Monitoring for external changes is now deactivated by default, since it
> > can also cause various problems.
>
> To save problems and performance, I have this feature turned off. What I
> would really like is a button which says "scan albums now" for change,
> because I know when I have changed things. At the moment I have to stop
> digiKam and restart it, which is also a pain.

[Mark Miller]

Thank you...

Get BlueMail for Android

On Jan 16, 2020, at 16:04, Ian McCarthy <[hidden email]> wrote:

On 15/01/2020 05:48, Maik Qualmann wrote:
 You are probably looking for the option to monitor the albums for external
 changes. You can find these in the digiKam Setup under collections. Monitoring
 for external changes is now deactivated by default, since it can also cause
 various problems.

To save problems and performance, I have this feature turned off. What I 
would really like is a button which says "scan albums now" for change, 
because I know when I have changed things. At the moment I have to stop 
digiKam and restart it, which is also a pain.

Le 16/01/2020 à 23:36, Mark a écrit :

>     To save problems and performance, I have this feature turned off. What I
>     would really like is a button which says "scan albums now" for change,
>     because I know when I have changed things. At the moment I have to stop
>     digiKam and restart it, which is also a pain.
>
right clic, "refresh"

jdd

--
http://dodin.org

[rutile]

"refresh"  is also rebuilding all the thumbnails, no?

If I process images in, say, Imagemagick, and write new images back into a
Digikam folder, Digikam doesn't 'see' them until I hit refresh for the
folder.

However, it seems to me that Digikam is re-doing all the thumbnails, because
it takes a very long time to 'refresh' and I can hear the hard drives
working for a long period.

So, for instance, if I have 1200 photos in a folder (individual shots for
startrails, not an unusual number for long winter nights in light polluted
areas), and I used Imagemagick to stack them into 12 images, I have to tell
Digikam to refresh the folder to see them, but it may take several minutes
to do so (I haven't timed it), as if it is rebuilding all 1200 thumbnails
instead of just adding 12 more.

Is it possible to break down that task into two buttons?  Refresh-find new
items and Refresh-rebuild all thumbnails?





--
Sent from: http://digikam.1695700.n4.nabble.com/digikam-users-f1735189.html

[leoutation]

On 1/16/20 11:18 PM, Maik Qualmann wrote:
> In principle, F5 does this task, but also generates new thumbnails. But we
> could still change that.
>
This is an old story ever described here: F5 is very slow, it's unusable
when folder contains hundred files/pictures. When monitoring is not set,
the better way, now,  to refresh folder is maintenance tool.


--
Maderios

[Maik Qualmann]

I added the key shortcut Ctrl + F5 to update the album without thumbnails.

 

https://invent.kde.org/kde/digikam/commit/ae3a124af340b9ebdc0f9039ce07a68ad9e4bcc2

Maik

 

Am Samstag, 18. Januar 2020, 15:02:28 CET schrieb [hidden email]:

> On 1/16/20 11:18 PM, Maik Qualmann wrote:

> > In principle, F5 does this task, but also generates new thumbnails. But we

> > could still change that.

>

> This is an old story ever described here: F5 is very slow, it's unusable

> when folder contains hundred files/pictures. When monitoring is not set,

> the better way, now, to refresh folder is maintenance tool.

>

>

> --

> Maderios

 

 

[leoutation]

On 1/18/20 9:36 PM, Maik Qualmann wrote:
> I added the key shortcut Ctrl + F5 to update the album without thumbnails.
>
Hi
Answer in late...
Why not updating thumbnails too? I don't understand...

> https://invent.kde.org/kde/digikam/commit/ae3a124af340b9ebdc0f9039ce07a68ad9e4bcc2
>
> Maik
>
> Am Samstag, 18. Januar 2020, 15:02:28 CET schrieb [hidden email]:
>
>  > On 1/16/20 11:18 PM, Maik Qualmann wrote:
>
>  > > In principle, F5 does this task, but also generates new thumbnails.
> But we
>
>  > > could still change that.
>
>  >
>
>  > This is an old story ever described here: F5 is very slow, it's unusable
>
>  > when folder contains hundred files/pictures. When monitoring is not set,
>
>  > the better way, now, to refresh folder is maintenance tool.
>
>  >
>
>  >
>
>  > --
>
>  > Maderios
>

--
Maderios

[leoutation]

On 2/21/20 7:06 PM, [hidden email] wrote:
> On 1/18/20 9:36 PM, Maik Qualmann wrote:
>> I added the key shortcut Ctrl + F5 to update the album without
>> thumbnails.
>>
> Hi
> Answer in late...
> Why not updating thumbnails too? I don't understand...

Bad question because this shortcut updates thumbnails too...

>
>> https://invent.kde.org/kde/digikam/commit/ae3a124af340b9ebdc0f9039ce07a68ad9e4bcc2
>>
>>
>> Maik
>>
>> Am Samstag, 18. Januar 2020, 15:02:28 CET schrieb [hidden email]:
>>
>>  > On 1/16/20 11:18 PM, Maik Qualmann wrote:
>>
>>  > > In principle, F5 does this task, but also generates new thumbnails.
>> But we
>>
>>  > > could still change that.
>>
>>  >
>>
>>  > This is an old story ever described here: F5 is very slow, it's
>> unusable
>>
>>  > when folder contains hundred files/pictures. When monitoring is not
>> set,
>>
>>  > the better way, now, to refresh folder is maintenance tool.
>>
>>  >
>>
>>  >
>>
>>  > --
>>
>>  > Maderios
>>
>
>
> --
> Maderios

--
Maderios

[Maik Qualmann]

The old behavior is still there. The F5 key refreshes an album and recreates
all thumbnails. This is slow for users who have added new images externally
and want to have them displayed. Now there is also the Ctrl + F5 key, this
also performs an album refresh, but thumbnails are only created for new
images. This is significantly faster for albums with a lot of images.

Maik

Am Freitag, 21. Februar 2020, 19:06:58 CET schrieb [hidden email]:

> On 1/18/20 9:36 PM, Maik Qualmann wrote:
> > I added the key shortcut Ctrl + F5 to update the album without thumbnails.
>
> Hi
> Answer in late...
> Why not updating thumbnails too? I don't understand...
>
> > https://invent.kde.org/kde/digikam/commit/ae3a124af340b9ebdc0f9039ce07a68a
> > d9e4bcc2
> >
> > Maik
> >
> > Am Samstag, 18. Januar 2020, 15:02:28 CET schrieb [hidden email]:
> >  > On 1/16/20 11:18 PM, Maik Qualmann wrote:
> >  > > In principle, F5 does this task, but also generates new thumbnails.
> >
> > But we
> >
> >  > > could still change that.
> >  >
> >  > This is an old story ever described here: F5 is very slow, it's
> >  > unusable
> >  >
> >  > when folder contains hundred files/pictures. When monitoring is not
> >  > set,
> >  >
> >  > the better way, now, to refresh folder is maintenance tool.
> >  >
> >  >
> >  >
> >  >
> >  >
> >  > --
> >  >
> >  > Maderios
>
> --
> Maderios

[leoutation]

On 2/21/20 7:15 PM, Maik Qualmann wrote:
> The old behavior is still there. The F5 key refreshes an album and recreates
> all thumbnails. This is slow for users who have added new images externally
> and want to have them displayed. Now there is also the Ctrl + F5 key, this
> also performs an album refresh, but thumbnails are only created for new
> images. This is significantly faster for albums with a lot of images.
After editing images, I use F5 to refresh thumbnails.
I see that Ctrl+F5 function updates thumbnails too after editing them.

--
Maderios

[Maik Qualmann]

That's right, if the image has been changed, Ctrl + F5 will also create a new
thumbnail. But not for ALL other images. Take the test with a really big album
and you will notice the difference.

Maik

Am Freitag, 21. Februar 2020, 19:48:37 CET schrieb [hidden email]:

> On 2/21/20 7:15 PM, Maik Qualmann wrote:
> > The old behavior is still there. The F5 key refreshes an album and
> > recreates all thumbnails. This is slow for users who have added new
> > images externally and want to have them displayed. Now there is also the
> > Ctrl + F5 key, this also performs an album refresh, but thumbnails are
> > only created for new images. This is significantly faster for albums with
> > a lot of images.
> After editing images, I use F5 to refresh thumbnails.
> I see that Ctrl+F5 function updates thumbnails too after editing them.
>
> --
> Maderios

[leoutation]

On 2/21/20 8:36 PM, Maik Qualmann wrote:
> That's right, if the image has been changed, Ctrl + F5 will also create a new
> thumbnail. But not for ALL other images. Take the test with a really big album
> and you will notice the difference.
It's clearer, thanks. I notice it's faster than F5, but not so fast than
'scan for new items'. For me, it would be a good thing to get a 'scan
for new items' shortcut possibility. I didn't find such one in settings.
Other question: in shortcut settings, i see refresh 'F5' | Alternate
'Ctrl+F5'. I replaced 'Ctrl+F5' with 'F6'. I hope i get same behaviour...

>
> Maik
>
> Am Freitag, 21. Februar 2020, 19:48:37 CET schrieb [hidden email]:
>> On 2/21/20 7:15 PM, Maik Qualmann wrote:
>>> The old behavior is still there. The F5 key refreshes an album and
>>> recreates all thumbnails. This is slow for users who have added new
>>> images externally and want to have them displayed. Now there is also the
>>> Ctrl + F5 key, this also performs an album refresh, but thumbnails are
>>> only created for new images. This is significantly faster for albums with
>>> a lot of images.
>> After editing images, I use F5 to refresh thumbnails.
>> I see that Ctrl+F5 function updates thumbnails too after editing them.
>>
>> --
>> Maderios
>
>
>
>

--
Maderios