P: Limit of 52 reorderings in custom-ordered collections and folders

15 Votes
Community Beginner ,
Jan 28, 2017 Jan 28, 2017

Copy link to clipboard

Copied

[I've verified this bug still exists in LR 10.0. See this post. -- John Ellis] 

After a while of custom sorting the order of photos and stacks within a collection (using Grid View), Lightroom starts to unpredictably refuse to sort photos. Some will get positioned where I drop them, others won't move at all and yet others will get positioned somewhere close by (eg. 4 or 5 photos before or after).

After digging into the catalog file I've come across what I think is the problem, but don't know how to fix it. In the attached file you'll see a screenshot of the database table for the collection, you'll see I've hilited the images that are part of the same collection, but their positionId is identical (which should never happen I'm assuming), probably due to the field size reaching it's maximum length. This is what I believe is causing the problem. Tested this on both Lightroom 5.7 and CC 2015.8.

This is a major bug and effectively stops user sorting from being functional, as well as now having potentially lost weeks of work. Any suggestions?



Thanks,

Adrian

Bug Fixed
TOPICS
macOS , Windows

Views

624

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines

correct answers 1 Correct answer

LEGEND , Dec 07, 2020 Dec 07, 2020

The most recent bug recipe now works in LR 10.1. Let's hope that LR 10.1 also fixes the errors getting thrown by collections using custom sort order.

Votes

Translate

Translate
87 Comments
New Here ,
Oct 14, 2019 Oct 14, 2019

Copy link to clipboard

Copied

Chiming in to say that a 3 year old bug of this magnitude needs to be addressed.  As a professional wedding photographer, my final collections for every project are near 1,000 images - I can't begin to tell you the frustration when I reach the end of a project, go to export, and find that LR has moved files around within the custom sort here and there.  It can take hours to go through, find them all, and rectify the problem.  Basically once a week I am dealing with this problem on a grand scale - which adds up to many lost hours per month.  C'mon Adobe - lets have a fix already!

PS - I have noticed that this random re-sorting primarily targets images I have color labeled Red - but not ALL images labeled Red, just some of them.  Occasionally a non-color labeled image will move but I would say that 95% of the time its a Red that's moved.  This seems somehow baked into the algorithm.  I generally don't use other color labels, so I can't confirm or deny that it affects Reds as opposed to certain other colors.

Votes

Translate

Translate

Report

Report
Community Beginner ,
Oct 17, 2019 Oct 17, 2019

Copy link to clipboard

Copied

And now Adobe has removed the ability to load any of the older releases where ordering was not broken!

Votes

Translate

Translate

Report

Report
LEGEND ,
Oct 17, 2019 Oct 17, 2019

Copy link to clipboard

Copied

"...any of the older releases where ordering was not broken!"

Unfortunately, the collection ordering has been broken at least back to LR 5.7.

Votes

Translate

Translate

Report

Report
Community Beginner ,
Oct 17, 2019 Oct 17, 2019

Copy link to clipboard

Copied

I'm not even talking about ordering collections.  I could order my regular photo sets in 8.0 but not 8.3.  I've reproduced the ordering problem on every release since.  I don't suppose there is a way to revert a catalog back to LR 6......

Votes

Translate

Translate

Report

Report
LEGEND ,
Oct 17, 2019 Oct 17, 2019

Copy link to clipboard

Copied

The same ordering algorithm is used for both folders and collections, in LR 8.4 and in all previous versions.  So reverting back to LR 6 won't in general avoid the bug.  If anything, the version of the algorithm in LR 6 may trigger the bug with fewer custom reorderings than in LR 8.4.

LR 8.3 changed the ordering algorithm in an attempt to fix the bug, changing the observed behavior, but it's still buggy for both collections and folders.  That you observed the bug in 8.3 but not in 8.0 is unsurprising -- the bug's behavior isn't completely understood (it's a bug after all).  

If you have a precise step-by-step recipe for reproducing the bug that's substantially different than this one:
https://feedback.photoshop.com/photoshop_family/topics/lightroom-major-bug-with-custom-sort-order?to...

then please post it here. The posted recipe requires moving large blocks of photos within a collection or folder, repeatedly, which doesn't represent typical user behavior and thus might be prone to de-prioritization by Adobe product managers when deciding on which bugs to fix.

Votes

Translate

