Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: MythTV: Users

All tuners are equal, but some tuners are more equal than others

 

 

MythTV users RSS feed   Index | Next | Previous | View Threaded


ylee at pobox

Jul 4, 2009, 10:59 PM

Post #1 of 3 (480 views)
Permalink
All tuners are equal, but some tuners are more equal than others

[Starting a new thread]

Michael T. Dean <mtdean [at] thirdcontact> says:
> > I agree that it would be nice to be able to tell the scheduler
> > that multiple tuners are identical in recording quality and thus
> > completely fungible (such as in my case, where all
> > programs--whether cable or over-the-air--are written directly to
> > disk in pure MPEG-2 streams directly from the providers).
>
> In the case described (a couple of identical inputs), the LiveTV
> user should just enable, "Avoid conflicts..." and Myth will
> generally do the right thing.

This isn't a comprehensive solution beyond Live TV, though. Since the
scheduler always thinks the lowest-numbered tuner is the highest
quality, it always wants to use it even if another tuner is
equivalent. This causes the scheduler to be dumber than it should be.

Consider the following scenario:

Tuner 1, FireWire
Tuner 2, FireWire (so, identical in quality to 1)
Each tuner's input priority is set to 0, the default.

Movie A, today at 8-10pm (only airing within the scheduling data)
Movie B, today at 8-10pm (only airing within the scheduling data)

Result:

Today at 8pm:
Tuner 1->Movie A
Tuner 2->Movie B

Now, consider:

Movie A, today at 8-10pm (only airing within the scheduling data)
Movie B, today at 8-10pm, and again in three days at 1-3pm

Result:

Today at 8pm:
Tuner 1->Movie A
Tuner 2->unused

In three days at 1pm:
Tuner 1->Movie B
Tuner 2->unused

Since the scheduler believes that the lower-numbered tuner 1 is
superior to 2, and since it knows that B happens to air again, the
scheduler records A at 8-10pm but delays B until the later airing so
it can use tuner 1, even though 2 is available today. We now see that
the scheduler only happened to do the right thing in the first
scenario by accident.

Now, consider:

Movie A, today at 8-10pm (only airing within the scheduling data)
Movie B, today at 8-10pm, and again in three days at 1-3pm
TV show C, in three days at 1:30-2pm (only airing within the
scheduling data)

Result:
Today at 8pm:
Tuner 1->Movie A
Tuner 2->Movie B

In three days at 1pm:
Tuner 1->TV show C
Tuner 2->unused

In this scenario the scheduler again does the right thing, but again
only by accident, because it is forced to by tuner 1 not being
available for the later airing.

I tried to compensate for the scheduler's behavior by increasing each
successive tuner's input priority by 1 (e.g., 0 for tuner 1, 1 for
tuner 2, etc.). The scheduler then simply uses those priorities and
seemingly ignores the tuners' order, however, which defeats the
purpose of the compensation in the first place.

--
Frontend/backend: P4 3.0GHz, 1.5TB software RAID 5 array
Backend: Quad-core Xeon 1.6GHz, 6.6TB sw RAID 6
Video inputs: Four high-definition over FireWire/OTA
Accessories: 47" 1080p LCD, 5.1 digital, and MX-600
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users


ijr at case

Jul 4, 2009, 11:41 PM

Post #2 of 3 (424 views)
Permalink
Re: All tuners are equal, but some tuners are more equal than others [In reply to]

On Sunday 05 July 2009 1:59:03 am Yeechang Lee wrote:
> [Starting a new thread]
>
> Michael T. Dean <mtdean [at] thirdcontact> says:
> > > I agree that it would be nice to be able to tell the scheduler
> > > that multiple tuners are identical in recording quality and thus
> > > completely fungible (such as in my case, where all
> > > programs--whether cable or over-the-air--are written directly to
> > > disk in pure MPEG-2 streams directly from the providers).
> >
> > In the case described (a couple of identical inputs), the LiveTV
> > user should just enable, "Avoid conflicts..." and Myth will
> > generally do the right thing.
>
> This isn't a comprehensive solution beyond Live TV, though. Since the
> scheduler always thinks the lowest-numbered tuner is the highest
> quality, it always wants to use it even if another tuner is
> equivalent. This causes the scheduler to be dumber than it should be.

I think your scenarios are flawed, or at least, I can't reproduce any such
behavior.

I just set up a recording schedule with:
2 Equal priority (ie, 0) SD tuners. All other default priorities set to 0,
'reschedule higher priority shows' disabled. ie, Everything's pretty much
default.

