ION in man mode

I also noticed that when I open another file, save it then open the church file the Playback Status screen is blank until I hit GO, then it populates and the first cue activates.

I sounds like someone has put the console in Manual Mode. Press [Fader Controls], you'll see a Manual Override softkey, press and hold the softkey and press the master load button. If the console was in this state, this will toggle it off.

It could also be that someone has pulled down the master playback faders as I think this displays Man as well. It definitely puts the cue in a red state as it's waiting for you to push the faders up.

Jeff Toussieng said:

I also noticed that when I open another file, save it then open the church file the Playback Status screen is blank until I hit GO, then it populates and the first cue activates.

This is correct, it doesn't know you've loaded the same showfile, so sits you at the top of the stack. It doesn't remove channel values which is also correct as you wouldn't want the desk to fade to black/out.

Hope this helps.

Nick

Faders are down. Will check between services. I don't like doing stuff live during a service. :-) Will lyk. Thanks. sounds like the faders.

faders were down so that fixed it. I do find it interesting they affect that. Aren't the faders technically 10 and 0 and 0 and 10 to allow smooth cross fading? So I don't understand fully why they do that to GO.

the faders aren't intensity masters but the represent the progress of the crossfade. if both are at the very bottom, the crossfade can start but will be "blocked" by the faders because the represent no progress.

The bigggggg deal is your answer fixed it. I mentioned it to a couple of other users at church and one told me it happened to him a while back (most likely on the Element which is the church console) I have my ION in there for an event we are doing next weekend. So thanks so much.

Regarding the cross faders it really is a mystery to me how up or down affects the GO but in reality since I know they must be up then that's the important thing. I see them as when both up one is full and the other one is off. When down the opposite is full and the other off. When I mean full or off I mean all the way to the next cue and the last cue all the way out. I'm seeing them as taking the currently running cue and crossing it to the next cue. When operating in manual that way I would think they would be pushed up all the way for the next cue then down for the next cue then up for the next cue then down for the next cue and so on.

Instead do they work this way: push them both up for the next cue, then back down and wait. push them both up again for the next cue then back down and wait and so on?

I never use manual so I am clueless. :-)

The thing to remember is the left fader can manually control the timing of whatever is happening in the cue you are going to, while the right fader is manually controlling the timing of the cue you are coming from.  

If the cue is always going to be a cross fade, then you need some form of manual over-ride for whatever unplanned timing change needs to happen.  It makes no sense to have them configured as left fader down, right fader up, even though there is logic to it.  It's just easier if you find yourself needing to over-ride, to grab both faders, lower to match (or lower to bottom) and using one hand, manipulate the cue.  

Note that this function goes back to the Concept console ?, so better then 25 years.  It's a function and logic inherent in every ETC desk since and if the operators learn it, they will know how it works across generations of consoles they may encounter.  

As well, ETC put a manual master cross-fader function into the later releases of the Eos line, that allows you to skip the Go button,  You just slide both faders up, the next cue in the stack is loaded, run the faders down to execute in a manual time, and the next cue loads in the stack.  A European work method.  

Since I never use that function and I have never operated an ETC console other than Element and ION I am unfamiliar with this function and will definitely play with it to see if it's something I would like to use. Not saying anything is wrong with how it works. The concepts I am used to working with on consoles is that one fader shows 10 at top and 0 at bottom and the other shows 0 at top and 10 at bottom. This is a two scene mode thing. Both faders remain side by side once the first scene is up. Take a 24 channel console. Set it to 24x24 or two scene mode. There are 24 faders across the top row and 24 across the bottom. Top row is A and bottom row is B.

To start the event place the cross faders at opposite ends so they are both at 0.

Set all the channels for the first scene on A to what is desired and the B faders for the second scene. Nothing is going out because both cross faders are on opposite ends which is 0. Slide cross fader A only to 10 and the first scene goes up. Now both cross faders are sitting side by side, A at 10 and B at 0 and the channels are up and running in A. Slide the faders together and A starts lowering and B starts raising, thus a smooth cross fade. Once they are at the other end and B is running then re-set the A channels for the third look and when ready for scene 3 slide the faders together again and B starts lowering and A starts raising. Repeat this for each scene. The most generic cross fading.

So that is where my thinking is coming from regarding the use of those two faders. Thinking it's not cross fading pre-recorded cues, it's cross fading manual channels from scene to scene while they are manually set during the time the last scene is running. I can see this is not how they operate on ETC consoles for a whole lot of good reasons.

Again, I will have to play with it on the EOS family. I might find it very useful.

Thanks again for your assistance.