Q-SYS Corner

[Tj Hopland]

On the POE front that is what I was getting at, with the POE you could see there was a mains issue or that it was in the process of restarting vs just nothing.

On the mixing of amps old school may be the wrong term, I don't think there is anyone planning an Atmos system with DC300's but who knows, maybe? Everyone has their own preference what amp designs they like for what application possibly within the same system so more flexibility would be nice and part of that may be to have an analog only amp in the mix. Or even with network amps when there is a company that makes up their own rules for the standard? So analog could be a reliable work around for that. But there are ways that can be done now if that's your jam so its not like that's a deal breaker, just seems like it would not have been that hard to implement just to give some more options.


Before the elimination of the cinema division I was working with other non cinema contractors and pointing out the DCIO and an option to get the HDMI and I think even the AES3 may have been a reasonable option cost wise if you needed that many channels compared to their other AES3 IO options at the time. I don't recall if the DCIO was listed and available to the non cinema people or not. If it was no one seemed to know about it.

I too always thought they could have given some control over the screen and buttons other than mute and gain.

Didn't they already do a revision on the DCIO? Seems like there was a footnote somewhere about before and after a certain SN you had to be careful what system software you were running. But ya I would guess its likely a while supplies last thing and since except for maybe that specific implementation of HDMI everything is available on other current modules if you really wanted em so I don't see them designing a new one for us.

I also wonder how much of the H version cost is in the hardware vs the licencing of Dolby and DTS decoding? There are applications where that is nice and worth the money but others where it maybe doesn't get used so if its a card or separate I/O box maybe there could be both versions? Or you need a licence to enable the decoding?

I like the idea of it being separate and having more than just HDMI on it. Basically a consumer AV interface, its got RCA jacks on it and maybe more than one HDMI port? Maybe bluetooth? In a multiplex where its not going to be needed in every room at the same time you could even move it and use what its it the dynamic paring? That's where based on the physical jack you plugged into it knows where to route those signals. You plug it into the RJ45 jack in the front of theater 1 it knows that those signals are now part of theater 1, plug it into 2 it knows they go to two.

You could have the 'rental' cart downstairs that has the BD player or game consoles or mics or what ever and you just wheel it into what ever room has the rental. Add a touch screen to the cart for control of the sound, projector, and lights and you got a pretty slick mobile system that any idiot can operate. Not that you can't do something similar with more conventional systems but its not gonna be as clean.

I have not looked at their video options lately are they getting better? Would be cool if this AV box actually handled the V part too? You stick the box with the HDMI and audio at one end like in the auditorium the you just had to get a B box that was maybe just HDMI out you stick by the projector. I know they could sort of do that a while ago but it was stupid expensive.

[Steve Guttag]

I wasn't referring to any Crown amps, for sure. I presumed you were referencing something like the DCA amp, which I like. Heck, they've been going over 25-years and counting...are quiet, accurate...etc. The current input attenuators fix the oxidation problem of the older ones.

The revision on the DCIO was to get around obsolete semiconductors during the supply chain issues. That forces people to use QDS 9.10 or later for those units.

When the DCIO came out, we could sell it for under $1,400 and the DCIO-H was under $1,800. So, as far as inputs go, the DCIO was reasonably priced for AES3 and HDMI decoding. And no, the cinema stuff was kept deliberately separate from "systems" dealers. If you were to line up the DCA vs the CX amps (DCA 1222 vs a CX 302, the DPA-Q8K8 versus the CX-Q8K8, the Core 110c vs the Core 110f and the Core 510c vs the Core 510i), you'd be surprised at how thin the margins are in cinema.

There is the reality that if you are $50 higher in cinema, you'll lose the sale. You can talk yourself blue in the face about superior this and that but, at the end of the day, you'll get a line that resembles $50 x screen count really adds up and it won't sell any more popcorn than the cheaper alternative. I have no doubt that the current management in Q-SYS decided that the thin margins combined with our incredibly slow refresh rate (cinemas change technology only when absolutely necessary) and combined with our anemic "recovery" post-C19 as not worth it. They have endless systems going in for zoom/team rooms and other hospitality spaces. They've pretty much ditched large sound systems, in general. Look at what they've canned over on the sound reinforcement side. It's no small wonder that, amplifier wise, the SPA-Q (long over due but too expensive) and the MPA-Q are the first out of the door for new amplifiers. Those are going to cover the largest group of installations.

