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.
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).
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:
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.
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 :)