Deploy compositions as Linux apps (including Raspberry Pi)

My problem is that I create live multimedia theater performances with live actors. My mobile MacBook Air has not enough power to drive a live performance, but I don't have money for Mac Pro... So imagine: with this feature we could build compositions on Macs, export a linux app and run it on a very powerful linux machine, which you can build especially for running Vuo compositions, eg. on a show, performance. You can build cheap machine with very good graphics, many monitor outputs and so on.

Also, don't keep your votes in a pocket! :) Cheers, Teo

If this was implemented, how far would it be from a full-fledged Linux release code wise? I can imagine a lot of the framework has to be ported for this to work?

Thanks for the explanation Jaymie! I noticed early that using QT gave the possibility for Vuo to become cross-platform eventually, so any news in that direction is greatly appreciated (Vuo is a lot of the reason I'm still mostly on a mac).

Since this is currently the #1 top-voted feature request, I want to point out that it's also one of the highest-development-time feature requests. We'd pretty much have to dedicate a release to it, and not implement any other top-voted feature requests in that release. When we (Vuo team) pick the feature requests that go into a release, votes are a very important factor, but we may pick a feature request with fewer votes over one with more if we believe it results in a combination of feature requests that has greater potential to expand the Vuo community, address the needs of the current community, and fit within a time frame of a few months.

GPIO nodes would be a separate feature request. Similar to Serial input/output, for using Arduino etc., they would enable a composition running on a Mac to communicate with a Raspberry Pi — whereas the current feature request is about making the composition run on the Raspberry Pi. Edit: GPIO nodes would enable a composition running on a Raspberry Pi to communicate with whatever's connected to the GPIO port. It would require some extra effort on top of the current feature request. The implementation time would be 1-2 dots (maybe a week or two of work).

Chris, I'm not sure. We'd at least be adding some basic support for cameras under Linux (since the current camera nodes are Mac-specific). We'd have to do some research to find out how difficult it would be to add support for camera modules / UVC webcams beyond that.

As a self identifying Apple Fanboi, this is a really hard post for me to write. Considering Apples current trajectory: soldered ssd, non existent pcie slots, this feature request may be nessesary for the future of Vuo.

I am interested in using Vuo for multiprojector setups, huge data walls, 360 etc, and currently- no matter how fantastic MacOS is, ( we all know how great and stable macos is) Apples hardware lock-in is becoming the most limiting factor.

It is impossible for me to set up a system for clients without crazy work arounds, (using old macpros which have pci slots etc ).

I believe strongly that Vuo will gain a whole new user base once it is Cross platform, and have a super exciting future!

I for one will vote for this as the number 1 priority for the next release cycle (post 1.3)

I am interested in a Linux version as well. However since much of my interest in Linux relates directly to the RPi I would actually be pretty disappointed if it wasn't supported right at the beginning.

This is important to the future of Vuo I would think. Not so much use to me for now, but expanding the commercial base of Vuo is critical to keep it developing the way we want it to.

Love the idea of cheap Linux 'rackmounts' driving installations and live performance at more reasonable cost and the idea of deployable RPi scientific and health devices for logging and processing real time physical world data. (And any kinds of sophisticated automation that can drive interesting graphical output/UI/UXs)

Air quality monitoring around industrial sites and fossil fuel extraction points with a simple user UI they can see on cheap touch screens. That's fancy UI stuff is all very hard to wrangle with Arduino/RPi today. Some kind of code bridge or binding to the hard core data aquistion and processing programs would be neat way to close this loop.

voted yes - this would be awesome. a seriously big deal (for me)- opening up huge possibilities in the world of remote kiosks and signage applications

Yes, please!

Would it be possible to get an estimate of the resources required to execute on this in a dollar value and some of us could possibly fund raise on a kickstarter type of platform for it?

I've come up with a concept I'd only be able to deploy on cheap devices like Raspberry Pi, not $1k Mac minis. I'm quite keen to see this happen from a personal perspective, but even more so for expanding the Vuo community and it's reach as any other reason. The sooner the Vuo community grows to be able to afford full-time developers working on core product features requests and UI improvements the sooner Vuo really takes off I think. It's getting close IMHO to having that ‘killer-app’ user base, even if the last decade has flown by.

Then again maybe being the highest polling feature today it's on the roadmap for 2022 already? Even If it is (almost) on the implementation roadmap, we can hurry it along with funds that would be worth it in my view. We could also set some stretch goals like the GPIO pin access bn86 asked for, and other add-ons for working with interesting 3rd party input and output devices.

I gave up on this feature request many years ago and have instead opted for using something like OSC or MQTT as a messaging bus to control something that runs natively on different platforms. As much as I would love to see Vuo expand in this direction, I have little faith in believing that this work would actually be implemented, unfortunately.

using something like OSC or MQTT as a messaging bus to control something that runs natively on different platforms

For the people who know how to create and maintain such systems, I'm sure that would work well. But I thought the target audience of Vuo was supposed to be artists and non-programmers.

I don't see Vuo as an 'artists' tool but it is accessible for people with limited coding knowledge and that's why it's worth supporting. What Matt (Matt) was describing was a common workaround for bridging platforms, sharing data and connecting apps... something a lot of artists would be interested in. Personally I use Vuo in quite a simple way to help support my VDMX projects for plugins, FX and media sources. Other people build complex applications, that's the great thing about this type of framework. I'm supporting this feature as I see it as a a way to expand my installation work and to accelerate Vuo as a viable platform for new users.

Agreed. For a non-coder like me, the idea that I can create a standalone app with Vuo in a few clicks is incredible, but many situations demand something like a pi for the project to be viable.

Maybe what I need is dedicated "show control" hardware, but I kinda wanted Vuo to be part of the solution.