public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Goga777 <goga777@bk.ru>
To: linux-dvb@linuxtv.org
Subject: Re: [linux-dvb] Problem "watching" (not tuning to?) Astra HD Promo/Anixe HD
Date: Mon, 23 Jun 2008 22:05:54 +0400	[thread overview]
Message-ID: <20080623220554.1d8c6df5@bk.ru> (raw)
In-Reply-To: <DDA4E5EE-7DCC-4EA1-A5A8-622C1A61B945@admin.grnet.gr>

have you the same problem as I described in vdr list ?
http://linuxtv.org/pipermail/vdr/2008-May/016766.html



> I have a Hauppauge HVR-4000. My system is running the latest Debian  
> testing kernel (2.6.24-7) plus drivers from  http://linuxtv.org/hg/v4l-dvb/rev/127f67dea087 
>   patched with http://dev.kewl.org/hauppauge/experimental/mfe-s2-7285.diff 
> , as per the wiki notes (mostly): http://www.linuxtv.org/wiki/index.php/Hauppauge_WinTV-HVR-4000#Drivers
> 
> I have no problem tuning with http://dev.kewl.org/hauppauge/experimental/szap-meow.tgz 
>   to any DVB-S or DVB-S2 QPSK/8PSK transponder I have tried. However  
> there seems to be a problem with the reception of the Astra HD Promo  
> service at 11914500H on Astra1H. I don't know what the problem is  
> exactly, since tuning seems to work:
> 
> tvbox2:~# szap-meow -r -p -c diseqc2_Astra-19.2E -m 1 -e 9 -o 2 -w 2  
> ASTRAHDPROMO
> reading channels from file 'diseqc2_Astra-19.2E'
> zapping to 1 'ASTRAHDPROMO':
> sat 1, frequency = 11914 MHz H, symbolrate 27500000, vpid = 0x04ff,  
> apid = 0x0503 sid = 0x0083
> using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
> status 1f | signal fd40 | snr 6199 | ber 00000000 | unc 00000000 |  
> FE_HAS_LOCK
> status 1f | signal fe80 | snr 64cd | ber 00000000 | unc 00000000 |  
> FE_HAS_LOCK
> status 1f | signal fe40 | snr 6333 | ber 00000000 | unc 00000000 |  
> FE_HAS_LOCK
> status 1f | signal fd80 | snr 6333 | ber 00000000 | unc 00000000 |  
> FE_HAS_LOCK
> status 1f | signal fe40 | snr 6199 | ber 00000000 | unc 00000000 |  
> FE_HAS_LOCK
> status 1f | signal fe80 | snr 6000 | ber 00000000 | unc 00000000 |  
> FE_HAS_LOCK
> 
> There is an occasional ber > 0 and the snr is not exceptional, but  
> there are other services with much worse snr/ber that have no problem  
> whatsoever.
> 
> I don't have vdr, mythtv etc. applications installed on the system. I  
> test by redirecting the output of vdr0 to a file, to play back the TS  
> later, or by piping to VLC, to stream on the lan. VLC clearly shows  
> there is a problem because there is always a flood of messages from  
> libdvbpsi on stderr like Bad CRC_32, TS discontinuity, invalid  
> section, PSI section too long etc. I'm not that confident about VLC  
> debugging, but I know for sure this doesn't happen when the service  
> works right.
> 
> I've tried tuning to freq 11915 as well as using different values for  
> roll-off (-o) and pilot (-w). It doesn't make any difference (-w 1  
> doesn't work if I remember right).
> 
> The same thing happens with the Anixe HD service, also on the same  
> transponder.
> 
> I have no problem tuning to other transponders on Astra1H that carry a  
> mix of scrambled+FTA or FTA-only services, like 11875500H or  
> 12051000V, but they are DVB-S. I also have no problem tuning to DVB-S2  
> transponders on other LNBs (I have a 4x1 diseqc v1.0 switch with this  
> LNB in position AB), but I could not test any other such transponders  
> with QPSK modulation.
> 
> I'm wondering what could be the cause of this problem:
> 
> At first I thought the problem could be that the transponder carries  
> scrambled services as well, but that does not seem to be the case.
> Then I thought the problem could be the H.264 video payload of the  
> video ES of these services, confusing VLC, hence the many error  
> messages, but I've been able to stream/play at least one other  
> "similar" service (Luxe TV) with no particular problems.
> 
> Finally I reconsidered the "saga" of the HVR-4000 driver, and started  
> thinking that perhaps I should have gone with one of the other  
> implementations in the first place. I had this card setup a few months  
> ago with 2.6.24 and multiproto, but I had to redo the installation and  
> this time I wanted to try to stick with the official linuxtv.org tree.  
> Could this be the reason? If so, however, I suppose tuning wouldn't  
> work at all, right?
> 
> Am I missing something here? Any ideas/suggestions you may have are  
> more than welcome...
> 
> Thanks,
> Z.
> 
> PS: Somewhat off-topic question, but here goes anyway, since I have  
> not found a definitive answer: Is there any device with DVB-S2 *and*  
> CI and driver support for both? I have noticed that TT-budget S2-3200  
> + CI could possibly be the one, but I believe the CI part still  
> doesn't work.
> 


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

  parent reply	other threads:[~2008-06-23 18:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-23 16:30 [linux-dvb] Problem "watching" (not tuning to?) Astra HD Promo/Anixe HD Zenon Mousmoulas
2008-06-23 16:35 ` Georg Acher
2008-06-23 18:05 ` Goga777 [this message]
     [not found] <mailman.67.1214243770.883.linux-dvb@linuxtv.org>
2008-06-23 18:10 ` Zenon Mousmoulas
2008-06-23 18:20   ` Georg Acher

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=20080623220554.1d8c6df5@bk.ru \
    --to=goga777@bk.ru \
    --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