Changing Syphon Server name from list

Status: 

Vuo version: 

OS version: 

  • macOS 10.14

How severely does this bug affect you?: 

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

Steps causing the bug to occur: 

  1. Load attached Comp
  2. Use on screen + and - Buttons to change Syphon Server Name
  3. The Syphon Server doesn't turn on

Have you found a workaround?: 

If I disconnect the cable going to the Server Name input of the Send Image via Syphon node and manually enter some text instead, run the comp, and then reconnect the cable the name change works as I expected it to. I haven't found a work around for this yet, instead I created 4 separate Mac Apps each manually named by the source rather than having one app that I can change the source name in.

Compositions: 

AttachmentSize
Binary Data Change Syphon Server Name.vuo6.13 KB

Create Folder Node Bug

Status: 

Vuo version: 

OS version: 

  • macOS 10.14

Steps causing the bug to occur: 

I have another odd things happening with the make folder node. My composition is designed to create a new folder to save some CSV files in and depending on the Convocation Ceremony we are doing, a custom named folder is created. What’s weird is that when the composition starts a properly named folder is created along with a text file called MyDtata.txt that it shouldn't create containing the string (,””,””,,,),. Sometimes when I advance the composition to the next Ceremony it creates the proper folder (along with that same strange text file) but other times it instead creates a single text file with the proper name of what the folder should have been called and contains the string (,"","","Ceremony - Friday PM",,) if Ceremony – Friday PM is the Ceremony I switch to. Once the composition starts creating text files it no longer creates folders any more.

If you look at the attached screen shots of the composition "1) Ceremony Selector" feeds into "2) CSV File and Folder Creation" the text output of the first screenshot feeds the text input of the second screenshot to create and name a new folder depending on the Ceremony we are running.

Have you found a workaround?: 

Not sure yet, I can't figure out what's happening yet. Manually create the folders I need maybe instead of having the composition create them???

Compositions: 

AttachmentSize
Package icon Archive.zip1.23 KB
Package icon CSV File and Folder Creation.zip348.89 KB

Crash when testing MakeRuggedTerrain.vuo example

eseftel's picture

Status: 

Vuo version: 

OS version: 

  • macOS 10.14

How severely does this bug affect you?: 

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

Steps causing the bug to occur: 

  1. Open MakeRuggedaterrain.vuo example
  2. Edit-Protocol-Image Generator
  3. Connect Time input to MakeNoiseImage Roughness

Crash reports: 

AttachmentSize
Binary Data MakeRuggedTerrain.crash74.65 KB

Possible 'Receive Blackmagic Video' Node issue

Status: 

Vuo version: 

OS version: 

  • macOS 10.14

How severely does this bug affect you?: 

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

Steps causing the bug to occur: 

On an extremely complex composition that I can't unfortunatly post I couldn't get 2 Receive Blackmagic Video nodes using 2 Blackmagic UltraStudio Mini Recorders to work in the same composition properly. Watch link below to see an example of the issue. Each BM UltraStudio Mini Recorder has it's own address and can be used in OBS together and usually worked in a much simpler Vuo composition but has issues in the complex composition. What's even stranger is that swapping the BM node out of the receive live video node fixes the issue with nothing else changed so this has to be an issue with the BM node itself I think. Right?

I have tried to create a simpler composition showing the issue but only ran across the issue one other time. However after a reload of that project it started working properly and I wasn't able to recreate the issue on that project again.

Have you found a workaround?: 

Make sure you are using MacOS 10.14.3 or earlier. With nothing else changed I replaced one of the Receive Blackmagic Video nodes for a Receive Live Video node and this resolved the issue.

Other notes: 

Pages

Subscribe to RSS - macOS 10.14