Has Anyone encountered a problem with the break function? I tried it out and it released some fixtures instead. Strangely it was limited to one fixture type, Robe Esprit, and not to any other fixture types.
I don’t know if it is a bug or if I did something wrong, so I would like some feedback from you fellows in MA land before I report it. 
There are certainly some circumstances where doing something before a break would result in release values after the break. I think we would need more information before saying whether what you saw was expected or not. In which case you might as well send the info to your distributor and ask whether what's happening in that specific show file is expected.
Thanks for your quick reply, Ryan. Do you have an exemple of such a circumstace? I need to try to recreate this problem again to find some kind of pattern. I didn’t have a lot of time and needed to do damage control. The manual clearly say ”The existing tracking values are not released but are protected from future changes”.
What I’m looking for is if any other user has run into situations were the break does not behave as expected.
Adding new fixtures or attributes to a cue before a break that did not already exist in the sequence would result in Release values for those fixtures / attributes after the break.
Are we considering that correct expected behavior?
Because it does kind of make sense.
Yes, that was an example of a time where it would be expected for a Break to result in Release values.
I see. That makes sense. But that wasn’t the situation in this case. I had data already stored throughout the sequence and suddenly there was release values where I didn’t expect it to be.
However, it very well might be a misstake on my part. That’s why I don’t want to jump to conclusions to early. I’ll investigate some more🙂
Don’t have an account yet? Register yourself now and be a part of our community!
