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. ⚠️

Problem with viewer & proxies

Purzel.Paulsen
Hi,

i am new to capture one (and to the forum - so hello everyone)

i noticed some strange behavior of the viewer:
sometimes the picture displayed appears blurry and low-res.

https://thumb.ibb.co/bRFBtR/A_Viewer.jpg

zooming in 100% or 200% does not help
https://thumb.ibb.co/btMef6/B_Viewer_Zoom.jpg

for reference: the same rawfile displayed in osx-finder
https://thumb.ibb.co/cMXKf6/C_OSX_Finder.jpg

zoomed
https://thumb.ibb.co/f2oWtR/D_OSX_Finder_Zoom.jpg

To me it looks as if Capture One is only displaying the thumbnail - even in the viewer and zoomed in.

I checked, if Capture One created proxies:

https://thumb.ibb.co/gQNPDR/E_OSX_Finder_Proxy.jpg

I manually deleted the cache in order to force creation of new proxies
New proxies have been created but it did not solve my problem.

For the last 2 days I’ve played around with sessions and catalogs and workflow - the problem happened repeatedly - always to a whole set of pictures from one import. never in sessions, sometimes in catalogs.

now it happened again, when i was trying to import from Aperture into catalog.

please help!

————————-
some random info to help you helping me

27“Mac late 2013, running macOS Sierra 10.12.6 and Capture One Pro 10.2.1
in C1: preview resolution set to 2560px (changing didn’t help)
restarting Capture One did not help
restarting OSX did not help
deleting Capture One and re-installing it did not help

—————-

one additional question i stumbled across in my hunt for a solution:

Sessions store thumbnails, proxies and settings inside CaptureOne-folder (located in the respective image/raw-folder)

Catalogs do store all of this inside the catalog-file. (Therefore the additional CaptureOne-folder would not be needed after importing from session to catalog if i don’t plan to revisit the session ever)

Right?


Thanks in advance
0

Comments

7 comments

Date Votes
  • Eric Nepean
    I have not seen this recently.
    But I have noticed thet COP can be somewhat "preoccupied" after import of a large Aperture library (which I do not do anymore), and so I leave it alone until it has finished generating all previews.
    0
  • Permanently deleted user
    One thing that catches us all in the beginning is that the 'preview'/proxy file is not full-res.

    When you zoom in past the preview size, Capture One fetches the raw file and renders from there. If you are storing your images on the average hard drive, this can take 5 seconds easily. Even longer if Capture One is busy generating previews, or anything else is using that same hard drive; at the same time.

    So... Are you using an internal hard drive? External hard drive? SSD?
    0
  • Purzel.Paulsen
    I am using the internal ssd.

    Due to my problems i created test-projects (sessions, catalogs, aperture) with only 15 pics.
    I checked activity-monitor for cpu- and hdd-usage: idle.
    I even left C1 alone for one hour and went for dinner - still same problem.

    [quote="gusferlizi" wrote:
    When you zoom in past the preview size, Capture One fetches the raw file and renders from there.

    Yes. Thats what i thought too. But zooming (even at 200%) doesn't trigger the render - see my second screenshot in first post.

    one important thing to point out: it does not happen every time in catalogs and never in sessions. So i can tell the difference between normal behavior for proxies and zoom and the problem i have got.
    0
  • SFA
    Based on this not being something that always happens have you looked at the possibility that it might be system cache/temporary file related?

    I'm thinking something like the rendering process finds a file that suggests to the performance logic code that the task has already been done so re-rendering does not happen.

    I don't know how Macs manage temporary files. Would a system shut down and restart tidy up or not? Such an activity does not always seem to work for Windows but can sometimes help.

    Grant
    0
  • Purzel.Paulsen
    - restarting Capture One did not help
    - restarting OSX did not help
    - deleting Capture One and re-installing it did not help

    if the problem occurs, that particular import/project with all its images is broken - and stays that way, no matter what i try (even manually deleting proxies - which C1 happens to recreate ... without using them).

    If i delete the project with all its pictures from the catalog and try to re-import them, the problem is still there.

    Other projects/imports are not affected at all. if i switch to an other set of pictures in the same catalog, everything is working perfectly fine.

    so i am guessing the Catalog-database is somehow involved.
    0
  • Purzel.Paulsen
    🤓 🤭
    i probably found the problem

    using "|" somewhere in a folder or db-name does not necessarily cause a warning but it can mess up C1 for sure.

    head -> table (3x)

    So problem solved for now and thank you all for your help. Have a nice start to your week.
    0
  • Permanently deleted user
    Not sure how and why but happened to me now!
    0

Post is closed for comments.