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

Every image is blurry

Arjen Klaver
I recently switch to CO from LR. Everything was nice, but after my latest import a huge bug appeared: ALL images became blurry/pixellated. (also all the previous images)

example:
http://www.klaver.co.uk/blurryasfk.jpg

I have a workaround that works for a minute or so.
- quit CO
- delete the cache
- start CO, everything is good, images are sharp and I can make alterations to them, great
- a few minute in, suddenly every change to the image will only update the thumbnail. When selecting any other image, everything becomes blurry again.

So what to do?
0

Comments

11 comments

Date Votes
  • Arjen Klaver
    okay tried some stuff:
    - new catalyst drivers: no effect
    - disabled opengl: no effect (enabled them again)
    - tested memory: no errors found
    - exporting to jpg gives sharp images, so it is a UI problem.
    0
  • Paul Steunebrink
    I have no clue. I would verify the catalog (File menu > Check Document). Check your preview size (Preferences). The default is high, bring it back to your monitor pixels (for example 1920 px). Next, select all images and regenerate previews. Restart CO7. Make sure you run CO 7.2.2.

    If that does not help, open a support case.
    http://www.phaseone.com/SupportMain.aspx
    0
  • Tan68
    I had this trouble as well.
    I don't recall how it resolved...
    But, it went away...

    It could have been resolved by updating C1; I haven't seen this trouble in a several months.
    I know I don't regenerate previews.. I didn't think of that as a thing to try. So updating might do then regenerate if not.. ?

    As you have noted, none of my images were damaged.
    0
  • Glenn101
    Before you update again do a clean uninstall as discribed here;

    http://www.phaseone.com/Search/Article. ... nguageid=1

    It solved a few minor problems I was having.
    0
  • Arjen Klaver
    When I verified the catalog I found an error: 'database content error, database check failed'. Repairing led to a 'no fix for: invalid layer relationships' and 'repair failed'. So that might be the cause. Maybe after it hits this problem in the database. it just stops processing any images and just uses the thumbnails.

    Removing everything and then reinstalling newest version just downloaded didn't help.

    Regeneration previews didn't help. Changing resolution didn't help.

    Tomorrow I'll open a support ticket, and then see what happens.
    0
  • Tan68
    My brief time with this behavior was with sessions.
    No catalog in use. Hadn't even ever started one.

    Good luck.
    0
  • Drew Altdo
    If an image isn't rendering it means that the "Image Core" isn't working.
    This is the same bit that process' images and creates previews. If that has stopped in the background, or is perhaps not working on this specific file, there will be a specific cause.
    We see this with Corrupt RAW files or Permissions restricted files.

    If you Zoom in 100% and the error persists, then their is no simple fix.
    The next step is for you to determine if it is this File alone or all files in the Catalog?
    0
  • Arjen Klaver
    With the support people the problem was found. A raw file was corrupted. When C1 sees this file it just crashes image core. It is only annoying that C1 doesn't notify the user when this happened and or try to recover image core while ignoring the broken file.
    0
  • SFA
    [quote="Arjen" wrote:
    With the support people the problem was found. A raw file was corrupted. When C1 sees this file it just crashes image core. It is only annoying that C1 doesn't notify the user when this happened and or try to recover image core while ignoring the broken file.


    True that is annoying. However one wonders whether there is a processing overhead to be suffered if every file was checked on every read. Especially since this ought to be a very rare occurrence.

    Perhaps the guidance about how to make best use of the "Check and Rebuild" tools available (Current and future tools) could be adapted to give clearer guidance and recommendations about how to proceed after faults have been assessed and error found?


    Grant
    0
  • sizzlingbadger
    [quote="SFA" wrote:

    True that is is annoying. However one wonders whether there is a processing overhead to be suffered if every file was checked on every read. Especially since this ought to be a very rare occurrence.
    Grant


    Bottom line is the image core process should handle corrupted raws without crashing 😉
    0
  • SFA
    [quote="sizzlingbadger" wrote:
    [quote="SFA" wrote:

    True that is is annoying. However one wonders whether there is a processing overhead to be suffered if every file was checked on every read. Especially since this ought to be a very rare occurrence.
    Grant


    Bottom line is the image core process should handle corrupted raws without crashing 😉


    Sort of depends on whether you can pre-guess every possible form of corruption and code for it accordingly. And do so without a processing overhead that users might feel was wasteful 99.9999% of times.

    In a perfect world there would be no file corruption ...



    😉


    Grant
    0

Post is closed for comments.