[MikeShandParticipant]

Interesting. That does sound similar, but I hadn’t done anything strange. I just powered on as normal. We use an EMO power sequencer, so I suppose it is possible that somehow it glitched, but that seems unlikely.

Thanks for replying.

[MikeShandParticipant]

Hi Dan,

Wow! That’s a long time ago, and I really can’t remember, or even understand my own post!

To give you some context, I was writing a python program running on a raspberry pi to interact with the GDL via midi. My memory is very hazy, but looking at the code it seems to be the case that pressing a mute button on the GLD sends a midi message saying it has been pressed, but doesn’t change the setting of the mute light on the surface, so what I do when I receive a mute pressed message is perform the actions I want, and then send a message back to the GLD to toggle the state of the light.

The midi configuration of midi channel 1 mute switch is

91,00,<VAR> local OFF

i.e. local is off. Hence pressing mute doesn’t change it on the surface.

See this snippet of python code in case it is any help at all.

elif m.type == ‘note_on’ and m.channel == 1:
if m.note < 0x20:
# MUTE
strip = m.note
if m.velocity >= 0x40:
print(“MUTE ON”, strip + 1)
# toggle the current mute setting for this channel
newMute = not lights[strip].getMute()
lights[strip].setMute(newMute)
# and echo it back to the GLD
sendMute(strip, newMute)

and sendMute is defined as

def sendMute(strip, muteOn):
“”” Send midi strip mute setting message to GLD.

MUTE ON send velocity 127
MUTE OFF send velocity 0
followed by note off
“””
if muteOn:
vel = 0x7F
else:
vel = 0x3F
muteMessage = Message(‘note_on’,
channel = 1,
note = strip,
velocity = vel)
gld.send(muteMessage)
muteMessage = Message(‘note_off’,
channel = 1,
note = strip,
velocity = 0)
gld.send(muteMessage)

I hope this might be of some small help to you, but I rather suspect not.

Mike

[MikeShandParticipant]

I’m not aware that you can adjust the amount of dim. You can only turn it on or off via the source screen on the talkback page.

[MikeShandParticipant]

If you haven’t already done so, you should get hold of the reference manual at

https://www.allen-heath.com/media/GLD-Touch-Screen-Reference-V1.5_1.pdf

And less useful, but still containing some key information, the user guide at

https://www.allen-heath.com/media/GLD-Chrome-User-Guide-AP9989_2.pdf

[MikeShandParticipant]

Any chance the scenes are changing the state of phantom on an open channel?

[MikeShandParticipant]

I don’t know about the SQ, the problem may be fixed there, but on a GLD, if you have phantom on an input, and you leave the fader up when you power down, then on power up you will get a pop as the phantom engages after the mixer has booted up. Since it takes a few tens of seconds to boot this comes AFTER the sequencer has turned on the amps. Our sequencer doesn’t have an adjustable delay. It is fixed at 10 seconds, although I am told that by jusicious changing of the components in the RC timing network, this can be extended. I haven’t tried that yet though.

Other than that, the sequencer works fine with the mixer and ar2412 on the first feed and the amps on the second.

It doesn’t always get powered off using the GUI before the power is cut, but that has never caused any problems. In theory, I believe, it may not correctly save the state if something has changed just before the power is cut, but that is unlikely. I guess there may be a slim chance that something could get corrupted if the power was cut while it was in the process of writing to the SSD, but I’ve never observed that. Always a good idea to keep a backup show on a USB stick though.

HOpe that helps.

[MikeShandParticipant]

OH! Will it need a new version of the iOS app? I know they are not backwards compatible, but are they forward compatible? Or is this too small a change to affect it?

[MikeShandParticipant]

According to the release notes it fixes some bugs in AMM which apparently were introduced by 1.60 . I haven’t observed those bugs, but there I did notice that 1.60 changed AMM such that My scene turning it on no longer worked and I had to set it up again. The more worrying bug is that power cycling can cause AMM to not pass audio, and since we use AMM for unattended operation and sometimes people forget to power down properly this might hit us.

So it looks like I had better do the update.

Slightly concerned by CHris’ observation. Can anyone confirm all is OK?

[MikeShandParticipant]

I wonder if you also need to enable the gain etc. In the channel. There are a number of things like that where you need two things enabled for them to work as you expect. Just guessing, since I can’t try it in the editor, which doesn’t do user stuff, and the GLD is in the church.

[MikeShandParticipant]

I’ve never tried this, and it would probably be too much hassle, but I THINK you could probably do this with a pc. Attach it, or copy the show using a USB, then with the network detached, make the required edits on the PCC, save the scene, then reconnect and save to the gld. Something like that. I’m just not sure what happens when you reconnect, but I think the PC sets to the current gld faders rather than the other way around.

But even if it works, it’s not exactly straightforward.

Mike

[MikeShandParticipant]

Can we see what the “various minor fixes” are?

[MikeShandParticipant]

Yes that will work fine. We did that with our gl2400 before we replaced it with a GLD.

[MikeShandParticipant]

So, You can have channels in multiple DCAs?

Certainly. No problem. Just add them.

[MikeShandParticipant]

You have a number of options…
When you assign the channel in the I/O Monitor tab, you can choose where you want to take the output from. Of particular interest here are

Input Direct Out
Input Socket
Mono (or Stereo) Aux

Direct out allows you to select any takeoff point you like (press select on any channel strip, choose the routing tab, and look at the Dir OUT SRC popup tab at the bottom. This will offer you Post..
PreAmp
HPF
Gate
Ins Ret
PEQ
Comp
Delay

BUT remember this is a GLOBAL setting. i.e. ALL direct outs have the SAME takeoff point.

Input Socket is equivalent to post preamp, but this allows you to have some aviom feeds effectively post preamp, and then set the global direct out to something else (say post EQ) and use that for other Aviom feeds, but if you are using direct out for some other purpose, like a per channel recording feed, remember that you may have a conflict.

The other more flexible alternative, if you have the luxury of AUX busses to spare, is to assign the Aviom feed to an AUX bus. Then you can assign one (or more) channels to the Aux bus as required, but critically the takeoff point when assigning to an AUX is per AUX, as opposed to global for direct outs. So you can, if you desire, have different AUXs with different takeoff points.

Hope this helps.

[MikeShandParticipant]

Are you logged in as an admin user? I don’t think you will see those settings with a restricted user.

For meters see page 18 of the touch screen reference manual. You basically just drag and drop the ones you want onto the custom page..

Hope that helps

[Author]

Posts