[mythtv-users] editing channel frequencies (UK)

[Steven Cruysberghs]

freqid should be values like E9 or SE13. Depending on your frequency table
(euro-west, ... ) these nrs. correspond to a frequency wich is a 6 digit
nr. like 511250 and that is 511,250 MHz
In current CVS version of myth you can use these nubbers in the channel
table. You have to change the colum setting from varchar(5) to varchar(6)
for them to fit.

Steven


> At 10:15 05/05/2004 +0100, you wrote:
>>Glad to hear you've finally got it going. I had a few similar problems to
>>what your having below, answers also below.
>>
>>When I first set up myth it got the channel numbers horribly wrong and
>> the
>>frequencies too. When changing channel (up or down rather than directly
>>selecting a number) it tries to find the next available channel using an
>>algorithm I couldn't figure out. Ok so I didn't spend that long on it,
>> and I
>>just used myth web to adjust the frequency and channel numbers. I might
>> also
>>have changed an option in the TV settings menu to order by channel
>> number.
>>I'm not sure if that'll help much.
>
> How odd. I edited the channel numbers directly in the SQL db, but now I've
> emerged MythWeb and am looking at the channel settings now (through links,
> aargh!), and the frequencies seem completely different.
> The data from my channel finding script using ptune.pl to change channels
> gave me these numbers:
>
> Channel 26              BBC 1 (London)          511250 8180
> Channel 33:             BBC 2 (London)          567250 9076
> Channel 23:             ITV (London)            487250 7796
> Channel 30:             Ch4                     543250 8692
> Channel 37:             5                       599250 9588
>
> I'm assuming the "freqid" is the second of the two numbers listed (they
> were both numbers spat out by ptune.pl - was never quite sure what they
> meant), since the freqid entry in the db has a varchar limit of 5. I'll
> just go and update 'em now, but I won't be able to test them out yet (why
> doesn't Windows have a built-in X client?! Argh!). Most people tell me to
> use the settings file from xawtv, but IIRC xawtv can't understand MPEG2
> streams.
>
> I've been reading up on this issue obviously, and like you say this
> problem
> seems to be due to wrong channel settings for both PAL and NTSC users, so
> it now looks like this is my only remaining problem. Once I get the right
> numbers in I'll be all set, wahoo!
>
>
>> > 2) Both the program guide, manual schedule and the OSD are
>> > all empty, which
>> > I find odd to say the least. Especially considering that the
>> > program finder
>> > is packed with all kinds of stuff. Well, not all kinds, just
>> > TV kinds of stuff.
>> >
>>
>>No idea, I thought when you had xmltv running you'd have this going. :(
>
> Sorry, this was related to my dumbness regarding the time error. Once I'd
> corrected the time, the program guide became nice and choc full. I'm
> assuming it's some sort of a bug/misconfiguration issue that no one else
> has been stupid enough to run across ;^)
>
>
>> > 3) Arr. Myth is displaying the wrong time - it's running an
>> > hour ahead of
>> > BST. Oops, just checked system time and *that's* an hour
>> > ahead too - d'oh!.
>> > Sorry, ignore this one!
>> >
>>
>>Since you using Gentoo, I'll assume you've symlinked the correct
>> zone-info.
>>When I had this problem, updateing /etc/rc.conf and changing a line that
>>looks something like
>>  CLOCK=UTC
>>
>>To
>>  CLOCK=local
>>
>>(maybe a reboot too)
>>
>>That brought everything into line.
>
> When I installed the machine, I stupidly set the BIOS to BST instead of
> GMT. Hence when I told Gentoo I lived in the UK, it helpfully added an
> hour
> onto the hwclock for me.
>
>
> _______________________________________________
> mythtv-users mailing list
> mythtv-users at mythtv.org
> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
>