jstrecker's picture

Jaymie (@jstrecker)

Groups

  • Vuo Founder
  • Team Vuo
jstrecker's picture
Jaymie commented on Magneson's Discussion, “Including library fails

In AsioWrapper.h, try moving #include "VuoData.h" inside the extern "C" { … }.

(The clue is that it's complaining about __Z12VuoData_makexPh, a mangled C++ symbol, instead of VuoData_make.)

jstrecker's picture
Jaymie commented on dee's Discussion, “Pro Version and exporting apps

Magneson is correct! There are some exported apps in the composition gallery if you'd like to try them: NDICast, NDI Funhouse Mirror.

jstrecker's picture

If you look at the port popover for the output of Combine Layers, you can see that the number of descendants within the layer's hierarchical structure is continually growing. Given the Cut List node, I'm guessing this isn't what you intended.

The first time Combine Layers executes, it outputs a structure consisting of a parent and a child:

x
|
x

The second time, now that it has input from Hold Value, it outputs a structure like this:

   x
 /   \
x     x
      |
      x

Each iteration after that adds another level of depth. I think instead what you want from that second execution is this:

    x
 /  |  \
x   x   x

The attached composition shows one way to do that — except I cheated and removed the Transform Layer that was in the original composition because it made things more complicated :) I imagine you can figure out how best to handle that within the context of your actual composition. If not, let me know.

All of that said — The composition shouldn't crash. My coworkers and I will discuss how to avoid crashing in the case of an unboundedly growing layer/scene object. (Can we change the nodes to prevent the problem from arising in the first place? If not, can we detect the problem and display an error message?)

jstrecker's picture
Jaymie commented on video piglet's Composition, “gibberish

Seems like the text layer node just doesn't like being hundreds of characters long.

Yep. We took some time profiles, and indeed most of the CPU time is spent rendering text. We already have it set up to cache rendered text so it will skip re-rendering the same text, but since the text is constantly changing here, that doesn't really help. Tentatively, it looks like most of the rendering time is spent in Apple's CoreText.

Fortunately, for this particular composition, you could avoid rendering large blocks of text by using Blend Image with Feedback. See attached example.

jstrecker's picture

Chris — If you create/input the switch imagery (including any animations) using layers/images, then yes.

Based on discussion with the team, we should probably revise the proposed node to something like this, to better support your use case:

Make Toggle Button Theme (Layers) — Layer input ports:

  • Off
  • Off: Hovered
  • Off: Pressed
  • On
  • On: Hovered
  • On: Pressed

To be clear, this is the highly customizable DIY solution. If you want a basic out-of-the-box switch where you don't have to provide the actual switch images, then I'd recommend creating a separate feature request.

Pages