From: Steven Toth <stoth@linuxtv.org>
To: Jonathan Coles <jcoles0727@rogers.com>
Cc: linux-dvb@linuxtv.org
Subject: Re: [linux-dvb] me-tv doesn't accept its own channel file
Date: Sun, 21 Sep 2008 22:19:07 -0400 [thread overview]
Message-ID: <48D7009B.2000404@linuxtv.org> (raw)
In-Reply-To: <48D688BE.80008@rogers.com>
Jonathan Coles wrote:
> me-tv scans ATSC channels on my HVR-950Q and creates a channels.conf
> file. The file has channel entries, even though the Channel Scan window
> reports nothing but "Failed to tune" messages. But me-tv cannot use its
> own file. It complains, "There's an invalid channel record in the
> channels.conf file." Oh, come on! Was this application tested even once?
>
> My file contains the following:
>
> CKXTDT\x10:509028615:8VSB:65:67:2
> CKXT:509028615:8VSB:81:83:3
> HDTV RADIO-CANADA OTTAWA:521028615:8VSB:49:52:11
> HDTV CBC OTTAWA:539028615:8VSB:49:52:10
>
> (I live in Canada. Our TV stations have until 2011 to go digital and
> they are moving slowly.)
>
> A possible problem is the strange 2-byte character following "CKXTDT" in
> the first line, hex 0810. Removing this line did not make the file
> acceptable to me-tv.
>
> Does anyone have experience with this glitch?
Looks like you have a weird control char on the first line.
Try removing this.
Also use 'azap -r CKTX' to see if you get lock.
- Steve
_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
next prev parent reply other threads:[~2008-09-22 2:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-21 17:47 [linux-dvb] me-tv doesn't accept its own channel file Jonathan Coles
2008-09-22 2:19 ` Steven Toth [this message]
2008-09-22 10:22 ` Jonathan Coles
2009-01-03 2:59 ` Michael Lamothe
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=48D7009B.2000404@linuxtv.org \
--to=stoth@linuxtv.org \
--cc=jcoles0727@rogers.com \
--cc=linux-dvb@linuxtv.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox