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

Process recipes

mhsch8
I only recently came across the following problem, it may have existed in previous versions but I only detected it in COP 10.0.2 when I started to export some of my NEFs on my primary workstation (iMac with El Capitan) to Photoshop (as TIFFs) in order to transfer them into b/w and processed with SilverEfex Pro which I still prefer SEP for that particular process. After the processing in Photoshop CC I re-imported the TIFFs into my COP catalog. I did the same with some files which I processed in PSCC and which were saved as JPGs. Both file types showed up in the catalog - as expected - however, when I tried to export the NEFs, TIFFs and JPGs by using (one or multiple) of my process recipes only the NEFs were processed and new output files were created.
I tried the same on my secondary machine (a MacBook Pro with El Capitan) where I copied the content of the Capture One folder from the ~/Library/Application Support/Capture One/ directory and pasted it into the corresponding folder on the MBP. I deliberately replaced all existing files as I wanted to be sure of having identical COP settings.
When I applied the same process recipes on the very same pictures (which I also copied from my iMac into the MBP catalog) I had no problems whatsoever and everything worked fine and all the files (NEFs, TIFFs, JPGs) were processed as expected.
As a next step I deleted the complete content of the ~/Library/Application Support/Capture One/ directory on my iMac and when I started COP for the next time a set of default settings (mainly empty folders for keyboard shortcuts, etc.) was created. Unfortunately, the output recipes still didn't work. Then I tried to create output files via the "regular" export command and by manually applying the output settings, I was able to get the expected results.

Does anybody have an idea what the problem might be or experiences similar problems? Does COP store anywhere else preferences (other than ~/Library/Application Support/Capture One/) which I could / need to delete as well?

Any reply / hint is appreciated as I’m a big fan of the process recipes and use them very often (but can’t get them to work with TIFFs and JPGs).

Thanks & regards,
Mark
0

Comments

17 comments

