[mythtv] Some bugs (0.15)

Chris Pinkham cpinkham at bc2va.org
Sat May 22 14:55:46 EDT 2004


> > This is fixed my tree as well.  I have reworked how the commercial flagging gets
> > started and am using a method similar to how transcoding works.  There is a
> > CommercialFlagger class instance that gets fired off by the backend and listens
> > for events.  The recorders and frontend can send start/stop events to tell the
> > CommercialFlagger to start or stop flagging a program.  This allowed me to do
> > several things like the above #6 in addition to these:
> 
> Any chance that this is easily extendable to designating a particular 
> machine as the commercial flagger?  ie, a master that's low-CPU but is 
> chock full of PVR-250 cards handing commercial flagging off to another 
> machine?

Yes, it's easily modifiable to support something like that.  The message that
gets sent to start a flagging process has the backend hostname in it, but the
message only gets sent to the local backend.  It could easily be modified to
get sent to all backends with a user-configurable hostname so all flagging
would happen on a user-defined backend.  I'll add something to my TODO to look
at this.  Could give the user a dropdown list in the setup screen with the
list being populated with the distinct hostnames in the settings table.

-- 

Chris



More information about the mythtv-dev mailing list