Coming from TiVo, I was able to use “Or” conditionals when setting up a season pass. Does channels offer similar functionality as it appears that all conditionals are stringed together as “And”, so if one condition is false then all the other conditionals are ignored. Am I missing something?
use contains ...
EXample.
Conditions
Tags == New
Channel CONTAINS 2.1
Channel CONTAINS 6.1
Channel CONTAINS 8.1
Channel CONTAINS 32.1
Channel CONTAINS 12.1
Time CONTAINS 8pm
Time CONTAINS 9pm
Time CONTAINS 10pm
Genres EXCLUDES News
Title EXCLUDES SIGN OFF
I'm not seeing CONTAINS as an option for Channel. Only ==, !=, < and >
1 Like
Right now, the advanced editor for passes is missing a few things with the latest releases.
NFL Pass parameters different - General - Channels Community (getchannels.com)
What does != do? I'm assuming the last 2 are less than and greater than.
Not equal
1 Like
In the latest prerelease there's these four
==
!=
CONTAINS
EXCLUDES
1 Like
Yeah a lot was dropped like greater and less than.
1 Like
With the last release with the updates to the pass modal, things did change.
In the current pre-release, Channel had Contains added back to it.
If there are other issues, discrepancies, or fields missing operators that would be helpful, please report them here in this topic.
missing > <
For what field? Please be more specific when reporting this.
Channel < 6000
Channel > 700
2 Likes
Ok. This is certainly a weird suggestion, which is why I did not include it. (In the interest of not overwhelming or confusing the user with many options).
Can you give some examples why it’s useful over?
It is not Weird at all my Cable Channels are from 702 to 825 my TVE are 6000 ...I want my movies to record on my Cable Channels and not TVE because they have better audio... But I want certain TV shows that are in re-run to record on TVE channels 6000 and above.
If I were to do that with contains my Pass would be over hundred contains long.
PS I have passes setup that way, but this feature was taken away.
Add to that users with an ATSC 3.0 tuner that want to select whether it records from an ATSC 1.0 or ATSC 3.0 channel.
ATSC 1.0 Channel < 100
ATSC 3.0 Channel > 99
Example from today
@maddox +1 on this. I use this a LOT in lieu of not having to define every channel I want or don't want. I have existing passes that are using channel < 100 to narrow it to OTA recordings. My existing passes are OK but I can't create new conditions with <>.
Avoiding ATSC 3.0 channels
< 100
Instead of CONTAINS or EXCLUDES
1 Like
Just don't remove Channel CONTAINS and Channel EXCLUDES
They are also useful
Would like to see
Channel ==
Channel !=
Channel <
Channel >
Channel CONTAINS
Channel EXCLUDES
2 Likes