I think I posted this a long time ago. Flame still doesn’t completely lock a sequence from alteration.
Whenever using Batch, I always have it automatically return the clip to the sequence I’m working on.
If I’ve got a locked sequence and re render a Batch that is also in that same sequence, it will replace it. Not something I would expect from a locked sequence.
@Hengy - Sometimes an openclip versioning workflow is better than this render-replace workflow. Painful news. Change is hard and all that.
Does locking a Sequence also lock the open clip shot, preventing any updating?
You can enable or disable the replace function for open clips.
I always use replace, so I would guess it would have the same issue.
well, not really - with ‘managed media’ the replace function is very useful, but openclip segments are versionable in your timeline anyway - this was all functioning well before ‘replace’ was a thing.
let’s say that I publish my shots sequence; i open one of the shot batch groups, my initial write node is set to replace so when i create my first render the open clip version gets updated on the timeline.
now i disable replace.
i render version 1 or version 2 (depending on whether i start at v000 - ugh - alien concept!!!)
now my timeline has the capability to version that segment up - but it doesn’t happen automatically.
moreover, if i use the option to update my version, a bold white outline appears around the new segment indicating there has been a change and this UI element will not go away until i explicitly perform a review.
i can show you if you want - but it won’t be by recording a video and posting it - i have my own struggles these days with other activities.
I think there was a way of working where you could leave a sequence in a library and then enable a pref to lock the libraries.
i never ever used that.
protection mode or something?