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

Mailing List Archive: MythTV: Dev

Channel scanning/validation in trunk (feedback post r14355)

 

 

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


mtdean at thirdcontact

Aug 30, 2007, 3:50 PM

Post #1 of 11 (1241 views)
Permalink
Channel scanning/validation in trunk (feedback post r14355)

The purpose of this thread is to provide feedback on the channel
validation patch Daniel recently added to SVN trunk ([14355] , see
http://svn.mythtv.org/trac/ticket/3842#comment:40). AIUI, Daniel is
looking for feedback from users with various different configurations
before backporting the fix to 0.20.2.

Anyway, on my system using SVN trunk r14361 with pcHDTV HD-3000's with
OTA HDTV, the channel scan and "Fetch channels from listings source"
worked flawlessly. To verify the patch works on a fresh DB, I used
"Delete all video sources" and "Delete all capture cards" to clear out
all of my current config. Then, I added capture cards, created a video
source (using SD), configured the inputs to use the video source,
scanned for channels, then used "Fetch channels from listings source" to
associate xmltvid's with the scanner-identified channels.

Also, Steven Adeff reported that it worked for his firewire-based
setup. http://www.gossamer-threads.com/lists/mythtv/users/286476#286476

Oh, and on the wow side... Nice work on the scanner since the last time
I used it, Daniel. Looks good, gives good feedback, and is easy to
use. Once I did my scan, I used "Fetch channels from listings source"
and it matched up the xmltvid's automatically (and even took care of
subchannels where the broadcaster didn't distinguish between
callsigns). This was soooo much easier than the last time I did a
scan. And, it was more accurate than my previous config (due to changes
by broadcasters and the fact that SD has a more accurate list of
channels available to the lineup)--almost to the point that I'd suggest
others (who know what they're doing) rescan their channels (and perhaps
provide feedback here if running SVN trunk >= r14355). :)

Thanks, again, Daniel. The scanner is looking good. If the trunk
version is this nice, I can't wait to see the improvements in the
mythtv-channel-scan branch.

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


danielk at cuymedia

Aug 30, 2007, 4:28 PM

Post #2 of 11 (1182 views)
Permalink
Re: Channel scanning/validation in trunk (feedback post r14355) [In reply to]

On Thu, 2007-08-30 at 18:50 -0400, Michael T. Dean wrote:
> The purpose of this thread is to provide feedback on the channel
> validation patch Daniel recently added to SVN trunk ([14355] , see
> http://svn.mythtv.org/trac/ticket/3842#comment:40). AIUI, Daniel is
> looking for feedback from users with various different configurations
> before backporting the fix to 0.20.2.
Yep.

> Also, Steven Adeff reported that it worked for his firewire-based
> setup. http://www.gossamer-threads.com/lists/mythtv/users/286476#286476
>
> Oh, and on the wow side... Nice work on the scanner since the last time
> I used it, Daniel. Looks good, gives good feedback, and is easy to
> use. Once I did my scan, I used "Fetch channels from listings source"
> and it matched up the xmltvid's automatically (and even took care of
> subchannels where the broadcaster didn't distinguish between
> callsigns). This was soooo much easier than the last time I did a
> scan.
When did you last do a channel scan?

BTW Except for a recent DVB-S fix, the channel scanner in 0.20.2 is
better than the one in trunk, I believe Janne and Jarod carefully
back-ported just the fixes so 0.20.2 has the most solid channel scanner
in MythTV yet. The channel scanner in trunk has some new features, but
it hasn't been put through it's paces like the one in 0.20.2 has.

Anyway, I'm not looking for feedback on the channel scanner anymore
than usual. At the moment I'm more interested in whether the channel
validation prevents channels from being added to the a Video Source
when they should be added, or adds channels when it shouldn't be
adding them. If someone is using esoteric recorders like DBOX2 or
IPTV, or using a diverse collection of recorder types, feedback is
especially appreciated.

-- Daniel

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


janne-mythtv at grunau

Aug 30, 2007, 5:36 PM

Post #3 of 11 (1193 views)
Permalink
Re: Channel scanning/validation in trunk (feedback post r14355 ) [In reply to]

On Friday 31 August 2007 01:28:16 Daniel Kristjansson wrote:
> On Thu, 2007-08-30 at 18:50 -0400, Michael T. Dean wrote:
> >
> > Oh, and on the wow side... Nice work on the scanner since the last
> > time I used it, Daniel. Looks good, gives good feedback, and is
> > easy to use. Once I did my scan, I used "Fetch channels from
> > listings source" and it matched up the xmltvid's automatically (and
> > even took care of subchannels where the broadcaster didn't
> > distinguish between callsigns). This was soooo much easier than
> > the last time I did a scan.
>
> When did you last do a channel scan?