Date Votes
  • Permanently deleted user
    Hi Mark,

    Did you check if the corresponding boxes were checked in Preferences (I mean "enable JPG editing", for instance) ?
    Cheers
    Robert

    Edit : I don't understand why you don't transfer directly your images from C1 to SEP, rather than going through Photoshop. This is what I do (very rarely, as I don't use very much SEP), and it works quite well with the C1 plug-in ("edit with....").
    0
  • mhsch8
    Hi Robert,
    thanks for replying. The point is that 2 machines using the same software (El Capitan and COP 10.0.2) behave differently: on the iMac I can't export TIFFs and JPGs via process recipes, whereas it works perfectly on a MacBook Pro.

    Regards,
    Mark
    0
  • H. Cremers
    [quote="Marco421" wrote:
    Hi Robert,
    thanks for replying. The point is that 2 machines using the same software (El Capitan and COP 10.0.2) behave differently: on the iMac I can't export TIFFs and JPGs via process recipes, whereas it works perfectly on a MacBook Pro.

    Regards,
    Mark


    I think we understand the issue you try to explain.

    However, have you checked the setting for 'Enable JPEG editing' in Preferences - Image (as tenmangu81 asked before)?

    Same for TIFF, of course.
    0
  • mhsch8
    ...yes, I did. JPEG is enabled, TIFF is enabled, PNG is enabled.
    0
  • Permanently deleted user
    But have you actually selected the output format as gif? It can happen that you change the actual output format to something else.

    It's the Tool called Process Recipe - then look in the "Basic"-tab. You'll find the Format right at the top of the toolbox.

    You can change it to whatever you like, even if the recipe is called "JPEG"
    0
  • SFA
    Some random thoughts.

    Are both machines activated as Pro level licences?

    Is there anything about the process definitions don't work that might be affected by path names (non-existent folder perhaps?) or access rights when run as batch?

    Apart from that - or any similar thoughts you might have off the back of it - I am stuck. Not being a Mac user may not help, also not using 2 machines.

    Good luck with resolving the matter.

    Grant
    0
  • mhsch8
    Hi,

    thanks for your replies / thoughts.
    I have "played" with the settings, but can't get the results on the iMac as I get on my MacBook Pro. Both are licenses are activated as Pro. I checked each and every single COP setting on both machines - absolutely identical...really frustrating ☹️

    Once again, thanks for your help anyway.

    Mark
    0
  • SFA
    Mark,

    What do you see in the Process Batch History?


    Grant
    0
  • HansB
    Some more questions.

    Any messages in CO's 'Event Log' window?
    Any messages in OS X's console?
    Any warnings/icons on the images ('Offline', question mark, exclamation mark)?


    Regards,
    Hans
    0
  • mhsch8
    Hi Hans,

    thanks for your reply / suggestion where to look. I was a few days "offline" - that's why I reply a bit late...


    Any messages in CO's 'Event Log' window?
    [color=#FF0000:rkaarnae]---> in the log it looks like everything went well, i.e. the NEFs, TIFFs and JPGs were created and exported (but in fact only the NEF based JPGs are written).[/color:rkaarnae]

    Any messages in OS X's console?
    [color=#FF0000:rkaarnae]---> couldn't find any suspicious messages...[/color:rkaarnae]

    Any warnings/icons on the images ('Offline', question mark, exclamation mark)?
    [color=#FF0000:rkaarnae]---> absolutely nothing, i.e. TIFFs and JPGs 'look' identical to the NEFs[/color:rkaarnae]

    Thanks anyway for your help,
    Mark
    0
  • SFA
    Mark,

    Seems like it has to be a variable somewhere.

    Are the output paths valid? If you select a process and it thinks it might have a problem in that respect the example output path and name will appear red.

    Is it possibly the files have been written but not where you think they are?

    Another variable would be the GPU/driver. Does it make any difference of any sort whether you have hardware acceleration set to Never (or Auto if it already set to Never.)?


    Grant
    0
  • mhsch8
    Hi Grant,

    thanks for your reply.

    Are the output paths valid? If you select a process and it thinks it might have a problem in that respect the example output path and name will appear red.
    I have TIFFS and JPGs which I processed in other programs than COP 10; they are stored in the same directory as the original NEFs and appear correctly in my COP catalog. When I export the original NEF, the TIFFs and JPGs by using the very same process recipe, only the NEF is processed and stored in the directory which is specified as output path. (if I process the very same files (NEF, TIFF and JPG) via the "Export" command and select the same settings as in the process recipe, everything goes well (apart from losing the advantage of having all the settings bundled in the recipe and makes the process much faster, efficient and consistent).

    Is it possibly the files have been written but not where you think they are?
    Doesn't seem to be logic, however, checked any possible directory, but couldn't find the output files that are not NEF-based.

    Another variable would be the GPU/driver. Does it make any difference of any sort whether you have hardware acceleration set to Never (or Auto if it already set to Never.)?
    played with the settings, but didn't have any effect on the problem.

    Regards,
    Mark
    0
  • HansB
    [quote="Marco421" wrote:
    ...
    When I export the original NEF, the TIFFs and JPGs by using the very same process recipe, only the NEF is processed and stored in the directory which is specified as output path.
    ...

    Maybe it's the difference between processing and exporting that causes some confusion?

    'Processing' doesn't create RAW files like NEF, CR2, ARW and others.
    You can process your RAWs into JPEGs, PNGs, TIFFs, DNGs and PSDs using process recipes.

    'Exporting' doesn't create JPEGs, PNGs, TiFFs, DNGs and PSDs. Therefore it doesn't use process recipes.
    You can export your original RAWs with or without adjustment sidecars.


    Regards,
    Hans


    Edit: 'Export Originals' does export original TiFFs, too.
    0
  • mhsch8
    Hans,
    the point is that since upgrading to COP 10.x machine A produces other ***output results*** than machine B, even if the versions of the used operating system (El Capitan), application software (COP 10.0.2.33) and all its parameters are identical. That confuses me!
    Maybe I wasn't that precise when I mentioned 'exporting', 'process recipes', etc. but I think you got the idea.....

    When I check this forum I'm not the only one who has problems related to TIFFs so I think PhaseOne needs do some bugfixes...

    Mark
    0
  • HansB
    Hi Mark,


    Yes, I got the idea. But the part I quoted really confused me. Therefore my post.

    I'm working with some tiff and jpeg images in CO at the moment. Some created from raws using CO, some created with other apps. Up to now I couldn't reproduce your findings. I can export the raws, tiffs and jpegs I imported and I can process them into new images.

    I was thinking about the preference settings for enabling tiff and jpeg editing for a moment. Disabled it should show a 'read only' symbol on the thumb and throw a 'read only' error message on processing. But exporting would actually work. I assume you can adjust your tiffs and jpegs in CO?


    Regards,
    Hans
    0
  • Ste-1
    Hi,

    Did you ever find a solution to this - I'm having a similar issue with TIFFs and output recipes.

    I'm running C1 Pro 10.2 (build 10.1.0.105) on a MacBook Pro and iMac, both with Sierra 10.12.5

    Basically, I'm experiencing very erratic behaviour when trying to output TIFFs to jpgs using output recipes.

    Here's the issue:
    Some (the majority) of TIFFs on both MacBook and iMac will not produce output files (jpegs). The recipe appears to run smoothly and all necessary sub-folders are created, however there're no export files. Other times I get an Event Log message saying "Can not export file". This problem occurs on both layered and flattened TIFFs

    There are also times when I have, for example, a batch of 20 TIFFs. 15 will export OK, 5 will not.

    I'm at a loss as to how to rectify this.

    Thanks,
    Stephen
    0
  • SFA
    Try clearing the process Batch history and any cache folder or temporary files that may be lying around.
    0

Post is closed for comments.