Highlight is behaving weird

Hi there,

I've tried to look this problem up, but I couldn't find an answer yet.

When I'm using Highlight on my Ion the <thru> button doesn't work when I have my flexi set to 'Active channels'.
If my flexi is off/all channels and when I turn off the Highlight function it works fine.

This has happened before, but most of the times I could fix it with <Go to cue -> out>
Since the 2.3.2 update that doesn't work anymore.

It looks like a bug to me, but I could be wrong...

Is there a function that I'm missing here?

Parents

0 ueliriegg over 9 years ago

thru will respect the flexi state. basically of the first and the last channel of your range are on screen, only channels in between them will be selected of they are already on screen.
try using Thru Thru in those situations
Cancel
Vote Up 0 Vote Down

Sign in to reply

Reject Answer

Cancel
0 Joostlim over 9 years ago in reply to ueliriegg

This works for me, thanks!!

However it doesn't make sense to me.
The channel list should be only used as a reference of what is active or not in my opinion (like the most lightdesks). The flexi state is in this case only to filter out all the unused channels.
Normally (without highlight) it works like this, why is it different in highlight mode?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 ueliriegg over 9 years ago in reply to Joostlim

uhm, it works the same in regular as in highlight mode... in Live, with the golden border around a live tab that has e. g. flexi active, select a channel that's currently on screen, thru, and another channel that's on screen but after a gap. only channels that are previously on screen will get selected.
I'm not aware of a difference between behavior in and outside of highlight...
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Joostlim over 9 years ago in reply to ueliriegg

Ok that's weird.

I just checked, and it works the way I was telling.

When I type:
<1 thru 20 #>
Every channel between 1 and 20 becomes active (It doesn't matter which flexi state I use)

When I do the same with highlight on, only 1 becomes active (or like said earlier the channels which have been selected before)

So yes it looks like there is a difference in behaviour.
This is the situation on both Ion's we have here...
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Reply

0 Joostlim over 9 years ago in reply to ueliriegg

Ok that's weird.

I just checked, and it works the way I was telling.

When I type:
<1 thru 20 #>
Every channel between 1 and 20 becomes active (It doesn't matter which flexi state I use)

When I do the same with highlight on, only 1 becomes active (or like said earlier the channels which have been selected before)

So yes it looks like there is a difference in behaviour.
This is the situation on both Ion's we have here...
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Children

0 ueliriegg over 9 years ago in reply to Joostlim

and in your example, channel 1 and 20 were both already on screen when you selected them in regular mode ?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel