I could not find a topic about this so..
my problem is that anytime I change the layer order or insert a layer between allready existing ones, the layer to slice routing, ie in advanced output the source for the slice, does not follow the changes made in the composition.
for example, I set a slice input to layer 3, then insert a layer below that layer 3, - layer 3 becoming layer 4, -
I have to manually change the slice input to layer 4.
with many layers this causes headache, and confusion.
layer to slice routing does not follow changes in comp
layer to slice routing does not follow changes in comp
Software developer, Sound Engineer,
Control Your show with ”Enter” - multiple Resolume servers at once - SMPTE/MTC column launch
try for free: http://programs.palffyzoltan.hu
Control Your show with ”Enter” - multiple Resolume servers at once - SMPTE/MTC column launch
try for free: http://programs.palffyzoltan.hu
Re: layer to slice routing does not follow changes in comp
I run into the same issue. I added extra layers to my current project so I didnt have to redo my TouchOSC template (each clip in Touch has a short description).
Re: layer to slice routing does not follow changes in comp
Right now the routing can only be tied to layer index, not an actual layer. This is partly because Advanced Output presets are not necessarily fixed to one composition. The main gotcha is that tie-ing a slice to a fixed layer might point a slice to a non-existent layer when switching comps.
Using indexes, when pointing a slice to an input index higher than what's actually available, it just defaults to the highest index available, which is always the comp input. It's a very safe mechanism that allowed us to add this feature as part of the 4.x release cycle, as opposed to having to shelve it till later.
We're aware of how annoying the current behaviour can be in some cases, and we'll think up something to handle this better.
Using indexes, when pointing a slice to an input index higher than what's actually available, it just defaults to the highest index available, which is always the comp input. It's a very safe mechanism that allowed us to add this feature as part of the 4.x release cycle, as opposed to having to shelve it till later.
We're aware of how annoying the current behaviour can be in some cases, and we'll think up something to handle this better.