Vuo Crash with Make Magic Visuals Installed

ecoAV's picture

Status: 

OS version: 

  • macOS 10.13

Steps causing the bug to occur: 

Hello All,

Was about to test Vuo & MMV intergration, and it keeps crashing shortly after start up. This began after installing MMV, and keeps happening even if it is closed. The only other reason I could think of is I updated my 3rd Party ISF Directory while Vuo was offline... but this doesn't sound like the reason to me. Reinstalled program with no luck either, any ideas? No error messages, was working beforehand. Specs below:

MacBook Pro (Retina, 15-inch, Mid 2014) 2.8 GHz Intel Core i7 16 GB 1600 MHz DDR3 NVIDIA GeForce GT 750M 2048 MB & Intel Iris Pro 1536 MB High Sierra 10.13.6

Vuo Community Edition

Magic Music Visuals Performer Edition

"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: 

Replace .vuonode in the Node Gallery appends a _suffix to the node, which doesn't work in Vuo

Status: 

Vuo version: 

OS version: 

  • macOS 10.13

CPU architecture: 

Intel x86_64

How severely does this bug affect you?: 

●○○○ — Not much; I'm just letting you know about it.

Steps causing the bug to occur: 

Probably not really a bug, but just wanted to know the best way to avoid that and if something could be done.

When replacing a .vuonode in the Node Gallery, one removes the old one first, and replaces it with a new version with the same name.
Even if on the node page the name is the same, the Vuo website adds a prefix at the end of the .vuonode file (for example example.vuonode_1), a name change which you only see once you've downloaded the node on your computer, but that node with an appended name then doesn't work anymore when placed in the Vuo Modules folder.

It does however still work when you change the name of a packaged .vuonode, but for simple nodes, what is the benefice of packaging it, if you don't have any specific Library Modules and the node description is coded in the file ?

Anyway, what do you guys recommend ?

  • Always pack in a packaged file (extra steps) ?
  • Hardcode a number version before compiling ? (but I liked the idea of when moving the new version in the Modules folder, it would ask to replace the old one, preventing to keep multiple versions.
  • Another workaround is to always zip the new version of the node first before uploading, but since the Vuo website allows to upload .vuonode files I was tempted to choose the faster way :)
  • Or could the Vuo Website be prevented from appending that suffix ?

Have you found a workaround?: 

Package in a set, or zip the the node before uploading.

Pages

Subscribe to RSS - macOS 10.13