[mythtv-users] PVR 250

[Mike Richardson]

On Tue, Jan 17, 2006 at 08:36:01PM +0000, Nick wrote:
> The freqid is solely used for tuning. I don't think it plays any part
> in scheduling.

I've set the freqid for the duplicate channel (BBC1, ITV1) etc to be the
same in each source and that has helped sort out scheduling issues. Now BBC1
only appears once in the listings and scheduling a program to be recorded
from channel '1' (BBC1) picks the most appropriate card depending on
scheduling clashes. This is a very nice system once you get the hang of it. 

> I created 3 separate sources - analogue, DVB, and NTL - as I have 3
> different 'types' of input. I run mythfilldatabase against each
> sourceid in turn (with an xmltv file for each source containing only
> the channel available on that source)

Ok, done that.

> (I would like to be able to configure a single grabber file to
> download a superset of all listings into a single file, and then feed
> that to mythfilldatabase once (but updating each source specified).
> However, if you do that MFDB will recreate any channels it finds in
> the XML that are not present in the database (which without a run time
> option, is not a feature in my book...))

I see what you mean. It ought to be possible to get MFDB to read the DB pick
out the sourceid and xmltvid and decide which to update, avoiding the need
for the perl cache. The --manual option could be used to add more channels,
if required.

> > Unless there is a way to tell MythTV to limit a card to a subset of channels
> > then it would seem that I have to use a different mythtv source for the
> > PVR250 but collecting data from the same data source (Radio times) for a
> > subset of the channels. I've done this and it appears to work but is this
> > the best way? (Ignore the other discussion about the DVB card's EPG for
> > now.)
> 
> See above. Create one source for analogue channels containing an xmltv
> file with the 5 channels, and another for DVB containing the DVB
> channels (its xmltv file should contain the channels available from
> uk_rt, the remainder will be set up to use the EPG for listings).

Ok, I plan to give this a go. Would it be possible for you to check
something for me first please? I'm still not convinced that the EPG data is
as accurate/usable as the RT data. 

Could you run this query and see what the data looks like?

mysql> select starttime, title,subtitle from program where title like '%smallville%';
+---------------------+--------------------------------------+----------+
| starttime           | title                                | subtitle |
+---------------------+--------------------------------------+----------+
| 2006-01-23 21:00:00 | Smallville: Superman the Early Years | Hidden   |
| 2006-01-30 21:00:00 | Smallville: Superman the Early Years | Aqua     |
| 2006-01-31 01:00:00 | Smallville: Superman the Early Years | Aqua     |
| 2006-01-30 00:30:00 | Smallville: Superman the Early Years | Hidden   |
| 2006-01-30 22:00:00 | Smallville: Superman the Early Years | Aqua     |
| 2006-01-31 02:00:00 | Smallville: Superman the Early Years | Aqua     |
| 2006-01-22 19:00:00 | Smallville: Superman the Early Years | Mortal   |
| 2006-01-29 19:00:00 | Smallville: Superman the Early Years | Hidden   |
| 2006-01-29 23:30:00 | Smallville: Superman the Early Years | Hidden   |
| 2006-01-23 22:00:00 | Smallville: Superman the Early Years | Hidden   |
| 2006-01-29 20:00:00 | Smallville: Superman the Early Years | Hidden   |
| 2006-01-22 20:00:00 | Smallville: Superman the Early Years | Mortal   |
+---------------------+--------------------------------------+----------+
12 rows in set (0.12 sec)

This above is from a DB populated purely with RT data. The below is from a
DB populated with EPG updates and looks messier.

mysql> select starttime, title,subtitle from program where title like '%smallville%';
+---------------------+--------------------------------------+--------------------------+
| starttime           | title                                | subtitle                 |
+---------------------+--------------------------------------+--------------------------+
| 2006-01-30 21:00:00 | Smallville: Superman the Early Years | Aqua                     |
| 2006-01-31 01:00:00 | Smallville: Superman the Early Years | Aqua                     |
| 2006-01-30 00:30:00 | Smallville: Superman the Early Years | Hidden                   |
| 2006-01-30 22:00:00 | Smallville: Superman the Early Years | Aqua                     |
| 2006-01-31 02:00:00 | Smallville: Superman the Early Years | Aqua                     |
| 2006-01-22 19:00:00 | Smallville                           | Superman the Early Years |
| 2006-01-29 19:00:00 | Smallville: Superman the Early Years | Hidden                   |
| 2006-01-29 23:30:00 | Smallville: Superman the Early Years | Hidden                   |
| 2006-01-29 20:00:00 | Smallville: Superman the Early Years | Hidden                   |
| 2006-01-23 22:00:00 | Smallville                           | Superman the Early Years |
| 2006-01-22 20:00:00 | Smallville                           | Superman the Early Years |
| 2006-01-23 21:00:00 | Smallville                           | Superman the Early Years |
+---------------------+--------------------------------------+--------------------------+
12 rows in set (0.12 sec)

Thanks,

Mike
-- 
Mike Richardson
Networks
IT Services, University of Manchester
Email: doctor at mcc.ac.uk
*Plain text only please - attachments stripped on arrival*