Forum Replies Created

Viewing 5 posts - 16 through 20 (of 20 total)
  • Author
    Posts
  • #37432
    Profile photo of Mark McFarlane
    Mark McFarlane
    Participant

    OK, I guess we can’t upload show files.

    #37431
    Profile photo of Mark McFarlane
    Mark McFarlane
    Participant

    As a full disclosure, this was my first concert on my new GLD112, but I am not a newbie. I have over a decade working regularly on digital consoles.

    For fun, I’ve attached my show file which was saved at the time I noticed the monitors went dead, in case anyone wants to look at it.

    #37430
    Profile photo of Mark McFarlane
    Mark McFarlane
    Participant

    Chris, Aux 1-6 were all patched to sockets. Aux 1-5 were pre-fder, 6 was post fader as you suggested. However, since I didn’t bring subs I didn’t have anything being sent to the subs, so there was no signal present anywhere on Aux. Unfortunately, not any useful new diagnostic info here, but a nice try, thanks again. 🙁

    #37410
    Profile photo of Mark McFarlane
    Mark McFarlane
    Participant

    To calrify, the subs were on Aux 6. Aux 1-5 were the ones that went dead.

    #37406
    Profile photo of Mark McFarlane
    Mark McFarlane
    Participant

    Thanks Chris for the help.

    I used the touchscreen meters to look at the aux signals immediately before and after the fader. There was signal before the Aux1 through Aux5 faders, and no signal after the aux faders. he faders were ‘up enough’ for the show volume (-30 DBFS).

    I only had 4 DCAs setup, none of then are connected to Auxes except my ‘Master DCA’ which controls L,R,M, and an Aux for subs.

    Today I made a new fader layer and put all 16 DCAs on it and reconfirmed that none of the DCAs are connected to the monitor axes except my one ‘Master DCA’ fader which was not connected to Aux 1-5, only Aux6 which I use for subs. Actually, there were no subs at this gig so I can’t comment on whether Aux 6 was also dead.

    Again, recalling the show file didn’t fix the problem, but a reboot followed by the recall fixed the problem.

Viewing 5 posts - 16 through 20 (of 20 total)