The same question came to my mind.

> BTW Except for a recent DVB-S fix, the channel scanner in 0.20.2 is
> better than the one in trunk, I believe Janne and Jarod carefully
> back-ported just the fixes so 0.20.2 has the most solid channel
> scanner in MythTV yet.

It was not only fixes. Jarod had to backport some larger changesets to
get the necessary fixes. We did extensive testing and it seems to be
regression free.

> If someone is using esoteric recorders like DBOX2

I'll get Michael Haas' dbox2 to fix the recorder which is afaik for more
than a year broken. So I doubt that anyone will test it in regard to
the datadirect changes.

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


simon at koala

Aug 31, 2007, 2:40 AM

Post #4 of 11 (1178 views)
Permalink
Re: Channel scanning/validation in trunk (feedback post r14355) [In reply to]

Daniel Kristjansson wrote:
> Anyway, I'm not looking for feedback on the channel scanner anymore
> than usual.
one thing that has always struck me as odd was when a scan is taking
place and you want to watch what it is doing - it obscures the log
messages with the popup which shows signal strength etc. my request
(sans source) would be that the page be rearranged so that didn't happen.
--
simon
_______________________________________________
mythtv-dev mailing list
mythtv-dev [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev


adeffs.mythtv at gmail

Aug 31, 2007, 5:33 AM

Post #5 of 11 (1181 views)
Permalink
Re: Channel scanning/validation in trunk (feedback post r14355 ) [In reply to]

On 8/30/07, Janne Grunau <janne-mythtv [at] grunau> wrote:
> On Friday 31 August 2007 01:28:16 Daniel Kristjansson wrote:
> > On Thu, 2007-08-30 at 18:50 -0400, Michael T. Dean wrote:
> > > Oh, and on the wow side... Nice work on the scanner since the last
> > > time I used it, Daniel. Looks good, gives good feedback, and is
> > > easy to use. Once I did my scan, I used "Fetch channels from
> > > listings source" and it matched up the xmltvid's automatically (and
> > > even took care of subchannels where the broadcaster didn't
> > > distinguish between callsigns). This was soooo much easier than
> > > the last time I did a scan.
> >
> > When did you last do a channel scan?
>
> The same question came to my mind.

The last time I tried an ATSC scan with my A180's was right after the
initial check in of the new scanning code before you and Daniel, etc.
started checking in bug fixes. I had done it to see how well it
worked, I didn't need to do it to add channels and Comcast only
recently started including the channel names with their PMT data (or
wherever its kept, i forget...). It ran flawlessly for me this last
go-round, and thankfully I chose the right frequency table =)

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


willyboyd at gmail

Aug 31, 2007, 6:58 AM

Post #6 of 11 (1177 views)
Permalink
Re: Channel scanning/validation in trunk (feedback post r14355) [In reply to]

On 8/30/07, Daniel Kristjansson <danielk [at] cuymedia> wrote:
> Anyway, I'm not looking for feedback on the channel scanner anymore
> than usual. At the moment I'm more interested in whether the channel
> validation prevents channels from being added to the a Video Source
> when they should be added, or adds channels when it shouldn't be
> adding them. If someone is using esoteric recorders like DBOX2 or
> IPTV, or using a diverse collection of recorder types, feedback is
> especially appreciated.
>
> -- Daniel
>

Would this improvement also apply to a HDHomeRun and QAM channels? I
haven't ran a scan in a while, mostly because I'm afraid of going
through the tedious task of finding all the "valid" channels. My
cable source (Comcast in Houston) has a lot of SD QAM channels (most
of the "basic" and "digital" tiers), and quite a few of the HD
channels (OTA, and a few others like ESPNHD, UniversalHD, and MTVHD).
So that's a lot of xmltvid's to put in. But, last time I ran the
scanner (couple months ago?), it also pulled in a load of channels
that won't play in the frontend (I did have it set to ignore encrypted
channels). Each time a channel won't play, I'd get dumped back to the
main menu, and have to try again on the next channel. I still haven't
gone through and deleted the invalid channels from my guide, so it
looks quite messy.

I've recently updated to trunk just after the 0.20.2 tagging, so I'd
be willing to go through it all again if that helps (and if it means I
might end up with a cleaned out channel list finally). Maybe taking a
backup of my channel table would be smart first, just in case. I'm
fairly comfortable with SQL. I do not want reinsert most of those
xmltvid's again if I can avoid it.

