jstrecker's picture

Jaymie (@jstrecker)


  • Vuo Founder
  • Team Vuo
jstrecker's picture

Thanks for reporting this problem, Philip. We'll investigate.

jstrecker's picture

Thanks, Bodysoulspirit, for pointing to some relevant feature requests. I'll add some more for the record...

Number 3, I see what you are saying, I guess I meant more in terms of in the rendered window using "mouse drags on Layers". I have a bunch of layers that represent items in a process list. and I'd like to reorder the process list based on actully dragging the layers in an app GUI, not the editor.

seanradio, do you mean like Position/orient 3D objects by using the mouse on the rendered output but for layers? Were you thinking of moving nodes just in 2D space (x,y) or also reordering which one is on top of which (z)? (For the latter, perhaps a view like https://github.com/chinmaygarde/hierarchydetective that shows the layers in 3D space?)

recording OSC or any other live data input parameters to a file, so it could be played back later.

Node that records data to a text file and plays it back (chosen to be implemented)

Number 6. if node library defaulted to the search field when opened might make more efficient, since if selecting a node you have to click regardless,. why click on search tab?

Cmd-Enter already puts keyboard focus on the search field when you open the Node Library. Or am I missing something?

Export as App, published ports as input parameters in apps. I know this has been discussed and split off to multiple feature requests, not sure where it stands right now.

A UI for storing and editing published input port values (open for voting)

Network Tools, more options for sending data over IP/UDP/TCP/unicast/multicast etc, like QC Network utilities ( i know this is a feature request as well I believe, just throwing it out there.)

Send and receive data via TCP and UDP (open for voting)

seanradio, I know you said you weren't necessarily thinking of feature requests, but I'd encourage you anyway to vote on the feature requests that you consider most important (I see you've already voted on a few), because votes are the number one way for Team Vuo to gauge community interest in a feature request.

Anything you'd like to say about why these particular feature requests are the top ones for you? For example, what kinds of projects are you typically making in Vuo, or what is your workflow?

jstrecker's picture

You're not live coding, are you? (Reduce the pause during live-coding reloads)

I'd look at trying to make the composition as efficient as possible. Particularly, minimizing the overlap between event streams in the audio and graphics parts of the composition. If there are a bunch of nodes that get executed with every audio event and every video event, maybe they only need to be executed by the video event.

Perhaps building up a replica of the composition from the very basics would help. If you just have Fire on Start -> Play Audio File -> Send Live Audio, the audio plays smoothly, right? As you add in the visualization piece by piece, at what point does the audio start falling behind?

If you still have questions, could you post the composition (or a reduced version of it that exhibits the problem)?

jstrecker's picture

That is the intended behavior, for now. When you run a subcomposition or a protocol composition, every event into any published input port goes through all published input ports.

However, since that behavior has been a source of confusion for many people, we're planning to change it in Vuo 1.3.

Changed -> Hold Value works, or you could do it with a single node, Allow Changes.

jstrecker's picture

Philip, that's an interesting idea. To avoid expanding the current feature request beyond its complexity of 1 dot / up to a few days of work, I've created a separate feature request covering items 1 and 2: Ability to collapse other nodes besides type converters.

For item 3, I think a good way to accomplish that would be with the separate feature request plus Ability to create composition-local subcompositions. You could group the nodes into a subcomposition and give it a meaningful name, which would be displayed when you collapse the subcomposition node.