dumski's picture

Teo (@dumski)

Community Spotlight

dumski's picture
Teo commented on Teo's Discussion, “Cannot include <iostream> with vuo-compile

Thanks, Jaymie for the answer. Unfortunately, even taking example of "vuoize" stateless node (which of course compiles ok when not edited) and changing extension to .cc and including iostream causes same error:

17:48:26: Running steps for project example.stateless...
17:48:26: Configuration unchanged, skipping qmake step.
17:48:26: Starting: "/usr/bin/make" 
/Users/dumski/Qt/5.9.5/clang_64/bin/qmake -o Makefile example.stateless.pro -spec macx-clang CONFIG+=debug CONFIG+=x86_64 CONFIG+=qml_debug
../../../framework/vuo-compile --output example.stateless.vuoize.vuonode example.stateless.vuoize.cc && mkdir -p ~/Library/Application\ Support/Vuo/Modules && cp example.stateless.vuoize.vuonode ~/Library/Application\ Support/Vuo/Modules
example.stateless.vuoize.cc:11:10: fatal error: 'iostream' file not found
#include <iostream>
1 error generated.
example.stateless.vuoize.cc: error: Broken node — The node <code>example.stateless.vuoize</code> couldn't be compiled to bitcode.  Check the macOS Console for details.

make: *** [example.stateless.vuoize.vuonode] Error 1
17:48:26: The process "/usr/bin/make" exited with code 2.
Error while building/deploying project example.stateless (kit: Desktop Qt 5.9.5 clang 64bit)
When executing step "Make"
17:48:26: Elapsed time: 00:01.

Also, passing path to Xcode's iostream with --header-search-path sometimes work, but a lot of other errors appear.

I googled whole day and cannot make it compile. I read that adding -stdlib=libstdc++ flag can tell compiler explicitly to use standard C++ library, but adding this option to vuo-compile causes "unrecognized option" error. I even don't understand what is the role of vuo-compile while developing a node? Is it some kind of "host" which redirects compilation to other compiler, or it's compiler itself? Because CMake outputs only command starting vuo-compile and I wondered if vuo-compile passes a compilation somwhere else, or does some "quiet" compilation using clang/clang++?

Can you explain the process of compiling a node?

Thank you, Teo

dumski's picture
Teo posted a new Discussion, “Cannot include <iostream> with vuo-compile

Cannot include <iostream> with vuo-compile

Hi, cannot include iostream while developing a node. Do you, guys, know what may be a problem? I googled around and I see that this "iostream" is a little tricky – for example, there is no such header in newest Xcode.

I'm trying to include iostream in simple stateless node. My goal is to develop a node capturing output from system command. Look what I've found here: https://www.jeremymorgan.com/tutorials/c-programming/how-to-capture-the-...

dumski's picture
Teo posted a new Feature Request, “More tint colors needed

More tint colors needed

I think it's quite easy to implement and it will greatly help coloring compositions – for me these 10 available colors is way too little. I know everyone has own convention of coloring (like, magenta for input nodes, green for output, etc.) but especially because of this fact we need more colors.

Often I need to distinguish green window nodes but I also NEED them to remain green-ish (e.g. for many output windows). If I had, let's say, five tones of green I'd color 5 output windows and distinguish them without changing convention (that green nodes are video outputs). Same with interface nodes – five tones of magenta will allows an user to color keyboard input a little bit differently from mouse input, HIDs and so on. Look at the attached picture – IMO, the lack of colors forces an user to change conventions in the same composition.

Of course, one can have completely different coloring convention – so I think we need about 20-30 colors (4 tones of 5 colors, 5 tones of 6 colors, or something similar). And cascade, two-level tint menu with colors on the first level, and tones of this color on the second level would be perfect!

What do you think, guys?


dumski's picture
Teo commented on Philip's Feature Request, “Nodes to convert from Text to most other types

I wanted to make a new feature request for something like de-summarize node and end up here. I think it's a very useable feature since we have a bunch of TREE nodes. Now we can take various data from our compositon (like settings of calibration adjusted for a very long time) and save them as JSON file. But a lack of de-summarizing node (for points, color, numbers, text/numvers lists, etc.) forces us to decode back a tree using dozens of nodes.

For example, to put a 4 points into saveable JSON: take a look at "save-4points" image. And now, to put only first of this points into VuoPoint2d back: take a look at "read-4points" image. Imagine nodes for decoding some 4d matrices or color palette...

I think vuo-nodes-wide de-summarize function will lift whole Vuo system up and make data manipulation symmetric.

dumski's picture

Vuo prevents to choose audio devices with the same name


Vuo version: 

OS version: 

  • Mac OS 10.11

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 two same named audio devices (like ext. USB soundards)
  2. Try to choose one of them, then another.

Have you found a workaround?: 

No workaround.

Other notes: 

Vuo can choose only one of the devices. If you want to choose another with the sam name, Vuo keeps the previous one chosen.