Thanks,
Willy
_______________________________________________
mythtv-dev mailing list
mythtv-dev [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev


danielk at cuymedia

Aug 31, 2007, 7:10 AM

Post #7 of 11 (1168 views)
Permalink
Re: Channel scanning/validation in trunk (feedback post r14355) [In reply to]

On Fri, 2007-08-31 at 08:58 -0500, Willy Boyd wrote:
> On 8/30/07, Daniel Kristjansson <danielk [at] cuymedia> wrote:
> > Anyway, I'm not looking for feedback on the channel scanner anymore
> > than usual. At the moment I'm more interested in whether the channel
> > validation prevents channels from being added to the a Video Source
> > when they should be added, or adds channels when it shouldn't be
> > adding them. If someone is using esoteric recorders like DBOX2 or
> > IPTV, or using a diverse collection of recorder types, feedback is
> > especially appreciated.

> Would this improvement also apply to a HDHomeRun and QAM channels?

Again I'm not asking for any special testing of the scanner. In trunk
the HDHomeRun scanner is much smarter about detecting encrypted channels
than it used to be, but there is a bug where the wrong tuning
information is sometimes used, usually from the transport immediately
before or after the correct one in the scan. I think Jarod might have
backported the fix that let MythTV detect transports which looked
encrypted on first glance, but upon further inspection revealed that
the A/V streams were not actually encrypted. I remember feeling really
nervous when I noticed commits along that line in 0.20-fixes, but as I
said before the 0.20.2 & 0.20-fixes channel scanner is the best yet
in any MythTV release.

> I've recently updated to trunk just after the 0.20.2 tagging, so I'd
> be willing to go through it all again if that helps (and if it means I
> might end up with a cleaned out channel list finally). Maybe taking a
> backup of my channel table would be smart first, just in case. I'm
> fairly comfortable with SQL. I do not want reinsert most of those
> xmltvid's again if I can avoid it.

If you do the default scan with "Existing channel treatment" set to
"Minimal Updates" it should not erase xmltvid's for existing channels.
However, there is an out standing ticket on this happening with the
scanner in trunk, but I believe this bug only effects DVB scans not
ATSC scans.

-- Daniel

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


willyboyd at gmail

Aug 31, 2007, 9:15 AM

Post #8 of 11 (1170 views)
Permalink
Re: Channel scanning/validation in trunk (feedback post r14355) [In reply to]

On 8/31/07, Daniel Kristjansson <danielk [at] cuymedia> wrote:
> Again I'm not asking for any special testing of the scanner. In trunk
> the HDHomeRun scanner is much smarter about detecting encrypted channels
> than it used to be, but there is a bug where the wrong tuning
> information is sometimes used, usually from the transport immediately
> before or after the correct one in the scan. I think Jarod might have
> backported the fix that let MythTV detect transports which looked
> encrypted on first glance, but upon further inspection revealed that
> the A/V streams were not actually encrypted. I remember feeling really
> nervous when I noticed commits along that line in 0.20-fixes, but as I
> said before the 0.20.2 & 0.20-fixes channel scanner is the best yet
> in any MythTV release.

My mistake; sorry about that. I was confusing channel "scanner" with
"validation".
I'll clearly have some reading up to do :) I'm hopeful that I did
indeed experience the tuning bug before, because maybe some of these
extra non-tuning channels will turn out to be available afterall.
_______________________________________________
mythtv-dev mailing list
mythtv-dev [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev


lists at wilsonet

Aug 31, 2007, 2:41 PM

Post #9 of 11 (1162 views)
Permalink
Re: Channel scanning/validation in trunk (feedback post r14355) [In reply to]

On Aug 31, 2007, at 10:10 AM, Daniel Kristjansson wrote:

> On Fri, 2007-08-31 at 08:58 -0500, Willy Boyd wrote:
>> On 8/30/07, Daniel Kristjansson <danielk [at] cuymedia> wrote:
>>> Anyway, I'm not looking for feedback on the channel scanner anymore
>>> than usual. At the moment I'm more interested in whether the channel
>>> validation prevents channels from being added to the a Video Source
>>> when they should be added, or adds channels when it shouldn't be
>>> adding them. If someone is using esoteric recorders like DBOX2 or
>>> IPTV, or using a diverse collection of recorder types, feedback is
>>> especially appreciated.
>
>> Would this improvement also apply to a HDHomeRun and QAM channels?
>
> Again I'm not asking for any special testing of the scanner. In trunk
> the HDHomeRun scanner is much smarter about detecting encrypted
> channels
> than it used to be, but there is a bug where the wrong tuning
> information is sometimes used, usually from the transport immediately
> before or after the correct one in the scan. I think Jarod might have
> backported the fix that let MythTV detect transports which looked
> encrypted on first glance, but upon further inspection revealed that
> the A/V streams were not actually encrypted.

Correct, changesets 13238 and 13243 were the backported bits to deal
with that issue.

> I remember feeling really
> nervous when I noticed commits along that line in 0.20-fixes,

I tested the living heck out of 'em before committing, and since
channel scanning was completely busted at the time anyhow, I figured
it'd be just fine to bring 'em along. :) (hindsight being 20/20,
looks like a good call!)

> but as I said before the 0.20.2 & 0.20-fixes channel scanner is the
> best yet
> in any MythTV release.

Both 0.20-fixes and trunk seem to work equally well for me, but then
I don't have anything particularly interesting with my setup -- just
run of the mill QAM cable.

--jarod



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


nigel at ind

Sep 2, 2007, 10:15 PM

Post #10 of 11 (1116 views)
Permalink
Re: Channel scanning/validation in trunk (feedback post r14355) [In reply to]

> one thing that has always struck me as odd was when a scan is taking
> place and you want to watch what it is doing - it obscures the log
> messages with the popup which shows signal strength etc. my request
> (sans source) would be that the page be rearranged so that didn't
> happen.


Short of redesigning the ScanWizard, no tidy way to do this.


I thought of changing the PopUp so that the user could drag
it around with the mouse, but that will take more than 10 min,
so here is a hack to move the popup over and up a little.
If your screen isn't 1280x720, change the x offset:

Index: scanwizardhelpers.cpp
===================================================================
--- scanwizardhelpers.cpp (revision 14385)
+++ scanwizardhelpers.cpp (working copy)
@@ -153,6 +153,7 @@
connect(dialog, SIGNAL(popupDone(void)),
parent, SLOT( CancelScan(void)));
dialog->ShowPopup(this);
+ dialog->move(540,0);
}

