public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Steven Toth <stoth@linuxtv.org>
To: David Schollmeyer <dschollmeyer@gmail.com>
Cc: linux-dvb@linuxtv.org
Subject: Re: [linux-dvb] HVR-1800 DVB Configuration
Date: Wed, 27 Aug 2008 03:06:59 -0400	[thread overview]
Message-ID: <48B4FD13.9030703@linuxtv.org> (raw)
In-Reply-To: <ed347ce40808262255s6bfc4f58ne2c8c00f56f95e44@mail.gmail.com>

David Schollmeyer wrote:
> Hi,
> 
> I have the Hauppauge HVR-1800 that I am trying to get setup. I can get
> the tuner to work on NTSC analog with my local cable provider (Cox
> Communications - Phoenix, AZ). I am trying to get the ATSC/QAM tuner
> to work with Cox as well. From what I've read, I should be able to get
> all of the unencrypted DTV local channels from Cox but I cannot figure
> out how to do so.
> 
> Following the steps at
> http://www.linuxtv.org/wiki/index.php/Testing_your_DVB_device, I
> created the following channels.conf file:
> KASW-DT:537000000:QAM_256:33:36
> KSAZ-DT:537000000:QAM_256:49:52
> KNXV-DT:555000000:QAM_256:33:36
> KPHO-DT:555000000:QAM_256:49:52
> KAET-DT-1:567000000:QAM_256:33:34
> KPNX-DT:567000000:QAM_256:49:52
> KAET-DT-2:567000000:QAM_256:67:70
> 
> I've tried running azap 'KAET-DT-2' gives:
> 
> using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
> tuning to 567000000 Hz
> video pid 0x0043, audio pid 0x0046
> status 00 | signal 0000 | snr 0000 | ber 00000000 | unc 00000000 |
> status 1f | signal 015e | snr 015e | ber 00000000 | unc 00000000 | FE_HAS_LOCK
> status 1f | signal 015e | snr 015e | ber 00000000 | unc 00000000 | FE_HAS_LOCK
> status 1f | signal 015e | snr 015e | ber 00000000 | unc 00000000 | FE_HAS_LOCK
> status 1f | signal 015e | snr 015e | ber 00000000 | unc 00000000 | FE_HAS_LOCK
> status 1f | signal 015e | snr 015e | ber 00000000 | unc 00000000 | FE_HAS_LOCK
> ...
> 

This looks normal. I do this in NY with Cablevision with the HVR1800 and 
it's working very well for me (and others).

> Any help on what may be wrong would be appreciated.


Chances are the streams you expect to see are encrypted. It's difficult 
to say without looking at the packets. mplayer cannot play encrypted 
streams. The other possibility is that you have the audio and video pids 
set incorrectly in your channels.conf file, this would also cause 
mplayer not to be able to play the stream correctly.

Try some other frequencies.

Also run dvbtraffic to see the packet traffic distribution across the 
pids. The video pids will have a lot more packets per second than audio, 
this may help you diagnose the problem.

I assume the channel names, pid values and service numbers in your 
channels.conf are accurate. Did this come as a result of running the 
scan app, or something else?

- Steve

_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

  reply	other threads:[~2008-08-27  7:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-27  5:55 [linux-dvb] HVR-1800 DVB Configuration David Schollmeyer
2008-08-27  7:06 ` Steven Toth [this message]
2008-08-27 15:27   ` David Schollmeyer
2008-08-27 15:39     ` Steven Toth
2008-08-27 23:30 ` Andy Walls

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=48B4FD13.9030703@linuxtv.org \
    --to=stoth@linuxtv.org \
    --cc=dschollmeyer@gmail.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