Translate

Report

Report
Community Beginner ,
Oct 17, 2019 Oct 17, 2019

Copy link to clipboard

Copied

I previously posted this in another Adobe forum and received no official response.

Win10 Laptop

All actions are performed on a brand new catalog with 100 images (0.jpg-99.jpg) copied from the same original image.

(same creation date)

I selected all images except the first 2. (So 2-99) I then dragged them to be between 0 and 1.

Next deselected only the first of my selected images (2) and dragged the rest between the first 2 images.
I repeated this until all images were moved. (0, 100, 99, 98, .....)

Next I repeated the above, selected all images but the first 2 and moved them between the first 2, deselected 1 image from my group each time.

Eventually I got to a gallery view of 0, 73, 72, 71, 70, ....... 1 74, 75, ..... 100 which 72->1 selected.
When I moved the group of 72->1 between 0 and 73 the ordered was invalid.

I ended up with 0, 1, 10, 11, 12, 13, ...... not what I expected (0, 72, ......)


Votes

Translate

Translate

Report

Report
Adobe Employee ,
Oct 17, 2019 Oct 17, 2019

Copy link to clipboard

Copied

@StormyTheCat,
Thanks for the reproducible steps. (The issue is reproducible.)
We are currently investigating.

Thanks,
Sunil

Votes

Translate

Translate

Report

Report
Explorer ,
Jan 09, 2020 Jan 09, 2020

Copy link to clipboard

Copied

I can tell you that I first encountered this bug in LR 9.1 (not 8.x !!).  My collection is about 290 photos, and I could no longer rearrange photos after about ONLY 10 operations.

My effective workaround is to shut down and restart LR.  That works, but it's a huge timewaster, considering the time to back up the catalog and then restart LR.

To the dev team:  How about a fix that works for a collection of say 50K images, larger than anyone is likely to have, instead of these band-aid (plaster, for our UK friends) solutions.

Votes

Translate

Translate

Report

Report
Community Beginner ,
Feb 11, 2020 Feb 11, 2020

Copy link to clipboard

Copied

Since it doesn't look we will get a fix for this, please post a workaround.  i.e.  Will something like closing down and restarting work - I don't think it will.  How about exporting the catalog and importing into a new catalog?  Will that fix the broken decimal indexes?

This has become much more critical now that Adobe has discontinued access to older version of the product that did not have this problem.  

Thanks you,
Steve

Votes

Translate

Translate

Report

Report
Explorer ,
Feb 11, 2020 Feb 11, 2020

Copy link to clipboard

Copied

@StormyTheCat

Please see my post from a month ago.  Shutting down and restarting Lightroom does work, but it's a huge timewaster.

Votes

Translate

Translate

Report

Report
Community Beginner ,
Feb 11, 2020 Feb 11, 2020

Copy link to clipboard

Copied

I did see your post.  I didn't work in the past for me.

Votes

Translate

Translate

Report

Report
Explorer ,
Feb 11, 2020 Feb 11, 2020

Copy link to clipboard

Copied

@StormyTheCat,

I solved this problem by trial and error.  At the time I encountered the problem, I didn't know that it was a long-standing issue.  If it matters, my system has 16 GB of memory.

Votes

Translate

Translate

Report

Report
Community Beginner ,
Feb 11, 2020 Feb 11, 2020

Copy link to clipboard

Copied

Ram doesn't matter. They store order indexes as floating point and renumbering enough gets to where the precision isn't enough.

Votes

Translate

Translate

Report

Report
LEGEND ,
Feb 11, 2020 Feb 11, 2020

Copy link to clipboard

Copied

"Since it doesn't look we will get a fix for this, please post a workaround.  i.e.  Will something like closing down and restarting work - I don't think it will."

Restarting won't fix the problem of too many insertions into a collection. But it may be that some other users here are experiencing another bug for which restarting helps.

 
A workaround for too many insertions into a collection was posted above:

1. Select all of the photos in the collection.
2. Do Library > Create Collection.
3. Select "Include selected photos".
4. Delete the original collection.
5. Rename the new collection to have the original's name.

Unfortunately, this workaround won't preserve any stacking in the original collection.

Votes

Translate

Translate

Report

Report
Community Beginner ,
Feb 21, 2020 Feb 21, 2020

Copy link to clipboard

Copied

