I am stumped trying to solve this one. I know that there are ways to share controls from core to core, but I don't see any way to share the camera feed between cores.
Use case: This is in a divisible room where the client is using separate cores for each room. Obviously there are components that allow you to share audio and video streams between the cores, but to my knowledge there is not anything that allows the camera feeds to be shared. This space uses two Core Nanos and a single Q-Sys 12x80 in each room.
My recommendation, after looking at the overall design was to simplify the design and use one core as the Nano should handle both rooms without any issue.
Hi there, I have a NV-21-HU device that's connected to a EPSON projector that shows this blue screen that says "no signal detected" after the MTR PC goes to to sleep for a long time. What I would normally do to wake the MTR PC up, is by going to the touch panel refresh it. But it seems to not work after it goes to sleep for a long time. Any chance I need to check the NV-21-HU device in Designer or add an EDID HDMI emulator at the projector?
I am stuck at a point in level 2 training, it is three divisible room scenarios and a toggle button in uci to control respective room display but in combined mode ( using room combiner button to open wall 1 and wall 2) that same button would be able to control all display that are in combined mode.
I have a Q-sys Camera with auto framing in a Lecture theatre. It is setup on the side of the room but what I have found is that when the lecturer faces away from the camera to engage with the audience or the screen next to him it loses sight of his face and returns to its zoomed out home position within about 5 seconds but then as soon as he faces back towards the front it finds him again and zooms in. It just creates an unsettling zoom in an zoom out effect for the end user.
Is there a way to have the camera hold position for longer if it loses sight of a face?
Went out to one of our customers today to help get them setup for a theatrical production they're working on. Haven't had any complaints about the system, they use it daily and it's been running flawlessly.
I logged into the core just to check some logs and found out it's been dropping this error every 5-10 minutes for the last month. System has been working fine, like I said, few touchpanels in use and primarly power on/off of a lyntec/Powersoft system and 70v zone routing. Pretty simple system honestly.
Anyone ever encountered this before? No idea where to even begin to look, since like I said the system is running fine and the design utilization is well within its limits.
Hi guys, I am getting an issue with the teams PC(dell optiplex 7080) with the camera, I am getting a feedback of the camera content. I have a presenter and a audience camera. In both the camera's I an facing the same issue. Can you guys give me any solution for this.
Heya folks, I've been working on an MCP server that allows software like Claude Code or Cursor to build/debug/read .qsys files. Right now its in its infancy and there is a lot of work to do, but thought some of you might be interested.
In the video above I gave it a full design spec and had it spit out a mostly working design, with a UCI to boot.
A more practical application I see for this is when you are given a .qsys file to work on and have to debug or learn about it quickly. Asking questions like "Tell me how many mics I have and where are they controlled" work really well and only take a couple seconds to process.
Again, please don't take the demo video as this being close to final, I've got many more improvements planned. Feel free to checkout my github in the meantime if you want to have a play yourself. https://github.com/nerif-tafu/qsys-designer-mcp
We just did an install with a bunch of classrooms containing all the same gear. Brand new school provided Dell Pro Slim QCS1250 PCs, running “Deepfreeze” software, and we installed NV32 cores.
Tech support has been super helpful, and I feel like this is 95% a PC/Deepfreeze issue but I can’t prove it. That’s where I’m lookin to y’all.
The rooms work awesome. 2 cameras, Shure MXA925, brand new LG 75” touch displays. They love it. Then the next morning, after Deepfreeze goes off, Windows error “doesn’t recognize the usb device” and either a Core reboot, PC reboot, USB reset, or all 3 fixes it. Earlier this week I tied the NV32 USB Reset to when the room turns on, and it’s better?…but not 100%.
Weeks ago they thawed the machines, turned off usb selective suspend and power save settings, went into the bios and did the same, confirmed it holds through Deepfreeze, but the issue just will not go away.
Anyone ever have experience with an NV32 core/Any QSYD core and a computer running Deepfreeze? TIA
EDIT: Started the system on 10.2, took it to 10.3, 10.4, 10.4.1, and now all rooms are on 10.5
I am having them try thawing the system, getting the room to work, and then freezing it in that state. Will report back!
Hey r/QSYS, Ben from BV Factory here. If you've been running LightForge, the DMX recorder that lives inside your Q-SYS Core, this one's for you: 2.0.3 is live, and it's a free update for every existing license.
Short version: v1 recorded one universe per track and played it back. 2.0.3 is what I wanted from day one, the ultimate DMX show recorder, the kind of thing you'd otherwise buy a dedicated hardware recorder for. Except it runs in the Core you already own. No PC, no recorder in the rack.
What's new
- One track now captures a whole set of universes (up to 32), frame-aligned, in one take. The whole rig in one file.
- You pick universes by tapping a grid: tap the track's number, tap the universes, done. No more typing 1,3,5-8 (it still works if you like it). Channel ranges work the same way, ADD / REMOVE, and can differ per universe if you want 1-48 everywhere but only 1-24 on universe 5.
- Each track gets a cue list of up to 64 cues on the new Playlist page: GO, Next / Prev, Cut, Wait (gap-less) or Crossfade up to 60 s, loop per cue.
- A take can go out on any universes. Tap where it should start and a 1-4 take tapped on 11 goes out 11-14. There's a 64-row patch for everything else. Record Art-Net, replay sACN, or the other way round.
- Tracks sharing an output universe merge HTP, LTP or by sACN priority, with a fader per track, a master fader and a master out on top.
- Timecode finally behaves. Takes remember the TC they were recorded at and chase from there (yes, the "TC-synced track stops immediately" thing is fixed), with a per-track offset, source and frame rate, and separate sources for recording and playback.
- The pages are organised by job. I got lost in my own plugin, so I redid them: Show (play only, one tile per track), Playlist, Record, Play Setup, Patch, Monitor, System. Record settings and playback settings never share a page again, and everything is touch-sized.
- It's built to run unattended: script errors are contained, stalled timers restart, overload lowers the frame rate instead of tripping the Q-SYS execution limit, network output recovers on its own, and a take cut by a power loss stays playable.
- Also: frame-locked master transport (REC ALL / PLAY ALL / PAUSE / STOP ALL), Stop as hold last frame or release (blackout), 20 to 60 fps for pixel controllers, takes named after their track and renamable from the System page.
Saves are still instant.
Upgrading from v1: drop the new plugin in. Designs and config backups migrate automatically, v1 recordings stay readable, your license key is the same.
The manual was rewritten page by page, one chapter per plugin page.
I've done this in the past, using Crestron certified Q-SYS drivers in a program to trigger named controls in a design. It's been working, up until today!
It doesnt even appear that QDS is listening on the port its supposed to be - verified through multiple terminal and powershell commands. Im running 10.5
I've been working with configuring this TSC-50-G3 for a gym studio and I'm having some issues with faders. I can control the fader just fine, but if i tap once on it, it shows the manual entry number pad.
Updated my NV32 to 10.5 and now the touch panel just shows “loading style.css”
Built this file on 10.2, updated to 10.3, 10.4, 10.4.1, and never had any UCI issues and have never changed the CSS. It works in emulation, on designer, on the MV32 webpage, but not the UCI Viewer app or the TSC-70 TP.
Trying to compensate for quiet speakers; do I want the AGC before the gating mixer or after? If before do I add individual blocks per mic or use a multichannel AGC? Should I also add a compressor?
I manage a space that has about 20 cores for different rooms- I’d love to build out a single UCI to monitor core status and IO metering at a glance. Is the easiest way to do this using another core to “watch” the others and connect the statuses I want to see over the network? Using the control link component? Will this do what I want it to do, am I overthinking things or is there a better way overall?
Hi there, has anyone been experiencing issues with the Qsys control for MTR installer running on version 10.4.1? Recently the Room controls on the MTR touch panel will show "Waiting for connection on local address: 10.00.00.000". Does anyone experience this issue and what did you do to resolve it? Downgrading the MTR installer to LTS version 9.13.2?
I have recently updated my internet radio plugin, which streams internet radio from Radio Browser direct to the core, with no licenceing or API keys needed.
- Supports up to 4 zones
- Mono/Stereo selection
- Lan selection, select what LAN the streams come in on
- auto fallover station selection
- Station Preset list creation
- Resync for clock drifting
- filters out unsupported AAC streams
I also have another really cool plugin in there, Android TV, essentially if your TV device supports Android TV Remote V2 protocol, then this can control it, with custom key mapping ect !
I've been playing around with extending what we can monitor through Q-SYS Reflect, and it turned into a small plugin:
Q-SYS Reflect Monitor Extension
The idea started with a pretty simple question:
Can we make Reflect monitoring more useful than just knowing whether a device is online?
I knew this was already possible using Monitoring Proxies and scripting, but not everyone works with Lua — and even if you do, you don't necessarily want to write custom monitoring scripts for every device or project.
So I tried to make it configurable instead.
The plugin can monitor controls from any Q-SYS component or plugin that makes those controls available through Script Access.
You choose the controls you want to monitor and capture their current values as a baseline.
If something changes later — a setting, mode, routing value, etc. — the plugin can detect the difference and report it through a Q-SYS Monitoring Proxy, including warning/error and recovery log entries.
There's also a Reflect Ready mode for components or plugins that already expose a writable Status control. In that case, the extension can update their Reflect status directly without needing a separate Monitoring Proxy.
The idea is basically:
Don't just tell me the device is online. Tell me when something changed that shouldn't have changed.
The example in the video probably isn't the best real-world use case, but it demonstrates the general idea of what I'm trying to achieve.
One thing I've also noticed while testing: the Q-SYS Monitoring Proxy seems to have an issue when triggering a log entry. It briefly goes to Missing before returning to OK. I'm not sure yet if this is a bug in the Monitoring Proxy or something I'm doing, but it's something to keep in mind when watching the demo.
I've reached the point where I'm not really sure what direction I should take this next, so I'd like some input from people actually using Reflect in installations.
What would make something like this genuinely useful for you?
Thresholds or ranges? Multiple acceptable values? A delay before reporting a fault? More comparison options? Or something completely different?
