keithlang's picture

Right — thanks. So there probably be a slightly different behaviour when right clicking on a port — it should insert a splitter with one end connected to the port, and the other end to n number of cables. In this case, there is the scenario where multiple Split nodes will need to be automatically added, to handle the case where events and values are wired to the same port.

keithlang's picture

Hold Command modifier to drag cable from OUTPUT of node

Problem: Often I need to change a cable coming out of one node, to instead come out of a different node.

Currently, dragging from the output port of a node will always spawn a new cable.

Suggestion: Hold Command on commencement of drag should grab the existing (last added) cable end, from the END of a node.

useful design's picture

Pretty sure I requested this about five years ago! Kineme made a tool to do this and many other things for QC and I and others used the right-click "Insert splitter" functionality A LOT. Vuo compositions tend to have less cables for any given task than QC compositions, but it's obviously still a time and frustration saver to implement this. Should be a trivial add like you say, Keith. (Note you could hack the Vuo XML code the same way we used to hack the QC file XML just for fun to manually do it, maybe even script it in a software editor to be automatic).

Mostly, in the use case where you'd have a bunch of noodles coming of an output port and you want to insert a patch between the port and all the noodles…say for example round a float type to an int type…the only only way to do it without rewire every receiving patch was to "insert splitter to the output port then wire the new patches to the output port and then to the splitter which would share then new code with the existing code.

keithlang's picture

'Insert Share' option when right-clicking on Cable

This one, I hope, is super-easy, but should save a lot of work.

Problem: I find it common to need to re-wire many cables coming from a single node port. In this case, I need to manually add a share, and then re-cable every single one of them. If these cables go long 'distances' on the canvas, this can be very laborious.

Suggestion: An option that appear when right-clicking on a cable that says 'Insert Share'. This simply inserts a single Share node, at the mouse position, appropriate to the cables Type (for example, list, event, value), keeping all connections.

For bonus points: Shen a cable is selected, some information is shown about it in the info panel. This would be similar to selecting a node, which shows info on this node. For a cable, this could be data type, event throttling. This panel could also expose the same right-click functionality, including 'Insert Share'.

keithlang's picture

Error states for patches or console output or other debugging method

I just pasted some Fetch Image nodes from one composition to another. For some time I couldn't work why they weren't working… had I put them below other Layers in the window?…had I forgot to trigger to the node to launch them?…Was there a problem with the transform somehow?

The answer was that the path was no longer valid, since those resources weren't local to the new vuo file.

Proposal: some method to detect obvious errors, like attempting to load an image that doesn't exist? This might appear in the Vuo app or the Composition Loader. Or worse case, it logs out to the Mac OS console?

Images in vuo, which are a fundamental part, unfortunately have a fragile workflow because they require an event to attempt loading, throw no errors if the image is not found, and the images are not bundled with the .vuo file, so have to be carefully managed separately by the user.

keithlang's picture

Pasting in nodes does not reset scrollable area

Status: 

Vuo version: 

OS version: 

  • macOS 11

CPU architecture: 

Apple Silicon (M1/ARM64)

How severely does this bug affect you?: 

●●○○ — It's annoying but I can work around it.

Steps causing the bug to occur: 

  1. Copy a large set of connected nodes from a .vuo document
  2. Paste into a separate existing .vuo document
  3. Scrollable area is not reset; ie you cannot scroll to see those nodes

Have you found a workaround?: 

While nodes are selected, drag them slightly on the canvas

jersmi's picture
jersmi commented on jersmi's Feature Request, “Delay

Or make a feature request for audio delay :)

Audio was top of the list for this FR, probably should have been more specific!

MartinusMagneson's picture
Magneson commented on jersmi's Feature Request, “Delay

keithlang True! But then again, you are de facto quantized in any digital application. I might have a strict definition of what a delay is (repetition of a previous event), but you can't delay anything that didn't exist in the first place at a place it isn't played back.

This means that if you in any application at a 30 Hz refresh rate delay something at for instance 0.95 seconds, it will visually play back after either 0.93 or 0.96 seconds.

From a UX perspective, a frame-independent presentation of a delay would certainly be neater, but I think you can still visually achieve the same results.

If the hypothetical action at 0.95 seconds were really really important to get right, there is also an option to subtract your delay from the source time for a duplicate node of what creates the control data. As far as I know, noise nodes in the same composition are for instance not random from each other, but will produce the same results given the same time/position input. This means you can visually achieve a delay-like effect with data that isn't present in the original flow.

jersmi yup, I think the enqueue node will enqueue channels of 512 samples each if i remember it right. I'm not sure if there exists a good solution for delaying audio yet either. I think the "easiest" approach would be to write the raw data to a data buffer of some sort, and then play it back from a set position in the buffer. Or make a feature request for audio delay :)

funwithstuff's picture
funwithstuff commented on Jaymie's Discussion, “Plan for cross-platform support

Understood. My main thought here would really be for a viewer app, so that iOS devices could be used for deployment, such as in an art installation, but I’m not sure that Apple’s guidelines around “running code” could be adhered to. Agreed that distribution of apps is a pain.

Pages

Welcome!

Vuo is more than nodes and cables, it's a community! Feel free to browse or add your voice.

Browse Discussions

Start a Discussion


Browse Feature Requests

Suggest a Feature


Browse the Composition Gallery

Share a Composition


How can I get notifications?

Learn more about the community

Learn more about Vuo

Vuo Announcements

Sign up for the Vuo announcements mailing list to get news and join the community. We post about once per month.