void MultiplexSetting::load(void)
--
Nigel Pearson, nigel [at] ind|"In this city I confess;
Telstra Net. Eng., Sydney, Australia | god is mammon, more is less.
Office: 9202 3900 Fax: 9261 3912 | Off like lemmings at the gun!
Mobile: 0408 664435 Home: 9792 6998 | I know better, still I run"
_______________________________________________
mythtv-dev mailing list
mythtv-dev [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev


simon at koala

Sep 3, 2007, 1:14 AM

Post #11 of 11 (1127 views)
Permalink
Re: Channel scanning/validation in trunk (feedback post r14355) [In reply to]

Nigel Pearson wrote:
>> one thing that has always struck me as odd was when a scan is taking
>> place and you want to watch what it is doing - it obscures the log
>> messages with the popup which shows signal strength etc. my request
>> (sans source) would be that the page be rearranged so that didn't
>> happen.
>>
>
>
> Short of redesigning the ScanWizard, no tidy way to do this.
>
>
> I thought of changing the PopUp so that the user could drag
> it around with the mouse, but that will take more than 10 min,
> so here is a hack to move the popup over and up a little.
> If your screen isn't 1280x720, change the x offset:
>
> Index: scanwizardhelpers.cpp
> ===================================================================
> --- scanwizardhelpers.cpp (revision 14385)
> +++ scanwizardhelpers.cpp (working copy)
> @@ -153,6 +153,7 @@
> connect(dialog, SIGNAL(popupDone(void)),
> parent, SLOT( CancelScan(void)));
> dialog->ShowPopup(this);
> + dialog->move(540,0);
> }
>
> void MultiplexSetting::load(void)
> --
> Nigel Pearson, nigel [at] ind|"In this city I confess;
> Telstra Net. Eng., Sydney, Australia | god is mammon, more is less.
> Office: 9202 3900 Fax: 9261 3912 | Off like lemmings at the gun!
> Mobile: 0408 664435 Home: 9792 6998 | I know better, still I run"
> _______________________________________________
> mythtv-dev mailing list
> mythtv-dev [at] mythtv
> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev
>
>
thanks
i did realise that as a popup - it was probably not geing to happen.
thinking about it - ripping a CD is a similar process where a popup is
not used to represent progress.

but you suggestion is a good "fix"

thanks
--
simon
_______________________________________________
mythtv-dev mailing list
mythtv-dev [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev

MythTV dev 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.