Mailing List Archive: MythTV: Users

New Channel Scanner is really annoying

Index | Next | Previous | View Threaded

stefan_jones at comcast

Nov 19, 2009, 11:27 PM

Post #1 of 6 (989 views)
Permalink

New Channel Scanner is really annoying

Oh, for cripes sake!

I've done four or five scans this evening.

Stations which formally were recognized and included in the channel lineup are skipped.

A carefully edited channels.conf doesn't seem to make a difference.

What is this cryptic crap about giving conflicting channels a new number, and then having the new number rejected?

What do I care about encoding types?

The choices for "off the air channels" are ignore, delete, or make invisible. What if I WANT them?

I finally used my channels.conf to guide me through adding some transports. Then I did a transport scan, and got my clear QAM local channels set.

devin.heitmueller at gmail

Nov 20, 2009, 7:01 AM

Post #2 of 6 (919 views)
Permalink

Re: New Channel Scanner is really annoying [In reply to]

On Fri, Nov 20, 2009 at 2:27 AM, <stefan_jones [at] comcast> wrote:
> Oh, for cripes sake!
>
> I've done four or five scans this evening.
>
> Stations which formally were recognized and included in the channel lineup
> are skipped.
>
> A carefully edited channels.conf doesn't seem to make a difference.
>
> What is this cryptic crap about giving conflicting channels a new number,
> and then having the new number rejected?
>
> What do I care about encoding types?
>
> The choices for "off the air channels" are ignore, delete, or make
> invisible. What if I WANT them?
>
> I finally used my channels.conf to guide me through adding some transports.
> Then I did a transport scan, and got my clear QAM local channels set.

Patches are always welcome from those who are the most significantly
bothered by the state of the code.

Devin

--
Devin J. Heitmueller
http://www.devinheitmueller.com
AIM: devinheitmueller
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

mitchell.gore at gmail

Nov 20, 2009, 7:14 AM

Post #3 of 6 (914 views)
Permalink

Re: New Channel Scanner is really annoying [In reply to]

On Fri, Nov 20, 2009 at 9:01 AM, Devin Heitmueller <
devin.heitmueller [at] gmail> wrote:

> On Fri, Nov 20, 2009 at 2:27 AM, <stefan_jones [at] comcast> wrote:
> > Oh, for cripes sake!
> >
> > I've done four or five scans this evening.
> >
> > Stations which formally were recognized and included in the channel
> lineup
> > are skipped.
> >
> > A carefully edited channels.conf doesn't seem to make a difference.
> >
> > What is this cryptic crap about giving conflicting channels a new number,
> > and then having the new number rejected?
> >
> > What do I care about encoding types?
> >
> > The choices for "off the air channels" are ignore, delete, or make
> > invisible. What if I WANT them?
> >
> > I finally used my channels.conf to guide me through adding some
> transports.
> > Then I did a transport scan, and got my clear QAM local channels set.
>
> Patches are always welcome from those who are the most significantly
> bothered by the state of the code.
>
> Devin
>
>

Agree with you. I have had .22 channel scanner issues since I got cable. I
have similar erros for QAM scanning.

I opened a ticket but it was rejected as not an error. But it clearly is.
To get around it I use my HDHR, the windows gui, and SiliconDust's lineup
server and manually enter channels into the MySQL DB. Its really
frustrating as it worked perfect in .21.

http://svn.mythtv.org/trac/ticket/6867

Not having the skills of programming to fix it, I really get a bad taste in
my mouth.

GL,
--
Mitchell

mtdean at thirdcontact

Nov 20, 2009, 7:22 AM

Post #4 of 6 (917 views)
Permalink

Re: New Channel Scanner is really annoying [In reply to]

On 11/20/2009 10:01 AM, Devin Heitmueller wrote:
> On Fri, Nov 20, 2009 at 2:27 AM, wrote:
>
>> Oh, for cripes sake!
>>
>> I've done four or five scans this evening.
>>
>> Stations which formally were recognized and included in the channel lineup
>> are skipped.
>>
>> A carefully edited channels.conf doesn't seem to make a difference.
>>
>> What is this cryptic crap about giving conflicting channels a new number,
>> and then having the new number rejected?
>>
>> What do I care about encoding types?
>>
>> The choices for "off the air channels" are ignore, delete, or make
>> invisible. What if I WANT them?
>>
>> I finally used my channels.conf to guide me through adding some transports.
>> Then I did a transport scan, and got my clear QAM local channels set.
>>
> Patches are always welcome from those who are the most significantly
> bothered by the state of the code.

