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

Michael T. Dean mtdean at thirdcontact.com
Thu Oct 5 04:55:01 UTC 2006


On 10/04/06 20:02, Daniel Kristjansson wrote:

>On Wed, 2006-10-04 at 19:09 -0400, Michael T. Dean wrote:
>
>>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.
>  
>
OK.  I'll make a patch once you get the other in (as anything I make now 
will likely fail to apply after the commit assuming you modify anything 
in the patch).  Should I just put in the value or plug in the equation 
with a CHANNEL_MAX define or something to make it easy to modify?

>>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.
>  
>
True.  Forgot that one.

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

I'll leave it up to you.  It's possible to do it, but it will be a 
rather large section of code for a rather small benefit (that's will 
probably only affect a very small percentage of users).  And, of course, 
since I'm so slow with it, anyone tracking SVN head has already fixed 
theirs and will have to re-fix them after the update.  :)

Thanks,
Mike


More information about the mythtv-dev mailing list