[BradWalkerParticipant]

Hi Nicola,

Thanks for the reply. I just sent the .cfg to Alex. Hopefully it reveals the mystery!
Brad

[BradWalkerParticipant]

I dressed a bunch of cabling in the back of the processor rack yesterday, and in the process rearranged the I/O for the AHM-16. This meant that I needed to do some testing to verify everything got plugged into the right places again.

During testing I found that x-over outputs 4-8 all worked as expected, and it was just the first three that didn’t. A little bit more testing showed me that the problem stayed with those three physical channels only.

On the AHM-16 at least, the I/O boards are in three-channel blocks. I think it’s possible I’m looking at a hardware problem, so I guess it’s time to file a service ticket.

AARGH

[BradWalkerParticipant]

For more information, here’s the eight outputs in use at the moment, and what I had to do with the PEQ to approximate a subwoofer crossover so I could at least get the SMAART phase and magnitude in the ballpark.

Attachments:

You must be logged in to view attached files.

[BradWalkerParticipant]

Schedule changes meant getting to the church yesterday, not Monday. Here are some pictures for the eagle eyes:

Crossover block and output assignment screenshots, also zone assignments, crosspoint routing. This crossover filter is for a line of KLA12 for a simple high-pass filter. No signal shown on the output meter, and no audio on the XOver block assigned to local output 1. All I have to do is assign it to the full-range output and it passes audio.

Attachments:

You must be logged in to view attached files.

[BradWalkerParticipant]

Thanks for the reply Highflyer1953! I’ll be back tomorrow at the project where this is installed, and will take some screenshots for you. It must be something simple, and I’ll be happy to have a D’oh moment when you point it out.

Thanks!
Brad

[BradWalkerParticipant]

Hi Alex,

Thanks for the confirmation about the minimum iOS version needed.

I suppose anything’s possible regarding network issues, but we hoped to eliminate that from the list of potential issues by using decent Ubiquity hardware, creating a dedicated mixer-only wifi network that included two mesh points. It’s a hidden SSID, so concert guests don’t try connecting to it, and we had only 2 connections to the mixer.

I was wondering if there’s an incremental processing power requirement taxing the iPad, dependent on how many channels are active and how many DEEP plugs are in use?
I guess another way to ask the question would be, “Beyond the minimum iPad requirement, is a beefier model needed to handle busier mixes? We were running ~ 48 inputs and over 20 outs.

We’ll keep an eye on it this coming weekend with a bit smaller rig, and a little more time to monitor things.

Thanks!
Brad

[BradWalkerParticipant]

Any other thoughts would be much appreciated! I’d still like to know how much horsepower is required by Avantis MixPad and OneMix…

[BradWalkerParticipant]

Hi Brian,

Thanks for the suggest on Mixing Station, I just checked it out. I’ve heard of it before, but the first time I saw it, it seemed much more clunky than what I just looked at.

I also just heard from one of the bands we’re mixing this coming weekend who have even older iPads, and the Avantis apps won’t even load on their devices. They’re basically demanding I provide them all iPads or wedges :rolleyes: I can understand that on one level, but they were all gung-ho about “Yeah, we’ll just use our iPads!” and only now try to load the apps I gave them the links for 2 months ago…

[BradWalkerParticipant]

Hi Jack and Alex,

Is a corresponding update to the Director, MixPad, and OneMix apps required? I don’t want to update the desk and get out of sync on the other devices…

Thanks!
Brad

[BradWalkerParticipant]

This is an independent issue from the SQ-to-GX4816 thread I just posted resolution to…

I went on a service call for a system we installed about 18 months ago. SQ5 -> DX168 in local rack where mains amplifiers and wireless receivers were housed, then -> cascaded to another DX168 in musician’s area. The issue was “no sound coming out of the main speakers.” This system is used every day with multiple users, some skilled, most not. This is the first time there’s been any problem.

The SQ5 I/O showed hatch-marked S-Link inputs, and the first DX168 showed power and network connection, but no “Ready” LED lit up. I should have but did not check the status indicators of the cascaded DX168. I do know it stays powered on almost continually, because the band members just leave it on. I do know we were getting sound out of a self-powered stage monitor connected to an output of the cascaded DX168 even while the main outputs were not working.

Several power-cycles of the system (mixer/FOH equipment and amp rack with first DX168 in it are sequenced from a single on-off switch) did not change the problem.

In the process of checking connections, I disconnected the _cascade_ ethercon cable from the first DX168. When I plugged it back in, the “Ready” LED on this first DX168 lit up again, and sound was restored. S-Link patch points in the SQ5 I/O screen were solid squares, no longer hatch-marked.

I couldn’t get the problem to repeat itself after this, so it leaves me wondering what the actual cause was. Would having a cascaded but always-on DX168 that finds the SQ5 before the first DX168 in the rack powers up cause this on some occasions? But why wouldn’t it be consistently a problem? This is the first time it’s been reported in 18 months.

Hopefully this extra data point helps with the troubleshooting. Keenly interested in what Keith and the team find out!
Brad

[BradWalkerParticipant]

Well, I’ll be! The firmware update did the trick, snake locked up with the “ready” LED lit as well. Note to self: ALWAYS keep A&H firmware up to date, even if just one bump up from what’s installed!

As a big bonus, the Avantis showed up today. I was able to get the SQ->GX4816 all happy and working, then watch the Avantis running 1.20 load its firmware (fast flashing LEDs) when connected to the same GX4816 a few minutes later. Locked up like a champ.

I always thought the idea of keeping the firmware in the console and letting S-Link auto-negotiate with the expanders was a pretty good architecture approach. Watching it happen today in real life was very cool. Or maybe I was just blinded by all the cool screens and buttons 🙂

Attachments:

You must be logged in to view attached files.

[BradWalkerParticipant]

Just to clarify, the firmware is version 1.5.2 r3947, not 1.5.8 as previously stated.

[BradWalkerParticipant]

Here’s the Info Screen:

Attachments:

You must be logged in to view attached files.

[BradWalkerParticipant]

Those who update, let us know how it behaves! I’ll probably keep what I have going right now until I hear some reports back.

[BradWalkerParticipant]

We hope that A & H can solve this as very soon as possible

It has been pop-free under V1.4. It sounds like A&H is working on it, and getting the fix is much anticipated. At least I’m still able to use DynEQ and MB plugins, which have become essential to my way of life 🙂

[Author]

Posts