OSC parames shuffled

Status: 

Vuo version: 

OS version: 

  • Mac OS 10.10

How severely does this bug affect you?: 

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

Steps causing the bug to occur: 

  1. open the patch
  2. send a OSC with 7 parameters to port 57111
  3. receive OSC with a server listening at 57112
  4. It should receive the same osc, instead parameters are shuffled

Have you found a workaround?: 

no

Screenshots: 

Compositions: 

Build List not behaving as expected when Building from another list of elements (same issue for Process List)

Status: 

Vuo version: 

OS version: 

  • Mac OS 10.10

How severely does this bug affect you?: 

●●●● — It prevents me from using Vuo at all.

Steps causing the bug to occur: 

  1. Make a simple loop to generate a list of integers [1,10] or 2D points [(1,1),(10,10)]
  2. Make a new loop to perform a simple calculation on the elements in the first list using the Get Item from List node.
  3. Make sure the second loop only has the one firing event from the first Build List node.
  4. Note the first two elements in the second list are repeated and the then the rest of the elements are not in correct place in list. 3rd element is what should be in 2nd element, 9th is what should be in 10th place. (See initial output of demo composition in illustration below)

Figure 1

  1. Now manually fire an event using the Vuo Editor either at the inputs or the output of the first Build List node (see pink arrows in Fig. 1). Now we have an even stranger output from the second Build List node, note what should be element 10 is now in the place of element 1 (Fig. 2 yellow arrow) and the rest of elements are out of place by one element (3 in 2nd place etc see Fig. 2 orange arrow):

  1. Now fire an event at using the Vuo Editor on the Fire input port of the second Build List node. (Fig. 1 "2" with green arrow) and the second Build List node output is correct. Omitting step 5 and going from step 4 to step 6 will produce the same correct result.

  1. This kind of element order and duplication anomaly happens using the Process List node also.

  2. Using a Hold List node for the first list and using various fire events to the refresh port doesn't seem make a jot of difference to this sequence of documented misbehaviors.

Have you found a workaround?: 

Unroll a loop and manually wire every single instance with copy and paste. Majorly time consuming for moderately sized lists, impossible for larger lists.

Other notes: 

This kind of unexpected behavior, and a lack of explanation in the Manual if it's a "feature", makes me extremely reluctant to rely on Vuo for real work ATM.

I've had to unroll loops and manually wire 25 instants of a series of nodes just to work around this issue. For longer lists this isn't even an option and given how slow Vuo gets with 100+ nodes on the editor and how hard it is to turn functioning nodes into an identical Sub-composition that just works (like making a QC macro just works) the node count rises quickly avoiding making loops.

Building and processing my own lists of various datatypes using fast C backed patches/nodes was the reason I first proposed a QC replacement. QC with JS just wasn't performant generating and manipulating large amounts of QC structured data … so when hearing about VUO was very excited to say the least (and supportive!).

But this fundamental task for me is not working — even so far into the Vuo development as 1.2.6 — this is frustrating.

There's not even a way to simply fire a "double event" to work around this problem that I can find. Certainly Spin Off Event(s) isn't doing it for me. The entire event paradigm while very powerful compared with QC's uniform pull paradigm is quite hard to debug and extremely hard to control at my stage of Vuo understanding. I think it needs work. Stepping through compositions frame by frame (and highlighting the event chain somehow in Editor) would be a start to easier debugging perhaps, but I feel like there needs to be a more user friendly abstraction over the top of it all for novice and intermediate users, I can't think how though yet. I tried dozens of permutations of event cables on this composition to force a second fire event on the second Build List node (without going to extreme of setting up a timer and firing again after 0.1 seconds or something). I feel like a "Make Double Event" node is required just to workaround this problem I keep colliding with in my experiments with Vuo, but how to even do it, wait for the next redraw from the screen? I'm not even using a render node in this. :-)

Rotation and Scale do not work for Make Text layer node.

Status: 

Vuo version: 

OS version: 

  • Mac OS 10.10

How severely does this bug affect you?: 

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

Steps causing the bug to occur: 

  1. Create a Make Text Layer and feed its output into a Transform Layer "layer" input.
  2. Wire Transform Layer output to a Render Layers to Window node. (For extra insurace wire Requested frame as event only wire to Transformation input.
  3. As another level of check create a Make 2D Transform node and adjust rotation and scale and wire to the TRansform input of the Transform Layer node you previously made.
  4. Run composition with either setup

Have you found a workaround?: 

Using a Make Text Image node.

Other notes: 

Apparently Make Text Layer produces crisper text, and it's not restricted in size use by the originating size like Image node. Otherwise I dont care other than it's confusing for new users.

Screenshots: 

Compositions: 

AttachmentSize
Binary Data rotate text 45º please.vuo2.55 KB

Open Recent Menu is dropping my compositions

Status: 

Vuo version: 

OS version: 

  • Mac OS 10.10

How severely does this bug affect you?: 

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

Steps causing the bug to occur: 

  1. Restart VUO
  2. See if the last few compositions you created are in the Open Recnt> submenu

Have you found a workaround?: 

Yes, just use the Open menu command and find the file.

Other notes: 

Doesn't always happen. THese files were on my root drive so it's not a removable drive issue (which does affect OS X Finder Sidebar shortcuts for example)

Inconsistent video input size

Status: 

Vuo version: 

OS version: 

  • Mac OS 10.10

How severely does this bug affect you?: 

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

Steps causing the bug to occur: 

  1. connect a Magewell USB capture HDMI gen 2 with a HDMI camera plugged into
  2. open the attached patch
  3. check "received frame" output pin: Size says 1980 x 1200
  4. Open Quicktime player
  5. Start new movie recording
  6. check again "received frame" output pin: Size says 1980 x 1080

Other notes: 

I0d expect it to be 1920 x 1080 at start

Screenshots: 

Compositions: 

AttachmentSize
Binary Data C920->Syphon.vuo2.76 KB

Pages

Subscribe to RSS - Mac OS 10.10