jstrecker's picture

Jaymie (@jstrecker)


  • Vuo Founder
  • Team Vuo
jstrecker's picture
Jaymie commented on Paul's Bug Report, “Serial communications

Yep, I see how that could be confusing. To clarify which part of the text is actually the name, we could add labels to the port popover. So in your example, the List Serial Devices popover would instead show:

Name: Keyspan, a division of InnoSys Inc. Keyspan USA-19H
URL: /dev/cu.serial-10002808D

We'll make that change in an upcoming release.

jstrecker's picture
Jaymie commented on Magneson's Node Set, “MM.Points

The newer version of the node set doesn't have the example compositions for some reason. Here are the example compositions from the older version: MM.Points_examples.zip

Having those compositions won't fix the broken links to examples in Vuo, but you can open them just as normal compositions.

In case you're interested, here's how we extracted the example compositions from the older version:

  • Download the "MM.Points July 2020" version. Just leave it in your Downloads folder; don't install it in Vuo.
  • Rename the file from MM.Points_0.vuonode to MM.Points_0.zip.
  • Double-click on the file to unzip it.
  • In the unzipped folder, find the examples in the examples folder.

The same process should work for any node set that contains examples.

jstrecker's picture
Jaymie commented on loddie's Discussion, “Video time delay
  1. Should the Black Magic IP4K video card appear as a device in Black Magic nodes? It seems it should, but I don't want to report a bug until I understand.

Yes, it should — the vuo.blackmagic documentation lists Intensity as one of the supported product lines.

I'd suggest creating a simple test composition that just contains a List Blackmagic Devices node. When you run the composition, is your IP4K listed in either the Input Devices or Output Devices from the node? If you go to Tools > Show Console, do you see any errors, warnings, or other messages about Blackmagic?

It is a bit surprising that Vuo detects your IP4K as a native video device. Do you by any chance have a DAL driver installed in /Library/CoreMediaIO/Plug-Ins/DAL ? If so, try moving it out of that folder, restarting your computer, and running your composition again.

  1. How does the attached composition need to be edited to provide video delay?

The structure of the composition looks OK based on the composition you got working with non-Blackmagic video. Presumably you'll want to replace the Receive Live Video with Receive Blackmagic Video once we figure out the problem with your device.

jstrecker's picture
Jaymie commented on Paul's Discussion, “Load scene (OBJ), textures and wrap modes

To change from wrapping (the default) to clamping, you'll need to pass each texture through Change Wrap Mode. Since the textures are loaded along with the .obj by Fetch Scene, that means reloading the textures from the image files, changing their wrap modes, and re-applying them to the scene object. The attached composition demonstrates.

jstrecker's picture

In our experience, likely causes of a "run out of application memory" error after running an application for a while are:

  • The application is using more and more memory (a memory leak) until it exhausts the available RAM / virtual memory.
  • The system startup disk is full. (macOS stores the swap files for virtual memory there.)

The second cause is easier to check. In Finder, locate the volume for your startup disk (under Go > Computer), click on it, and see how much Finder says is available in the bottom bar of the window. If there's less than about 10 GB, free up some space, then reboot and see if the problem still occurs.

If that doesn't fix it, then you can check if Vuo, the Syphon client, or another application is using more and more memory over time. In Applications > Utilities > Activity Monitor, select the Memory tab and View > All Processes, and make sure the table is sorted from highest to lowest memory usage. Since you're diagnosing a fairly slow leak, I'd suggest taking a screenshot of Activity Monitor at the beginning and another after a few hours to see how they compare.

If you find that the problem is caused by Vuo, please let us know. To debug it, we'd need more information (such as providing the composition and the video files) so that we can reproduce the problem. We'd run the composition with Apple's Instruments to locate the code that is leaking memory.