[prev in list] [next in list] [prev in thread] [next in thread]
List: mythtv-dev
Subject: Re: [mythtv] Adding automatic DVB-C/T scan using W-scan
From: Hesder T <zendhetmij () gmail ! com>
Date: 2009-01-30 16:08:26
Message-ID: 54451290901300808h64e9fe58ode3e94fc2da774c8 () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
// > 3) I was thinking about adding an extra scanning option (e.g.
// > automatic DVB-C/T scan) and hanging the new scanning method under
// > this, agreed?
// Integrating it with mythtv-setup will be difficult.
// Getting the user to run an external utility
// (to generate a channels.conf file),
// and then importing that in mythtv-setup,
// is much easier.
That's how my current sollution works. There are however two problems about
this approach:
1) the channels.conf file does can not contain all nececcary data
2) mythtv automaticly checks the channeldata which in the case of non
standard DVB protocols does not work. So to follow this option I would need
to come up with an new type of configuration file, like the one of caffeine
for example (as my current implementation).
Thinking about this, adding a RAW import function(no checks) based on a
complete configfile would be rather nice to have. It adds extra
functionality and makes it possible to reuse existing configuration files
from other DVB software as well.
I assume there's nothing against a raw import function based on a
caffeine-configfile beside the existing importfunction?
Suggestions to where I can find the relevant code for the existing import
function would also be welcome.
Will take a look at it this weekend.
// > 4) Not yet familiar with the tuning part of myth, can someone bring
// > me up-to-speed on this? What files do I need to edit to add this
// > extra tuning option?
// >
// It is complex, but libs/libmythtv/scanwizardhelpers.*
// contains the UI stuff.
// An "External Scan Utility" option, could be added?
// It could maybe call a script like "mythexternalscan",
// that wrote an output file like channels.conf ?
// ScanTypeSetting::SetInput() adds "Import channels.conf"
// menu selectors for most card types, so it wouldn't be
// too hard for a new ScanTypeSetting::Type to be added,
// (something like ExternalScanUtil), and to trick the
// existing parser to also parse the output.
// (I can't find that code right now -
// the fastest way would be to search on
// Trac for the relevant channel.conf commits)
Ok Thanks for the info. Will take a closer look at this code to get an
estimate of the impact before choosing my path.
// --
// Nigel Pearson, nigel[at]ind.tansu.com.au| I've been talking to |
// Telstra Net. Eng., Sydney, Australia | the ship's computer. |
// Office: 9202 3900 Fax: 9212 6348 | ... It hates me! |
// Mobile: 0408 664435 Home: 9792 6998 | Marvin |
[Attachment #5 (text/html)]
<p>// > 3) I was thinking about adding an extra scanning option (e.g. <br>// > \
automatic DVB-C/T scan) and hanging the new scanning method under <br>// > this, \
agreed? </p> <p>// Integrating it with mythtv-setup will be difficult. <br>// Getting \
the user to run an external utility <br>// (to generate a channels.conf file), <br>// \
and then importing that in mythtv-setup, <br>// is much easier.</p>
<p>That's how my current sollution works. There are however two problems about \
this approach: <br>1) the channels.conf file does can not contain all nececcary data \
<br>2) mythtv automaticly checks the channeldata which in the case of non standard \
DVB protocols does not work. So to follow this option I would need to come up with an \
new type of configuration file, like the one of caffeine for example (as my current \
implementation).</p>
<p>Thinking about this, adding a RAW import function(no checks) based on a complete \
configfile would be rather nice to have. It adds extra functionality and makes it \
possible to reuse existing configuration files from other DVB software as well.</p>
<div>
<div>I assume there's nothing against a raw import function based on a \
caffeine-configfile beside the existing importfunction? </div> <p>Suggestions to \
where I can find the relevant code for the existing import function would also be \
welcome. </p> <p>Will take a look at it this weekend. </p></div>
<div> </div>
<div><br>// > 4) Not yet familiar with the tuning part of myth, can someone bring \
<br>// > me up-to-speed on this? What files do I need to edit to add this <br>// \
> extra tuning option? <br>// > <br>// It is complex, but \
libs/libmythtv/scanwizardhelpers.* <br> // contains the UI stuff. </div>
<p>// An "External Scan Utility" option, could be added? <br>// It could \
maybe call a script like "mythexternalscan", <br>// that wrote an output \
file like channels.conf ? </p> <p>// ScanTypeSetting::SetInput() adds "Import \
channels.conf" <br>// menu selectors for most card types, so it wouldn't be \
<br>// too hard for a new ScanTypeSetting::Type to be added, <br>// (something like \
ExternalScanUtil), and to trick the <br> // existing parser to also parse the output. \
<br>// (I can't find that code right now - <br>// the fastest way would be to \
search on <br>// Trac for the relevant channel.conf commits) </p> <div>Ok Thanks for \
the info. Will take a closer look at this code to get an estimate of the impact \
before choosing my path. </div> <div> </div>
<p>// -- <br>// Nigel Pearson, nigel[at]<a \
href="http://ind.tansu.com.au">ind.tansu.com.au</a>| I've been talking to | \
<br>// Telstra Net. Eng., Sydney, Australia | the ship's computer. | <br>// \
Office: 9202 3900 Fax: 9212 6348 | ... It hates me! | <br> // Mobile: 0408 664435 \
Home: 9792 6998 | Marvin | <br></p>
_______________________________________________
mythtv-dev mailing list
mythtv-dev@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic