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

Recipes with Watermarks

Permanently deleted user
Running Capture One 6 basically works very well on my laptop (WIN7 64bit). The new offerings look promising to me. I hope this will improve Phase One's position against competition as planned.

As always in new software releases some hick-up become visible as well. The most important issue at the moment for me is working with Recipes containing Watermarks. For any reason defining new recipes from scratch and using them within a current session of Capture One works fine. But after re-starting Capture One 6 recipes with watermarks are not displayed for selection any more! It does not matter whether I use watermarks as text or pictures. Recipes without watermarks still can be selected and work fine all the time. Unfortunately this is not a real workaround since it forces me to use a second application in a subsequent step.

After becoming aware of this strange behaviour I tried to work with recipes created from scratch in Capture One 6 only to avoid any interference with previous definitions from older Capture One recipes. Unfortunately it does not help at all! Phase One Support is already contacted but maybe this is a know issue to other Capture One Users as well.

Regards,
Bernhard
0

Comments

3 comments

Date Votes
  • Permanently deleted user
    After digging much deeper I like to give a little update on my issue on Recipes with Watermarks.

    Capture One re-wrtites all recipes when shuting down the application. For any reason on my computers (Win XP and Win7 with German localization) all numbers in the parameter "WatermarkColor" are written with a wrong decimal delimiter by Capture One. Not the expected decimal point (".") can be found in its entries but a decimal comma (","). You must be aware this does not happen if you prefer to use a plain black, white, red, blue or red for the text color.

    My current workaround is to edit such recipe files manually after exiting Capture One. While editing it is quite simple to get rid of some very strange looking parameter settings most likely caused by bad formating of number in the code (i.e. 0.500000009536743 is written instead of 0.5!) as well. Last step is to apply a write protection to files editied before. This prevents Capture One from writing out wrong formats to such files.

    The sweet spot for me is that now I am sure to work with my setup in the individual Recipe since no changes are written to it permanentely any more. During a Capture One session modifying settings even for such write protected Recipes is still applicable and handy to do. Maybe not everybody will agree but I like to avoid unnecessary efford for the output of pictures by starting with my basic settings instead of using some temporarily applied changes from last nights session in Capture One.

    Regards,
    Bernhard
    0
  • Drew Altdo
    Bernhard,
    Kudos on finding the workaround. If you wouldn't mind forwarding your findings through a support case I would be happy to report them to R&D to find a better long term solution.
    0
  • Permanently deleted user
    Drew,
    A support case on this issue is in place since last Friday. Yesterday I updated your Support Team with my findings and workaround. Feel free to forward all information as needed and helpful.

    Regards,
    Bernhard
    0

Post is closed for comments.