"problem" using recipes and cooking

BECOME PART OF THE COMMUNITY - Sign up here
  • hey folks i've got a question/problem. so i have a sequence, with tracking=on. i built some cues and now i have got hard values and tracked values saved in there.

    no i am trying to manipulate the sequence using recipe lines in cues. and here comes my problem.

    let's say fixture 1 has a hard preset value "red" stored in cue 2 and "red" is tracked from cue 3 to cue 5. now i try 2 things with recipes. at first i go to cue 3 and create a recipe line , by putting fixture 1 into my selection and preset "yellow" into my value. everything works AS I WOULD EXPECT. which means, now there is preset "yellow" stored into my cue 3 for fixture 1. if i say "cook cue 3 please /remove", "yellow" gets removed and there is a tracked value of "red" in my cue 3 again. perfect, that is exactly what I EXPECTED.

    but, when i go to cue 2, where the "red" value is a hard value, and i create a recipe line where my selection is fixture 1 and the value is preset "yellow", nothing happens. the value is still "red".

    if i say "cook cue 2 /merge", NOTHING HAPPENS, the value is still "red". only if i say "cook cue 2 /overwrite" the value in cue 2 becomes "yellow", BUT when i then say "cook cue 2/remove", both values, the "yellow" value gets removed(as expected) plus the former hard value "red" gets removed too(as expected) and there is the tracked value which comes from cue 1 in there...

    so that is my problem. i do not want to have to use cook /overwrite, so that my hard values get changed by a recipe. i want to use cook /merge, so that when i cook /remove the recipe, my hard values still exist and aren't gone, because that makes absolutely no sense to me. do i get something wrong? can someone please explain? thank u in advance!

  • I'm not sure if this is documented anywhere, if not it should be. but this sounds like an order of operations thing. Stored values take precedence over recipe values (this is me guessing not a fact).


    If that is the case then it makes sense that cook /merge does nothing, it merges the cooked values but the stored values take precedence. It also explains why cook /remove does what it does,


    No idea if this will work but have you tried using cue parts or enabling Allow Duplicates?

  • Kind of the same issue on this other thread. Hope this Will Be helpfull.

  • that behaviour is absolute nonsense. when i have got a sequence, and i want to manipulate it very fast and convinient, by using recipes in cues, why the hell should manually saved data take precedence? if i always have to use overwrite so that my recipes have effect and by doing so, my original sequence gets destroyed, what exactly is the sense of recipe lines in cues then? i just want to switch my values with the values in the recipe lines and if no longer needed, have back the original values which were saved into my sequence.

  • why the hell should manually saved data take precedence?

    I'm just guessing as to the cause. Something has to take precedence though, they both can't be at the same precedence level or else the result would be "random".


    Either way for the moment, if you place the recipe in its own part might that solve the issue?

  • hoss i understand that something has to take precedence, but logically that should be the recipe, i think for at least 98 percent of users that might be their wish...

    i have to try that, using an extra cue part, thank u for the tip.

  • that behaviour is absolute nonsense. when i have got a sequence, and i want to manipulate it very fast and convinient, by using recipes in cues, why the hell should manually saved data take precedence? if i always have to use overwrite so that my recipes have effect and by doing so, my original sequence gets destroyed, what exactly is the sense of recipe lines in cues then? i just want to switch my values with the values in the recipe lines and if no longer needed, have back the original values which were saved into my sequence.

    I'm just guessing as to the cause. Something has to take precedence though, they both can't be at the same precedence level or else the result would be "random".

    The logic is that recipes are generic, while manually-stored data is specific. Specific should take precedence over generic.


    Say you have created a new empty cue, and you put a recipe in it. Data is created in the cue from the recipe as expected. Now in that cue you need a couple of those fixtures to do something else (e.g. hit someone with a special), so you give them manually-stored data. Then a little bit later on, you realize that the recipe needs to be adjusted slightly (maybe referencing a different preset, or different MAtricks information). Do you want the Special to go away? No, so you choose to Cook /Merge (or rather it chooses this option by default so that you don't lose the Special). Now things have changed slightly again, and the Special is no longer needed. So you Cook /Overwrite to reapply the entire Recipe regardless of the previous content.


    As mentioned in the other thread linked earlier, we need a 3rd option between the current Merge and Overwrite behaviors, one that will replace everything that conflicts with the recipe line but not touch information that doesn't conflict with the recipe line.