"Fetch Scene" node causes exported Mac Apps to crash on start up.

Status: 

Vuo version: 

Fixed in Vuo version: 

OS version: 

  • macOS 10.13

CPU architecture: 

Intel x86_64

How severely does this bug affect you?: 

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

Steps causing the bug to occur: 

  1. Exporting Mac App with a fetch scene node in the composition.
  2. App crashes on start up

Have you found a workaround?: 

No.

Other notes: 

This is a new problem. In the past (with previous versions of VUO) I have been able to export compositions with the 'fetch scene' node, and they would run without issue.

Thank you for looking into this.

William

Compositions: 

AttachmentSize
Package icon Scene Fetch Bug.zip14.83 MB

Crash reports: 

no distinction between rgb and rgba in naming styles

Status: 

Fixed in Vuo version: 

How severely does this bug affect you?: 

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

Steps causing the bug to occur: 

  1. search for rgb or rgba node objects
  2. most objects that deal with rgba use rgb titles

Have you found a workaround?: 

no

Other notes: 

rgb is three lanes rgba is four lanes rgb is not rgba

Crash: Make audio frame with more channels than Save Frame to Movie expects

Status: 

Vuo version: 

Fixed in 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. Make Audio frame that has (say) 5 channels
  2. Connect Make Audio Frame to Save Frames to Movie
  3. Vuo Crashes
*** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '*** -[AVAssetWriterInput initWithMediaType:outputSettings:sourceFormatHint:] AudioChannelLayout channel count does not match AVNumberOfChannelsKey channel count'
abort() called
terminating with uncaught exception of type NSException

Have you found a workaround?: 

Not sure yet

shader uniform/input port bug

Status: 

Vuo version: 

Fixed in Vuo version: 

OS version: 

  • macOS

How severely does this bug affect you?: 

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

Steps causing the bug to occur: 

  1. create new shader
  2. attempt to use input port names as uniforms
  3. shader error

Have you found a workaround?: 

Asking what the uniforms are on VUO forum.

Other notes: 

It is a bug for input ports to be created and not be able to be used as uniform variables.

tooltip behavior

Status: 

Vuo version: 

Fixed in Vuo version: 

OS version: 

  • macOS

CPU architecture: 

Intel x86_64

How severely does this bug affect you?: 

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

Steps causing the bug to occur: 

  1. create composition which uses shadertoy node in a graph that can evaluate, and run composition
  2. click in fragment shader input port
  3. fragment shader code editor appears, but tooltip with readout of entire fragment shader code also seems to always appear

Have you found a workaround?: 

I have not found a workaround.

Other notes: 

I would expect to have to "hover" above a port in order to trigger a tooltip to render. I would also expect that if a tooltip was triggered by accidentally hovering over a port, that it would disappear after briefly displaying. But even though I am not hovering the cursor, and have clicked into the port, the tooltip persistently renders. When I attempt to close the tooltip by clicking in the top left corner of the tooltip display window, it immediately spawns again.

This bug has been around for several versions of VUO, possibly as long as this node has existed. In earlier cases this bug would seem to drag down evaluation of the graph and prevent code entry. Now those side effects do not seem to occur, making it more of a nuisance level bug than a show stopper.

I have not specified that this bug is limited to the shadertoy node in the summary title, because I have not done testing to rule out other nodes.

Pages

Subscribe to RSS - Resolved