Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[tzr916]

11. Changed: Removed the custom expressions "TVInfo(ChannelKeywords)" and "TVInfo(IsOnNonTopGroupedChannel)" from the default Theater View Television Guide setup since they are now handled differently and more efficiently.

Does this break custom guides? Such as:

Code: [Select]

-[=TVInfo(ChannelKeywords)&DataType=[List]]=[Favorite]

Code: [Select]

-[=TVInfo(ChannelKeywords)&DataType=[list]]=[OTA]What's the new method to accomplish custom guides?

[Yaobing]

Does this break custom guides? Such as:

Code: [Select]

-[=TVInfo(ChannelKeywords)&DataType=[List]]=[Favorite]

Code: [Select]

-[=TVInfo(ChannelKeywords)&DataType=[list]]=[OTA]

No it does not break custom settings.  Your expressions will still be honored.  I only removed those two expressions from the default template.  So future users will not have those two in the template.  For current users, those will remain until you do a Theater View reset.  For you, or any other user with custom settings, you obviously don't want to do a reset, but you can manually remove those two expressions.

What's the new method to accomplish custom guides?

Custom expressions will still be evaluated.  Only the following two expressions will not: will not be directly evaluated when dealing with Theater View guide:

Code: [Select]

-[=TVInfo(ChannelKeywords)&DataType=[List]]=[Hidden]
[=TVInfo(IsOnNonTopGroupedChannel)]=[0]

These expressions are slow to evaluate, and since they appear at the initial filter of the guide, and thus affecting ALL guide entries, it made displaying of guide very slow.

Important: These expressions are no longer needed for Theater View Guide, but their functionalities are NOT removed from MC.  They will still function as they were designed to do, and you can still use these expressions (although there are not many/any? places where you really need them).

[tzr916]

Thanks Yaobing. I have tested, and all my guides look good.

[Yaobing]

I will use this thread to explain some more on it.

Remember I talked about the "parent" of your custom views?  Here is what I meant:

In Theater View, you have Audio, Image, Video, etc.  Under video, you have Movies, Shows, and Guide.  And under Guide, you have various ways of showing parts of guide entries:

Video/Guide/Guide
Video/Guide/Favorite
Video/Guide/To Be Recorded
Video/Guide/Search
etc.

In your case, you have
Video/Guide/Client Guide
Video/Guide/Server Guide
etc.

The bold face part is what I meant by "parent" (the second portion). 

Your custom rules (OTA, Favorite, etc.) are rules for the third portion of those paths.  The default rules for the second portion (Guide) are the following:

Code: [Select]

Custom: [TVTime]=>#TVGuideStartDate
Custom: -[=TVInfo(ChannelKeywords)&DataType=[list]]=[Hidden]
Custom: [=TVInfo(IsOnNonTopGroupedChannel)]=[0]

and one modification: Database location: Television Guide.

The combined expression looks like this:

Code: [Select]

[TVTime]=>#TVGuideStartDate -[=TVInfo(ChannelKeywords)&DataType=[List]]=[Hidden] [=TVInfo(IsOnNonTopGroupedChannel)]=[0] ~d=g

In build 62, MC will automatically replace that expression with this one

Code: [Select]

"[TVTime]=>#TVGuideStartDate ~d=g"

to gain efficiency.  So you do not even need to do anything to enjoy the new efficiency.  However, if you modified those rules manually, by adding something extra, or by changing the order of the default rules, then MC will not be able to identify that string, and therefore will not run faster.  In that case, you can manually remove the two rules that are meant to be removed.

[tzr916]

30.0.66 (2/21/2023)
12. Fixed: When showing television guide by time in Theater View ("This evening", "Tomorrow morning", "Tomorrow afternoon", etc.) a random program could be selected when entering the grid view, instead of the program showing at the upper left corner.

30.0.62 (2/14/2023)
8. Changed: Additional optimization of Theater View television guide display speed.
11. Changed: Removed the custom expressions "TVInfo(ChannelKeywords)" and "TVInfo(IsOnNonTopGroupedChannel)" from the default Theater View Television Guide setup since they are now handled differently and more efficiently.

30.0.61 (2/9/2023)
1. Changed: Reverted the Theater View TV guide change in build 60 because of its undesirable effects.
6. Optimized: Theater View television guide display is much faster.

30.0.60 (2/3/2023)
5. Changed: Slightly improved Theater View TV guide display speed.

Something is very wrong with theater view tv guide. Not sure how far back this goes but I tried versions 68, 66, 65, 64, 62, they all do the same thing, on Server and Clients...

Open guide > it properly highlights the top left program, but if I type in any new channel number it jumps to that channel, but 10 days in the future!

Seems to have to do with my custom guides, because if I load a "default guide" the issue does not happen.

Code: [Select]

-[=TVInfo(ChannelKeywords)&DataType=[List]]=[Favorite]

Code: [Select]

-[=TVInfo(ChannelKeywords)&DataType=[list]]=[OTA]
Now what?

[Yaobing]

You did not say if you tried 60 or 61.  Maybe it started with 61?

I can reproduce, whether you have customized view or default view.  I did not get it 10 days in the future, but a couple of hours in the future, or, in one case, a half hour in the past.  It may have to do with the change that gave me the best performance enhancement, i.e. build 61.  I will figure it out.

[tzr916]

59 guides show up and direct input of channel number does not jump 10 days into the future
60 guides are BLANK issue is introduced
61 guides show up but direct input of channel number jumps 10 days into the future

[tzr916]

Just updated to v73 on Server and Clients.
Punching in a channel number while in the guide does not work at all now. I can see the numbers "fly up" on the screen, but the guide remains stuck on the original channel, does not move.
However one out of every five or six times of trying, it will actually work. It's so intermittent, I cannot find any pattern.

EDIT: After restarting MC Server, things do seem to be working properly.