jstrecker's picture
Jaymie commented on Kewl's Discussion, “Visual data beyond Vuo "space"

Your could use Tile Layer, as in the attached example.

jstrecker's picture

So you mean all other .plist OSX files would work as well ?

Good question — I meant that Make Tree from XML would handle property lists stored as XML text, like the iTunes file. But usually macOS stores property lists in a binary format (if you try to open the file in a text editor, it's just a bunch of weird characters), so that would be a separate node, beyond the scope of this feature request.

Thanks for pointing out the existing feature request for reading iTunes playlists.

jstrecker's picture
Jaymie commented on Kewl's Discussion, “Cylindrical projection to fisheye

You could render the image onto the inside of a cylinder (Make Tube), then place a camera (Make Fisheye Camera) inside the cylinder.

Or maybe somebody's made a PBMesh file that maps from cylinder to fisheye, which you could use with Warp Image with Projection Mesh.

jstrecker's picture
Jaymie commented on Bodysoulspirit's Feature Request, “Scrollable Port Popups

Opened for voting. Thanks for the suggestion, Bodysoulspirit.

(The yellow tooltips pop up if you hover over a port whose constant value is truncated, allowing you to see the full value, such as a long URL. They also pop up for published ports.)

jstrecker's picture

Soundflower

When Soundflower is installed, Vuo sees these options:

When you pick a device from Receive Live Audio's input editor, it matches based on the device model. However, both the 2- and 64-channel Soundflower devices have the same model number, so that will always choose the 2-channel version since it's listed first.

Since the models are the same but the names are unique, you can use Make Audio Input from Name to pick the 64-channel device. Example attached (64channel.vuo).

Loopback

We installed and tested Loopback (in "true virtual mode", using audio from iTunes), and Vuo is successfully receiving audio data from it for us.

Could you post your Loopback configuration and Vuo composition? Or try with the settings we used. Here's what we tested with:

root's picture

API documentation says library file extension is optional, but it's actually required

Status: 

Fixed in Vuo version: 

Steps causing the bug to occur: 

On ARToolkit node github repository, mic reported that adding the library libAR.a to a module's dependencies as "dependencies" : [ "AR" ] doesn't work, but adding it as "dependencies" : [ "AR.a" ] does. This contradicts the documentation, which says that either should work.

For some libraries (those within Vuo.framework?), both options do work. Team Vuo should either allow both options for all libraries or fix the documentation.

Have you found a workaround?: 

Include the file extension.

jstrecker's picture

We’re actually going to be doing a poll soon to ask you / the community for your input on how Vuo’s development should be funded. We’re considering changes to how much / how often people have to pay for Vuo, to try to get a lot more people using Vuo and helping fund its development. Stay tuned :)

bLackburst's picture

Thanks Jaymie. What I was doing wrong: I was plugging the layer into the "Layers" port on the Render node, rather than individual layer number.

Pages

Welcome!

Vuo is more than nodes and cables, it's a community! Feel free to browse or add your voice.

Browse Discussions

Start a Discussion


Browse Feature Requests

Suggest a Feature


Browse the Composition Gallery

Share a Composition


How can I get notifications?

Learn more about the community

Learn more about Vuo

Vuo Announcements

Sign up for the Vuo announcements mailing list to get news and join the community. We post about once per month.