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

Preview image flashing and corrupted

petharnz
Hello.

OSX 10.8.2 and C1 Pro 7.02. Editing D800E NEFs.

Loaded C1 to do some editing and the preview of the highlighted thumbnail started to flash "on and off" continuously. Sometimes the preview image became distorted with colours totally messed up.

Tested images in other folders to find some folders "near" the initial one showed same problem.

I turned the hardware acceleration off and also rebooted but no improvement. Re-installed programme but no change.

Eventually I deleted the associated CaptureOne folder and allowed the previews etc to regenerate.

This resolved the problem but editing steps were of course lost.

Anyone else experience this? Cause?

This is the first time the problem has occured.

Thanks

Peter
0

Comments

17 comments

Date Votes
  • Paul Steunebrink
    Peter, you can delete the previews without deleting the adjustments you made, so no work gets lost.
    0
  • petharnz
    [quote="Paul_Steunebrink" wrote:
    Peter, you can delete the previews without deleting the adjustments you made, so no work gets lost.


    Thanks Paul.

    How do you do that?

    Any idea what caused the problem?

    Regards
    0
  • petharnz
    Re-generating previews doesn't resolve the fault. In fact it appears to be worsening.

    The focus screen is also faulty.

    Image displays (except thumbnails) are flashing at about 1 per 0.5 to 1 sec. Images blank (white), colours messed up or normal. Frames for images within left column of screen are sometimes misplaced.

    Reverting to 7.0.1 does not resolve the problem.

    Unfortunately C One is becoming unusable.

    The plot thickens!

    Anyone recommend a complete clean uninstall and re-installing?

    Cheers

    PS Further experimentation confirms that deleting the CaptureOne folder almost always fixes the fault.
    0
  • rap_digital
    I just had that problem swell with some D800e files. Cant say what exactly fixed it but I turned Canon off in the providers list (unlikely to be the fix), I turned OpenCL to Auto for both preview and processing (Mac BookPro quad i7, AMD Radeon HD 6750M), and changed the preview image size to 1680px (normally my standard but this laptop isn't a shoot comp' so for some reason was set to the default).

    I restarted to make these prefs stick and all was good. Hope it helps.
    0
  • petharnz
    [quote="rap_digital" wrote:
    I just had that problem swell with some D800e files. Cant say what exactly fixed it but I turned Canon off in the providers list (unlikely to be the fix), I turned OpenCL to Auto for both preview and processing (Mac BookPro quad i7, AMD Radeon HD 6750M), and changed the preview image size to 1680px (normally my standard but this laptop isn't a shoot comp' so for some reason was set to the default).

    I restarted to make these prefs stick and all was good. Hope it helps.


    Thanks for conveying your experience Rick.

    The preview image size seems a hopeful lead. For some reason mine is set at 2560.I have never changed it. My display is 1920x1200 if that makes a difference.

    Will try it and restore some of my "CaptureOne" folders from two weeks ago.

    Peter
    0
  • SFA
    Peter,

    I don't have V7 so this is a long shot related to something I have seen a couple of times on a PC with a monitor that is scaleable to fill the available screen realestate (and happens to have touch control capability as well.)

    I got some very odd results, sometimes including events similar to those that you describe, after a series of events that happened to include an update for the nvidia driver system used by the graphics card.

    Somewhere along the line the settings file was changed to a value that the scaling software could not deal with and I could not work out how to reset things. In the end, being a PC, I deleted the drivers and re-installed.. There had been about 4 updates in 6 weeks so I was a bit suspicious anyway!

    That gave me back the control I needed.

    V7 has, as I understand it, a larger default preview setting (2560) in order to attemtp to same rendering time in editing sessions and so on. Severl comments in the tutorial videos, blogs and in some posts in this forum. You can change that to something else if you wish. It might be interesting to see if doing so makes any sort fo difference at all.

    Whilst this certainly sounds like a system installation related problem (not everyone has it!) pinning these things down in the current era of IT development does appear to be quite challenging quite often.


    Grant Perkins
    0
  • petharnz
    Thanks Grant.

    I have tried changing preview size and unfortunately it didn't make a difference.

    It seems that the folders of images where the fault is occurring are roughly grouped time-wise around the middle of last year.

    Now, recently I had a hard disk error that was detected and repaired by the Mac OS X Disk utility. I wonder if that is related to the C One error.

    Back to the symptoms: For one image the fault shows with the original but not with the variant!

    Peter
    0
  • SFA
    Peter,

    Pity there was no result for you there but I guess with these odd things there is no harm in trying.

    Have you run a verification process on the problematic session(s)/catalogues?

    I can't find a reference to it in the User Guide but Paul has mentioned it a few times in other posts and from what you said I sound like the sort of routine that might at least tell you if it finds problems and where they are.

    Grant Perkins
    0
  • petharnz
    [quote="SFA" wrote:
    Peter,

    Pity there was no result for you there but I guess with these odd things there is no harm in trying.

    Have you run a verification process on the problematic session(s)/catalogues?

    I can't find a reference to it in the User Guide but Paul has mentioned it a few times in other posts and from what you said I sound like the sort of routine that might at least tell you if it finds problems and where they are.

    Grant Perkins


    Thanks for your continuing help Grant.

    My whole set of photographs is under one default session (I'm a Nikon Capture NX2 user) . At your suggestion I ran the "Verify Catalog or Session".

    No faults were found.

    Current approach to get things operational:
    For the affected folders I check for adjusted images that aren't affected and pack them. Then I exit C1 and delete the related "CaptureOne" folder. Run C1 again check that every image is stable then unpack the previously packed "stable" images. At this point it seems to be then only solution.

    And so it goes on!

    Peter
    0
  • andrew waller
    I had this very issue with d800e file last month...

    my solution is to confirm that you are using the capture 7 processing engine, in the colour toot tab their usually is a "base characteristics" tool it has the ICC profile of the camera and curve you are using an da third line "engine" after I switched to C1 7.0.2 from 6 I had the choice to use the 6 engine or the 7 using the 6 resulted in a constantly flashing on and off in the viewer...fixed by switching to the 7 engine

    hope this helps, it drove me crazy for a day or so
    0
  • petharnz
    [quote="Andrew13" wrote:
    I had this very issue with d800e file last month...

    my solution is to confirm that you are using the capture 7 processing engine, in the colour toot tab their usually is a "base characteristics" tool it has the ICC profile of the camera and curve you are using an da third line "engine" after I switched to C1 7.0.2 from 6 I had the choice to use the 6 engine or the 7 using the 6 resulted in a constantly flashing on and off in the viewer...fixed by switching to the 7 engine

    hope this helps, it drove me crazy for a day or so


    Thanks Andrew. That is an interesting observation.

    I had a cursory check and it seems that all problem folders were of photos loaded prior to my installing C1 v7.0.0 and therefore many likely to have been edited using C1 v6. Those images I subsequently worked on were converted to the v7 engine.

    Interestingly the flashing preview and colour corruption was only noticed after updating to v7.0.2. That is, v7.0.0 and 7.0.1 seemed fine.

    Peter
    0
  • petharnz
    Update: have found an earlier folder with a combination of v6 and v7 Engine images. All images are stable (so far) during browsing.
    0
  • andrew waller
    interesting I as well did not have any issues with 7.0.0 or 7.0.1 it only started when I updated to 7.0.2...it over all seems a little buggy.... I still enjoy 7 new work flow but am worried about any continuing quirks...I'm keeping a close eye on it.
    0
  • Francesco de Robertis
    I have the same problems could someone help me?
    0
  • Francesco de Robertis
    It really seems that problems occurred only with D800E files because with my old A900's files, processed with CO v. 6.4.4. there are no problems.....
    0
  • andrew waller
    that may very well be true my IIQ file have none of theses issues, however I have recently had processing problems with my IDS file....yes I have a lot of cameras... it seems the camera profiles are having issues with capture 7.0.2. I'm hopping its just growing pains that will be fixed with the next update, please may it come soon !
    0
  • Francesco de Robertis
    I solve the problem (the support solve the problem!):

    ""This is a known issue with files from D800E rendered in 6 engne settings. Back up your images and settings first. Then, to fix the images, select all, then upgrade the engine in the base characteristics tool to Capture One 7 Engine"".

    i try and now all is ok!!
    Thanks
    0

Post is closed for comments.

Didn't find what you were looking for?

New post