pbourke's picture

Paul (@pbourke)


3 months ago
4 months ago
4 months ago
pbourke's picture
@pbourke posted a new Bug Report, “Crash fetching large images

Crash fetching large images


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

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
@pbourke 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.

pbourke's picture
@pbourke posted a new Feature Request, “sinks and sources

sinks and sources

An observation ... when creating compositions I find clear layout is crucial. I find myself clumping functional units together, eg: IO section, display section and so on. Then occasionally one want to connect one part with a distant other part which often involves connections passing under nodes and immediately seems to make things messy, especially when the source or destination cannot be seen on the screen at once. This confusion also arises from links connections from the right to the left in a composition, eg: those pesky window request frame connections.

What I think would be "nice" would be a node that acts as a "sink" for data+events and another node that acts as a "source". These would be associated together by an id, or better a name. They could of course be colour coded ... seems to me this could be used to add clarity to larger compositions.

pbourke's picture
@pbourke posted a new Question, “Editing text nodes

Is there a way around the following, or a good explanation why it is this way ....

The GLSL shader has a "text" input which one can enter text, sure not a full editor but one can manage/choose to use that or something external. BUT, nodes like "Append texts" while it also has a "text" input does not allow the same editing, for example I cannot use the return key to create a new line.