Opened 16 years ago

Last modified 15 years ago

#9152 closed defect

Don't Autoflag commercials not honored — at Version 7

Reported by: km@… Owned by: Raymond Wagner
Priority: minor Milestone: 0.25
Component: MythTV - Mythcommflag Version: Master Head
Severity: medium Keywords:
Cc: Ticket locked: no

Description (last modified by Raymond Wagner)

I'm running the trunk. My default behavior is to have recordings automatically commflagged, and to not run on certain commercial free channels, which works properly. When mythcommflag is run with no options, to pick up any missed recordings, it ignores the commercial free tag for channels.

Change History (7)

comment:1 by robertm, 16 years ago

Owner: set to cpinkham
Status: newassigned

comment:2 by Raymond Wagner, 15 years ago

Owner: changed from cpinkham to Raymond Wagner
Status: assignedaccepted

This will be taken care of as part of #7990.

comment:3 by Raymond Wagner, 15 years ago

Status: acceptedinfoneeded

Can you confirm this is still a problem? I just attempted to, and was unable to reproduce it.

Please open up mysql and run:

select recordid,title,subtitle,autocommflag from record where autocommflag=0;

to ensure the rule you did not want to run commercial detection was in fact disabled.

comment:4 by km@…, 15 years ago

It's probably my misunderstanding. Left to its own myth does not flag the programs I've designated for it not to flag. However, if I run mythcommflag with no arguments it does flag them. I guess thats by design, that mythcommflag flags everything not just whats queued.

However, the reality is that when mythcommflag runs the queue it doesn't take much for it to fail on some recording and not run the rest of the queue.

I need some way to run mythcommflag by hand on just the programs queued.

comment:5 by Raymond Wagner, 15 years ago

So the automatic commercial flagging when something records works properly, but this ticket is reference to the mythcommflag behavior where when given no recording, it blindly operates on all recordings and ignoring that setting?

comment:6 by km@…, 15 years ago

Yes, thats correct. When I submitted the ticket I expected mythcommflag to honor the setting.

comment:7 by Raymond Wagner, 15 years ago

Description: modified (diff)
Milestone: unknown0.25
Status: infoneededassigned
Note: See TracTickets for help on using tickets.