[MikeShandParticipant]

You can certainly do that. You can assign a single input port to multiple channels and hence faders. You can either do this in the preamp page (choose the input port you want assigned to that channel), or the io page (select the input port and then choose the channel you want to assign it to. Use info at the bottom to find what is already assigned. Each channel you assign is added to the set. Use “unassigned” to clear out the list.

See page 8/9 of the manual for details of assigning via the preamp page, and note what it says about trim on surface etc. Basically you can only control the preamp gain of the input port from one place, but on the other channels to which it is assigned you can use trim to adjust the level up or down from what the port gain is giving you. But note that changing the preamp gain will change all the channels.

See the manual page 34 for info about setting via the io page.

Hope this gives you a start.

Mike

[MikeShandParticipant]

Never seen that problem. Have you tried the usual iPad tricks?

1. Shutting down the app (press home 3 times quickly then swipe up) and restarting
2. Deleting and reloading the app.

Might help.

Mike

[MikeShandParticipant]

There is certainly nothing published. I suspect AH don’t want to make that publicly available. My guess is attempting to reverse engineer that would be quite challenging if the show file format is anything to go by. I took a look at that in the hope it was some nice XML so I could print out configurations, but it turned out to be an archane binary format.

[MikeShandParticipant]

When I looked at this some time ago I couldn’t see a way to do what you want ( but that may just be me). You can set the faders to a particular position via midi, and you can get midi messages when you move them, so I was thinking of starting off by setting them all to zero to get a known state. I was looking at this because I had a similar idea of writing some python code to interface to the GLD from a raspberry pi. However I never got any further than thinking about it.

I’d be very interested in what you have done.

Mike

[MikeShandParticipant]

Well side chain would be nice to have, but I’m not sure I would be prepared to pay much for it. Say £100 max.

What I WOULD like is multitrack recording as on the QU, but I can already get that by paying £900 or so, and for that I get ALL the channels, so again it would need to be significantly cheaper than that.

More mix busses would be wonderful. I’d pay a fair bit for that, but I won’t hold my breath.

Mike

[MikeShandParticipant]

See section 10.10 on pages 58ff of the manual. Note that you can have up to 100 individual scenes per show on the QU and as many shows as you like (within the limitations of the memory or USB stick etc.)

When you save (or recall) a scene it is saved into (or recalled from) the current configuration in the desk. If you want that configuration including all the associated scenes saved, then save it as a show.

Mike

[MikeShandParticipant]

A show saves the entire setup of the desk including scenes, libraries and all the various settings ( with one or two exceptions). Crucially, You can only recall shows in their entirety.

A scene saves most, but not all of the settings on the desk. However the crucial difference is that you can control which aspects of a scene are recalled using filters. So for example you could have a scene that only changes a single channel or group of channels. Or one that just changes some compressor settings etc.etc.

Hope this helps you understand the difference.

Oh, and in general you don’t want to be recalling a show during live sound. It typically takes a few seconds and goodness knows what happens to the sound during the recall. Whereas a scene recall is much faster and can be used in forcexample live theatre ( with certain oft expressed limitations).

So shows are for…. entire shows, and scenes are for… well… scenes!

[MikeShandParticipant]

I did have a look at doing this for the GLD a while ago. But unfortunately the show and scene files are not in something easy to parse like XML, but in an arcane binary format that I didn’t have the enthusiasm or time to reverse engineer. I assume the QU will be similar. I can see why A&H would do that. All the more reason for them to supply the tool.

I too would find it very useful if it worked for GLD as well.

[MikeShandParticipant]

Back in the dark ages before Ethernet was invented, I worked on a LAN technology called Cambridge Ring. It used a phase locked communication over two twisted pairs. We tried to run it between two buildings about 1/2 mile apart connected by a CCTV multicore cable running in a duct. After a LOT of experimentation we discovered that for reasons of minimising cross talk the video cable pairs had different rates of twist and were consequently of a slightly different length. We inserted an extra 1.5 metres in one of the pairs, and hey presto it all started working.

And now back to your scheduled programme.

[MikeShandParticipant]

I’m afraid that is becuase there ISN’T a way to make a read only template like the factory templates. The above suggestions are offered as workarounds.

[MikeShandParticipant]

Use Ganging? Or a DCA.

[MikeShandParticipant]

They should just be there! Load the show in the editor then press scenes and they should all be there. You are actually loading the show aren’t you?

[MikeShandParticipant]

My understanding is that rtp-midi is an implementation of midi over RTP not TCP. Can it be configured to run over TCP?

[MikeShandParticipant]

The processing is IN circuit or OUT of circuit.

[MikeShandParticipant]

You certainly can do that, but my preference would be to use a mono aux fed post fade from just the speech mics (or whatever else you wanted). That way you get to send ONLY what is necessary to the loop. You could also add an ambience mic to that, but my experience is that just makes things LESS intelligible. Sadly there is no ducker on the GLD, otherwise that might work well with the ambience being ducked by the speech mics.

[Author]

Posts