What about the case where the original problem is not part of a collection?

Votes

Translate

Translate

Report

Report
LEGEND ,
Feb 21, 2020 Feb 21, 2020

Copy link to clipboard

Copied

In the case of custom order for a folder, I just tested a similar workaround, which appears to work:

1. Select all of the photos in the folder.
2. Right-click the parent folder and do Create Folder Inside.
3. Select "Include selected photos".
4. Delete the original folder.
5. Rename the new folder to have the original's name.

Votes

Translate

Translate

Report

Report
Community Beginner ,
Feb 21, 2020 Feb 21, 2020

Copy link to clipboard

Copied

What is the sort order after this set of steps?  Is the custom order retained?

Thank you

Votes

Translate

Translate

Report

Report
LEGEND ,
Feb 21, 2020 Feb 21, 2020

Copy link to clipboard

Copied

It appears to be (I haven't done extensive testing).

Votes

Translate

Translate

Report

Report
LEGEND ,
Feb 22, 2020 Feb 22, 2020

Copy link to clipboard

Copied

Has this been fixed in LR Classic 9.2? I think I've run into this issue but haven't understood that there's a bug with Custom Order. I use Shared Collections a lot and adjust what's in them occasionally so this is worrisome. I'm on LR Classic 8.4.1 still as I've learnt that every new version of Lightroom makes new bugs for old issues and better move slow.

Votes

Translate

Translate

Report

Report
LEGEND ,
Feb 22, 2020 Feb 22, 2020

Copy link to clipboard

Copied

I retested more thoroughly in LR 9.2, and it fails with collections as small as 3. To reproduce:

1. Make a new catalog with photos.
2. Create a collection with all n photos.
3. Select the collection and do View > Sort > Custom Order.
4. Select all n photos and deselect the first and second, leaving the last n - 2 selected.
5. Drag the n - 2 selected photos between the first and second photos.
6. Repeat steps 4 and 5 for m - 1 more times.
7. Note that what was the first photo is no longer first (incorrect).

Here's a table of and m values that provoke the bug:



In general, for - 1 a power of 2, m = 1 + floor (52 / log2 (n - 1)). (Intuitively, each insertion reduces the number of bits available in the 53-bit floating-point mantissa for representing the different positions.)

The values in the table column AgLibraryCollectionImage.positionInCollection specify the positions of the photos within the collection, and they should all be unique (since each photo has a different position). But after step 6, most of the values in the column are identical:



That means LR has lost track of the custom ordering.

Votes

Translate

Translate

Report

Report
LEGEND ,
Feb 23, 2020 Feb 23, 2020

Copy link to clipboard

Copied

I will be amazed if Adobe isn't able to solve this puzzle for the next bug fix update. Critical problem.

Votes

Translate

Translate

Report

Report
Community Beginner ,
Feb 23, 2020 Feb 23, 2020

Copy link to clipboard

Copied

John, thank you for the investigation. 

Is there any way to flag this to the powers to be at Adobe?  It's been affecting me since LR8 so I haven't been able to upgrade.  I've opened tickets in the past but they just sit with no action.  Even after I get feedback from Adobe that the issue is reproducible.

Votes

Translate

Translate

Report

Report
Community Beginner ,
Feb 23, 2020 Feb 23, 2020

Copy link to clipboard

Copied

Have you been able to confirm the sort order for your suggestion of moving the contents of a folder to a new folder as a workaround?

Votes

Translate

Translate

Report

Report
LEGEND ,
Feb 23, 2020 Feb 23, 2020

Copy link to clipboard

Copied

StormyTheCat said

"Is there any way to flag this to the powers to be at Adobe? "


Adobe is well aware of the ongoing issue as they have acknowledged it several times.  They have more than enough info provided in this thread, especially the detailed info provided by John Ellis, to address the issue.  Unfortunately they have chosen not to do so.  I agree that if you do a lot of custom sorts this would be very irritating issue.

Votes

Translate

Translate

Report

Report
Adobe Employee ,
Feb 24, 2020 Feb 24, 2020

Copy link to clipboard

Copied

I have added the new notes to our existing bug and brought it to the Product Manager's attention for prioritization. Thanks @john Ellis for the new repro instructions and analysis. 
Rikk Flohr - Customer Advocacy: Adobe Photography Products

Votes

Translate

Translate

Report

Report