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

Error: Error Output Processing File, Set Source ???

Comments

12 comments

  • NNN634487619466059669
    Having the same problem with TIFF files. Support is working it. Just wondered if you ever got the problem resolved and how? I also never had this problem with ver 6.
    0
  • Drew Altdo
    Anyone else having this issue please crate a support case.
    We would very much like to determine the cause of this.
    0
  • sankos
    I'll take the risk of asking something obvious: have you set the folder where you want to output the conversion to ["Output to" option]? Make sure it points to an existing folder on your drive. I've no idea what else might be the cause of the error (i.e. it could be a bug).
    0
  • MikeSp
    [quote="sankos" wrote:
    I'll take the risk of asking something obvious: have you set the folder where you want to output the conversion to ["Output to" option]? Make sure it points to an existing folder on your drive. I've no idea what else might be the cause of the error (i.e. it could be a bug).


    That was obvious and I tried it to no avail, but when I rebooted my computer again (3rd time after loading CS6), C1 started sending files to CS6 as it should and now is working with CS6 -- have no idea of what happened to change things.

    I DO WISH that Phase One would create a downloadable manual like they have for previous versions of C1-Pro -- while I hate reading manuals for fun, they can be very valuable as reference material.

    MikeSp
    0
  • NNN634487619466059669
    This “SET SOURCE†error has some different meaning other than where the output file is going. Just need the Code writer to help with that. I finally did get C1.7 to put a processed RAW files in the session output folder though.

    But ! if I import a 16 bit TIFF file into the session (which has been worked from a RAW file in PhotoMatix Pro and exported as the 16 bit TIFF) the first thing that is suspicious is there is no preview of the file in the import window. Just a blank window and the file name. When I select the file anyway to import it into the current session with other RAW files, the Tiff file then appears properly in the filmstrip.

    Once I select the Tiff file and make the adjustments and try to process it using the same session recipe , it starts then stops with the error processing file set source. Funny thing is, once this error happens, I can no longer process any RAW files in that session with out the same error.

    C1 6.4.4 cranked these same files without a problem. So I was surprised that when I upgraded to version 7 the flow ended. The machine does use a dual graphics system with the Nvidia Optimus technology, but it never caused a problem with C16. And I have set Capture One to use the Nvidia Graphics only.

    Phase One support has been DILIGENTLY helping me with this issue. I am very happy so far with their support and don’t mind the teething pains with ver 7. I have seen others having the same problem and was hoping to discover a commonality that might help resolve this problem.
    0
  • NNN634487619466059669
    Update. I think I figured out what may have caused this problem for me. I had done a session on a USB drive. Then I switched to saving sessions to the local drive. Thats when the problems started with this SET SOURCE error. In the maze of trouble shooting, trying to figure out what was wrong I just happen to check the output folder in the Library tab for the new session I was working on. It showed the output directory as G:/user/pictures/output/session, when the session and output recipe was set to local C:/user/pictures/ouput/session.

    I have no idea how C1 7 came up with the G: drive as the output source since the new session and recipe were all set to local C: I saved all the finished work and deleted every C1 file and session folder I could find. Rebooted and created a new session. Loaded the same job that was giving the errors. Verified that the output folder directory under Library tab was the same as output recipe and hit process. I was a happy chap. I have been fighting this error for weeks with help from support but was unable to make much headway. I have no idea why C17 would load the USB drive directory ( which was no longer connected) for every session I had created. Even though the new directories were established. Not sure how I really fixed it,but having a session in drive G: then later the same session now in drive E: because it is now in diffrent priority or not there at all may cause C1 to get confused.
    0
  • Drew Altdo
    If any other users are seeing this I would ask that you create a support case so we can get details.
    So far we have 6 users that have reported this. We are looking for a common connection between them so we can address it in the software as it does seem to be a bug, but what is causing it is still unknown.
    0
  • Drew Altdo
    Still hoping more than 7 people out there can give us some insight into this error.
    If you see this please provide us with;

    System Profile-
    http://www.phaseone.com/Search/Article. ... nguageid=1
    Log Files-
    http://www.phaseone.com/Search/Article. ... nguageid=1

    So far the only thing we have found is that creating a new session avoids this but that is, of course, not a proper solution. Just a workaround for the time being.
    0
  • phillip murphy
    i seem to have same problem -

    working with tif files - cannot process or export...

    using version 7....

    giving up for the day...
    0
  • phillip murphy
    rebooted - relaunched app (i did relaunch few times)

    did not change anything - my 3 images still in window...

    process is fine -

    i am thinking a script somewhere in the app, may have a memory leak...

    p.
    0
  • Drew Altdo
    Any chance for a support case with the requested info???
    0
  • NNN634553644001436208
    Hi,

    I think this problem is fixed on 7.0.1.
    I experienced the same problem on CO 7 and opened a support case with the information above, then upgraded to 7.0.1 and did the same test then finally the error dialogs disappear.

    Thanks
    0

Post is closed for comments.