Skip to main content

⚠️ Please note that this topic or post has been archived. The information contained here may no longer be accurate or up-to-date. ⚠️

CO1 15.3 Image browser jumping when checking/unchecking filters

Christiaan mak

As reported in a support request. This bug was also present, and reported, in the beta's:

"When I have an image selected in the viewer, the image browser will be positioned with the correct thumbnail (marked with a border) in view in the fimstrip.

BUT... when I check a filter, such as star rating, the fimstrip "jumps" to a seemingly arbitrary thumbnail image position anywhere in the current collection of images, and I will have to manually scroll all the way back or forward through the collection to arrive at the proper thumbnail again.

This behavior happens with EVERY action of checking/unchecking a filter."

 

0

Comments

4 comments

Date Votes
  • Boris Tomsic

    I agree this is annoying, but until the problem is resolved, to make life a little easier for you, when this happens, click on image in the Viewer then press Up or Down arrow key (you may need to have the mouse cursor in Pan or Select mode (north-west pointing diagonal arrow), A lot quicker and easier than scrolling thru 1000's of images

    0
  • Christiaan mak
    • Edited

    I grab the handle to the right of the filmstrip, which does something similar as using the arrow keys. But in a collection of 1300 images, it then races through, so in the end to get to the right image, it still takes a fair amount of scrolling.

    My post is intended to update CO1 15.3 users on this issue, in the hope they will open a support case, because if only one person opens a support case, they initially assume faulty use or some rare/obscure system configuration. It was this way with the big v15.0 viewer bug as well, where arbitrary strings of images were selected in the viewer whenever closing > opening CO1, which you had to de-select all the time. I reported this at the time of the first beta, and at all subsequent betas, but it still made it into the final release and took multiple support cases from different users to get it fixed in v15.1

    0
  • Giovanni Gori

    same here, with capture one 21 and 22. Very very annoying

     

    0
  • Christiaan mak

    @Giovanni: If you have not already, it would be beneficial to open a support case. There is already a number of users known to the CO1 team that have this issue and reported it, but the way it goes, is that they will only prioritize a fix when the number of reports gets high enough. As it now stands, this issue has not been fixed in the current CO1 v23 beta.

    0

Post is closed for comments.