The ability to send/receive network commands over TCP IP. The serial node set is good for controlling equipment but is distance limited. Lots of equipment has Ethernet control for automating startup and shutdown etc. Some other software packages also offer UDP multicasting too. This would be excellent for long-term installations.

QC equivalent: 

UDP Network Broadcaster/Receiver

Component: 

Tags: 

Notes from Team Vuo

Vuo Pro: 

Yes — requires a Vuo Pro license

Complexity: 

●○○○ — Up to a few days of work

Potential: 

●○○ — Appeals to current community

The proposed nodes would allow sending and receiving bytes of data over TCP and UDP. Like the existing Send/Receive Serial Data nodes, they would have a Data input/output port, and would be used together with nodes such as Convert Data to Text / Convert Text to Data.

Comments

Perhaps I should have made

jstrecker's picture
Submitted by

Perhaps I should have made that more clear when I opened it for voting. Sorry, @bLackburst. The idea behind Pro features is that they would be particularly useful to professionals in the industry, and not so essential to hobbyists. For TCP and UDP messages, a lot of the equipment that they would be used with is professional-grade and fairly expensive. Hobbyists have the alternative of using OSC (a protocol on top of UDP) and some other protocols. So that's why this feature request is Vuo Pro.

I think what you're trying to

bLackburst's picture
Submitted by

I think what you're trying to say is that you wouldn't vote for something you're not interested in, which is good, it's what it's about . I'm talking about people who would find the feature useful but won't vote because it's been relegated to pro. It's not about me buying a pro license, I'd be happy to if the features were there, but they won't get there in the first place like this. For instance, what proportion of users are pro?.. They get the same amount of votes so the weighting isn't there, and they'd have to buy it before they can vote and wait for it to be implemented. I honestly don't see how a network command is any more "pro" than lots of other standard features like serial etc. It's just another protocol. Anyway, these kinds of conversations have kind of become systemic with vuo. The devs are smart people, I'm sure they understand their place in the market etc, they'll decide what they think is best. Just offering a second opinion.

@bLackburst

Bodysoulspirit's picture
Submitted by

@bLackburst

Yeah sorry my comment was in bad english, edited it.

I honestly don't see how a network command is any more "pro" than lots of other standard features like serial etc. It's just another protocol

Yeah it's all about the right balance to find between what is pro and what not. And as you said so yourself, I think the team is really fair regarding that.

What do you mean generally then ? That the feature requests should not inform about regular / pro implementation ? Or just in this case that TCP / UDP is standard protocol that many non pro users would use ?

The devs are smart people, I'm sure they understand their place in the market etc, they'll decide what they think is best. Just offering a second opinion.

Yeah hope you don't get me wrong, I just wanted to add my 2 penny.
The team is always welcome to hear comments, suggestions and questions like yours and discuss it I guess, so it's all good ;)

@bLackburst and

jstrecker's picture
Submitted by

@bLackburst and @Bodysoulspirit, interesting discussion, thank you.

Yeah it's all about the right balance to find between what is pro and what not.

Yeah. We try to find a good balance, and hopefully are getting better at it over time. The criteria we use to decide if a feature is Pro or non-Pro have been evolving as we learn more about how people are using Vuo and what people like and dislike about the pricing structure.

For instance, what proportion of users are pro?.. They get the same amount of votes so the weighting isn't there,

There's some weighting behind the scenes, though, because we'd try to add some Pro features into a release if the top-voted features were all non-Pro.

I honestly don't see how a network command is any more "pro" than lots of other standard features like serial etc. It's just another protocol.

Part of Team Vuo's thought process behind this is to try to guess whether the typical (median, average, whatever) project using the feature would be high-budget or low-budget. Like, how the cost of Vuo Pro would look relative to that budget. For the serial protocol, a lot of people would be interfacing Vuo with an Arduino or Raspberry Pi, and there's a large community of hobbyists using those for maker/DIY stuff that is relatively low-cost to build. For general-purpose use of TCP and UDP protocols — and I'm talking about being able to send free-form data via those protocols, not using the more structured protocols that sit on top of them like OSC — that's a less common thing to do, and many projects would involve the scenario that you brought up, @bLackburst, of interfacing with particular equipment or software packages. Although there would be exceptions, our best guess is that typical projects using this feature request would have higher budgets, and thus Vuo Pro would be more affordable than in a more maker/DIY-type project with a shoestring budget.

Anyway, I appreciate your wanting to hash this out, and maybe through discussions like this we can find ways to improve the feature requests process.

Feature status

When we (Team Vuo) plan each release, we try to implement as many of the community's top-voted feature requests as we have time for. Vote your favorite features to the top! (How do Vuo feature requests work?)

  • Submitted to vuo.org
  • Reviewed by Team Vuo
  • Open for community voting
  • Chosen to be implemented
  • Released

Votes

6 votes so far!

Who voted?

seanradio's picture
binaryburford's picture
heikopetersen's picture
bLackburst's picture