Forum Replies Created
-
AuthorPosts
-
2023/09/29 at 12:07 am #115231
Not exactly an octaver, but the Hypabass effect (paid add-on) is pretty similar (and depending on what exactly you are trying to accomplish, may work better than an octaver)
2023/07/15 at 1:57 pm #113700What’s the advantage to Thunderbolt here vs the USB that’s already built into the console? 32×32 channels at 96k/24bit fits into the data rate limits for USB 2 (which are roughly 70 channels of 96k/24bit audio), and bumping up to USB 3 would allow for more channels of I/O than the SQ series supports. And that’s without getting into the higher speeds that you can get with Thunderbolt.
2023/05/18 at 1:03 am #112930Scene was only recalled back at the shop, so no idea if it would have fixed things onsite.
Wasn’t channel balance – all inputs were mono and panned center. Patch was checked and inserts were disabled as part of troubleshooting. “Meters working” was the main L/R meters with nothing PFL’d indicating both L and R at the same level.
I’m perfectly willing to chalk this up to user error, but I’m trying to figure out what the error might have been. Especially since I’ve not been able to find anything on the console or in the reference materials for how to even treat the two sides of the main L/R bus separately (other than the pan/balance controls on the channels and buses, all of which were checked)
2023/05/14 at 10:39 pm #112889Hugh,
I’m aware that the DX32 is an expansion rack that lacks processing. I was suggesting that making a version with dLive processing (think DM0 with slots for Prime cards in place of the digital expansion card slots in the current DM0) would be interesting, especially if it were kept to a compact footprint. Kit it out as one of the “Compact Touring” systems and you’ve basically got your “Flex 8”.2023/05/12 at 11:37 am #112861As interesting as something small would be, I don’t think that a 15″ touchscreen is going to get you a compact footprint. Dropping down to a 10″ touchscreen would pair better with a 9 fader unit.
But even without all new development and a new product line, something like a DX32 that adds the dLive processing core and an Slink slot would be interesting (CDM16? DM16?). Combine it with an ip8 and a touchscreen PC and you’ve basically got the Flex8
2023/05/12 at 11:23 am #112860+1 on this As an alternate, having a way of ganging the enable/disable across multiple channels would solve some of the headaches here. Perhaps add the Tube Stage controls to the DCAs?
2023/05/12 at 11:19 am #112859+1
Having to go 2 screens deep in a typical scenario to be able to disable an insert makes using FX slots as insert (why burn a bus if you’re only using it on one channel) much less useful. Especially when just about everything else in the processing path has a hardware enable/disable button on the console.
It’d also be nice to have the same sort of enable/disable option for the Tube Stage preamp plugin as well.
2023/03/26 at 5:00 pm #112156+1 on this. And it’s not like A+H hasn’t figured out how to manage unmuting individual channels that were muted via mute groups in the past – the ML3000 series could do that…
2023/03/26 at 4:56 pm #112155+1
The lack of metering when the AMM is engaged makes it impossible to know at a glance if the microphone is functioning (power switches on wireless bodypacks…), and the lack of PFL when the AMM is engaged makes it impossible to EQ the lavs on presenters before they go onstage. The current workaround is to turn off the AMM when the mics are offstage, but that often invites feedback if the AMM isn’t engaged before the mics go live.
My use case for this is live mixing of things like panel discussions where there are multiple presenters on lavalier microphones. Typical workflow is that the presenters are mic’d up offstage, and EQ is done via PFL (no onstage soundcheck). Wireless systems are usually in play, and power/mute on the bodypacks aren’t guaranteed to be disabled. The AMM is used to increase gain before feedback (that extra 6dB going from 4 open mics to 1 open mic can make a big difference) and help manage the transition between lavs and lectern mics if both are in use.
2022/12/04 at 4:18 pm #110297A followup on this, and an apology. It appears that despite my understanding that the console was on 1.5.4, the console in question hadn’t been updated past 1.5.0, and was experiencing the known lockup issue that was fixed in subsequent firmware releases. No issues were observed with multitrack recording on 1.5.7. So the “please verify you are running the latest firmware” request was absolutely warranted.
That said, from a customer service perspective, there’s a HUGE difference between a response of “This was a known issue with firmware version prior to 1.5.2. We’ve been unable to reproduce the described problem on the firmware version you state to be running, so please make sure you are running the latest firmware version and update if needed to be sure you have the latest fixes” and a response of “We fixed that bug, and aren’t going to take any further troubleshooting or problem reproduction steps on the issue you’ve reported until you can verify that the unit is running the latest firmware”, even if the final outcome is the same.
2022/11/12 at 1:32 am #109964Keith,
I’ve spent a bit of time on the other side of this sort of technical support, so I’m somewhat sympathetic to the desire for getting a support ticket created, but it’s not clear to me how useful that support ticket is going to be. The console in question was a rental unit (yes, I have a bit of time on that specific unit, but it’s not my console and I don’t have access to it outside of using it on jobs), so getting more information about the state of the unit will be difficult. Additionally, the information that is available (which is mostly already in the forum post) is based on my recollection of the event, and may be incomplete as I had more pressing issues than troubleshooting a console at the time (like mixing the live show, and wondering if the recording the client was paying for was going to be corrupted). But I’m happy to copy the information into a support request if that’s what’s needed for someone to take another look at the issue.
I’ll also note that problems may have multiple causes, and the proximate cause that resolves a problem 99% of the time may not be the root cause that has to be fixed for the problem to be resolved 100% of the time. It’s also far too easy for folks in the office to lose sight of the realities of what’s involved with getting good data from the trenches – it’s very easy to ask for all the diagnostic data that makes trapping an issue easy, but actually getting that data may be impossible. So I’ll offer up a gentle reminder to start with the information you have, and not count on getting better data (and I say this as someone who is more often than not the person in the office, but who has lugged test equipment across the country and up onto scissor lifts to collect site data on occasion – I know exactly where the desire for more information is coming from).
Unfortunately, although I do like the SQ consoles and the other (mostly older) A+H gear I’ve worked with, my experience has been that it lacks the rock-solid reliability that some other manufacturers have (which sometimes comes at the expense of feature set and sound quality, and almost always comes at higher cost, to be fair). And this makes me a bit leery of using it in high profile situations. Consoles locking up mid-show (which has happened before on older firmware as well, likely due to since-fixed bugs) and requiring a reboot to resolve the issue pretty much obliterates any joy that comes from how the console performs when it’s functioning properly.
</rant>
2022/11/06 at 4:02 pm #109869This situation is a small rental company that downsized dramatically (and almost disappeared) during the pandemic. As there isn’t any shop tech (or really, any fulltime employees other than the owner) firmware updates either involve updating on a jobsite (with the associated risk of no console if something goes wrong, and the extra time required), or setting up the console in the storage room (not really fair to call it a “shop”) to do the update. So firmware updates that don’t bring benefits (at least per the release notes) aren’t a priority given the hassle involved with updating.
2022/10/29 at 2:50 pm #109746I’m not sure this is completely fixed.
I ran across a more minor version of this bug on 1.5.4 (system is old enough that there didn’t appear to be benefits to updating to 1.5.5 or 1.5.6, so it hasn’t been a priority), and there was a note from another tech that they’d seen a “touchscreen lockup with multitrack recording and RTA)”.
When I saw it, the touchscreen (only) would freeze on the EQ screen with a multitrack recording running, but only about 2 hours into the recording. Recording was at 48khZ, 24 tracks being recorded to an external SSD. S-link to a DX168 connected to the console, but no other network connections (so no iPad connected). Rebooting the console fixed the lockup, although the scene status was reset on the reboot (console settings hadn’t changed, but the scene that had been loaded at lockup was no longer shown as loaded).
This bug is more than a little disconcerting, as without a softkey to stop the recording (which fortunately I had), the console reboot would result in a loss of the (at this point, 2+ hours of) recording. And there isn’t any way to access the SQ-Drive from the iPad app, so that isn’t a recovery option either.
2022/09/26 at 7:50 pm #109217Providing DC power via a USB-A connector is not rocket science, and managing the ground connections is easier when the power and signal wires go the same place, vs. when they originate separately. The presence or absence of an external power supply has very little bearing on if the USB drive can support the sustained data rates required for recording. And as A+H support has noted on multiple occasions, the primary reason for a USB thumb drive not working reliably for recording is insufficient sustained data rates. There are plenty of bus-powered external USB drives based on 2.5″ laptop drives or M.2 SSDs that work just fine for recording on an SQ desk.
2022/09/26 at 7:41 pm #109216Muting the return clips the reverb tail, muting the send does not. Better to mute the send if the console makes it easy to do so (some do, some don’t, the flexible strips in the A+H consoles do)
-
AuthorPosts