As for video, you can stay with Q-SYS and use their NV products (NV32H, NV21H-U or the NV-1-H). In fact, the NV32H can be your Core (with up to a 64x32 channel count) and be a 3x2 HDMI switcher as well as work with other NV products for streaming video/audio. In the right application, it could very much be a very cost-effective solution. With Q-SYS, it doesn't become really cost-effective until you are using, substantially, all of a product's capability.

However, there are other AV over IT solutions, like Visionary Solutions. They make encoders and decoders too and they integrate with Q-SYS for control. So, you can take a lectern, put an HDMI switcher in there (I'd use an Extron, but that is me...their stuff "just works.") put a TSC-70-G3 for a touchscreen as well as a USB-bridge. Have the lectern plug into a single Ethernet jack for sending A/V up to the booth as well as providing touchscreen control. If you configure dynamic pairing, you can move that Lectern from screen to screen and Q-SYS should track with that so that is always controlling the right theatre. In the lectern you could put whatever A/V gear you want. To set up for Zoom/Team spaces, you'd have to add in cameras/microphone(s) and that could get pricey and, possibly involve a bit of set up, if you are trying to reuse them in different screens.

AV over IT is a game changer, in my opinion. You can now use simple Ethernet to transport HDMI stuff. It is like having exactly the right sized matrix switcher. Think about it. Let's say you want to have Blu-ray support or Cable TV for the Oscars or some other event. Or even one of the various Opera offerings. You can centralize your sources and then plug in your endpoints in which ever theatres you want to to show the event. Most of that stuff is PoE so really your user interface is providing a place to hold the endpoint and an Ethernet jack to plug it in. Plug the HDMI cable into your IMB (presuming a semi-modern system) and ta-da you have a very nimble system with as many screens running the content as you want (you'd need an end point for your worst-case scenario). You no longer have to mount expensive equipment waiting for the day it gets used.

This is one of the reasons I want to divorce the HDMI from the DCIO...how many HDMI decoders does one complex need? Just get as many as your worst-case and route it as needed.

[Elia Orselli]

I'm considering QIO-AES8x8 as replacement for DCIO, leaving the hdmi audio extraction to the IMB. And I'm curious to test the new Barco ICMP-XS integration to Q-SYS (with audio processor enabled, audio processing license and DCIO seems to have a similar pricing).

[Tj Hopland]

I have not yet used the 8x8 but it should do the job. What were you thinking for connectors? Its interesting that they didn't go with a DB25 that could then be used with a Tascam cable to get what seems to be the standard of XLR. I suppose that's more of a portable standard and this is an install piece so the terminals makes sense? I'm assuming we could just do the bare cat wire into the terminal block?

Note the 8 in the name is the audio channel count, not AES3 channels so if you are doing 7.1 audio you will have to handle other channels like HI VIN if you need them another way.

I have not looked close at the ICMP-XS but it lists both AES67 and AES3 as the audio outputs. Is the AES67 always going to be available even if you don't have the audio processor enabled? If its always available and if you have a Qsys Core in the system you should not need the audio processing licence or the QIO. You should be able to send the raw audio directly to the core and let the core do the processing and routing.

Its certainly possible that the AES67 only works with the onboard processing enabled so then its cost vs features that you want. The least expensive option assuming you already have a Core would be to use the QIO to get the conventional AES3 into the core and the core will handle the processing. The QIO 8x8 looks like its about half the price of a DCIO, and that is the base DCIO, not IO-H. The H option adds about the cost of the QIO again.

If the processor licence is roughly the same cost as the DCIO and doesn't really add any features you can use then the QIO will still be the lower cost option remembering you may still have to deal with HI VI or other alternate tracks in another way. If those additional tracks had to get into the core then you were looking at a 2nd QIO which is roughly the same cost as the DCIO which can do all 16 channels or the licence which we assume could also get all the channels into the core over AES67 with no extra modules needed. At that point it would just be a matter of which one gives you the most features you want since the cost would be similar.