Ocean's Twelve, starting at 10 am this Sunday on AMC.
The Break-Up, starting at 10 am this Sunday on USA - repeats at 7pm Sunday
and next Friday at 9pm.

(picked movies on common stations, with one movie repeating and the other
not).

Both movies were told to record as 'find one', via mythweb. All defaults
otherwise for each recording schedule.

Both movies were scheduled by the backend to record at 10am on sunday - ie,
the first available showing, and definitely doing the proper thing.

Isaac
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users


mtdean at thirdcontact

Jul 5, 2009, 10:08 AM

Post #3 of 3 (404 views)
Permalink
Re: All tuners are equal, but some tuners are more equal than others [In reply to]

On 07/05/2009 01:59 AM, Yeechang Lee wrote:
> Michael T. Dean says:
>
>>> I agree that it would be nice to be able to tell the scheduler
>>> that multiple tuners are identical in recording quality and thus
>>> completely fungible (such as in my case, where all
>>> programs--whether cable or over-the-air--are written directly to
>>> disk in pure MPEG-2 streams directly from the providers).
>>>
>> In the case described (a couple of identical inputs), the LiveTV
>> user should just enable, "Avoid conflicts..." and Myth will
>> generally do the right thing.
>>
>
> This isn't a comprehensive solution beyond Live TV, though. Since the
> scheduler always thinks the lowest-numbered tuner is the highest
> quality, it always wants to use it even if another tuner is
> equivalent. This causes the scheduler to be dumber than it should be.
>
> Consider the following scenario:
>
> Tuner 1, FireWire
> Tuner 2, FireWire (so, identical in quality to 1)
> Each tuner's input priority is set to 0, the default.
>
> Movie A, today at 8-10pm (only airing within the scheduling data)
> Movie B, today at 8-10pm (only airing within the scheduling data)
>
> Result:
>
> Today at 8pm:
> Tuner 1->Movie A
> Tuner 2->Movie B
>
> Now, consider:
>
> Movie A, today at 8-10pm (only airing within the scheduling data)
> Movie B, today at 8-10pm, and again in three days at 1-3pm
>
> Result:
>
> Today at 8pm:
> Tuner 1->Movie A
> Tuner 2->unused
>
> In three days at 1pm:
> Tuner 1->Movie B
> Tuner 2->unused
>
> Since the scheduler believes that the lower-numbered tuner 1 is
> superior to 2, and since it knows that B happens to air again, the
> scheduler records A at 8-10pm but delays B until the later airing so
> it can use tuner 1, even though 2 is available today. We now see that
> the scheduler only happened to do the right thing in the first
> scenario by accident.
>
> Now, consider:
>
> Movie A, today at 8-10pm (only airing within the scheduling data)
> Movie B, today at 8-10pm, and again in three days at 1-3pm
> TV show C, in three days at 1:30-2pm (only airing within the
> scheduling data)
>
> Result:
> Today at 8pm:
> Tuner 1->Movie A
> Tuner 2->Movie B
>
> In three days at 1pm:
> Tuner 1->TV show C
> Tuner 2->unused
>
> In this scenario the scheduler again does the right thing, but again
> only by accident, because it is forced to by tuner 1 not being
> available for the later airing.
>
> I tried to compensate for the scheduler's behavior by increasing each
> successive tuner's input priority by 1 (e.g., 0 for tuner 1, 1 for
> tuner 2, etc.). The scheduler then simply uses those priorities and
> seemingly ignores the tuners' order, however, which defeats the
> purpose of the compensation in the first place.

There's a reason I say that no one should /ever/ modify input priorities
without first reading section 12.6 of the HOWTO (
http://www.mythtv.org/docs/mythtv-HOWTO-12.html#ss12.6 )--and, really,
all of section 12 ( http://www.mythtv.org/docs/mythtv-HOWTO-12.html ).

This particular case is explicitly covered in 12.6. It explains why
when you set input priorities you may be telling Myth not to record some
shows that your recording rules say to record. I.e. by telling Myth to
defer recording the movie until the better input is available, you've
told it you don't want the movie recorded on the lesser input. So, if
the network changes the schedule and does not air the later showing,
you've effectively told Myth not to record it (by saying, "if you can't
get it on the best input, I'd rather chance missing a later showing").

Of course, one you read all of section 12, you'll know that you don't
want to set any input priorities, so the point will be moot.

But, in this case, Myth is just doing exactly what you told it to
do--even though you didn't know you were telling it to do so.

Mike
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

MythTV users RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact Gossamer Threads
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.