Yes. Specifically, the channel scanner was basically rewritten from
scratch for 0.22 to fix a ton of problems in the old channel scanner. A
/lot/ of testing was done by the developers to ensure it worked properly
with the broadcasts to which they had access. Those who receive
broadcasts very different from the broadcasts the developers were able
to test need to help us fix the new channel scanner to work with their
broadcasts (rather than just complaining about change).

However, based on your e-mail address, I'm guessing you just need to use
a different tool that supports the as-yet-unsupported by MythTV SCTE65
standard. See http://www.mythtv.org/wiki/Comcast_Users_And_scte65scan .

And, yes, I could have suggested that to you even without the "New
Channel Scanner is really annoying" and "for cripes sake!"
complaints--i.e. if you showed a little bit more respect for the people
who invested a lot of their time to improve things (especially since
what's causing you problems, now, is not so much 0.22, but your cable
company's having changed the way it's doing things).

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

mtdean at thirdcontact

Nov 20, 2009, 7:27 AM

Post #5 of 6 (910 views)
Permalink

Re: New Channel Scanner is really annoying [In reply to]

On 11/20/2009 10:14 AM, Mitch Gore wrote:
> Agree with you. I have had .22 channel scanner issues since I got
> cable. I have similar erros for QAM scanning.
>
> I opened a ticket but it was rejected as not an error. But it clearly
> is. To get around it I use my HDHR, the windows gui, and
> SiliconDust's lineup server and manually enter channels into the MySQL
> DB. Its really frustrating as it worked perfect in .21.
>
> http://svn.mythtv.org/trac/ticket/6867
>
> Not having the skills of programming to fix it, I really get a bad
> taste in my mouth.

It is not an error. SCTE65 is an as-yet-unsupported-in-MythTV
out-of-band channel metadata encoding standard. Therefore, #6867 is a
feature request without a patch.

http://www.etherguidesystems.com/Help/SDOs/SCTE/Standards/SCTE65.aspx

Without a patch, it's a feature that will be added to MythTV when a
developer with access to such encoding and with the time to write the
code to support it gets around to doing so. With a patch, it would
likely get included in MythTV trunk sooner.

Mike

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

greg12866 at nycap

Nov 20, 2009, 7:48 AM

Post #6 of 6 (911 views)
Permalink

Re: New Channel Scanner is really annoying [In reply to]

Mitch Gore wrote:
> On Fri, Nov 20, 2009 at 9:01 AM, Devin Heitmueller
> <devin.heitmueller [at] gmail <mailto:devin.heitmueller [at] gmail>> wrote:
>
> On Fri, Nov 20, 2009 at 2:27 AM, <stefan_jones [at] comcast
> <mailto:stefan_jones [at] comcast>> wrote:
> > Oh, for cripes sake!
> >
> > I've done four or five scans this evening.
> >
> > Stations which formally were recognized and included in the
> channel lineup
> > are skipped.
> >
> > A carefully edited channels.conf doesn't seem to make a difference.
> >
> > What is this cryptic crap about giving conflicting channels a
> new number,
> > and then having the new number rejected?
> >
> > What do I care about encoding types?
> >
> > The choices for "off the air channels" are ignore, delete, or make
> > invisible. What if I WANT them?
> >
> > I finally used my channels.conf to guide me through adding some
> transports.
> > Then I did a transport scan, and got my clear QAM local channels
> set.
>
> Patches are always welcome from those who are the most significantly
> bothered by the state of the code.
>
> Devin
>
>
>
> Agree with you. I have had .22 channel scanner issues since I got
> cable. I have similar erros for QAM scanning.
>
> I opened a ticket but it was rejected as not an error. But it clearly
> is. To get around it I use my HDHR, the windows gui, and
> SiliconDust's lineup server and manually enter channels into the MySQL
> DB. Its really frustrating as it worked perfect in .21.
>
> http://svn.mythtv.org/trac/ticket/6867
>
> Not having the skills of programming to fix it, I really get a bad
> taste in my mouth.
>
> GL,
> --
> Mitchell
> ------------------------------------------------------------------------
>
> _______________________________________________
> mythtv-users mailing list
> mythtv-users [at] mythtv
> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
>
Do a regular back-up of your database,then the next time you update,just
import the old database and you will be good to go...Just yesterday I
had a problem where my HD-PVR got un-plugged..This caused the tuner
assignments to change..Five minutes to restore the DB and I was back in
business..Thanks to Mike Dean..
I will admit the new scanner is a handful,especially if you don't know
what it's asking for when the scan is done,but it does work.. I just
choose ignore and continue.. When it's done all my channels are in the DB...

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

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact Gossamer Threads