For university AV teams
We are looking for university AV teams to build a real space on OpenAVC and tell us how it goes. Selected universities get the hardware and the support to do it.
It runs OpenAVC directly, so the same device is the control processor and the touch interface. One network cable does data and power. Nothing else goes in the rack, and the panel stays with you when the pilot is over.
Questions, troubleshooting, and a second set of eyes on how you have the space laid out. You are talking to the person who builds the platform.
If something in your space has no driver yet, we write it. Getting your equipment supported is part of the program, not something you wait in line for.
You add the devices, design the panel, and write the macros. This is your control system, not one we hand you finished.
Tell us what works and what gets in your way. OpenAVC is pre-v1, so what you run into has a real effect on what gets built next.
We would like to hear how it went once the space is running, with the possibility of a case study if you are up for it.
OpenAVC is open source. The drivers we write for your equipment and the fixes that come out of your feedback ship to everyone running the platform, not just to your space.
Tell us about it and we will take it from there.
Start an applicationQuestions first? Email info@openavc.com or join the Discord.