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

New Version 7.2.3 MAYDAY

NNN634487619466059669
MAYDAY, MAYDAY, MAYDAY !

Up graded to latest version 7.2.3 and now I cannot process a single file. Just get the following error:

Error processing file 00190.cr2 - Error [1 - resError]

Went back to version 7.2.2 and all was fine again. Used same settings and same file from same session.

Win 7 pro
I7 3960 Extreme
64 G ripjaws Memory
Quadro 4000 with Open CL set to auto

Anyone else having issues ❓
0

Comments

39 comments

Date Votes
  • NN138244UL
    [quote="FredBGG" wrote:

    To change the exif data you have to edit the exif data on the RAW files.
    There are exif editors that can do this in batch. They can do it very quickly.

    I use exif Editor for MAC, but you could use this:



    just change the camera parameter from ILCA-77M2 to slt-a77.

    To play it safe test this on a copy of your RAW files to check it works with whatever exif editor you use.

    You only need to change the Camera parameter in the exif data because Capture One does not take into account firmware revision of the camera so you can leave the software parameter in the exif alone.


    Thank you so much for the valuable information!
    I can finally develop the pictures taken at Shetland.
    0
  • Permanently deleted user
    [quote="NN138244UL" wrote:
    [quote="FredBGG" wrote:

    To change the exif data you have to edit the exif data on the RAW files.
    There are exif editors that can do this in batch. They can do it very quickly.

    I use exif Editor for MAC, but you could use this:



    just change the camera parameter from ILCA-77M2 to slt-a77.

    To play it safe test this on a copy of your RAW files to check it works with whatever exif editor you use.

    You only need to change the Camera parameter in the exif data because Capture One does not take into account firmware revision of the camera so you can leave the software parameter in the exif alone.


    Thank you so much for the valuable information!
    I can finally develop the pictures taken at Shetland.


    Glad to be of help!
    0
  • NN138244UL
    [quote="FredBGG" wrote:
    Glad to be of help!

    Sorry Fred, but maybe I sang victory too soon...
    I have downloaded the program you suggested, but Opanda(trial version) can't see the raw files of the 77 mark 2 ☹️
    0
  • Permanently deleted user
    [quote="NN138244UL" wrote:
    [quote="FredBGG" wrote:
    Glad to be of help!

    Sorry Fred, but maybe I sang victory too soon...
    I have downloaded the program you suggested, but Opanda(trial version) can't see the raw files of the 77 mark 2 ☹️


    I'll take a look at what I have on my windows machines on Monday... I'll let you know.
    0
  • Adam52
    Fell over 3 times this morning processing a big wedding - getting fed up with it ..... never had an issue with 7.22 ....... just locks up , sometimes with a corrupt navigator pane, only way out is to close via the task manager ..the one time the crash report widget popped up and I filled in the details so hopefully they`ll fix whatever they screwed up in the update from 7.22 to 7.23
    0
  • SFA
    [quote="Adam52" wrote:
    Fell over 3 times this morning processing a big wedding - getting fed up with it ..... never had an issue with 7.22 ....... just locks up , sometimes with a corrupt navigator pane, only way out is to close via the task manager ..the one time the crash report widget popped up and I filled in the details so hopefully they`ll fix whatever they screwed up in the update from 7.22 to 7.23


    Adam,

    The generic crash report pane is just that - a generic crash report pane submitted anonymously for statistical analysis.

    What you need is personalised support that will look at your particular problems on your machine using the full log files and other information.

    I'm running 7.2.3 with no problems that I have noticed and certainly no unexpected crashes.

    Are you using catalogs or sessions?

    The one time I did have a problem with V7 - some releases back and about a year ago - it was due to a corrupt edit file in the session or, ,possibly, a corrupt index that referenced that edit file within that session. There were about 3000 images involved so it took me a while to spot a single dodgy preview image that was the clue to the solution. It was not one I had been working on (or near) when the problems seemed to start.

    I deleted the edit (not the RAW file of course!) and the problem was fixed. I added a new edit file and the problem stayed fixed. Your problem may be different but in case it is similar scan the previews looking for any image which is evidently "bad" - chunks missing, colour distortions, that sort of thing. If you find one, delete it. (To be extra safe make sure you have a backup copy of your work on the project so far). See if that makes things more stable. If it does go back to the original image later and re-edit from the start. Make sure the preview looks OK.

    If you are using a catalogue you may need to do something similar but as I don't use catalogues I will leave it to someone else to advise the best approach.

    HTH.



    Grant
    0
  • Adam52
    That seems to ring true - it was one or two images which crashed it first and the following times when I looked at them . I managed to develop the images but when I`d done that batch , it didn`t crash again. I didn`t have any corrupt previews or anything else with 7.22 or earlier versions of C1
    0
  • SFA
    [quote="Adam52" wrote:
    That seems to ring true - it was one or two images which crashed it first and the following times when I looked at them . I managed to develop the images but when I`d done that batch , it didn`t crash again. I didn`t have any corrupt previews or anything else with 7.22 or earlier versions of C1


    Mine would crash attempting to access an image. Then it would be ok for several images before crashing again. The problem image, as sorted by name in the browser, was a loooong way from any I was working on at the time of the crash. Of course one has to think in terms of database connection rather than what one sees on the screen!

    It is the nature of database problems that the visibility of the problems may be very erratic and not very visible.

    I think my example was back in 7.1 times or maybe earlier but I very much doubt that the cause (I never did identify anything with certainty) was purely a C1 application error. I suspect it was just a file write glitch of some sort. They happen, though fortunately quite rarely.


    Grant
    0
  • Adam52
    I use this software all the time (for my job) and I`d not seen it before 7.23 , I`ve had it happen since my last post too .. it doesn't seem to do it if you wait for the image cache of all the files in the folder to build up before starting developing them and don`t do too many at once unless batched (in otherwords , doing image adjustments while its developing) ... this is the least stable revision of any version of capture one I`ve encountered (since 3.11 anyway)
    0

Post is closed for comments.