[mythtv] [mythtv-commits] mythtv commit: r11390 by danielk

Daniel Kristjansson danielk at cuymedia.net
Thu Oct 5 00:02:54 UTC 2006


On Wed, 2006-10-04 at 19:09 -0400, Michael T. Dean wrote:
> On 10/03/06 08:38, Daniel Kristjansson wrote:
> I uploaded a patch to http://svn.mythtv.org/trac/ticket/2087#comment:17 
> .  I modified the existing FREQ define--I couldn't find other macros, so 
> please let me know if I should have done it differently.
Sounds good, I'll look at these this week.

> HRC, and IRC), so we could easily modify it as desired.  I would 
> recommend making HRC and IRC go up to 159, also, for the digital 
> tables.  While it may take longer to perform scans, it would help more 
> people find more channels.  Please let me know if you want a patch.
Yep, everyone is going up to higher frequencies these days.

> Also, standard cable's high frequency table starts at channel 78 
> (~550MHz), while HRC's and IRC's start at channel 76 (~535MHz).  Do we 
> want to make these more consistent?
Nah, it's close enough. In a year or so it might make sense to lower
this to 450Mhz or 400Mhz, then we can make it more consistent.

> Finally, we haven't yet made a two frequency tables for standard cable 
> (one with a positive offset and one with a negative offset for 
> aeronatical radiocommunications/radionavigation bands).  I didn't get 
> any useful responses when I asked for information from people who are 
> using standard cable and had to specify finetune values, so either a) no 
> one is seeing issues because of this or b) no one wanted to help.
Or c) they had no idea what you were talking about.
People are so used to crappy looking analog channels that they
don't even try to finetune things unless they are really far off.

> The dbcheck patches for updating finetune values will take a bit 
> longer--after your commit [11415], I found out that using LEFT JOIN on 
> an UPDATE or a DELETE is only valid in MySQL 4.x, so I have to do it the 
> hard way.
Sorry about that. I wrote a DB update once that depended on 4.x,
it was a mess to clean up with a 3.x compatible query. Perhaps this
isn't even needed in light of your experience with the two standard
cable offsets...

-- Daniel



More information about the mythtv-dev mailing list