samtrak wrote:-nesting layers like AE, for grouping layers and treating them together.
You can edit multiple layers at a time with active values. Otherwise you can use the layer history.
samtrak wrote:-routing outputs to layers, like share layer texture
As we are not based on submixes but on rendering the composition to the output, this would create an infinite loop, as you would see the output in itself. Nevertheless I will add it to the list.
samtrak wrote:-currently you can only use 3 lights per layer. shouldn't there be no limit to this?>
It makes a differences if you render 3 lights after another or if these are processed at the same time, so you need to have the appropriate effect. At the moment these are limited to 3.
samtrak wrote:-layers show/hide used in sequence. each sequence shows the layers used in that sequence.
Already on the list.
samtrak wrote:-share obj texture. like share layer texture but mesh based. this may not help with load on the the system, but would be a cool shortcut.
As you said yourself, it will not save any performance, but could be a programming shortcut, yes.
samtrak wrote:-remove fx from layer(s) selection. currently you can only remove fx from one layer at a time.
Indeed, that would help.
samtrak wrote:-unhide/hide multiple or single layers from multiple servers at once
Good idea and as far as I know, already on the list.
samtrak wrote:-consistent group selection. the groups tab and groups folder react differently.
This is a known issue at the moment.
samtrak wrote:-recorder groups, views, presets like layer order
If you mean rEOrder (not recorder - this confused me for a second *g*), this would be helpful as well.
samtrak wrote:-keyframes should stick to container bounds, not get lost in limbo before or after container
I'm not sure what you mean. By shortening the length of a container, a new keyframe is processed at the end of it. The only exception is, if you manually move a keyframe to a timecode where the container does not exist, by typing in a timecode.
samtrak wrote:-share layer texture via dmx patching. other media servers that support routing offer this feature.
We decided for this feature as well as for the particle system, that there will be some limits in programming Pandoras Box via a lighting desk. Not all features do make sense or are easily programmable by external controls.
Share layer texture would need a static Folder- and File-ID including the reference which layer shall be taken. As we can have more than 256 layers (and these projects do exist) we would need to have an ID-Range with more than 8bit.
Thanks for the feedback, I will add the missing thoughts to the list.
Markus