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

Could not load raw data

nighthawk
Hi all, just wondering if i'm doing anything wrong or is anyone else expriencing this.
I have a RAW file, which I edited in Photoshop, yielding a TIFF file.
I have 2 recipes for processing, 1 which exports a full res, high quality JPEG, the other which exports a web sized JPEG at lower quality.

If I process the TIFF file, only the web sized JPEG is produced, and an error pops up in C1Pro, saying "Could not load raw data" and Error 19 or something like that. I notice this version (10.0.2) has this exact error marked as fixed in the Mac version. But since I didn't see it in the Windows version, I'm wondering if I'm the only one experiencing it.

PS. CR2 files work just fine and produce both JPEGs as expected
0

Comments

4 comments

Date Votes
  • nighthawk
    OK I did a bit more playing around and found what causes this.
    Basically, if more than 1 Process Recipe is selected, only 1 recipe is processed, and the error comes up.
    If I only leave 1 recipe enabled when I process, it processes fine, even if I select the recipe that "failed" when 2 were enabled.

    Sounds like a bug so will open a support case
    0
  • SFA
    Based on another post that was updated in the past few hours and mentioned Error 19 ...

    .... that one seems to have been connected in some way to a related XMP file so presumably some Exif synchronisation was being applied.

    Are you also synchronising via XMP files?

    If so, as a quick experiment, it may be worth testing to see if turning off the XMP sync option eliminates the problem.

    If it does that should narrow the problem area somewhat and, hopefully, result in a faster resolution or at least suggest an easier work around for your needs if this is a task you intend to perform frequently.

    That said I would guess that running the two output processes consecutively is not going to be too onerous in this situation? In which case you may feel it's not worth the effort to chase things along. Hmm. I'm really not sure what I would do in that situation.

    I guess reporting the results (if as guessed) for the benefit of all users (hopefully via a software adjustment) might be most appropriate.


    Grant
    0
  • nighthawk
    Thanks Grant. I found the post you refer to in the 9.x folder. I turned off all XMP options in preferences and restarted CO and it processed 2 recipes just fine so thanks a lot for that.

    It is strange I never had this issue in 9.x with the XMP options set in preferences, so was quite concerned since I upgraded to v10 and lost the convenience of multiple recipes, so I'm happy to have sorted this 😊

    Nonetheless I think Phase One should fix it, seems like an obvious software bug to me.
    0
  • SFA
    [quote="nighthawk" wrote:
    Thanks Grant. I found the post you refer to in the 9.x folder. I turned off all XMP options in preferences and restarted CO and it processed 2 recipes just fine so thanks a lot for that.

    It is strange I never had this issue in 9.x with the XMP options set in preferences, so was quite concerned since I upgraded to v10 and lost the convenience of multiple recipes, so I'm happy to have sorted this 😊

    Nonetheless I think Phase One should fix it, seems like an obvious software bug to me.


    It does seem odd I agree. Especially if it is something that can occur in V9 even if you have not seen the problem when using 9.

    On the other hand it could be some odd thing deep in the pot of code sources that make up a Windows installation ...

    If you have the inclination to create a Support Case that should put the issue on the attention list - mentioning the other reported problem and referring to the forum posts may well be useful.

    I very very rarely use any external applications alongside C1 and have nothing to sync so I'm not really in useful position to make a Support Case contribution myself.

    Glad you found the cause and a way to work around the problem.


    Grant
    0

Post is closed for comments.