Power Search inactive flag not being inherited by results

[brian@…]

I have the "Premieres and Pilots (Power Search)" in my recording rules and in it I have "inactive" selected. However the recordings that are scheduled as a result of this search are not set with the inactive state. They were only a month or three ago.

[gigem]

I don't understand what you mean by "the recordings that are scheduled as a result of this search are not set with the inactive state" nor can I reproduce anything wrong in this area. Can you please elaborate?

[brian@…]

Replying to gigem:

Can you please elaborate?

sure. i have a power search for premieres and pilots. it's a canned search from either mythtv itself or the myth community. i'd be happy to extract it from the database if you can describe a sql command that will achieve that if that makes it easier to understand.

in any case, that search has the "inactive" flag set. up until a few weeks ago, any recordings that matched that search got added to the recording schedule but remained with their inactive flag set so that they wouldn't record by default and one had to take action to get it to actually record. this was my preference as the ratio of crap that i don't want to record as of that rule to the stuff i do want to record is high.

[gigem]

I don't see that behavior using current master. All I see is the expected behavior. Before an inactive program starts, it is shown as inactive in Upcoming Recordings. After it starts, it doesn't record and is shown as inactive in Previously Recorded.

What version are you running? Please see the ticket howto with regard to providing that information. There was a bug fix a couple of weeks ago that might have affected what you are seeing.

Are you using mythweb? Perhaps there is a bug in mythweb in handling inactive recording rules.

Are you sure you don't have another recording rule that is not set as inactive and matches the same programs? You can check in the Manage Recordings | Recording Rules screen.

What locale/language settings are you using? There's a new bug report from someone using Greek that has some similarities to your report. There were some changes awhile back to handle case insensitvity issues. Perhaps there is an issue there with some languages.

If none of the above sheds any light on the problem, you'll have to give me more details so I can try to reproduce it myself. Please tell me exactly how you produce the problem step by step. Also, run your master backend with "-v general,schedule" logging and provide the logs.

[brian@…]

Replying to gigem:

Before an inactive program

I am not referring to an inactive specific "program" recording. I am referring to a recording that is scheduled via a power search (i.e. /tv/schedules/custom in mythweb or http://www.mythtv.org/wiki/Custom_Recording) that has the inactive flag set. Specifically I am using the Premieres and Pilots power search.

What version are you running?

v0.25-beta-99-gff73126

Are you using mythweb?

Yes, but that's orthogonal really, as I'm just using it to view the results of the search, which has been in place for probably a year or two now, but only just recently has the inactive status of the recordings it's scheduling changed.

Perhaps there is a bug in mythweb in handling inactive recording rules.

Well, mythweb doesn't really do any scheduling itself. It just shows the settings of rules and the resulting recordings. It's the scheduler that is not carrying the inactive flag from the custom recording rule to the resulting scheduled recordings.

Are you sure you don't have another recording rule that is not set as inactive and matches the same programs?

Yes, positive. There are way too many matches that are all active for there to be any other rules matching them. Additionally, when I view the details of a program that will be recorded by that rule the Search Phrase in the extended information screen shows the same phrase as the custom recording rule.

I will attach a mythfrontend screenshot of the custom recording rule I am using.

[brian@…]

custom search screenshot

[brian@…]

As you can see in the screenshot, the active status for that rule is disabled. Yet every recording that rule custom search creates has it's active flag enabled.

[gigem]

Pardon me for being pedantic here, but you are seriously misusing some terminology and that is doing nothing but confuse me.

A recording rule matches programs to consider for recording. A recording rules does NOT create recordings.

A matched program has a recording status that indicates whether or not a program will be or was recorded and if not, why not. A program does NOT have an active flag.

A recording rule has an inactive flag that influences whether or not matched programs are recorded. If the flag is not set, matched programs will not be recorded and their recording status will (usually) be "x" or "Inactive."

If the scheduler determines that a matched program should be recorded, it will be given a recording status of "<card number" or "Will Record." When the program starttime arrives, the scheduler will direct a recorder to record the matched program. Then, and only then, is a recording created.

Like a matched program, a recording has a recording status. It does NOT have an active flag. While a recording is being created, it and the matched program will have a recording status of "<card number>" or "Recording." Afterwards, they will have a recording status that is usually "R" or "Recorded."

Before a matched program or recording ends, its recording status is shown on the Upcoming Recordings screen. After a matched program or recording starts, its recording status is also shown on the Previously Recorded screen.

Now, as I said earlier, all I see is the expected behavior where a program matching an inactive recording rule is not recorded and is shown with recording status of x/Inactive.

If you do not see this behavior too, then please give me detailed, step by step instructions using only mythfrontend on how you produce the problem. Please include screen shots of the Upcoming Recordings screen from before and during a matched program and of the Previously Recorded screen during and after a matched program. Also, please provide screnn shots of every page of the schedule editor.

[brian@…]

upcoming recordings screenshot

[brian@…]

Maybe one more screenshot and question might clear things up.

In the ​upcoming recordings attachment, what is the status of the highlighted "Monster Man" showing? It does not appear to be assigned any tuner or status but that screenshot does say that it "Will Record". Additionally, the mythweb "Upcoming Recordings" shows it scheduled to record the same way it shows any other programs to be recorded.

[gigem]

I assume the status is "Will Record." The green bar showing the selected item appears to be too short and is truncating/hiding the card to use. I don't know why that is.

[brian@…]

upcoming recordings screenshot 2

[brian@…]

I did check for that possibility before I posted my last comment and the screenshot. Here's ​another screenshot with the green bar moved to another line so that you can see the line that was under it and that the green bar does not truncate/hide the tuner/status of the recording

[Github]

Allow more room for double-digit cardids in the MythCenter?[-wide] and default[-wide] themes.

For some reason, the font handling needs a little more room now. These changes work on my TV. Hopefully, they work for others, too. Also, added the base, DroidSans?, font files needed by the MythCenter?-wide theme. If the other DroidSans? variants are needed, they can be added later.

Refs #10444

Branch: master Changeset: 6ed2587179a735093af34a4d4af8066111f32636

[gigem]

The display problem in Upcoming Recordings should be fixed now in master.

As for your original problem, I can only make wild guesses that something is badly hosed on your system at this point. Until you provide the detailed, step by step directions (using only mythfrontend) and logs asked for above, there's nothing more I can do. If you can provide that information, please also provide the results from following sql commands where <recordid> is replaced with the actual recordid from your recording rule.

select * from record where recordid=<recordid>\G

and

select * from recordmatch, program where recordmatch.recordid=<recordid> and recordmatch.starttime=program.starttime and recordmatch.chanid=program.chanid order by program.starttime, program.chanid\G

[brian@…]

Replying to gigem:

The display problem in Upcoming Recordings should be fixed now in master.

It is. Thanks.

please also provide the results from following sql commands where <recordid> is replaced with the actual recordid from your recording rule.

Please excuse my ignorance but how do I get the recordid from my recording rule? What table are power search rules stored in?

select * from record where recordid=<recordid>\G

[dekarl@…]

you can hit INFO twice on the upcoming recording in mythfrontend, it shows more information that way

[brian@…]

I seem to have resolved it. Your direction to looking at the record and recordmatch tables helped me find some errant supposedly Power Search that wasn't really a Power Search, or didn't act like one anyway which was hiding the real Power Search that didn't have the inactive flag set.

This ticket can be closed AFAIAC.

Thanks for your patience.

[gigem]

Glad you found the problem. Thanks for reporting back.