If the Core design isn't already done and paid for the costs to have someone do a full processor design will have to be considered. If you went the route of the audio licence in the ICMP-XS then the core is just going to be more of a router and maybe dealing with crossovers. That is a much more simple design and won't require much if any of a user interface which can also be time consuming to design from scratch.

[Steve Guttag]

Here is my take:
The QIO-AES8x8 fails on several counts:

• It is a single-NIC (not network redundant) and, therefore, excluded from 90% of my systems.
• It does not have enough inputs for a 7.1 system and HI/VI, leaving me to deal with that in some other manner.
• Its connectors are something that will need adapters for current Cinema servers.
• It leaves me with having to addresses HI/VI outputs to an IR emitter.
• It omits the fader/mute controls that I'm using on my low-cost user interface.

I'd need to get two of them to address the input count issue and likely use an AES3 to analog adapter for HI/VI. At that point, it has lost its cost advantage and it is already less reliable (missing the second NIC). So, that is a hard pass, for now.

AES67 does not offer network redundancy. On my Atmos systems, I still run AES3 as a backup as it is rock solid and keeps network redundancy. It has come in handy to keep a show going.

I think, using a server as the sound processor sounds nice but is incredibly restrictive. I don't want my B-chain processing done there as it wouldn't help with anything other than DCP. I have this wonderful DSP processor that allows me to have the type of tuning I want and apply it to all sources...the server is the wrong place. It could be argued that for a simple system, a server with audio processing and suitable amplifiers (e.g. an IMS3000 with a DMA and you're done) is fast/cheap...then why are you looking to squeeze that into a Q-SYS design? Let each part do what it is best at.

Servers, for the most part, do not "decode" HDMI. They extract PCM audio. Dolby does decode Dolby formats...all of the way up to Atmos, if you have the suitable enablements. Depending on the needs of the site, that may be sufficient. For most of my sites that want HDMI audio, it is not. We need to be able to up-mix 2-channel sources via pro-logic (Just Left/Right is a very bad presentation as there is WAY too much separation).

Since I mentioned it, my low-cost user interface looks like this:

image.png

It is a standard 2U rack panel with 8 buttons. The top four allow for the common formats of 5.1, 7.1, HDMI and Non-Sync. The bottom ones allow for turning on/off the booth monitor, showing the status (just with the color and the ability to put the system into Bypass (or see that it is in bypass). The DCIO (-H) provides the volume control, mute button as well as display if one wants to check input SPIs. Remember, this does not preclude providing a full UCI via a web browser or the UCI-Viewer apps. But it is about ⅓ the price of putting a physical touchscreen on the rack that 99% of the time...nobody is looking at or using. The buttons themselves are by Key Digital and it is a PoE device, so installation is a single Ethernet cable. The rack panel is custom, naturally as is my user component to interface it the way I want.

FWIW, on the DCIO, I've used just about every feature on it. My least used feature is the GPI via the RJ45. Had they made it on a phoenix type connector, I would have considered it more.

What I would like from Q-SYS on a DCIO redesign is to put my button panel onto it. Give it 4-8 general purpose pushbuttons and, perhaps a S/PDIF input on the back (optical and/or coax though that could go on a QIO-HDMI, if they make that).

[Tj Hopland]

All valid points that should go onto the pros and cons sheet for planning the project. Redundancy on the QIO wasn't one that was on my radar yet. I do recall noticing the RJ jacks were not labeled A and B or 1 and 2 but I think when I noticed that it was while looking for something else so it really didn't sink in that its single network. The 2 jacks that I assume are on most if not all of the QIO series must be an internal hub sort of a thing? Idea is you have a few of these modules stacked in one location and rather than having a home run for each back to your switch where ever that happens to be you could just daisy chain them together?

I have used the GPI on the DCIO a couple times. One time it was for some basic buttons for the VIP room which was next to the booth where the DCIO was so that was the shortest cable run. The other I think it was house lighting controls for the film projectors. I think on that one I had already used the GPI's on the core also for lighting controls but those were different settings in different locations like on the stage and janitors closet. In that venue the main show controls were via a touch screen which could be moved between the sound/lighting booth and the stage depending on the type of the show so you could not count on the touch screen always being in the same spot.

I like that KD-WP8-3 button panel and I think may start its own thread to talk about using it outside of Qsys. When first reading about it I hoped it would be a little cheaper but for what it does I guess its a decent price which from the likes of B&H Photo is currently $468. That's gonna be what in the ballpark of 1/3 the price of a 5" touch screen?

You can't display live text data on this but it looks like through the plug in I'm assuming you can do some stuff with the button lights? I'm assuming it can, given a properly thought out and executed design display live status based on lighting and the color of the buttons? This is good because if say the server sends a cue and changes between 5.1 and 7.1 you will be getting a live status of the current format. Sure you could build your own panel with push buttons, maybe even lighted ones and use some GPO's to run the lights but the costs are going to add up especially if you have to throw in labor to drill holes and solder and such.

I'm assuming there isn't really a limit to how many of these you could use on a system? Looks like they can operate stand alone so I'm guessing that Qsys more or less treating them as a raw device so you can just bring as many of them as you want into your design as long as they all had a unique IP that worked within the rest of your network. And I don't mean raw device as in you have to program every aspect and enter the command strings which you can do in qsys if you need to. I'm thinking that's whats basically going on in the background but that's where the plug in comes in, its packaged neatly often fairly graphical so most of what you are doing to integrate into your design is drag and drop and hook up some virtual wires.

In the past I have scrolled through the plug in list in designer to see whats there but there is a lot and you can't exactly search by feature within designer to see if anyone makes a supported device to do what you may not even yet know you want to do so I missed this one.

[Steve Guttag]

The smaller QIO does use their NICs for daisy chaining units. So, if you have four of them in a 1U space, you just need the one Ethernet cable to your switch. However, if you use that feature, you have to provide power to them. If you are using them singly, then you can use the PoE. So, pick your preference.

As to the Key Digital, we sell it on the rack panel for $500. Cost wise, not it is not as cheap as the components of 8 buttons and 8 LEDs but, as you noted, by the time you build out that panel and wire it (how are going to fire those LEDs? You need power, resistors, wiring and some sort of GPO to trigger them), I can provide this sort of panel for far less in labor and final cost. We have the panels fabbed so assembly is two screws (M3.5, of all things) and an Ethernet cable. So, installation is faster too. Oh and it gets you another RS232 port, if you need it.

The buttons don't have much travel...just click. I think the thing I like least about it is the fact that it only has 2 LED colors...Blue and Red and just a single intensity of each. I would have liked a third, perhaps amber or white or orange. Green would have had uses too (for my status one). The plugin is annoying in that it makes you choose a color that is not assignable from within the Q-SYS design. However, if you use its API, you can do what you want with the colors. How dumb is that?

Another thing to consider in the cost of a UI is not just the thing that gets mounted but what it takes to make that UCI. How fast can you implement buttons versus creating a whole UCI? The button panel is cheaper from the get-go and stays that way. I'm not saying it is for every case but it can be for most cases in cinema. You can still provide a UCI for the client and even mix/match systems so if they have a screen that will get a lot of A/V...sure...splurge...put the touchscreen in or use an iPAD and set it up. But for the other screen where nobody even sees the equipment (unless there is a problem), why spend the money?

[Steve Guttag]

QDS 10.1.1 has been released with the following bug fixes:

Resolved Known Issues

Video:

• Resolved an issue where when running a design with NC-Pro15x peripherals for extended hours causes peripherals to become stuck in an “initializing” state and freezes all controls in Q-SYS Designer, with no Core Manager event log messages indicating peripherals initializing.
• Video:Resolved issue where NC-20x60 camera autofocus could intermittently “pump” or breathe in and out while trying to keep subjects in focus, instead of smoothly locking focus on the subject in the frame.
• Video: Resolved an issue where the camera auto-focus zone logging reported incorrect region values—showing center, top, bottom, and face focus zones with mismatched identifiers—when changing AF sensitivity and zone settings.
• Video: Fixed an issue where switching resolution from 4K to 1080p during Tile-View streaming could cause the NV-21 encoder to enter a bad state, resulting in stream hangs.

[Steve Guttag]

QDS 10.2.0 has been released. A notable Cinema issue addressed is on the Atmos receivers:

Resolved an issue where the multicast address configured on an Atmos RX component did not persist across Core reboots or design re-deployments, causing the Multicast Address field to be blank and require re-entry after restart.

Oddly, no new hardware (like the MDA-Q) are supported on this version. The release notes mention QDS 10.2.1 so this one is likely to be short lived since (also) the MPA-Q are due out March/April. There is a new look to QDS for how it displays the RSP components (it is configurable in Preferences, if you like the previous method).

They are claiming that Windows 10 is now deprecated for QDS 10.2.0 however I just installed it and opened it on a Win10 Pro computer without issue. Perhaps if I were to push a design it might error out. Then again, this may be Q-SYS' way of saying that they are no checking it against W10 anymore so if you have issues, don't blame them.


v10.2.0


Version 10.2.0 was released February 24, 2026 and includes these updates and resolved issues.

Platform

Refreshed Q-SYS Peripheral Manager Experience
Expanded Date and Time Configuration for Peripherals
Early Warning When Opening Older Designs in a Newer Major Version
Enhanced Schematic Elements UI and Improved Plugin Organization
Deprecated: Windows 10 Support

Windows 10.x is no longer supported by Q-SYS Designer Software.

Security

New Unified Security Configuration for Peripherals
New Custom Certificates for Q-SYS Peripherals

Control

Code-Focused Tab Names in Script Programmer Mode
Certificate validation for Q-SYS Lua TLS Sockets
Design-Specific Script Programmer Mode
Set a Default Script Access for New Components

Q-SYS Designer 10.2 adds a “Default Component Script Access” setting under File → Preferences → General that lets you choose how Script Access (None / External / Script / All) is applied to components as you add them to a design, so new components automatically follow your preferred scripting workflow.

MTR Component Transition to Q-SYS Connect
Q-SYS Connect for Zoom Rooms

[Steve Guttag]

Resolved Known Issues

• Control:Resolved an issue where pressing a button on a visible top‑layer UCI page and sliding a finger into the area of a hidden lower‑layer control could trigger that hidden control on all TSC‑G3 touchscreens.
• Control:Resolved an issue where multiple MTR UCI Viewer components in the same design would all change to the same UCI selection, preventing independent UCI selection per component.
• Control:Resolved an issue where UCI navigation buttons intermittently loaded the wrong page or did not load any page when clicked, affecting designs opened in Q-SYS Designer emulation and in Windows UCI Viewer across versions 9.10.2, 9.12.1, 9.13.x, and 10.0.x.
• Control:Resolved an issue where touching and holding an empty area of a TSC touchscreen caused all UCI elements (such as audio meters) to appear frozen and stop updating for as long as the touch was held.
• Control:Resolved an issue where Q-SYS Designer v10 crashed during emulation when both Q-SYS KNX IP Interface v1.0 and Q-SYS KNX Companion v1.0 plug-ins were used in the same design, linked by CodeName, and the Number of Groups (GA) property on the interface was set above 250.
• Control:Resolved an issue where setting the Date/Time component to Format = Custom with Format String = %s caused Q-SYS Designer to lock up and crash when emulating a design.
• Control:Resolved an issue where, the link to a css file's 'Local Source' was missing from Design Resources for an installed style.
• Control:Resolved an issue where TSC-101-G3 touchscreens reloaded the UCI when the screen was turned Off or when Screen Timeout turned the screen Off in designs that used Pin Pad controls placed on the UCI.
• Control:Resolved an issue where iterating over the controls of a component inside a plug-in using pairs(myComponent) returned the first control repeatedly until reaching the Max Execution Limit, instead of iterating through all controls as expected.
• Control:Resolved an issue when the TSC-101-G3 screen turns Off (either by pressing Screen → Off or through Screen Timeout), the panel unexpectedly reloads the UCI / design instead of simply turning the screen Off.
• Control: Resolved an issue where Designer crashes when switching between UCI pages containing meters styled with CSS filmstrip classes.
• Control: Resolved an issue where non-ASCII characters drawn via the <text> element in SVG-based button graphics did not render correctly when viewed in Core Manager or Reflect.

• Control: Resolved an issue where enabling the Preview Stream for an NC-12x80 camera caused the Windows UCI Viewer screen to go black and stop displaying video, while disabling the Preview Stream restored normal UCI Viewer operation.

• Control: Resolved an issue where TSC-101-G3 touchscreens ignored the .meter-vertical-indicator custom CSS class for Vertical Meter components, causing meters to display the default vertical bar style instead of the intended custom SVG / PNG styling.
• Control: Resolved an issue where custom CSS was not applied properly when viewing a UCI in Core Manager or Reflect.
• Control: Resolved an issue where button icons on TSC-101-G3 and TSC-70-G3 touchscreens would intermittently fail to load and instead display a swirling loading indicator after design deployment or panel reboot.
• Control: Resolved an issue where toggle button images using Custom Button Image would not display on TSC Gen 3 touchscreens or in Windows UCI Viewer when a custom CSS file was applied, even if the CSS did not define any image-related rules.
• Control: Resolved an issue where the Plugins section of the Schematic Elements pane in Designer 10.1 incorrectly instructed users to “Open Asset Manager to download plugins” instead of referencing the Q-SYS Library.
• Control: Resolved an issue where Demo Modules were visible in the Components list, in Q-SYS Designer Software.
• Platform: Resolved an issue where Administrator only displayed command buttons A–H for PS-TSCG3 paging stations, even when the station was configured for additional command buttons, preventing assignment of commands to buttons I–Z.
• Platform: Resolved an issue where configured command buttons did not appear in the Revert To drop-down for Virtual Page Stations (VPS) and PS-TSCG3 paging stations, causing the list to show only no Command even when command buttons were configured.
• Platform: Resolved an issue where the multicast address configured on an Atmos RX component did not persist across Core reboots or design re-deployments, causing the Multicast Address field to be blank and require re-entry after restart.
• Platform: Resolved an issue where PTP Announce messages from Q-SYS Cores could include an incorrect message length when the Core name had an even number of characters, causing Wireshark to report malformed packets and preventing compatibility with the Linux ptp4l library and Meinberg hardware clocks.
• Platform: Resolved an issue where the Q-SYS Configurator displayed a white LED for online and healthy Cores, instead of a green LED.
• Platform: Resolved an issue where NMOS registration could fail when a Core 510i started with one or more network interfaces physically disconnected, due to invalid interface information being reported for those ports.
• Video: Resolved an issue where NC-series PTZ cameras with Auto Framing disabled, Transition Speed set to Instant, and Face Count enabled could output a cropped USB video stream after toggling camera privacy On and then Off when no faces were detected.
• Video: Resolved an issue where NC-series camera peripherals reported “Missing - Camera Status Missing” in Q-SYS Designer after enabling Secure Communication on the Core without setting a password on the camera, instead of correctly reporting “Fault - Authentication failure, Communication failure.”
• Video: Resolved an issue where Dell Inspiron 16 5625 laptops with AMD Ryzen 7 5825U CPUs were unable to establish USB bridging with NV21 over USB‑C.
• Video: Resolved an issue where Dell Inspiron 16 5625 laptops exhibited inconsistent USB‑C DisplayPort Alt Mode behavior when connected to NV21, resulting in cable detect without a valid video format, intermittent loss of video, loss of video bridging, or delays of up to several minutes before video was established.
• Video:Resolved an issue where UCIs hosted on Windows UCI Viewer and deployed from Core did not load custom CSS files after upgrading from Q-SYS Designer 9.10 to 9.11 or later, causing UCIs with link rel="stylesheet" references in the HTML header to render without their intended styling.
• Video:Resolved an issue where IO-USB Bridge could introduce packet loss, image distortion, and approximately 2 seconds of video lag when bridging MJPEG video from NC cameras in UC&C + HD USB Video format, in designs originally created in older Q-SYS Designer versions and then upgraded to 9.10 or later.
• Video:Resolved an issue where Generic Display mute buttons on decoders would toggle visually but fail to mute audio when used in designs deployed with Q-SYS Designer 10.1.
• Video:Resolved an issue where selecting an unassigned Mediacast input on an NV-32 in either Core or peripheral mode could cause the design to temporarily stop and display the NV-32 informational splash screen.
• Video:Resolved an issue when running a design with NC-Pro15x peripherals for extended hours causes peripherals to become stuck in an “initializing” state and freezes all controls in Q-SYS Designer, with no Core Manager event log messages indicating peripherals initializing.
• Video:Resolved issue where NC-20x60 camera auto-focus could intermittently “pump” or breathe in and out while trying to keep subjects in focus, instead of smoothly locking focus on the subject in the frame.
• Video: Fixed an issue where switching resolution from 4K to 1080p during Tile-View streaming could cause the NV-21 encoder to enter a bad state, resulting in stream hangs.
• Video: Resolved an issue where the Windows UCI Viewer stops playing Mediacast Output preview streams, reverting to low frame rate images after a few seconds.
• Video: Resolved an issue where the camera auto-focus zone logging reported incorrect region values—showing center, top, bottom, and face focus zones with mismatched identifiers—when changing AF sensitivity and zone settings.

[Leo Enticknap]

Has anyone come across this?

image.png

I have a site with a failing IOFrame, which is to be replaced with a DCIO and 2 x QIO-AES8x8s (the design calls for 12 channels of AES3 out). Before we decided on this, I checked the spec sheets for both the Core 110c and the QIO-AES8x8, and saw nothing to suggest that they could not be used in the same design together. As both units are supported by the version of Designer I'm working in (10.2), there was nothing whatsoever to suggest that this could be a problem. The above error appeared when I tried to emulate the changed design for the first time.

[Steve Guttag]

I would suspect that the problem is in 10.2. It was brought out for a specific purpose with 10.3 due to be released any day now (needed to support MPA-Q amps that are being released and on the April price sheets. I checked. The 110c is having problem with QIO-AES8x8 on all versions of 10 but the Core 110f is not.

I would open a ticket with Q-SYS as I can't believe that this is a known problem (yet). I guarantee you they aren't checking against the "c" Cores anymore.

[Leo Enticknap]

Thanks Steve. This will actually be a major issue for us if there isn't a workaround (e.g. downgrading to an earlier version), because the stuff has already been shipped and the install is scheduled for two weeks from today. I've opened a support case with QSC.

[Elia Orselli]

Just tried with v.10, 10.1 and 10.2: the error is always there. However, 9.13.1 works without errors: why don't you stay/downgrade to 9.13.1 until the issue is solved? Do you have other HW requiring at least 10.0 in this design?

[Leo Enticknap]

Thanks Elia. I don't: the total hardware inventory (after the IOFrame has been retired) consists of the Core 110c, a DCIO-H, and 2 x QIO-AES8x8s.

Problem is that I just tried to open the design file saved in 10.2 in 9.13.1, and it won't let me - says it's an invalid Q-Sys file. Tried a progressive downgrade: opened and saved it in 10.1 successfully, but then hit the invalid file problem when I tried to open it in 10.0.2, 10.0.1, and 10.0.0. I've added that news to the support case, and am awaiting QSC's response.

Update - just discovered by looking on the website that there is a 10.0.3 that passed me by. That enabled me to open the version saved in 10.1. I then successively uninstalled and reinstalled from 10.0.3 > 2 > 1 > 0, opening and saving the design file at each step. I now have the design file in 10.0.0, but that will not open in 9.13.1. So I'm back to awaiting a response from QSC.

I am seriously unimpressed with QSC over this. Firstly they provide no documentation or clue whatsoever - not even a "This design contains hardware that is not supported by this version" when you open the design file, as is the case with the IOFrame - and then get you into a situation whereby if you save a design file in a later version, it seems that there is no going back, and I will have to spend several hours reconstructing the design by copying and pasting, and manually recreating whatever does not make it across by that method successfully. It looks like they seriously botched the version 9 to 10 transition.