thru-on function

maybe i'm misunderstanding, but isn't Select Active doing what you want?

[1][Thru][101][SelectActive]

If I'm correct this also selects channels that have gone to zero (green) or contain a move on attributes. Thru-on only selects channels with levels greater then or equal to 1%

[Select Active] does not include channels at zero.

uhm, actually, i think you're wrong.

the 2.0 manual on p.153 says:
"The [Select Active] key is used to select all channels that currently have intensity levels above
zero. Pressing [Select Active] once will capture all active levels. Pressing [Select Active] twice
will capture all active manual levels and those from playbacks except for submasters. Select
NonSub Active will post to the command line."

Thank you very much! This is a huge time saver. I couldn't find it in the manual at first. 

Ueli - if that is what is written in the manual, then that is slightly misleading

Select Active once selects all channels with levels above zero (manual, from cue lists and submasters)

Select Active twice excludes submaster contributions (collecting channels with levels above zero from manual and cue lists)

These commands can be appended to a channel list to narrow the selection.

The copy should read "Pressing [Select Active] twice will select channels with manual and playback intensity values above zero.

(I thought you were on holiday!)

Thanks!

a

i copy/pasted from "Eos Titanium_ Eos_ and Gio_v2.0_Operations_Manual.pdf" but hadn't realized i still had the preliminary version. the wording hasn't changed, but the page has. it's now p.158 (printed page 176).

(holidays over. have some days off, but i'm back home)

Thank you for your answers. I understand that other consoles of the family (except ion) have a dedicated button for "Select Active". On the ion you have to first [SHIFT]+[Select Last] and then press the softkey {Select Active}.

For me (even with the dedicated key) the fastest way to get to the Select Active function would still be [SHIFT]+[THRU], as this doesn't interrupt the flow of typing.

As @MikeEvers suggested in another thread, maybe Chan#[THRU][THRU] could be for selecting a channel range until the next gap in patched channels.

Then you switch consoles new key strokes are always going to feel slower then your normal console, this is because you need to think about the syntax. I worked on a strand for over 10 years and if I then back to that console Thru On would feel wrong and slow after 6-7 years on Eos.

Every effort is made on Ion to make it as quick as possible but this can't be at the decrement of the higher end consoles, this is why a lot of people invest in some form of x-keys.

Thru Thru is already a valid syntax to select channels out of your current flexi state.

Then you switch consoles new key strokes are always going to feel slower then your normal console, this is because you need to think about the syntax. I worked on a strand for over 10 years and if I then back to that console Thru On would feel wrong and slow after 6-7 years on Eos.

Every effort is made on Ion to make it as quick as possible but this can't be at the decrement of the higher end consoles, this is why a lot of people invest in some form of x-keys.

Thru Thru is already a valid syntax to select channels out of your current flexi state.

I agree. Thanks again!

I must add, that in favour of the lower end consoles, most of the time the less keys there are the faster you can operate, because your hand can stay where it is and your eyes can stay on stage... but I understand that more keys and faders sell better ;-)