Forum Replies Created
-
AuthorPosts
-
2014/11/28 at 3:41 pm #43416
The way I understand the GLD operation is as follows
CURRENT always gives the name of the most recently recalled scene. But of course as soon as you make ANY change on the board what you have no longer corresponds to the “current” scene. It is the current scene plus the changes you just made. I guess something could be put in the GUI that indicated that you had changed something, but I really don’t see how that would be helpful since either
1. You are trying to change the stored scene, in which case you do recall, make your changes, save, or
2. You are actually using the scene to do something, so you will almost inevitable make some change or other almost immediately after recalling.
In either case you kind of know that what you have on the board is different from the most recently recalled scene.The only exception to the above is when you first boot up, when current is blank , not unreasonably, since you haven’t yet recalled a scene.
NEXT always show the name of the scene which is selected in the scenes menu. So if you do a save it will save the current state of the board overwriting THAT scene name. Similarly if you do a recall it will recall that scene replacing whatever configuration you currently have on the board, modulo scene safes and filters of course.
On boot up this is not unreasonably set to scene 1.
Auto increment is simply equivalent to moving the selection down one.
I don’t do theatre so don’t really understand what the requirements are there, but for my uses the above arrangement seems perfectly logical and useable.
I haven’t noticed any random behaviour or any which isn’t explained by the above semantics.
Mike
2014/11/23 at 7:17 pm #43253I can’t check right now, but I’m pretty sure that PFLing a DCA gives you all the channels that the DCA is controlling. And yes, you can definitely set additive PFL mode.
2014/10/08 at 9:20 pm #42080+1 for the trim control on the USB recording. Mix outputs are a really scarce resource for me, so this would be helpful. As would be not having to configure them in pairs, but I’m guessing that is not an easy fix.
And of course the mute on phantom settling, especially at power up would be a life saver.
2014/10/03 at 5:24 pm #42005Yes, that would be nice for a scene recall too so that the board went to a known state. Or even all three. i.e. assign a soft key that recalls a scene, sets the mix to LR AND sets both banks to A layer. A similar result could be acheived if a scene could set mix and layers.
2014/09/28 at 7:52 am #41877Good thinking John, but no. I have all soft keys globally scene safe, AND blocked in the specific recall filter for this scene.
Actually I had recently made them NOT globally scene safe, but still filtered in this scene, but I just went back to an old show where all the soft keys are scene safe, as above, and it makes no difference to the behaviour. It really does seem that the LED on the scene recall soft key is reflecting the PAFL status. Perhaps this is intended behaviour, but it is confusing. But that doesn’t explain why it only does the scene recall every second press. I could sort of understand it if it never re-recalled a scene if that was the current scene, but why, then, does it actually do a recall on the third press?
For comparison, if it set it to a simple scene recall, then the LED comes on when you press it, and the scene gets recalled again for each subsequent press, leaving the LED on. So the behaviour above is definielty linked to the PAFL.
I’m only doing the sel mix pafl scene recall so I can force the LR mix key on when the scene is recalled. I wonder if there is some other way I can acheive that. But I haven’t found any other way so far.
2014/09/27 at 1:36 pm #41857Ah, its more complicated than that. I am actually using Sel Mix PAFL Scene with Mix PAFL type and an associated scene and main LR as the channel. The idea being to force the mix setting to LR on loading the scene, to avoid any subsequent foot shooting. (I don’t actually want the PAFL, but there is no “mix only” type.)
When you first press the soft key, it loads the scene as expected, and turns the LED ON. However, the LED seems to be associated with PAFL, becuase it you clear the PAFL, for example by pressing the default assigned soft key 9, the LED on the original soft key is toggled off.
Moreover, if you press the soft key once, it loads the scene as expected, but the second time you press it it DOESN’T re-load the scene. e.g. if you move the faders (level being allowed in the scene recall filters), they are NOT reset by pressing the soft key. But it does toggle the LED OFF and clear PAFL. Pressing the soft key a THIRD time DOES load the scene again, and turns the LED ON as for the first press.
Weird!
Anyone know what is really going on?
2014/09/26 at 1:58 pm #41842Tried the 20db pad trick this moning, and it may be a one off but it seemed better. Just a click and no feedback. I’ll see if it stays that way.
2014/09/25 at 4:35 pm #41839Hmmm. I wonder if putting the 20dB pad in and turning up the gain by 20dB would help mitigate it somewhat? Assuming there was still enough gain for the mics. I’ll give that a go next time I’m in church.
2014/09/25 at 3:46 pm #41837My phantom mics are all on the AR2412. Haven’t tried whether it happens on the surface inputs. I had assumed it would be the same, but you never know. Interesting you mention the feedback. I get that too, and had kind of assumed it was kicked off by the pulse of sound into the room, but I’m wondering now if the gain is actually changing as the thing comes on. Need some more experiments.
2014/09/25 at 3:07 pm #41835I tried putting gates with pretty long attack times, but at the sort of times that are still viable for normal operation it doesn’t make a great deal of difference, presumably because the “signal” is so large. Strange that you didn’t have it before and now you do. I’m running 4.1. I’m looking at getting the power sequencer modified to bring the amps up after the GLD has booted, but that length of delay isn’t standard, so I’m not holding my breath.
Sorry QU folks for hijacking your thread. Does the v1.5 fix on the QU fix the power up problem as well as the originally reported phantom status change issue on scene changes?
2014/09/22 at 12:32 pm #41791Any chance we could have this on the GLD? And if so would it apply on power up? The problem we have is that sometimes people shut the desk down in a hurry leaving a fader up un a channel with phantom enabled. Then when we turn it on again we get a thump as it finishes booting. We DO have a power sequencer, but unfortunately the delay is not long enough to accommodate the boot time. So the power comes on to the gld, then to the amps, THEN the gld finishes booting and… Pop.
Obviously the solution is “don’t do that”‘ but inevitably people do!
2014/09/14 at 2:11 pm #41618Yes, run them from a matrix fed from LR.
(Sorry George, posts crossed.)2014/09/10 at 5:13 pm #41517Thank you. So good to have it back!
Mike
2014/09/03 at 2:55 pm #41484Thanks, Cornelius, that certainly does the trick.
Wise words George, and I totally agree. But for some (e.g. early morning) services we have no option but to present people with a VERY simple interface which only operates the speech mics.
Thanks to both of you.
2014/08/01 at 8:48 am #41190Thanks Nicola. That seems to work very well. I can also include fader levels and mutes to set different defaults for matrices etc.
Mike
-
AuthorPosts
