Which devices and protocols would you like Vuo to support next?

Discussions
1

Two years ago, we ran a poll to help us understand which devices and protocols you, the Vuo community, wanted to see Vuo support.

We listened. As of Vuo 1.0, Vuo supports 13 of your top 16 requests, including OSC, MIDI, Syphon, Audio, Video, Images, Art-Net ArtDmx, Leap Motion, and Kinect — and we have more coming soon, like Serial I/O and USB HID.

So, now we'd like to know — which devices and protocols would you like Vuo to support next? Please choose your top 5. This poll will be open for 1 week.

In the list below, there are a few MIDI devices — since Vuo already supports MIDI, you can already use these devices. Vote for them if you'd like us to make all-in-one nodes that make these controllers easier to use (similar to the Behringer BCF2000 nodes we already made).

USB Video Input use USB (UVC) video cameras to feed images into Vuo
11% (1257 points)
Blackmagic use Blackmagic devices to feed images into Vuo
8% (930 points)
Oculus Rift navigate your Vuo compositions' 3D worlds
7% (802 points)
Multitouch on Apple Trackpads use multiple fingers to control Vuo compositions
6% (693 points)
Myo use Myo gestures to control Vuo compositions
5% (560 points)
SpaceNavigator use 3D mice to control Vuo compositions
4% (511 points)
Leap Motion (this was a write-in vote; Vuo already supports Leap Motion) (Write in)
4% (500 points)
Livid controllers use buttons, dials, and sliders to control Vuo compositions
4% (449 points)
Wacom tablets use tablets (including stylus attitude) to control Vuo compositions
4% (443 points)
Arduino (this was a write-in vote; support for Arduino is coming in Vuo 1.1) (Write in)
3% (409 points)
Xbox One Kinect (Kinect V2) (this was a write-in vote)
3% (358 points)
Firewire Video Input use Firewire (IIDC/DCAM) video cameras to feed images into Vuo
3% (348 points)
Heroic Robotics PixelPusher use Vuo to send images to LED strips via PixelPusher
2% (268 points)
Dataton Watchout (this was a write-in vote), I-CubeX use interactive/environmental sensors to control Vuo compositions, Bluetooth Low Energy (this was a write-in vote)
2% (250 points)
AKAI APC series use buttons, dials, and sliders to control Vuo compositions
2% (223 points)
HTTP MJPEG Video Input use network video cameras, such as Axis, to feed images into Vuo
1% (216 points)
RTSP Video Input receive network video streams in Vuo
1% (198 points)
Native Instruments controllers use buttons, dials, and sliders to control Vuo compositions
1% (178 points)
Korg Nano series use buttons, dials, and sliders to control Vuo compositions
1% (173 points)
AJA use AJA devices to feed images into Vuo
1% (158 points)
E1.31 (sACN) use sACN to control Vuo compositions, and use Vuo to control sACN devices
1% (153 points)
Phidgets use interactive/environmental sensors to control Vuo compositions
1% (133 points)
QuNeo use touch-sensitive pads to control Vuo compositions
0% (108 points)
See in comment (this was a write-in vote) (Write in)
0% (100 points)
GigE Vision Video Input use network video cameras to feed images into Vuo
0% (95 points)
CITP use CITP to control Vuo compositions, and use Vuo to send images to CITP consoles, OpenBCI use your brain to control Vuo compositions
0% (83 points)
NeuroSky MindWave use your brain to control Vuo compositions, Palette (modular controller) use buttons, dials, and sliders to control Vuo compositions
0% (70 points)
Open Pixel Control use Vuo to send images to LED strips (this was a write-in vote)
0% (66 points)
Behringer X-TOUCH series use buttons, dials, and sliders to control Vuo compositions, Google Cardboard navigate your Vuo compositions' 3D worlds
0% (58 points)
Emotiv Epoc use your brain to control Vuo compositions (this was a write-in vote) (Write in), Firewire Video Output use Vuo to generate Firewire video feeds, Magewell use Magewell devices to feed images into Vuo, Meta AR navigate your Vuo compositions' 3D worlds
0% (50 points)
Structure.io (this was a write-in vote), PrioVR use a motion tracking suit to control Vuo compositions, King's Assembly use a gaming mouse/joystick/keyboard to control Vuo compositions, DJ TechTools MIDI Fighter use buttons and dials to control Vuo compositions
0% (25 points)
DFG1394 (this was a write-in vote)
0% (20 points)
Novation ZeRO SL MkII use buttons, dials, and sliders to control Vuo compositions, viln.is one control your Vuo compositions with video-buttons, Durovis Dive navigate your Vuo compositions' 3D worlds, OSVR navigate your Vuo compositions' 3D worlds, CastAR navigate your Vuo compositions' 3D worlds, DIYVR navigate your Vuo compositions' 3D worlds
0% (0 points)
Total votes: 228
2

1 - Real time info on the patch ports like in Quartz by mouse-over or like Kineme’s feature as an overall view.

