Mixpad fix ID-1586 (remote devices limit) missing from software

Forums Forums CQ Forums CQ feature suggestions Mixpad fix ID-1586 (remote devices limit) missing from software

Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
    Posts
  • #124780
    Profile photo of RenZORenZO
    Participant

    About this fix :
    ID-1586: No reason given when maximum number of remote devices exceeded.

    Android MixPad 1.2.0 says :
    A maximum of 2 CQ Mixpad connections, or a single editor sync session are allowed.

    But it’s missing from Windows software. By the way, I don’t have any Mac to try.
    I guess it’s an oversight 🙂

    #124804
    Profile photo of guitarplayerjaxguitarplayerjax
    Participant

    Does this mean can’t have more then 2 wireless connections to the CQ mixers? A limit of two connections seems very low to me. What if soundman wants to have 2 or 3 tablets connects left set to different screens and maybe some band members also want to be set up to adjust their own IEM mixes. The wireless connections to the mixer could add up quickly.

    #124860
    Profile photo of D3nn15D3nn15
    Participant

    As far as I know, the device has 2 full sessions as standard with additional (limited) sessions for only the IEM / Monitor channels. (cq4you) So this is not a problem

    #124866
    Profile photo of RenZORenZO
    Participant

    Yes, the limit concerns MixPad, soundman can expect to use a main computer on a desk, and a tablet/phone to move around.
    Also, there is the CQ screen which allow settings on scene, usefull when everybody is plugging.
    Then as said by D3nn15, CQ4You is for IEM and wedges. I think the limit is 6.

    For Allen & Heath : my post was just about the message, updated on Android but not on Windows version.

    #124873
    Profile photo of SteffenRSteffenR
    Participant

    Help file installed with the MixPad app on my Win11.

    Attachments:
    You must be logged in to view attached files.
Viewing 5 posts - 1 through 5 (of 5 total)
  • You must be logged in to reply to this topic.