<br><br><div class="gmail_quote">On Fri, Sep 9, 2011 at 3:05 PM, Brian J. Murrell <span dir="ltr"><<a href="mailto:brian@interlinx.bc.ca">brian@interlinx.bc.ca</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">On 11-09-09 05:51 PM, Michael T. Dean wrote:<br>
><br>
> Not according to the printsched output you posted. The one and only<br>
> occurrence of Person of Interest on that schedule is:<br>
><br>
> 2011-09-08 08:13:57.424734 I Person of Interest - Pilot 84-77 WWNY 22 21:00-22:00 2 0 0 A C -3<br>
<br>
</div>But WWNY is available on both digital and analog. Perhaps I am being<br>
misguided by an assumption I have been following all along and that<br>
assumption being that the (schedules direct) guide data for digital<br>
channels and analog channels (i.e. those with the same callsign) will be<br>
equally present. Perhaps that is not the case?<br>
<div class="im"><br>
> So, if you're saying there's now a showing on one of your analog<br>
> channels, that is probably one of the things that changed that caused<br>
> the scheduler to "strangely" schedule/place things differently such that<br>
> you didn't need an override--exactly what Kevin was talking about where<br>
> more information becomes available allowing MythTV to better optimize<br>
> usage of resources. (Of course, before you do add any channel<br>
> priorities, please read and understand all of<br>
> <a href="http://www.mythtv.org/docs/mythtv-HOWTO-12.html" target="_blank">http://www.mythtv.org/docs/mythtv-HOWTO-12.html</a> because it will have<br>
> other effects. :) Adding a negative priority to the Ontario channels<br>
> (preferred approach) or a positive priority to the NY channels (a worse<br>
> approach of attempting to solve the same problem) will actually mean<br>
> that MythTV may choose to record a -3 priority show on WWNY rather than<br>
> a -2 priority show that airs only on CJOH.)<br>
<br>
</div>Well, I don't care if the scheduler uses Ontario channels vs. NY<br>
channels. Sometimes one is preferred, other times, the other is. What<br>
would be ideal (and I know it doesn't happen since I've been down this<br>
road before) is that the scheduler just prefers the channels that yields<br>
the most recording from the multirec tuners. If that means that the<br>
109- channels is best, great but if it means that the 84- channels are<br>
the best choice, so be it.<br>
<div class="im"><br>
> How about you post your capturecard and cardinput tables along with the<br>
> schedule on your website instead of making me guess at all the possible<br>
> different configurations you might have that might make a difference?<br>
> :) And, really, based on what you've said above, I'd like to see your<br>
> channel table, too.<br>
<br>
</div>Well, perhaps we can short circuit all of this by either confirming or<br>
denying my above assumption. If it's in fact a false assumption, then<br>
that probably does explain everything.<br>
<div class="im"><br>
> If you had done that, your capture cards and inputs should all be<br>
> starting at 1, not 19.<br>
<br>
</div>Hrm. My experience is that even when you delete all capture cards, it<br>
doesn't actually doesn't reset the index. Witness:<br>
<br>
cardid videodevice audiodevice vbidevice cardtype defaultinput<br>
audioratelimit hostname dvb_swfilter dvb_sat_type<br>
dvb_wait_for_seqstart skipbtaudio dvb_on_demand dvb_diseqc_type<br>
firewire_speed firewire_model firewire_connection signal_timeout<br>
channel_timeout dvb_tuning_delay contrast brightness colour hue<br>
diseqcid dvb_eitscan<br>
22 /dev/dvb/adapter0/frontend0 NULL NULL DVB DVBInput<br>
NULL pvr 0 0 1 0 1 0 0 NULL 0500 3000 0 0 0 0 0 0 0<br>
23 /dev/dvb/adapter0/frontend0 NULL NULL DVB DVBInput<br>
NULL pvr 0 0 1 0 1 0 0 NULL 0500 3000 0 0 0 0 0 0 0<br>
24 /dev/pvr_mpeg0 NULL /dev/vbi1 MPEG Tuner 1 NULL pvr 00 1 0 0<br>
NULL 0 NULL 0 1000 12000 00 0 0 0 NULL 1<br>
25 /dev/pvr_mpeg1 NULL /dev/vbi2 MPEG Tuner 1 NULL pvr 00 1 0 0<br>
NULL 0 NULL 0 1000 12000 00 0 0 0 NULL 1<br>
20 /dev/dvb/adapter0/frontend0 NULL NULL DVB DVBInput<br>
NULL pvr 0 0 1 0 1 0 0 NULL 0500 3000 0 0 0 0 0 0 0<br>
21 /dev/dvb/adapter0/frontend0 NULL NULL DVB DVBInput<br>
NULL pvr 0 0 1 0 1 0 0 NULL 0500 3000 0 0 0 0 0 0 0<br>
19 /dev/dvb/adapter0/frontend0 NULL NULL DVB DVBInput<br>
NULL pvr 0 0 1 0 1 NULL 0 NULL 0500 3000 0 0 0 0 0 0 0<br>
<div class="im"><br>
> So, it seems you may have done that before, but<br>
> have since changed things around?<br>
<br>
</div>Nope. Not to the best of my recollection.<br>
<font color="#888888"><br>
b.<br>
<br>
</font><br>_______________________________________________<br>
mythtv-users mailing list<br>
<a href="mailto:mythtv-users@mythtv.org">mythtv-users@mythtv.org</a><br>
<a href="http://www.mythtv.org/mailman/listinfo/mythtv-users" target="_blank">http://www.mythtv.org/mailman/listinfo/mythtv-users</a><br>
<br></blockquote></div><br>did you select delete all tuners on host or delete all tuners? In my experience deleting all tuners across all hosts (yes even if you have only one backend host) will reset the indexes.<br clear="all">
<br>-- <br>Working on World Domination since 2001<br><br>