Forum Replies Created

Viewing 15 posts - 1 through 15 (of 112 total)
  • Author
  • #87556

    Hello Paul,
    The ’24v mod’ is not related to preamps. It was an engineering change issued to distribution several years ago pertaining to non-modular main PCBs.
    We have a general preamp service kit for non modular IO PCBs, part number 004-495. This can be ordered through our distributor for your country.

    Where to buy

    Best regards,
    A&H Product Support


    Hi @billhaberkamp

    Yes, it is possible to bridge the Dante Control Network to a DHCP server and operate in that manner if you wish although you would then need to bridge the Shure Control network to the dLive with an additional connection.

    DHCP configuration certainly offers a simpler setup, but if there problems with the connection to the DHCP server then there is the possibility – depending on factors such as DHCP lease time – of a Dante device having an IP address change which could result in a loss of audio and/or control whilst the Dante device reboots.

    Also, as you suggest, if the DHCP server were to fail during a show, you would need to change the Shure Control back to Static IP which could be stressful in the heat of battle!

    Dante’s Zeronconf (Zero Configuration Network) works well in most scenarios for the audio side of things and we generally recommend using Static IP addresses for “critical” connections within the system so you always know the IP address of any given device which can be very helpful for many reasons 🙂

    So yes, there’s more than one way to cook an egg!



    Hi all,

    Could you fire us an email at with your log files attached we’ll look into that for you.

    You can copy the logs to a USB drive in the history screen.



    We don’t currently support naming custom encoders. We’ve added it to our feature request list.


    Hi all,

    We’ve made some improvements to the responsiveness of the system in firmware 1.41 which was made available earlier today.

    After startup of console there is an delay between selecting and displaying system screen pages. After the first selection of one page this page is showed immediately. The other pages needs to be selected first too to show itself immediately.

    This behaviour is normal, once a screen has been loaded once it will load more quickly on subsequent views of the screen.


    It is not imperative to use on of our approved cables, but they are the only ones we can guarantee to work as the specification of the cables is fixed and will not change.

    In theory any good “touring grade” quality CAT5e/6/7 cable should suffice but ideally you want to try before you buy, or buy from somewhere with a good returns policy, so you can ensure that it works as expected.

    I should add that although @gcumbee has had success with >100m cable runs, it is not something we support so you would be going above 100m at your own risk.


    Hi @lishinsky,

    Copper CAT5e cables in excess of 100m are unlikely to work I’m afraid – the IEEE 802.3ab standard has a maximum cable length of 100m.

    For cable runs in excess of 100m we’d usually suggest a fibre connection although it is possible that you could use 2x pieces of active network hardware to act as “repeaters” in conjunction with 3x 100m cable runs. However the fibre option would probably be more convenient and would introduce fewer potential points of failure.


    Hi All,

    We have been able to reproduce this issue and we’re currently working on a solution.

    To give you an idea of what we believe is going on;
    Our DAW Control Driver translates the MIDI messages from the surface to either Mackie Control or HUI protocol. To send these to the DAW, it uses virtual MIDI ports (the four you select from in your DAW). These are created on an ad-hoc basis, and are addressed when initiated, avoiding conflicts. This means that when initiated (on restarting the computer for example), the address is different, and it seems that this address is what the back end of Logic is using to ‘remember’ connections.
    There is no issue with the firmware, nor the DAW Control Driver, and once the connection is made, everything runs perfectly.
    The problem here is just with the persistence of the connection.

    Unfortunately the only work around for the moment is to re-make the connections when any virtual MIDI ports have been re-made. Though as mentioned, we are working on a solution.

    Cheers, Keith.


    Hi @ddff_lv,

    Sorry to hear about this, could you drop us an email to with some more details so I can look into this for you.

    Best Regards,


    Hi @ddff_lv ,

    Sounds like a feedback loop caused by the tie-lines to the JoeCo feeding back into itself via the Virtual SoundCheck routing when the JoeCo playback is stopped.

    The Virtual SoundCheck feature has a Record Send option – this uses the VSC routing to output audio to the VSC device and maintains your “normal” input patching. I would suggest removing your tie-line routing to the JoeCo and instead use the Record Send mode in VSC to achieve the same results, albeit without the feedback!

    Best Regards,


    Hey @neakmenter

    Really pleased to hear you’re enjoying the dLive system so far and thanks for the feedback and suggestions also 🙂

    Regarding your issues with OneMix losing configuration and scene recall times, would you mind dropping us an email to with your show file and also information on how the iPads are configured on the network (i.e. IP addressing etc) so I can take a look for you.

    Best Regards,


    Hi all,

    This is not something we often see and it sounds as though you have been through most of the troubleshooting already. You did ask about calibration too though, so if you haven’t;

    1. Backup all shows/scenes that are needed.
    2. Perform a hard reset on the unit (holding reset and setup buttons for at least 5 seconds when powering on the Qu)
    3. Format a compatible USB key in the Qu
    4. Reinstall the latest firmware (using the key you just formatted)
    5. Perform another hard reset and check firmware version is ok
    6. Calibrate touchscreen and faders (Setup > Utility > Calibration)

    Then before loading shows/scenes again, see if you have the same issue.

    I know some of this sounds basic, and you don’t need to do this everytime you want to calibrate, but it’s the best way of ruling-out any firmware/software issues.

    If you are still seeing the same thing happen – then as Harry suggested, you should contact your distributor who will need the desk back to check hardware. ( )




    Have you seen our knowledgebase article on the subject of gigaACE on a network?



    Please send us an email with as much detail as possible to so we can look into this for you.



    Please can you send in an email to with the details of your system so we can look into this.

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