[jcarterParticipant]

Could the faders have been incorrectly calibrated at some point?

Might be a good idea to have your customer run through the fader calibration routine to see if that fixes the problem.

[jcarterParticipant]

When we were demoing a GLD I asked the (Canadian) distributor’s product rep about this.

His response, as I recall, is that the extra latency in the longer signal path is automatically compensated with a delay added to the shorter signal path, in order to keep the two signals in phase when they hit the LR bus.

So as long as all signals stay inside the GLD I wouldn’t expect to hear any comb-filtering between different signal paths (if there’s any external hardware inserted in one of the signal chains all bets are off, of course).

Not sure if the *total* latency of the console is constant (based on the longest possible internal routing path) or if it depends on the routing.

[jcarterParticipant]

Good to know, thanks!

[jcarterParticipant]

quote:

---

Originally posted by Chris93

Yep, you’ve recalled a scene in which your softkey assignments aren’t the same as they were in the previous scene.

Can softkey assigns be scene safed?

Chris

---

In practice it probably doesn’t matter. There’s no general “next scene in cue list” softkey function, only recall of a specific scene, at least as of v1.0.2 of the firmware.

It’s still possible, as I understand, to set up a show where you want to advance scenes via softkey. However, the “advance scene” softkey will be different in every scene…

-in scene #1 the “advance scene” softkey will recall scene #2
-in scene #2 it has to recall scene #3
-in scene #3 it will recall scene #4
-etc.

Therefore, in any show using softkeys for advancing scenes you can’t scene safe them.

[Author]

Posts