public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Marco Lohse <mlohse@motama.com>
To: linux-media@vger.kernel.org
Subject: Re: Problems with ngene based DVB cards (Digital Devices Cine S2 Dual 	DVB-S2 , Mystique SaTiX S2 Dual)
Date: Tue, 23 Mar 2010 10:49:49 +0100	[thread overview]
Message-ID: <4BA88EBD.7060607@motama.com> (raw)
In-Reply-To: <4BA88B5A.3040204@motama.com>

[-- Attachment #1: Type: text/plain, Size: 4297 bytes --]

Marco Lohse wrote:
> Devin Heitmueller wrote:
> [..]
>> Hi Marco,
>>
>> Ok, great.  Like I said, I will see if I can reproduce it here, as
>> that will help narrow down whether it's really an issue with the ngene
>> bridge, or whether it's got something to do with that particular
>> bridge/demod/tuner combination.
>>
> 
> We made some more tests and found some additional issues that we would
> like to report.
> 

Sorry, I forgot the attachment (modified szap-s2)

> Have fun, Marco
> 
> *Problem A revisited * *****************************
> 
> It was suggested that due to a bug the dvr should never be closed (as a
> work-around)
> 
> How does this affect channel tuning times?
> 
> Test (using the latest version of the modified szap-s2)
> 
> 0) su -c "rmmod ngene && modprobe ngene one_adapter=0"
> 
> 1) Run szap-s2 using a channels.conf with "Das Erste" and "ZDF" on
> different transponders
> 
> szap-s2 -S 1 -H -c channels_DVB-S2_transponder_switch.conf -a 0 -n 1 -i
> reading channels from file 'channels_DVB-S2_transponder_switch.conf'
> 
>>>> Das Erste
> zapping to 1 'Das Erste':
> delivery DVB-S2, modulation QPSK
> sat 0, frequency 11836 MHz H, symbolrate 27500000, coderate auto,
> rolloff 0.35
> vpid 0x0065, apid 0x0066, sid 0x0068
> using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
> Opened frontend
> Opened video demux
> Opened audio demux
> status 1f | signal  69% | snr  67% | ber 1 | unc -2 | FE_HAS_LOCK
> Delay zap_to : 0.586872
> 
>>>> ZDF
> zapping to 2 'ZDF':
> delivery DVB-S2, modulation QPSK
> sat 0, frequency 11953 MHz H, symbolrate 27500000, coderate auto,
> rolloff 0.35
> vpid 0x006e, apid 0x0078, sid 0x0082
> status 1f | signal  67% | snr  63% | ber 1 | unc -2 | FE_HAS_LOCK
> Delay zap_to : 0.580473
> 
>>>> Das Erste
> zapping to 1 'Das Erste':
> delivery DVB-S2, modulation QPSK
> sat 0, frequency 11836 MHz H, symbolrate 27500000, coderate auto,
> rolloff 0.35
> vpid 0x0065, apid 0x0066, sid 0x0068
> status 1f | signal  69% | snr  67% | ber 1 | unc -2 | FE_HAS_LOCK
> Delay zap_to : 0.553754
> 
> => Good, you will see low tuning times.
> 
> 2) in parallel to 1) - and without terminating 1) - run a second
> instance of szap-s2 that reads from the device
> 
> szap-s2 -S 1 -H -c channels_DVB-S2_transponder_switch.conf -a 1 -n 1 -r
> reading channels from file 'channels_DVB-S2_transponder_switch.conf'
> zapping to 1 'Das Erste':
> delivery DVB-S2, modulation QPSK
> sat 0, frequency 11836 MHz H, symbolrate 27500000, coderate auto,
> rolloff 0.35
> vpid 0x0065, apid 0x0066, sid 0x0068
> using '/dev/dvb/adapter1/frontend0' and '/dev/dvb/adapter1/demux0'
> Opened frontend
> Opened video demux
> Opened audio demux
> ..
> 
> 3) while 2) is running, go back to 1) and tune to different transponders
> again:
> 
>>>> ZDF
> zapping to 2 'ZDF':
> delivery DVB-S2, modulation QPSK
> sat 0, frequency 11953 MHz H, symbolrate 27500000, coderate auto,
> rolloff 0.35
> vpid 0x006e, apid 0x0078, sid 0x0082
> status 1f | signal  67% | snr  63% | ber 1 | unc -2 | FE_HAS_LOCK
> Delay zap_to : 1.774598
> 
>>>> Das Erste
> zapping to 1 'Das Erste':
> delivery DVB-S2, modulation QPSK
> sat 0, frequency 11836 MHz H, symbolrate 27500000, coderate auto,
> rolloff 0.35
> vpid 0x0065, apid 0x0066, sid 0x0068
> status 1f | signal  69% | snr  67% | ber 1 | unc -2 | FE_HAS_LOCK
> Delay zap_to : 1.772805
> 
> => Not good, whenver you use both tuners you will see tuning times to
> increase from approx. 0.5 secs to 1.7 secs.
> 
> 
> *Problem B revisited * *****************************
> 
> We also found that when reading data from the dvr device immediately
> after tuning was completed (e.g. the lock was successful), then approx.
> once in 50 iterations, we still get "old" data from the device. With
> "old" I mean from the transponder previously tuned to.
> 
> This results, for example, in the wrong "old" PAT received first.
> 
> Work-around: Simple and annoying. Add a sleep(1) before starting to read
> from device.
> 
> *Remark*
> 
> Both problems can _not_ be reproduced with any other board we tested
> (Tevii, KNC, ..)
> 
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-media" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html


[-- Attachment #2: modified_szap_s2.tar.gz --]
[-- Type: application/x-gzip, Size: 11853 bytes --]

  reply	other threads:[~2010-03-23  9:49 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-17 16:41 Problems with ngene based DVB cards (Digital Devices Cine S2 Dual DVB-S2 , Mystique SaTiX S2 Dual) Andreas Besse
2010-03-18 10:00 ` Andreas Besse
2010-03-18 14:09   ` Devin Heitmueller
2010-03-18 15:07     ` Marco Lohse
2010-03-18 15:12       ` Devin Heitmueller
2010-03-23  9:35         ` Marco Lohse
2010-03-23  9:49           ` Marco Lohse [this message]
2010-03-24 17:18             ` Marco Lohse

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=4BA88EBD.7060607@motama.com \
    --to=mlohse@motama.com \
    --cc=linux-media@vger.kernel.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