jersmi's picture

This has to be a FR somewhere, part of many discussions, but I couldn't find the focused idea, so here. I did see the keyframe FR, but this one is more basic, also purposely less complex than the QC timeline with multiple timelines and all that. Most basic graph module that allows a user to add points to it, normalized/mapped to [0,1] along x and y axes. Personally, I'd be fine with linear interpolation and no spline handles. And leave the graph exposed in the editor. The only "extra power" feature that might be cool to consider is ability to group multiple into a subcomp/single GUI. Or not -- something, anything!

Side note: I live in the SF Bay Area. I know a coder who worked at Pixar, talking about a huge breakthrough for animation at the time -- it was this idea -- a simple spline graph animators could use to quickly animate/articulate characters.

Screenshots, Mockups, and Videos: 


Notes from Team Vuo

Vuo Pro: 

No — available with both Vuo CE and Vuo Pro


●●○○ — A few weeks of work


●○○ — Appeals to current community


To clarify, are you wanting a

jstrecker's picture
Submitted by
Feature status:
Waiting for review by Team Vuo
Waiting for more information from reporter

To clarify, are you wanting a spline (curvy path) or linear interpolation (straight-lines path, like in your mockup)?

In either case, how about a node that's similar to Curve, but instead of selecting an easing curve, you draw control points for your own curve? The node could have an input port called Keyframes with an input editor that looks basically like the image you posted. You double-click on the Keyframes port, it pops up this input editor where you can add and remove dots and drag them to reshape the curve. Like Curve, the node would have inputs for time and duration. The node's output would be a number: the position on the curve based on the time and duration.

If that meets your approval, we'll open this feature request for voting.

One option until this is implemented, or for more complex timelines, would be to send timeline data to Vuo using Vezér.

With the lerp graph I was

jersmi's picture
Submitted by

Cool, Jaymie. With the lerp graph I was suggesting the most pared down approach. Of course splines with handles are nice, but for 99.9% of actual use cases, "close enough" curves are fine, just add more points.

And yep -- adding/deleting/moving control points in a graph view is the heart of the matter. (Probably single mouse click on the current line to add, double click a point to delete, click/drag a point to move. Adjacent points create boundaries on the x-axis -- drag a point up to the prev/next on the x-axis, dragged point stops. If a lerp graph, a precision feature to (key cmd +) click on a point to input numerical x/y position might be good (for future release)).

If keeping it in the current Vuo style is important to Team Vuo then sure, adapt Curve parameters. But those things could also be controlled through the time port using existing tools. I'm suggesting a "lite" approach -- time port and a (0,1) x (0,1) lerp graph. Then calculate range, offset, etc. after the graph. If the graph view could be included in a subcomp then forget all extra features cuz we could make our own. All this "simplicity" of course does not consider conserving computer resources, that is on Team Vuo. :)

Vezér is indeed this concept on steroids. This FR is more about maximizing productivity + creative possibilities within one environment with no bells and whistles. I'm sure Vezér works great, but I see this tool more as a primary building block.

Hmm, that strikes me as a

George_Toledo's picture
Submitted by

Hmm, that strikes me as a very good point about focusing on the different needs of visuals. I don’t mean for my mention of DAW automation implementations to distract from the original post either, it was a thought that came from reading subsection posts.

And I think your initial intuition about spline/curve type functionality is well needed for many visual animation contexts.

I think mentioning DAW

jersmi's picture
Submitted by

I think mentioning DAW automation is on the money.

Well, my intuition says that Vuo is missing some basic tools, so I'd vote for the simplest, most direct approach, then a more developed tool later -- after Team Vuo sees how immediately useful and popular it is. :-)

Feature status

  • Submitted to
  • Reviewed by Team Vuo
  • Open for community voting
  • Chosen to be implemented
  • Released

When we (Team Vuo) plan each release, we try to implement as many of the community's top-voted feature requests as we have time for.

If anyone would like to help this happen sooner, we're also accepting open source contributions and commissioned work.

Read more about how Vuo feature requests work.