MartinusMagneson's picture

Magneson (@MartinusMagneson)

Compositions

MartinusMagneson's picture

I guess this is a case of: "Make OSC Output" = Broadcast - This will make Vuo spit out OSC data to all connected interfaces and IP ranges they are set to (usually a terrible idea, but useful in some limited cases). "Specify OSC IP Output"= Unicast - This will make Vuo spit out OSC data to a specific IP (most likely connected via a specific interface within the specified range).

Can't you also disable the offending network (wifi) from receiving OSC messages in VDMX?

MartinusMagneson's picture

Mailed it over yesterday, did you get it?

MartinusMagneson's picture

Subcomp crashes editor when publishing ports

Status: 

Vuo version: 

Fixed in Vuo version: 

OS version: 

  • macOS 10.14

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 subcomp from nodes in editor without published ports
  2. With both main and subcomp open, publish a port (3d?)
  3. Change name
  4. Crash

Have you found a workaround?: 

No

Other notes: 

Vuo build 10830

Console output:

default 13:48:07.375457 +0200   Vuo                                    redo():122   martinusMagneson.spiroTimebase.vuo:      Publish input port 'Speed'
default 13:48:07.459618 +0200   Vuo            compileModulesFromSourceCode():1520  Compiling martinusMagneson.spiroTimebase
default 13:48:07.495491 +0200   Vuo                   loadModulesAndSources():3064  Removed from composition-local environment: martinusMagneson.spiroTimebase
default 13:48:07.502136 +0200   Vuo                   loadModulesAndSources():3122  Loaded into composition-local environment: martinusMagneson.spiroTimebase

I can mail over the full crash log if needed.

MartinusMagneson's picture

Shouldn't be too hard, I would imagine something like this would work; if (item1 - item2) < [item1 AND threshold], do something.

MartinusMagneson's picture

If you want to make it more complicated though, you could use an enqueue node set to two items, get them, and compare them as the boolean operation. Then you would have a directional threshold ;)

Pages