Compositor improvements

Archive
160

Trying to summarize the thread so far.

I. Ideas:

1. Perfomance

  • Faster compositor
  • Caching system
  • Avoid unnecessary refreshs

2. Usability

  • Working with masks
    – On screen controls for widgets like transforms
    – Paint and roto as nodes
  • Working with nodes:
    – Frame node paper cuts
    – Better workflow to work with single node (e.g. isolate node then go back to full view quickly)
    – Can’t zoom out far enough

3. New nodes

  • OCIO nodes
  • Time related tools, e.g.
    – frame hold
    – frame offset
  • Pixel expression node
  • Grid/Spline warping
  • Multi-channel support for nodes (e.g. Dialate/Erode)
  • Support of arbitrary number of channels

II. Next steps:

Full-frame compositor (CPU) and real-time compositor have come a long way since this thread started. I think the next steps should be the following:

  1. Performance: Finish full-frame compositor and replace the old one (I can work on this)
  2. Usability: Revise the compositor workflow. Validate the workflow of working with masks with users using mockups or prototypes (I can also work on this)
  3. Performance: Caching system
  4. New nodes

So… what do you think? @Jeroen-Bakker any thoughts from your side on this? Especially next step 1 and 2?

14 Likes