why isn't collect images:folders showing all my photos?

Thanks! That’s a handy tip. I’ve updated to 3.0.1.2.

That’s not fixed my folders problem though. I can find photos with film roll, and tags, and time, that are not showing up in folders.

Can you start dark able from the terminal, darktable -d all and post any output?

Thanks @paperdigits I’ve not figured out how to install/activate the darktable in command line on a Mac. When I install it from the dmg, it runs as a regular Mac app but Terminal doesn’t recognise the command “darktable”.

I haven’t yet found instructions on how to get darktable working from the Mac Terminal. If a Mac darktable user can give me a prod in the right direction, that would be great!

What OS version you have? Has there been a recent update?
Since you’re working on stable version - has the setup worked previously? I mean - thins were working with 3.0.0 but changed in recent weeks?

@ johnny-bit I’m still on MacOS 10.14.6. I’ve so far stayed away from Catalina (10.15) as I’ve got some old 32-bit apps that I occasionally use.

I’ve been using darktable since 2017 and haven’t had any problems with folders until recently, several weeks after I’d shifted to darktable 3.0. It started when I made a new library for all of my photos for 2016–now. With pre-3.0, I’d had a library for each year because otherwise darktable got too slow. That was always a hassle so with 3.0 I decided to make a library for the last five years. Soon after that, folders started misbehaving, but not until after I’d imported a few sessions of new photos.

I’m wondering if I’m going to have to just rebuild that library again.

Damn… I’d love to get debugging output for us to figure out what’s wrong…

can you try oppening up terminal and using full path do darktable, eg:
/Applications/darktable.app/Contents/MacOS/darktable -d all
?

we’ll see what the problem might be.

The screenshot shows a folder with 389 pictures. The scrollbar on the right of the lt seems to indicate that a very small portion (9 exactly) of the pictures are displayed. But there is nothing striking, the images are there and I suppose that if you scroll you’ll see of of them. So your screenshot just shows nothing wrong to me.

I also don’t really see any problems on your capture screen, except that your D800 folder doesn’t appear on darktable (probably just not imported) but “New downloads” folder on the left show 389 images and on top of lighttable view, I see 0 of 389 images. Of course, you have 9 shown but that just because you have 3 per line and your screen let 3 lines possible to shown. But I also see a scrollbar on the right, so scrolling will show you other images. Or did we miss something?

Said that, @Pascal_Obry: this discussion show that links on install page of darktable.org have not been updated. They are still on 3.0.0. I don’t know who update that page until now.

1 Like

Thanks for the tip on how to get darktable running from Terminal. Good to know! That works a treat. I’ve attached the Terminal code below.

@Pascal_Obry and @Nilvus the issue is that my 2020 folder in darktable folders should be displaying the same folders as in my Finder screenshot. My folders 202001, 202002, and 202003 are missing from the folders view, and New downloads is showing 389 photos but contains over 8,000 photos. And, oddly, all of those other photos are still in darktable if I look for them by time, film roll, or tag.

Thanks everyone for your persistence with this.

darktable launch.txt (452.4 KB)

Do you have the recursive folder import option checked?

Yes, “recursive directory traversal when importing filmrolls” is checked. I’ve not touched that.

I’ve just created a PR for updating dtorg install page.

2 Likes

BTW: is anyone checking redmine? there are new issues till poping there. If you want I can browse as much as possible, try to replicate issues and see if there’s anything more needed so redmine could be effectively closed.

2 Likes

No, Redmine is dead for me now and I certainly don’t have time to look there.

1 Like

I’m quite surprised Redmine is not already on read-only mode. It’s easier to have one place to follow darktable development and Github is the main place. That was discussed few weeks ago. Maybe closing Redmine or put it read-only and advertise people to go on Github would be better.

2 Likes

For redmine to be read-only for everybody you’d have to disable insert/update permissions on database to redmine-database user… or create new user with disabled permissions so it’s tricky.

I don’t have redmine account and it cannot be created (which is good, because no new people will join) but if somebody with access has time, it would be good to advertise github all over the redmine, move articles from redmine to github wiki and then disable insert/update to redmine database :slight_smile:

As for issues themselves - there are at least 13 new issues since 3.0.0 release (10 since 01.01.2020) and over 200+ modified since 01.01.2019… many seem to be not present in github (or are since closed) so checking on them & closing (or just mass flood reply “post issue to github if you can replicate it on darktable master”+close) would be good overall.
Ultimatelly redmine.darktable.org should just redirect to github (once move is complete).

I figured it out!! And it’s a head slap thing.

I’d been overlooking something obvious. I’d built my new multi-year library starting with my 2020 darktable library and adding my earlier 2016–2019 photos (they all have xml sidecar files from their previous darktable libraries). As part of this, I also then moved all my 2020 photos from an external hard drive onto one of my laptop’s drives. I used the “search filmroll” in darktable to tell it where these photos had moved to.

And then I started using darktable by importing in a backlog of newer photos in my New downloads folder on my computer. It turns out that it was only these newer photos that I was seeing in my 2020 folder on darktable.

The trick is that these newly imported 2020 photos showed up in darktable with a different file path to the older 2020 photos that I’d relocated onto my laptop with “search filmroll”. The newly added photos are all in /Users/jonsullivan/Pictures/Darktable/Photos/2020/… while all of my other 2020 photos were in /Volumes/Morus/Users/jonsullivan/Pictures/Darktable/Photos/2020/… Note that this is exactly the same folder.

Embarrassingly, I’ve got the “Volumes” part of folders view collapsed in the screenshot I posted and I hadn’t noticed until today that it contained my other 2020 photos as well as my photos from earlier years.

Interestingly, if I add some of those older 2020 photos onto darktable again (by dragging a folder on to the darktable icon in the Mac dock), they end up being duplicated in darktable, by being added to /Users/jonsullivan/Pictures/Darktable/Photos/2020/… while also still being present in /Volumes/Morus/Users/jonsullivan/Pictures/Darktable/Photos/2020/… (even though that’s the same place on my drive).

My solution was to add all of my 2020 photos again, dragging them onto darktable, so that they are all together with my more recent photos in /Users/jonsullivan/Pictures/Darktable/Photos/2020/… I then went to /Volumes/Morus/Users/jonsullivan/Pictures/Darktable/Photos/2020/… and selected all the photos and removed them from darktable.

Things are all tidy are functional again.

This does seem to have revealed an odd quirk in darktable 3, at least on Mac.

I drag photos from my Pictures folder onto the darktable icon in the dock, and they end up with full path /Users/jonsullivan/Pictures/

Once I’ve tagged them up, I use the move… tool inside darktable to move them to another folder in Pictures, but then they end up with full path /Volumes/Morus/Users/jonsullivan/Pictures/… (where Morus is my main laptop hard drive).

So they end up in different parts of the folders view. I have to use other ways (like date) to view my recently imported and tagged photos in the same lighttable view.

I think this is a darktable 3 thing, as I didn’t run into this before 3.0 and my workflow is the same.

This looks more like Mac lying about paths. I mean - if /Users/jon is same as /Volumes/Morus/Users/jon and Mac sends first when doing query and second when doing image operations, the app has little chance of knowing that they are identical without some additional checking.

On a Mac /Volumes/ shows you every mounted disk. Its a little weird, but the paths he lists are essentially equivalent.