Hi,
I think jrxc and Joris are RIGHT!
For the sake of this discussion, let's define an new feature:
Clip Pools (aka "Pool")
- Generic Container: A pool is a generic container of clips.
- Target Layer: A pool can be assigned a Target Layer. When a clip from the pool is triggered, it will be played on the Target Layer.
- Layer Removal: If a Layer is removed, then a Pool that had the removed Layer as it's target layer, would now become target: none. But the pool will still exist.
- Layer Reordering: reordering layers has no affect on the Pool.
- UI - Separate Window: A pool can be displayed in a separate window. It has arbitrary columns and rows. It has pages.
(Yes! We could finally efficiently use an external touch monitor for triggering clips)
- UI - Drag & Drop: A Clip can be dragged from a pool and dropped in any arbitrary Layer.
For example, a clip of a shape, can be used as a shape to be disaplyed or as a mask in a Mask-Layer.
The current Clip Pools
Now, if we look at the behaviour of Arena now, a Layer's clip row, could be our Pool, and the decks could be pages of the pool.
For example, if we have 2 layers, Layer-1 and Layer2.
and 2 Pools assigned to Layer-1 and Layer-2 respectively.
Then switching to Deck-2, show us page-2 of Pool-1 and Pool-2.
Apart from the "broken" behaviour described in this discussion, we have our Pool feature.
My brain stopped working
Zoltan, how do you suggest we continue this discussion?
I think it's a rather serious one for Resolume.