[mythtv-users] Why does Myth HD channel scan miss some frequencies that HDhomerun gets?
Michael T. Dean
mtdean at thirdcontact.com
Fri Jun 1 03:47:47 UTC 2007
On 05/31/2007 10:52 PM, William Munson wrote:
> Rick wrote:
>
>> This is a two parter (the first being more important) ...
>>
>> I just got an HDhomerun and can see incredible potential. When I use
>> the HDhomerun Gui, I can see a few channels that Myth appears to be
>> missing from it's channel scan. Can someone tell me how I can add it
>> manually and what fields I need to update?
>>
>> The second part is more of a curiosity. My TV has a QAM tuner in it.
>> For some reason the frequencies it points to is slightly different than
>> the ones that Myth points to. For example, tuning the tv to '84.3'
>> might give me ABC, but in myth it was scanned as '84.4'. Why the slight
>> discrepancy?
>>
>>
>
> The channel scanning is broken in myth. Badly so. For some reason the
> devs do not seem to be doing anything about it.
So, Daniel's creating a whole branch specifically to address channel
scanning is "not ... doing anything about it?" I'm sure posts like
yours really make get him excited about spending more of his time
working on it. (And, last I looked, he had far more lines of code in
Myth than...well, certain other people...)
> Please report these
> error in the trac system. Maybe if enough people bitch they will fix it.
Well, it may look that way to the uninitiated, but in truth, it will be
fixed not because people are bitching, but because those fixing it have
finally found enough time available to do so.
The reality is, bitching about it in Trac only slows the process because
a dev will have to close the invalid ticket; then someone will reopen it
and bitch about how it's really the highest priority ticket ever; then a
dev will have to close it again; then someone will reopen it saying,
"Some user support. With this attitude I doubt you'll attract new
users."; then a dev will close it saying, "Trac is not a forum for
discussion;" then someone will reopen the ticket; then a dev will close
it saying, "When the lead developer of the project closes your ticket 3
times, it's an indication that it should remain closed;" then someone
will post a comment saying, "I'm not reopening the ticket because the
devs are whining so much, but really this is a show stopper and should
be opened at super-duper double-dog high priority because it makes my
Myth box a paperweight."
So, you think that sentence took forever to read? Well, imagine if each
one of those exchanges required a dev to see a message in e-mail, read
it, understand that it's more useless bitching in the bug-tracking
database, go to the web page, and write up a message saying why the
ticket is being closed. Now, imagine if instead the developer had spent
that time writing code to improve channel scanning... See where I'm
going with this?
Please do all your bitching on the lists. Keep the useless comments out
of the bug-tracking database.
Just remember that with most open-source software--Myth included--you
get infinitely more than you pay for, but you're entitled to exactly
what you pay for. (And, your entitlement extends only to he whom you've
paid. So if you buy a pre-configured Myth box, bitch to the guy who
sold it to you.)
> I had to make a scan using the scan tool and then manually fix the
> channels table to the correct values.
...
> PS - Earlier tonite someone posted a message about a custom script to
> fix the channels so that zap2it listings would be correctly imported.
> You might want to check that out too.
>
Which makes it sound like you're saying that the fact that Myth can't
find the DataDirect stationid inside the broadcasted data (because the
broadcasters aren't putting it there) is how, "channel scanning is
broken in myth. Badly so."
Funny, though, how things can be made to sound so important to some
people, but yet their actions show that it's not important enough for
them to do something about it. (And by that I mean something
constructive--not bitching.)
Mike
More information about the mythtv-users
mailing list