Forum Replies Created

Viewing 15 posts - 1 through 15 (of 154 total)
  • Author
    Posts
  • #119413
    Profile photo of Dave Meadowcroft
    Dave Meadowcroft
    Participant

    Cool, thanks David!
    I’ll check it out as soon as v2.0.5 becomes available and check that anyone using Mixing Station is on that version or higher before sharing network login details.

    #118011
    Profile photo of Dave Meadowcroft
    Dave Meadowcroft
    Participant

    Thanks Flo84 !

    #115147
    Profile photo of Dave Meadowcroft
    Dave Meadowcroft
    Participant

    No, the latency of the A/D on the DX168 is the same as the onboard A/D.
    The sound of the local preampss are a little different though. Not bad, just different.

    #114436
    Profile photo of Dave Meadowcroft
    Dave Meadowcroft
    Participant

    FWIW I agree totally Tobi.
    The preamps turn an analog signal to digital. The core ‘only’ processes once digital, therefore it is totally agnostic to the preamp whether DX/GX, AR or Prime.

    #113903
    Profile photo of Dave Meadowcroft
    Dave Meadowcroft
    Participant

    Direct Out Post Preamp is after the Digital Trim.
    Tie Lines are before the Digital Trim.
    Apart from that, there is no difference.

    #113661
    Profile photo of Dave Meadowcroft
    Dave Meadowcroft
    Participant

    Nothing that’s documented.

    It’s not part of the MIDI spec so that route is closed.

    MixPad does it, and so does Mixing Station (which David created by reverse engineering the protocol that MixPad uses), so it’s possible, but you would have to reverse engineer it yourself. Allen & Heath are very unlikely to release the spec.

    OSC support has been asked for several times for many products, but no sign yet that it is being considered.

    I’ve been looking into Stream Deck / Companion myself the last couple of days. It looks like the SQ Companion connector has been abandoned by the developer. Stream Deck has a MIDI plugin now though that looks like it will do most things that the SQ provides access to.

    #113659
    Profile photo of Dave Meadowcroft
    Dave Meadowcroft
    Participant

    I’ve finally got around to looking into MIDI control again.
    Still not tested the parameters I mentioned before, but here is the detail in the current version (Issue 4), plus a couple of other mistakes I’ve spotted.

    Are these invalid?
    Page 23: Level Parameter Numbers – FX Returns to Groups
    Page 26: Balance Parameter Numbers – FX Returns to Groups
    Page 27: Balance Parameter Numbers – Master Sends: FX Sends to Output

    Other Errors
    Page 9: 3.1 Scene change Examples
    The last example has the MIDI channel wrong for the Program Change (should be C2, not C0)
    Page 21: Mute Parameter Numbers – Inputs to LR/Aux
    Matrix to Output has Mtx1 listed 3 times instead of Mtx1 00 55, Mtx2 00 56, Mtx3 00 57

    #113657
    Profile photo of Dave Meadowcroft
    Dave Meadowcroft
    Participant

    Just Auxes, Groups and LR to Matrix on SQ.

    Your workaround can still work though. Would have to unassign house music (plus anything else needed) from LR and instead send to an unused Aux (probable best Post Fader for this scenario) or Group (not assigned to LR) and send that to to the FOH Matrix. Muting/unmuting LR would then leave the house music still playing.

    The only downside is burning a valuable Aux/Group as we only have a total of 12 in any combination of Auxes or Groups.

    The Hard/Soft DCA mute on Midas/Behringer is extremely useful and avoids these complicated workarounds. I’m really not sure why A&H haven’t implemented it on their products yet.

    #113645
    Profile photo of Dave Meadowcroft
    Dave Meadowcroft
    Participant

    Currently the FX Sends are only available to the internal FX.
    In addition, the FX Returns can only be fed a signal from the internal FX.
    As you know, you can patch the FX Returns to Output sockets so you can get a full wet signal out but that is all.

    To use external FX you should do it the old fashioned way with a (normally post fader) Aux patched to an Output socket (or two for stereo Aux) – and returning to a normal Input channel using an Input socket (or two for a stereo return). As pointed out, you can hack the send by using an FX that has a bypass (or some other means of doing no processing) and using the FX Return to Outputs to get a dry signal out – and then return to Input(s).

    Not Currently Implemented
    It would be cool to have each of the FX Sends with a pre-internal FX tap point available to patch to an Output socket so they can also act as limited buses (no processing and mono only) that we can use for whatever we like, such as external FX sends, without needing to burn an Aux.
    It would also be cool for each of the FX Returns to be optionally fed from a pair of Input sockets instead of the internal FX so they can act as limited stereo inputs (only EQ and fixed stereo) that we can use for whatever we like, such as external FX returns, without needing to burn a pair of Inputs.
    Neither of these options would require any processing overhead in the SQ as it’s just tapping before and after the internal FX, and the flexibility it would bring with up to 4 buses and 8 stereo inputs extra at the expense of internal FX could be very useful sometimes.

    #113631
    Profile photo of Dave Meadowcroft
    Dave Meadowcroft
    Participant

    1 stage of the opamp going down seems to drop around 13 dB.
    Not sure what would happen if both go (it’s a dual stage).
    When the one on my DX168 went I had to add over 20 dB, but I used that socket this weekend, even with the fault as I needed the I/O, and I had to reduce it to ‘just’ the extra 13.
    I didn’t get chance to test the possible scenes with recall filters workaround unfortunately. Instead I manually disengaged phantom pre patching/unpatching which was a little nerve-wracking with the band trying to clear the stage ASAP for the next band as it takes a while with the press and hold!

    #113587
    Profile photo of Dave Meadowcroft
    Dave Meadowcroft
    Participant

    So tonight at a rehearsal I had another socket exhibit the same problem, this time on a DX168 that I use to drop on stage for support bands. Again, a socket that normally has phantom power applied as it’s generally used for a SDC for an overhead.

    This is a problem. 3 sockets now gone faulty on boxes that, let’s be honest, are pretty expensive pieces of kit.

    Love the desk and the GX/DX boxes sound amazing, but this is getting very worrying!

    #113566
    Profile photo of Dave Meadowcroft
    Dave Meadowcroft
    Participant

    Thanks Mark.

    I had thought of that, but I need to check it will turn it off on all connected sockets. I’m not sure but I think it will just do those currently assigned to inputs. If an input from a previous show/scene has phantom left on, but the new show/scene doesn’t patch that socket to an input then it may get left on.

    I’ll test this weekend.
    A global override toggle (on sockets where it’s on) or ‘kill phantom’ so a scene reload is required to turn it back on would be easier – but happy to use any workaround!

    #113564
    Profile photo of Dave Meadowcroft
    Dave Meadowcroft
    Participant

    There is no global switch needed.

    Do you have an alternative solution that you might like to share Steffen?

    #113525
    Profile photo of Dave Meadowcroft
    Dave Meadowcroft
    Participant

    True about the caps, but the mic, still connected after toggling off, should drain those in a few seconds at most.

    #113512
    Profile photo of Dave Meadowcroft
    Dave Meadowcroft
    Participant

    I’ve just had a second input on my GX4816 lose around 13dB and go a little noisy – my tech is sure it’s caused by ‘hot plugging’. The two inputs are both ones that normally have phantom on.

    It’s a quick, easy fix to swap out the op-amp (it’s one side of a dual that goes), but I’d rather avoid it if possible.

Viewing 15 posts - 1 through 15 (of 154 total)