pbourke's picture

Paul (@pbourke)


2 years ago
2 years ago
2 years ago
pbourke's picture
Paul commented on Paul's Feature Request, “sinks and sources

As is usually/often the way, my questions end up revealing that there are capabilities of Vuo that I am not yet aware of. Thanks, hidden cables serve as well as I was proposing. A nice touch would be if the cable was made visible if the nodes at either end are selected.

pbourke's picture
Paul posted a new Bug Report, “Crash fetching large images

Crash fetching large images


Vuo version: 

Fixed in Vuo version: 

OS version: 

  • macOS 10.13

How severely does this bug affect you?: 

●●●○ — It prevents me from completing a specific task with Vuo.

Steps causing the bug to occur: 

  1. Fetching a PNG image that is 17000 pixels wide.
  2. Choosing jpg didn't help.
  3. Simple composition and sample images attached.

Have you found a workaround?: 

No problems for a 16000 pixel wide image, I didn't narrow the search but perhaps a 2^14 issue.


Package icon Archive.zip29.29 KB
pbourke's picture
Paul commented on Paul's Discussion, “Editing text nodes

Damn, surely I tried that ... obviously not. Thanks. So that is the solution, but why is there different behaviour of text input between nodes, seems confusing.

pbourke's picture
Paul posted a new Discussion, “Management of sub-compositions

Management of sub-compositions

A question and suggestion.

How do people handle sub-composition when it comes to distributing compositions. For example, I might have a number of subcompositions I've created and use regularly, they are located in my node library. When it comes time to pass the composition I'm working on to others it is easy to miss a required subcomposition ... or just time consuming to find them and test.

Suggestion, a new save or export choice which has an "include sub compositions" option.