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

Corrupted preview revisited

Steinar12
Ok, just had this happen again, corrupted image in C1. On a few images.

I have a new HD for image storage, and these images were taken with my friend´s D3. Only thing in common this and last time it happened was the CF card.

C1 showed a few images as corrupted. I remembered the name of one of these images so I did a little experiment: My friend could open it in CS3 without issues on his PC when imported from the CF card. My local photography shop could do the same. I just installed CS4 and can also open it when I import it from the CF card. We all used other applications for import than C1 4 Pro.

The file imported by C1 will NOT open in ACR. But having just used windows to re-import it it displays fine in C1.

Any body else experienced something similar? ❓
0

Comments

5 comments

Date Votes
  • Christopher
    Have you tested the RAM in your machine?

    The most reliable way I know is to run Memtest86+. You can get various downloadable versions here: http://www.memtest.org/#downiso It does need full access to all the RAM so it can't be run from within an OS like Windows. I find burning the ISO from inside the ZIP file at that link is the easiest way.
    0
  • thowi
    [quote="Steinar" wrote:
    Any body else experienced something similar? ❓
    Seems to be a problem with proof profiling.... that's what I have here. Previews are terribly corrupted.
    When I start C1 4.5.1 a proof profile in ICC V4 specification (I think so) is loaded (seams to be a CMYK profile as it is one of the second list below - can't read the profile name as it is greyed out in the list).
    OR ... maybe it's always on restart as my monitor profile is in ICC V4.

    When I then set my selected output profile as proof profile the previews regenerate and everything is fine.
    So... workaround...: start C1 and set your output profile as proof profile. If the output profile is already set as proof profile (default) just set it again as proof profile.

    F**K!

    Why is there still a bug with icc profiles reported over a year ago!!!
    Is it our job to sort that basic stuff out?
    0
  • thowi
    that's how I see it on start of C1:
    http://home.arcor.de/thowidaten/fc/451_previews.jpg

    when I set my output profile as proof profile everything is fine.
    0
  • Steinar12
    Hi!

    Thanks for the replies!

    Did a memtest, half the screen turned red! 1358 errors after a few seconds! No wonder I have been having problems!

    New ram installed now. No errors at all after completed memtest.

    So it was a hardware failure after all. 😊

    Steinar
    0
  • Christopher
    Cool, glad that found the problem.

    Bad RAM is more common than most people think. I ordered 8 sticks totaling 32 gig a couple months ago, 2 of those were bad, when I got my replacements still 1 of those were bad, finally the last replacement was OK. But that's 3 out of 11 faulty.

    The bad thing was they were good enough to get the OS loaded, but some programs would hang or crash. After that I've been testing all the RAM before doing anything else with a machine.
    0

Post is closed for comments.