2 - Faster editor and live-coding. Scrolling the editor is laggy and receive composition frame turns the fans on on my i5 2,5 4go ram.

3 - Options export feature in a preference menu. Like Quartz alouded it for the screensaver prefs.

4 - Screensaver export feature.

5 - OS X notification bar subscribe option to retrieve all info like iTunes songs.

And so many other things that makes Vuo unusable to me so far …

  • Rss get is so slow :( 1 minute to get info where Quartz need 1 second.
  • Sort patch in library options like by name or last used
  • and so on
3

I dont’t understand why there are so many midi devices in here that can already be used with the midi nodes.

4

I totally agree. Vuo has midi support, why spend time working on multiple obscure implementations at this early stage in it’s life.

5

@monkey0815 and @digitalfx, did you see the note about that at the top of the poll? —

In the list below, there are a few MIDI devices — since Vuo already supports MIDI, you can already use these devices. Vote for them if you’d like us to make all-in-one nodes that make these controllers easier to use (similar to the Behringer BCF2000 nodes we already made).  

6

I used my write-in reply for something else and couldn’t add another one, but OSC output would be pretty crucial for me.

Specific MIDI devices are not so interesting to me. I would rather see the ability to create sub-compositions so the community could create their own implementations for specific devices.

7

Take the time to consider GigE alongside USB Video Input. USB is obviously important but GigE will be better in many ways and we need platforms to start supporting this. If Vuo takes up the GigE challenge it will put it ahead of others and in turn will encourage other developers to consider accelerating its adoption.

8

Hi, @bodysoulspirit. We appreciate that you took the time to list out some specific issues. Rather than having those issues get lost in this device/protocol poll, I split off each issue into a separate thread:

  • [#633] — I created this discussion for you.
  • [#634] — I created this discussion for you.
  • [#630] — Vuo user @ddelcourt already requested this feature.
  • [#635] — I created this feature request for you.
  • [#602] — Ah, you already submitted a feature request for this.
  • [#636] — I created this bug report for you.
  • [#637] — I created this feature request for you.

Hopefully Vuo users will vote on features you’re interested in.

By the way, this poll represents just part of what we’re currently working on. By asking the community which devices/protocols they’d like us to focus on, we’re not abandoning our work on the rest of Vuo; we’re just trying to set priorities for some of the work we’re doing.

9

Hi @Smokris,

Thank you for your answer and I apologize for the requests I could have submitted and that already are available in Vuo :(
As you took the time to answer each point separately I will take the time to answer all of them separately too in each discussion.

I am aware of the fact that Vuo is a new born software and that it will grow in the feature. I also love what you guys have done so far.
Quartz is dead for a while now, and without the efforts of Kineme and the Origami team it would have been dead for an even longer time.
You guys make miracles.
But improving a software and adding nodes to it is easier then creating a whole visual coding environment from zero. And that’s what you guys are doing. And we really put much hope in you guys, because you are the feature of visual coding.

However some points in Vuo 1.0 disappointed me. Perhaps I was hoping to much from it for a first release. Some small bugs I encountered plus the fact that I was too much used to Quartz Composer it’s UI made me closed it to fast, waiting for some next releases to try it again.

However, I’m glad to see some of your answers prove me I missed some already existing features that I will sure explore again !

Thanks Smokris,

BSS

10

@smokris Ah, no I didn’t notice that. It just looked like small print. Who reads small print ;)

That said, I took the controller options to mean what you said, so still stand by my comment. Personally, I’d rather see Vuo push forwards in other broader areas such as video input, multi-touch trackpads etc that just aren’t possible without converters right now :)

11

As you guys proved me I was wrong on some points where I tought Vuo could have disappointed me and that some of my feature requests already exists I decided to me a copy of Vuo :)

Thank you guys !

Lets start creating :)

12

I absolutely would love to see VR get involved somehow. One of the newest things I’m trying to do at my company is utilize the Oculus Rift to some extent for making intense visual experiences to sell stuff and so on. The issue has been with time as usual and being able to quickly develop environments and interaction has been key. So not only do we have to work out technical issues quickly, we also have to constantly march through what our clients want as well. Vuo comes in so handy in these situations. Nodey programming + awesome things = tons of potential. Having said that I threw in a vote for the Oculus Rift! Also threw in votes for video input and track pad. Everybody wants those. :)

13

Hey, small suggestion: combine votes for “OpenPixelController” with “Heroic Robotics PixelPusher”, as they’re actually both referring to the controlling of LED through PixelPusher

14

I would like to see an AVB (IEEE 802.1BA-2011) standards implementation for uncompressed video over network. It is fairly new, so it hasn’t been developed for a lot of applications yet. This will however be the next thing in video transmission and is backed by a wealth of large companies and organizations. From what I’ve heard, the only available implementation up to now is in healthcare video monitoring, and in some cars as a means of camera transmission. On the audio front it has started to get released in new products. It will require a new switch with support for it as it includes prioritized traffic, but this should also start to get more widespread now.