Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

After upgrade 4.8.1 to 5.0 grouping is changed #18059

Open
ruudsieb opened this issue Dec 24, 2024 · 1 comment
Open

After upgrade 4.8.1 to 5.0 grouping is changed #18059

ruudsieb opened this issue Dec 24, 2024 · 1 comment
Labels
scope: DAM managing files, collections, archiving, metadata, etc. scope: UI user interface and interactions

Comments

@ruudsieb
Copy link

Describe the bug

Have several collections with CR3 and JPG files which were grouped automatically after import in 4.8.1
After upgrading to 5.0 grouping was changed/corrupt. Lighttable showed only JPEG files, groupleader was indicated as CR3 file.
Now trying to manually correct this problem, LT does not update the thumbnail view when regrouping the images by hand. Have to toggle collapse/expand grouped images to update the view.

Steps to reproduce

  1. install 4.8.1
  2. import/copy images containing JPG + CR3
  3. make sure the images are grouped, CR3 is leading
  4. upgrade to 5.0

Expected behavior

Leave grouping as is

Logfile | Screenshot | Screencast

No response

Commit

12d9454

Where did you obtain darktable from?

downloaded from www.darktable.org

darktable version

5.0.0

What OS are you using?

Windows

What is the version of your OS?

Windows 11

Describe your system?

No response

Are you using OpenCL GPU in darktable?

Yes

If yes, what is the GPU card and driver?

No response

Please provide additional context if applicable. You can attach files too, but might need to rename to .txt or .zip

No response

@ruudsieb ruudsieb changed the title After upgrade 4.8.1 to 5.0 grouping is gone After upgrade 4.8.1 to 5.0 grouping is changed Dec 24, 2024
@ralfbrown ralfbrown added scope: UI user interface and interactions scope: DAM managing files, collections, archiving, metadata, etc. labels Dec 27, 2024
@matt-hoskins
Copy link

I've experienced the same with ARW and JPG files - it was showing only JPEG and not the ARW I was using as the primary before.

Howver I tried fiddling with a few different things to see if I could get it to behave and found that although the "module order" filter setting was showing as "all images" if I changed it to something else and then back to "all images" it was now correctly showing the ARW files as the group leader.

Note that this filter seems to behave a bit weirdly in general with respect to "v5.0 RAW", "v5.0 JPEG" and "none" - for a recent collection starting from "all images" if I change it to "v5.0 RAW" or "v5.0 JPEG" it continues to show all images. If I change it to "v3.0 JPEG" it then shows none and then if I change it back to e.g. "v5.0 JPEG" it shows none still (i.e. those 3 settings don't seem to change what's selected for me).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
scope: DAM managing files, collections, archiving, metadata, etc. scope: UI user interface and interactions
Projects
None yet
Development

No branches or pull requests

3 participants