As a longtime user of QC and building User Interface’s to drive QC graphical displays suitable (user friendly) for anyone to use I found QC quite cumbersome. Even with Quartz builder the replication of Input Inspector and resorting to building your own QC buttons, sliders etc was a pain and the results were unimpressive most of the time.
When I started using Mirek’s Web-socket plugin it opened a whole new world of web based Custom UIs for QC. It also allows remote operation a possibility from iOS devices etc. Great for a client of mine doing large screen twitter feeds at International sporting events. OSC is the closest current existing tool to do this but it requires using a pre-determined iOS App of some kind and often that’s just not what you want to give to your client, just not relevant. Also Websocket has packet security and I’ve had issues with OSC dropping messages in the past.
HTML/CSS/JS is so quick to build compeling UI/UX with and Vuo/QC are not so I recommend this node to Vuo users to vote for.
Make a basic HTTP server node that would send integers, reals, and text from a web browser into Vuo. With that, a user could use/create various form elements: buttons, text fields, select lists, radio buttons, checkboxes. The node or nodes would be similar to “Receive OSC Messages” and “Get Message Values.”
I don’t really mind what underlying methods are used but two-way flow of data and low-latency are usually determining factors of UI/UX success.
For my needs Mirek’s Websocket was easier to use and more powerful than Kineme’s web server and client patches. So I guess that’s where my preference is. Seeing as you already are using ZMQ library for the Vuo Editor maybe you can leverage that?
I really wanted to use the Kineme patches in preference to Websocket in QC to build my UI but in the end I had no choice. If it’s going to be like the QC patches, then I’m less than overjoyed. Maybe if I’d done IP networking 101 I could have got more out of server/client patches – dunno.
If you want more of an idea about websockets check out this video and the source code for Mirek’s QC Websocket plugin on GitHub. An XML and/or RSS feed node are some things a bit different from this request but would be useful also.
@Bodysoulspirit, WebSocket (uppercase) described on this feature request is different from the websocket (lowercase) used in Kineme NetworkTools. If you’re interested in being able to make HTTP requests to URLs (and parse the data), it would be great if you could create a separate feature request.
Would love to see native Websockets built-in. I was able to run Python Websockets with inside Vuo but ran into some issues with being able to kill the websockets port on Vuo App close. Again, websockets would be a GREAT addition for integration and controllability from other external sources. I currently have several projects that I would love to use Vuo on but can’t due to lack of Websockets communication ability. I tried hacking it with OSC but was unsuccessful with that.
when you put it like that — I’m not quite sure. Maybe I really want to control Vuo from OBS?
ok so I’m just Trying Stuff Out To See What Works. I’m using Vuo to generate live graphics which is both projected into the room and added as an OBS source for my band’s live stream, if I can ever get it working to a point I’m happy with. At the moment I’ve got DMX & Artnet controlling video generation and lights, and NDI video streams flying all over the place. Trying to integrate it all with Ableton Live so I can trigger scene/lighting/graphics changes from a single point. It’s getting there, I think?