メインコンテンツへスキップ

⚠️ 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 "not enabled"

コメント

11件のコメント

  • Paul Steunebrink
    Not sure whether this is the same situation, but I have tried to reproduce it. The text message I get is:
    "The selected recipe will not be used for processing because it is not enabled." Cancel/Continue.

    When I continue, the image will be processed by the enabled recipe, which is not the selected recipe, hence the message.

    After a check I noticed that the selected recipe is not enabled (checkbox set) and the enabled recipe was not selected. I could not reproduce unintended change of the recipe (restarting CO Pro 6, changing sessions).

    CO Pro 6.3.3 / OS X 10.7.2
    0
  • Permanently deleted user
    Thanks for the reply, Paul.

    So, I suppose my confusion comes from having not had the desired recipe both highlighted AND checked (enabled).

    I still encounter the output folder changing in each recipe. It seems to remember the last destination output folder I set in the most recent recipe I created and applies that as the default destination across all recipes.

    Is this the way the software is supposed to function? Shouldn't the original output folder be specific to each recipe and stay the same?
    0
  • Paul Steunebrink
    [quote="NNN634593484503991018" wrote:
    So, I suppose my confusion comes from having not had the desired recipe both highlighted AND checked (enabled).

    That is correct. It is basically what the message says. CO6 includes the output profile of the SELECTED recipe into the display of the image of the viewer. When the ENABLED recipe is different from the SELECTED, you process to something which may be different from what you are looking at. Hence, the warning.
    [quote="NNN634593484503991018" wrote:
    I still encounter the output folder changing in each recipe. It seems to remember the last destination output folder I set in the most recent recipe I created and applies that as the default destination across all recipes.

    Is this the way the software is supposed to function? Shouldn't the original output folder be specific to each recipe and stay the same?

    Key here is how you configure the output folder: the Output folder or a specific folder. I suspect the first, but you'd better use the latter. Check this:

    Select a process recipe in the Process Recipes tool. In the Process Recipe (singular) tool below, open the Advanced tab. In Root Folder, which might show Output Folder, open the drop-down list, choose Select Folder and select your folder for that recipe. Repeat the process for each recipe.
    Now each recipe will have its own output folder independent from any previously used recipe or session. In case you have multiple recipes enabled during processing each output file will be saved in the recipe's respective locations.
    0
  • NN634685736257195808UL
    Wrong, wrong, wrong. I am having the same issue... I get the message saying the recipe is not enabled even when the recipe is selected AND checked. C1 will not allow me to "enable" the recipe (I click and nothing happens). If this is not a bug then it is bad development. Why do we need to "enable" a process recipe in the first place? This seems redundant.
    0
  • Paul Steunebrink
    [quote="NN634685736257195808UL" wrote:
    ...
    Why do we need to "enable" a process recipe in the first place? This seems redundant.

    This may seem redundant but...

    The image you look at in the main viewer takes the properties of the selected profile into account as CO6 is a fully color managed application. This can only be one profile at a time, obviously. By default this is the profile of the selected process recipe although the proof profile feature allows you to select a different profile (temporarily).

    In the Process Recipes tool can contain many different recipes. You can select one or more recipes for processing. As a result the situation can occur that you have selected a different profile (for viewing) than the recipe(s) selected (or processing). Let's say it is an enhanced feature. Fortunately, when this happens and you start processing, CO6 informs you of the fact that you are processing to a result that may differ from what you are looking at.
    0
  • mlflix
    I just had the same thing happen, which has oddly happened before.
    I hit + in Process Recipe and then it works.
    0
  • Alan Shortall
    I'm confused about the "Recipes".
    For example, I have a recipe to make 600 pixel jpegs (sRGB, output to a specific folder, etc) but If I need an 800 pixel jpeg and I just go in to the 600px recipe and change it to 800 px, it doesn't automatically change back the next time I open C1.
    I was assuming that even if I made a change, the original recipe would remain (there's no dialog box that comes up asking if I want to save the changes to the recipe)?
    Am I missing something here?

    Alan.
    0
  • Paul Steunebrink
    [quote="Alan5" wrote:
    I'm confused about the "Recipes".
    For example, I have a recipe to make 600 pixel jpegs (sRGB, output to a specific folder, etc) but If I need an 800 pixel jpeg and I just go in to the 600px recipe and change it to 800 px, it doesn't automatically change back the next time I open C1.
    I was assuming that even if I made a change, the original recipe would remain (there's no dialog box that comes up asking if I want to save the changes to the recipe)?
    Am I missing something here?

    Create an additional recipe with different settings, i.e. one for 600px, one for 800px.
    0
  • Alan Shortall
    Seems odd that the "recipe" isn't actually "saved" anywhere, as it means that, to be sure, you always have to look thru all the setting and paramaters in a recipe, in case they have been accidentally changed by someone else using the computer.....?
    Alan.
    0
  • Paul Steunebrink
    It is saved in the user's Application Support folder; one file for each recipe. By the way, are you on CO Pro or Express?
    0
  • Alan Shortall
    I'm using C1 Pro (6.3.2)

    Alan.
    0

投稿コメントは受け付けていません。