Navigating between images slow
Hi all,
I've a mac Mini M1 with 16GB Ram and when moving between images, I get a blurred image for 0.5 to 3 seconds before it shows clear and correctly. If I then change and go back to same image, same again. I'm sure it used to cache these. It is like it makes previews every time. I've checked and my previews are set to the same as my max width of display. I tried changing my mac to a lower screen res, and it was faster, but still does it.
Also tried on C1 22, but just the same.
Is this normal? Any ideas?
Thanks,
Steve
-
This is not normal behavior. You could toggle the hardware acceleration on/off in Preferences. Please let us know whether this makes any difference.
0 -
Thanks Paul.
No difference I can see with it on or off. I do see that some images are instant and some take a second or two. I see a spinning ball at the top of the preview and when that stops the image is high res. If I wait for the wheel to stop I can then go back and forward between images and it stay hi res, but only for about a minute. If I flick back and forward all is good. If I then go back 2 mins later, back to waiting again.
0 -
Sorry, should have added. Regenerate previews make no difference.
0 -
I have this exact same problem. Thought it was just early M1 support, but at this point it is a deal breaker as it is very frustrating to switch between images.
0 -
Give C1 the chance to see that many users are impacted by reporting this as a bug via "submit a request", if you didn't already.
0 -
More information. This only happens when the app is sized a certain size. If you open the app full screen on a 4K monitor it’ll do this. If you size down the app to about half the size of the screen it no longer happens.
0 -
Once again this speed issue seems to be related in some way to the 4k (and 5K) screens. That means there is a lot of detailed data to manipulate for every image. Either because the preview size is relatively large to start with (and remember that C1 tries to pre-load memory in preparation for an anticipated editing session) or because, sometimes, the preview file size is NOT very large and is deemed to need recalculating (rather than just upscaling) in order to present a full quality view based on all of the data available.
Electing to use a smaller Preview file size may not help that much if the preview then needs to be recalculated anyway. If a very large Preview file size is selected it may be necessary to downsize it considerably to "fit" the available screen real estate unless working at Full screen mode.
I would imagine working with 2 monitors of different resolutions could be a complete mess.
These factors are mentioned in the Release Notes which suggest a specification well above the basic specifications will be desirable for 4k and 5k screens.
Whether there is any possibility of finding ways to enhance the results without resorting to "Instant" on-screen processing based on fewer pixels and then quietly updating behind the scenes as work continues I don't know. Possibly not in C1's architecture but others may be using such techniques to make responsiveness appear faster to the human eye's interpretation of screen re-writing.
0 -
I don’t think I know any modern photo editor that takes 4-5 seconds to display image A. Then when you move to image B and go back to image A you have to wait 4-5 seconds again.
Non M1 Capture One didn’t do it. And neither should this.
0 -
Agreed. Therefore:
https://support.captureone.com/hc/en-us/requests/new
0 -
Matthew,
How much memory did you have in your previous system? Were you already using the 4k monitor?
0 -
I was previously on a 32GB Intel Mac mini on this 4K monitor. Then moved to a 16GB M1 Mac Mini.
I do still have a 16GB 2019 MBP I could install Capture One on for comparison purposes though. I could plug it into this 4K monitor.
0 -
Hey - has anyone any idea how to fix the issue described in the original post? I am having the exact same issue with my Mac mini M1 and 5K display.
0 -
I am now on a Mac Studio 32GB M1 Max and it is much better. So its definitely an optimization / speed problem past a certain resolution.
0
Post ist für Kommentare geschlossen.
Kommentare
13 Kommentare