[mythtv] [mythtv-commits] Ticket #7818: allow preffered input group forscheduling

Mark Spieth mark at digivation.com.au
Tue Dec 29 19:29:52 UTC 2009


> My gut reaction is to reject this new patch for the same reasons we didn't
> do more in the first place -- it isn't flexible enough to justify the
> extra complexity.  I'd much rather see effort put into making the existing
> power priority support be made more accessible.

fair enough.
what kind of flexibility?

>
> Still, I might consider this change, and that's an awfully big might, if
> the following issues can be addressed.
>
> 1. Use negative numbers to identify inputgroups instead of +1000.  I
> thinks that would be a little more elegant.
easy
>
>2. The join condition on the inputgroup table in the scheduler BUQ (big
> ugly query) is bogus.
this info is only available AFAICT in the inputgroup table.
how else could this be done? cache this info for all schedules and fuse, but 
this increases the complexity quite a bit.
add inputgroup column to cardinput table? dont like this either. the info 
would then be duplicated.
>
>3. This is the biggie.  Inputs can belong to multiple inputgroups.  Even
> if the join condition mentioned above is fixed, this wouldn't be handled
> correctly.
how is this possible? the only info for inputgroups is in the 1 table, setup 
by the channel scanner.
this functionality this purely there to associate dvb multiplex inputs for 
multirecord. thats the whole point of this functionality from the recorder 
side.
prefer a physical device for a certain recording, say due to better FE 
performance for say UHF band. but dont care which particular virtual input 
is actually chosen. otherwise you have to make manual scheduling choices for 
this purpose.
This functionality doesnt exist currently and would be better if it did 
(obviously).

regards
mark 



More information about the mythtv-dev mailing list