Re: [linux-dvb] How to use scan-s2?

Re: [linux-dvb] How to use scan-s2?

[Jens Krehbiel-Gräther]

Artem Makhutov schrieb:
> Hello,
>
> I am wondering on how to use scan-s2.
>
> When running scan-s2 like this I am only getting 13 services:
>
> scan-s2 -a 2 -o zap /usr/share/dvb/dvb-s/Astra-19.2E > channels.conf
>
> when running
>
> scan-s2 -a 2 -n -o zap /usr/share/dvb/dvb-s/Astra-19.2E > channels.conf
>
> then I am getting 152 services.
>
> When running the old dvbscan application I am getting 1461 services:
>
> dvbscan -a 2 -o zap /usr/share/dvb/dvb-s/Astra-19.2E > channels.conf
>
>
> Have I missed a parameter in scan-s2 or what else could be the problem?
>
> Thanks, Artem


Hi Artem!

I had the same "problem".When add no options I am only getting a few 
services.
When I add the "-n" option I get some more services but all services I 
only get, when I am adding "-n -5".

the "-5" means:
multiply all filter timeouts by factor 5 for non-DVB-compliant section 
repitition rates

The scan takes a long time then, but I get 1476 services (Astra 19.2).
My device is a Pinnacle PCTV 452e (USB).
Perhaps this switch is working with your device, too?

Jens

_______________________________________________
linux-dvb users mailing list
For V4L/DVB development, please use instead linux-media@vger.kernel.org
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

[linux-dvb] How to use scan-s2?

[Artem Makhutov]

Hello,

I am wondering on how to use scan-s2.

When running scan-s2 like this I am only getting 13 services:

scan-s2 -a 2 -o zap /usr/share/dvb/dvb-s/Astra-19.2E > channels.conf

when running

scan-s2 -a 2 -n -o zap /usr/share/dvb/dvb-s/Astra-19.2E > channels.conf

then I am getting 152 services.

When running the old dvbscan application I am getting 1461 services:

dvbscan -a 2 -o zap /usr/share/dvb/dvb-s/Astra-19.2E > channels.conf


Have I missed a parameter in scan-s2 or what else could be the problem?

Thanks, Artem



_______________________________________________
linux-dvb users mailing list
For V4L/DVB development, please use instead linux-media@vger.kernel.org
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] How to use scan-s2?

[Alex Betis]

[-- Attachment #1.1: Type: text/plain, Size: 1755 bytes --]

On Sun, Jan 25, 2009 at 11:49 AM, Jens Krehbiel-Gräther <
linux-dvb@okg-computer.de> wrote:

> Artem Makhutov schrieb:
> > Hello,
> >
> > I am wondering on how to use scan-s2.
> >
> > When running scan-s2 like this I am only getting 13 services:
> >
> > scan-s2 -a 2 -o zap /usr/share/dvb/dvb-s/Astra-19.2E > channels.conf
> >
> > when running
> >
> > scan-s2 -a 2 -n -o zap /usr/share/dvb/dvb-s/Astra-19.2E > channels.conf
> >
> > then I am getting 152 services.
> >
> > When running the old dvbscan application I am getting 1461 services:
> >
> > dvbscan -a 2 -o zap /usr/share/dvb/dvb-s/Astra-19.2E > channels.conf
> >
> >
> > Have I missed a parameter in scan-s2 or what else could be the problem?
> >
> > Thanks, Artem
>
>
> Hi Artem!
>
> I had the same "problem".When add no options I am only getting a few
> services.
> When I add the "-n" option I get some more services but all services I
> only get, when I am adding "-n -5".
>
> the "-5" means:
> multiply all filter timeouts by factor 5 for non-DVB-compliant section
> repitition rates
>
> The scan takes a long time then, but I get 1476 services (Astra 19.2).
> My device is a Pinnacle PCTV 452e (USB).
> Perhaps this switch is working with your device, too?
>

I also run it with "-5".
I personaly don't like to use network advertisements (-n switch) since I
don't trust them.
I use a full frequency filled INI file.

If you have a stb0899 device, don't forget to add "-k 3".


>
> Jens
>
> _______________________________________________
> linux-dvb users mailing list
> For V4L/DVB development, please use instead linux-media@vger.kernel.org
> linux-dvb@linuxtv.org
> http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
>

[-- Attachment #1.2: Type: text/html, Size: 2564 bytes --]

[-- Attachment #2: Type: text/plain, Size: 228 bytes --]

_______________________________________________
linux-dvb users mailing list
For V4L/DVB development, please use instead linux-media@vger.kernel.org
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] How to use scan-s2?

[Artem Makhutov]

Hi,

Jens Krehbiel-Gräther schrieb:
> Artem Makhutov schrieb:
>   
>> Hello,
>>
>> I am wondering on how to use scan-s2.
>>
>> When running scan-s2 like this I am only getting 13 services:
>>
>> scan-s2 -a 2 -o zap /usr/share/dvb/dvb-s/Astra-19.2E > channels.conf
>>
>> when running
>>
>> scan-s2 -a 2 -n -o zap /usr/share/dvb/dvb-s/Astra-19.2E > channels.conf
>>
>> then I am getting 152 services.
>>
>> When running the old dvbscan application I am getting 1461 services:
>>
>> dvbscan -a 2 -o zap /usr/share/dvb/dvb-s/Astra-19.2E > channels.conf
>>
>>
>> Have I missed a parameter in scan-s2 or what else could be the problem?
>>
>> Thanks, Artem
>>     
>
>
> Hi Artem!
>
> I had the same "problem".When add no options I am only getting a few 
> services.
> When I add the "-n" option I get some more services but all services I 
> only get, when I am adding "-n -5".
>
> the "-5" means:
> multiply all filter timeouts by factor 5 for non-DVB-compliant section 
> repitition rates
>
> The scan takes a long time then, but I get 1476 services (Astra 19.2).
> My device is a Pinnacle PCTV 452e (USB).
> Perhaps this switch is working with your device, too?
>   
I just tried it out. It does not work :( I am getting 217 services now.
So I am still missing ~1200 services.

I have run the scan using a TeVii S650. Now I have run then same using
my SkyStar HD and I got 1467 services.

So there is something not working using the TeVii S650...

Any ideas?

Regards, Artem

Re: [linux-dvb] How to use scan-s2?

[Hans Werner]

> If you have a stb0899 device, don't forget to add "-k 3".

Oh. Can someone say what's different about the stb0899 here,
and how -k 3 helps ?

Thanks,
Hans


-- 
Release early, release often.

Psssst! Schon vom neuen GMX MultiMessenger gehört? Der kann`s mit allen: http://www.gmx.net/de/go/multimessenger

Re: [linux-dvb] How to use scan-s2?

[Alex Betis]

[-- Attachment #1.1: Type: text/plain, Size: 1612 bytes --]

On Sun, Jan 25, 2009 at 4:41 PM, Hans Werner <HWerner4@gmx.de> wrote:

> > If you have a stb0899 device, don't forget to add "-k 3".
>
> Oh. Can someone say what's different about the stb0899 here,
> and how -k 3 helps ?


Since I've added it, I'll try to defend it :)

stb0899 driver (or maybe the chip?) has some buffers inside that are not
reset between tunnings.
In that case messages from *previous* channel will arrive after the tunning
to new channel is complete.
Those messages will create a big mess in the results, such as channels
without names, duplicate channels on different transponders.
-k option specifies how many messages should be ignored before processing
it. I couldn't think of a more elegant way to ignore messages from
previously tuned channel. I use "-k 3" by myself, but after playing around
with "-k 2" saw that its also working. "-k 1" was still not enough.

The proper way is to have an option to reset that buffer in the driver after
tunning.
Since I don't know how it can be done and how it will affect tunning of
channels for viewing, I didn't want to go that way and solve it in scan-s2.

Regards,
Alex.


>
>
> Thanks,
> Hans
>
>
> --
> Release early, release often.
>
> Psssst! Schon vom neuen GMX MultiMessenger gehört? Der kann`s mit allen:
> http://www.gmx.net/de/go/multimessenger
>
> _______________________________________________
> linux-dvb users mailing list
> For V4L/DVB development, please use instead linux-media@vger.kernel.org
> linux-dvb@linuxtv.org
> http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
>

[-- Attachment #1.2: Type: text/html, Size: 2619 bytes --]

[-- Attachment #2: Type: text/plain, Size: 228 bytes --]

_______________________________________________
linux-dvb users mailing list
For V4L/DVB development, please use instead linux-media@vger.kernel.org
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] How to use scan-s2?

[Hans Werner]

> On Sun, Jan 25, 2009 at 4:41 PM, Hans Werner <HWerner4@gmx.de> wrote:
> 
> > > If you have a stb0899 device, don't forget to add "-k 3".
> >
> > Oh. Can someone say what's different about the stb0899 here,
> > and how -k 3 helps ?
> 
> 
> Since I've added it, I'll try to defend it :)
> 
> stb0899 driver (or maybe the chip?) has some buffers inside that are not
> reset between tunnings.
> In that case messages from *previous* channel will arrive after the
> tunning
> to new channel is complete.
> Those messages will create a big mess in the results, such as channels
> without names, duplicate channels on different transponders.
> -k option specifies how many messages should be ignored before processing
> it. I couldn't think of a more elegant way to ignore messages from
> previously tuned channel. I use "-k 3" by myself, but after playing around
> with "-k 2" saw that its also working. "-k 1" was still not enough.
> 
> The proper way is to have an option to reset that buffer in the driver
> after
> tunning.
> Since I don't know how it can be done and how it will affect tunning of
> channels for viewing, I didn't want to go that way and solve it in
> scan-s2.
> 
> Regards,
> Alex.

OK, thanks, I will check if I see that problem. Which card(s)
did you see this with?
Hans
-- 
Release early, release often.

Psssst! Schon vom neuen GMX MultiMessenger gehört? Der kann`s mit allen: http://www.gmx.net/de/go/multimessenger

Re: [linux-dvb] How to use scan-s2?

[Alex Betis]

[-- Attachment #1.1: Type: text/plain, Size: 1982 bytes --]

On Sun, Jan 25, 2009 at 6:29 PM, Hans Werner <HWerner4@gmx.de> wrote:

> > On Sun, Jan 25, 2009 at 4:41 PM, Hans Werner <HWerner4@gmx.de> wrote:
> >
> > > > If you have a stb0899 device, don't forget to add "-k 3".
> > >
> > > Oh. Can someone say what's different about the stb0899 here,
> > > and how -k 3 helps ?
> >
> >
> > Since I've added it, I'll try to defend it :)
> >
> > stb0899 driver (or maybe the chip?) has some buffers inside that are not
> > reset between tunnings.
> > In that case messages from *previous* channel will arrive after the
> > tunning
> > to new channel is complete.
> > Those messages will create a big mess in the results, such as channels
> > without names, duplicate channels on different transponders.
> > -k option specifies how many messages should be ignored before processing
> > it. I couldn't think of a more elegant way to ignore messages from
> > previously tuned channel. I use "-k 3" by myself, but after playing
> around
> > with "-k 2" saw that its also working. "-k 1" was still not enough.
> >
> > The proper way is to have an option to reset that buffer in the driver
> > after
> > tunning.
> > Since I don't know how it can be done and how it will affect tunning of
> > channels for viewing, I didn't want to go that way and solve it in
> > scan-s2.
> >
> > Regards,
> > Alex.
>
> OK, thanks, I will check if I see that problem. Which card(s)
> did you see this with?
> Hans

I'm aware only about Twinhan 1041 and TT-3200 based stb0899 cards. Both have
the same problem.


>
> --
> Release early, release often.
>
> Psssst! Schon vom neuen GMX MultiMessenger gehört? Der kann`s mit allen:
> http://www.gmx.net/de/go/multimessenger
>
> _______________________________________________
> linux-dvb users mailing list
> For V4L/DVB development, please use instead linux-media@vger.kernel.org
> linux-dvb@linuxtv.org
> http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
>

[-- Attachment #1.2: Type: text/html, Size: 2886 bytes --]

[-- Attachment #2: Type: text/plain, Size: 228 bytes --]

_______________________________________________
linux-dvb users mailing list
For V4L/DVB development, please use instead linux-media@vger.kernel.org
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] How to use scan-s2?

[Goga777]

> I have run the scan using a TeVii S650. Now I have run then same using
> my SkyStar HD and I got 1467 services.
> 
> So there is something not working using the TeVii S650...

have you any duplicates channels in channels list after of scan with tevii ?
could you have a look on debug logs of cx24116 during of scan ? have you any messages like these 

unsupported rolloff selected (3) 

Goga

Re: [linux-dvb] How to use scan-s2?

[Mika Laitio]

> I also run it with "-5".
> I personaly don't like to use network advertisements (-n switch) since I
> don't trust them.
> I use a full frequency filled INI file.

Hi

It might be that the signal is not the best possible for me as I can only 
scan about 500 channels with scan by using a command:
./scan -o vdr -a 1 Astra-19.2E

In Astra-19.2E I have single line:
#Astra 1KR (19.2E) - 10743.75 H - DVB-S (QPSK) - 22000 5/6 - NID:1 - TID:1051
S 10743750 H 22000000 5/6

However, once scanned the channels like eurosport, arte, skynews, cnn 
international shows up just fine with vdr-1.6.0.

But if I try to use the same Astra-19.2E file with scan-s2, it can only 
find the channels from frequency 10743750 if I have stopped the "scan" 
after it had found those channels... If I let the scan to run in the end 
to other frequencies, then scan-s2 can not find anything...

./scan-s2 -a 1 -5 -n Astra-19.2E

Propably Klaus Schmidinger reported something related with his TT-3200 in
http://www.mail-archive.com/vdr@linuxtv.org/msg08493.html
I have however hvr-4000.

To prove how it goes, here is the tuning log for 4 different runs.
1) scan when allowed it to swich to other frequence after tuning 
channels from 10643750
2) scan-s2 run after that (no channels found)
3) scan when stopping it immediately after it has found channels from 
10643750
4) scan-s2 after that (now it found correctly all 5 channels that are 
repoted to be in 10543750, but failed to tune from other freqs)

1)
[lamikr@tinka scan]$ ./scan -a 1 Astra-19.2E
scanning Astra-19.2E
using '/dev/dvb/adapter1/frontend0' and '/dev/dvb/adapter1/demux0'
initial transponder 10743750 H 22000000 5
>>> tune to: 10743:h:0:22000
DVB-S IF freq is 993750
0x0000 0x7031: pmt_pid 0x0000 ARD -- EinsExtra (running)
0x0000 0x7032: pmt_pid 0x0000 ARD -- EinsFestival (running)
0x0000 0x7033: pmt_pid 0x0000 ARD -- EinsPlus (running)
0x0000 0x7034: pmt_pid 0x0000 ARD -- arte (running)
0x0000 0x7035: pmt_pid 0x0000 ARD -- Phoenix (running)
Network Name 'ASTRA'
>>> tune to: 12692:h:0:22000
DVB-S IF freq is 2092250
0x045d 0x32c9: pmt_pid 0x03e9 ORF -- ORF1 (running, scrambled)
0x045d 0x32ca: pmt_pid 0x03ea ORF -- ORF2 (running, scrambled)
0x045d 0x32cb: pmt_pid 0x03f3 ORF -- ORF2 W (running, scrambled)
0x045d 0x32cc: pmt_pid 0x03f4 ORF -- ORF2 N (running, scrambled)
0x045d 0x32cd: pmt_pid 0x03f5 ORF -- ORF2 B (running, scrambled)
0x045d 0x32ce: pmt_pid 0x03f6 ORF -- ORF2 O (running, scrambled)
0x045d 0x32cf: pmt_pid 0x03f7 ORF -- ORF2 S (running, scrambled)
0x045d 0x32d0: pmt_pid 0x03f8 ORF -- ORF2 T (running, scrambled)
0x045d 0x32d1: pmt_pid 0x03f9 ORF -- ORF2 V (running, scrambled)
0x045d 0x32d2: pmt_pid 0x03fa ORF -- ORF2 St (running, scrambled)
0x045d 0x32d3: pmt_pid 0x03fb ORF -- ORF2 K (running, scrambled)
0x045d 0x32d4: pmt_pid 0x03fc ATV+ -- ATV+ (running, scrambled)
0x045d 0x32d5: pmt_pid 0x03eb ORF -- HITRADIO OE3 (running)
0x045d 0x32d6: pmt_pid 0x03ec ORF -- ORF2E (running)
0x045d 0x32d9: pmt_pid 0x03ef arena -- Bundesliga 5 (not running, 
scrambled)
0x045d 0x32da: pmt_pid 0x03f0 arena -- Bundesliga 6 (not running, 
scrambled)
0x045d 0x3390: pmt_pid 0x04b0 ORF -- AlphaCrypt (running)
0x045d 0x339a: pmt_pid 0x04ba ORS -- Siemens Download (running)
0x045d 0x33a4: pmt_pid 0x0000 ORF -- VESTEL OAD2 (running)
0x045d 0x33ae: pmt_pid 0x04ce ORF -- VESTEL DOWNLOAD (running)
^CERROR: interrupted by SIGINT, dumping partial result...
dumping lists (25 services)
...

2) [lamikr@tinka scan-s2]$ ./scan-s2 -a 1 
/home/lamikr/dvb/apps/dvb-apps_20090126/util/scan/Astra-19.2E
API major 5, minor 0
scanning /home/lamikr/dvb/apps/dvb-apps_20090126/util/scan/Astra-19.2E
using '/dev/dvb/adapter1/frontend0' and '/dev/dvb/adapter1/demux0'
initial transponder DVB-S2 10743750 H 22000000 5/6 AUTO AUTO
initial transponder DVB-S  10743750 H 22000000 5/6 AUTO AUTO
----------------------------------> Using DVB-S2
>>> tune to: 10743:hC56S1:S0.0W:22000:
DVB-S IF freq is 993750
WARNING: >>> tuning failed!!!
>>> tune to: 10743:hC56S1:S0.0W:22000: (tuning failed)
DVB-S IF freq is 993750
WARNING: >>> tuning failed!!!
----------------------------------> Using DVB-S
>>> tune to: 10743:hC56S0:S0.0W:22000:
DVB-S IF freq is 993750
WARNING: >>> tuning failed!!!
>>> tune to: 10743:hC56S0:S0.0W:22000: (tuning failed)
DVB-S IF freq is 993750
WARNING: >>> tuning failed!!!
ERROR: initial tuning failed
dumping lists (0 services)
Done.

3) [lamikr@tinka scan]$ ./scan -a 1 Astra-19.2E
scanning Astra-19.2E
using '/dev/dvb/adapter1/frontend0' and '/dev/dvb/adapter1/demux0'
initial transponder 10743750 H 22000000 5
>>> tune to: 10743:h:0:22000
DVB-S IF freq is 993750
0x0000 0x7031: pmt_pid 0x0064 ARD -- EinsExtra (running)
0x0000 0x7032: pmt_pid 0x00c8 ARD -- EinsFestival (running)
0x0000 0x7033: pmt_pid 0x012c ARD -- EinsPlus (running)
0x0000 0x7034: pmt_pid 0x0190 ARD -- arte (running)
0x0000 0x7035: pmt_pid 0x01f4 ARD -- Phoenix (running)
^X^CERROR: interrupted by SIGINT, dumping partial result...
dumping lists (5 services)
EinsExtra:10743:h:0:22000:101:102:28721
EinsFestival:10743:h:0:22000:201:202:28722
EinsPlus:10743:h:0:22000:301:302:28723
arte:10743:h:0:22000:401:402:28724
Phoenix:10743:h:0:22000:501:502:28725
Done.

4) [lamikr@tinka scan-s2]$ ./scan-s2 -a 1 
/home/lamikr/dvb/apps/dvb-apps_20090126/util/scan/Astra-19.2E
API major 5, minor 0
scanning /home/lamikr/dvb/apps/dvb-apps_20090126/util/scan/Astra-19.2E
using '/dev/dvb/adapter1/frontend0' and '/dev/dvb/adapter1/demux0'
initial transponder DVB-S2 10743750 H 22000000 5/6 AUTO AUTO
initial transponder DVB-S  10743750 H 22000000 5/6 AUTO AUTO
----------------------------------> Using DVB-S2
>>> tune to: 10743:hC56S1:S0.0W:22000:
DVB-S IF freq is 993750
>>> parse_section, section number 0 out of 0...!
service_id = 0x0
service_id = 0x7031
pmt_pid = 0x64
service_id = 0x7032
pmt_pid = 0xC8
service_id = 0x7033
pmt_pid = 0x12C
service_id = 0x7034
pmt_pid = 0x190
service_id = 0x7035
pmt_pid = 0x1F4
>>> parse_section, section number 0 out of 0...!
   VIDEO     : PID 0x012D
   AUDIO     : PID 0x012E
   TELETEXT  : PID 0x0130
   OTHER     : PID 0x0172 TYPE 0x05
   OTHER     : PID 0x0173 TYPE 0x0B
   OTHER     : PID 0x0818 TYPE 0x0B
>>> parse_section, section number 0 out of 0...!
   VIDEO     : PID 0x00C9
   AUDIO     : PID 0x00CA
   TELETEXT  : PID 0x00CC
   OTHER     : PID 0x010E TYPE 0x05
   OTHER     : PID 0x0818 TYPE 0x0B
>>> parse_section, section number 0 out of 0...!
   VIDEO     : PID 0x0065
   AUDIO     : PID 0x0066
   OTHER     : PID 0x00AA TYPE 0x05
   OTHER     : PID 0x00AB TYPE 0x0B
   OTHER     : PID 0x00AC TYPE 0x05
   OTHER     : PID 0x00AD TYPE 0x0B
   OTHER     : PID 0x00B0 TYPE 0x0C
   OTHER     : PID 0x0818 TYPE 0x0B
>>> parse_section, section number 0 out of 0...!
   VIDEO     : PID 0x01F5
   AUDIO     : PID 0x01F6
   TELETEXT  : PID 0x01F8
   OTHER     : PID 0x0816 TYPE 0x05
   OTHER     : PID 0x0818 TYPE 0x0B
>>> parse_section, section number 0 out of 0...!
   VIDEO     : PID 0x0191
   AUDIO     : PID 0x0192
   AUDIO     : PID 0x0193
   TELETEXT  : PID 0x0194
   OTHER     : PID 0x0816 TYPE 0x05
   OTHER     : PID 0x0818 TYPE 0x0B
>>> parse_section, section number 0 out of 0...!
0x041B 0x7031: pmt_pid 0x0064 ARD -- EinsExtra (running)
0x041B 0x7032: pmt_pid 0x00C8 ARD -- EinsFestival (running)
0x041B 0x7033: pmt_pid 0x012C ARD -- EinsPlus (running)
0x041B 0x7034: pmt_pid 0x0190 ARD -- arte (running)
0x041B 0x7035: pmt_pid 0x01F4 ARD -- Phoenix (running)
>>> parse_section, section number 1 out of 1...!
>>> parse_section, section number 0 out of 1...!
Network Name 'ASTRA'
dumping lists (5 services)
EinsExtra;ARD:10743:hC56M2S0:S19.2E:22000:101:102=ger:0:0:28721:1:1051:0
EinsFestival;ARD:10743:hC56M2S0:S19.2E:22000:201:202=ger:204:0:28722:1:1051:0
EinsPlus;ARD:10743:hC56M2S0:S19.2E:22000:301:302=ger:304:0:28723:1:1051:0
arte;ARD:10743:hC56M2S0:S19.2E:22000:401:402=ger,403=fra:404:0:28724:1:1051:0
Phoenix;ARD:10743:hC56M2S0:S19.2E:22000:501:502=ger:504:0:28725:1:1051:0
Done.

Mika

Re: [linux-dvb] How to use scan-s2?

[BOUWSMA Barry]

On Sun, 25 Jan 2009, Alex Betis wrote:

> On Sun, Jan 25, 2009 at 6:29 PM, Hans Werner <HWerner4@gmx.de> wrote:
> > > On Sun, Jan 25, 2009 at 4:41 PM, Hans Werner <HWerner4@gmx.de> wrote:

> > > > > If you have a stb0899 device, don't forget to add "-k 3".

> > > > Oh. Can someone say what's different about the stb0899 here,
> > > > and how -k 3 helps ?

> > > stb0899 driver (or maybe the chip?) has some buffers inside that are not
> > > reset between tunnings.
> > > In that case messages from *previous* channel will arrive after the
> > > tunning
> > > to new channel is complete.
> > > Those messages will create a big mess in the results, such as channels
> > > without names, duplicate channels on different transponders.
> > > -k option specifies how many messages should be ignored before processing
> > > it. I couldn't think of a more elegant way to ignore messages from
> > > previously tuned channel. I use "-k 3" by myself, but after playing
> > around
> > > with "-k 2" saw that its also working. "-k 1" was still not enough.

> > OK, thanks, I will check if I see that problem. Which card(s)
> > did you see this with?

> I'm aware only about Twinhan 1041 and TT-3200 based stb0899 cards. Both have
> the same problem.

This may be going typically off-topic, but I do experience
similar artifacts with some STV0299 cards (looks superficially
alike; I don't know), which I'll toss out here just for giggles.

It turns out I have three if not four such stv0299 cards, and
I either experience `scan' difficulties or recording issues,
or nothing.

First off, for reference:  a PCI SkyStar2 card that gets
priority for recordings, using a 2.6.14-ish kernel that I'm
in the long slow process of planning to update on that
production machine.

When making two recordings separated by time from the same
transponder, often the second recording will have a few
video frames left over from the previous recording.  This
appears in my quality-control as video frames with differing
timestamps as well as errors when run through `mplayer'
video codec ffmpeg12, but timing data remains intact (I can
`dd' away the first second or more and get a flawless
partial transport stream).

This is not a problem when I switch between transponders
to make the second recording.  And it can be many hours
between recordings from the same transponder, yet the
leftover data still remains.

I've never noticed that this affects `scan' which changes
transponders; that in itself seems to be enough to lose
the buffered data.  This is only a minor concern as the
first few frames of confused data are almost certainly
disposable, as a fraction of a second in the padding
leading up to the content of interest.


As exhibit number two, where I have had problems with
regular `scan' seeing data from the previous transponder
and causing problems getting current data, another
stv0299-based device, the Opera-1 USB-connected tuner.
I have *never* seen any recordings made from this
device contain frames from an earlier tuning session,
though.

As far as `scan' tuning goes, I would regularly see
previous ``phantom'' channels appearing, combined with
zero-value PIDs for channels on the intended current
transponder.  At least until recently; my latest scans
have been flawless, either due to hacks I added to
that `scan' or to kernel updates on that test machine.


Exhibit C, m'lud, will be -- again on the 2.6.14-ish
kernel machine, but this time connected via USB 1.1 --
an early Nova-S device.  Apart from bandwidth issues
due to the usb1 interface, I've never noticed problems
with stale packets when recording from either the same
or a different transponder.  I do have other issues
which may be due to the age of the kernel, but `scan'
also has not had problems.


Now with exhibit IV, again I see problems similar to
those experienced with leftover packets, but which
appear to be compounded by the internal mangling of
the transport stream components into a proprietary-
yet-open delivery stream.  This device is the ttusb-
dec DEC3000-s, of unknown-based-on-kernel-code
heritage, though I may have taken it apart long ago
and written the results on a long-since hidden drive.

This device is connected via USB1, and is incapable
of delivering more than an MPEG2 video and mp2 audio
stream to a recording, making it useless for multiple
audio, teletext, AC3, H.264, or PMT tables to start.

It also internally converts the transport stream
into the PVA format, with side-effects such as that
the timestamps do not match the original transport
stream components, cycling after some 40 000 secs
rather than the 90 000-ish seconds delivered in the
streams from other devices.

Recordings from this device all-too-often would have
timing problems as well as leftover data from a
previous recording.  (Whether from same or different
transponder, I cannot say.  I added a hack-workaround
to my recordings to tune briefly a different txp,
then tune back.  Sometimes it worked.  Often with
high load, nothing could help.)  Sometimes the timing
would be based on the leftover video data and would
increase linearly from that, being well out-of-step
with the audio timing.  Other times the video data
timing would be stuck at a non-increasing value.
Obviously this caused major problems with utilities
like `mplayer' which try to skew the presentation of
the data until the timestamps match; other applications
could better (though not perfectly) handle some data
with botched timestamps and at least display a
watchable video with consistent sub-second audio
offset.

Yet, a few recordings from this device would have
the video data totally corrupt and unrecoverable
without great and pointless effort.  Anyway, the
timing issues even when correctly recorded as
partial transport streams cause problems seeking
with `mplayer' at times, so basically I limit any
use of this device nowadays to audio recordings
where timing doesn't matter after being stripped to
a simple mp2 file, and even then, often this device
can't recover from a temporary loss of a quality signal
(heavy rainstorm, half a metre of snow on the LNB)
so, well, yeah.

Use of `scan' was made using this device in the
distant past; I neither remember blatant problems
nor obvious successes other than issues with one
particular device with the BSkyB Open-dedicated
transponders.  It generally works recording radio
unless it's somehow half-bricked itself needing a
power-off, but due to the timing issues and
occasional botched video recording, I've avoided
using it for anything else for quite a few months
now.

This device is used regularly to record audio, and
due to the nature of its tuning, I generally need
to specify an unused PID as video, lest a previously-
used video PID carry over to a different transponder
(or the same) and add many times over the bulk to
the recording.  Not so much an issue since I've
avoided it for video recordings...

I've had a few cases recently where due to whatever
reason (power failure, use of `kill'), the previous
recording from this device has not been closed
cleanly.  The next recording made, then has several
seconds worth of leftover audio.  Often this will
precede the desired audio at a different bitrate.
In order to skip the stale data, I'll need to `dd'
the file with a `skip=' parameter, else my player
will fail to detect the change.  For audio recordings
the last few which have had this problem have been
coarsely ``fixed'' by a value of `skip=1200', with
transport stream frame blocksize `bs=188'.

Whether this value transfers to video, I cannot
say.  Generally I prefer to lob off the minutes
worth of padding I provide to accommodate programme
over-/under-running and similar last-minute changes,
than to worry about an uninteresting stream.  The
lower bandwidth of audio makes a tweak of 100 TS
frames more meaningful and easier to handle.

As a side note that eventually, as part of my slow
progress in updating the 2.6.14-ish machine to the
requirements of today's Real World (use of flash
storage via USB for the entire OS has successfully
passed the one-month-without-panic mark and is now
poised for widespread adoption), I've also noticed
that at least with the .14-ish kernel, and perhaps
on the test machine with .18-era, I have not been
able to get this plus the other USB1 device to
coëxist and simultaneously function via the same
bus, getting a panic when using both devices
simultaneously.  I intend to verify this with a
far-more-recent kernel before complaining loudly.

Note that in general, shared use of a USB1 port
should not cause me problems, as I've pretty much
limited use of my USB1 devices to lower-bandwidth
radio streams, or to a handful of channels whose
bandwidth never approaches that of DVD-quality;
that is, generally non-german-public-broadcasters.


Wow, I'm able to talk about nothing for minutes on
end.  Too bad I can't type so fast and spend the
remaining time coding something useful...


barry bouwsma
scum

Re: [linux-dvb] How to use scan-s2?

[Alex Betis]

[-- Attachment #1.1: Type: text/plain, Size: 1498 bytes --]

On Mon, Jan 26, 2009 at 1:48 AM, Mika Laitio <lamikr@pilppa.org> wrote:

> > I also run it with "-5".
> > I personaly don't like to use network advertisements (-n switch) since I
> > don't trust them.
> > I use a full frequency filled INI file.
>
> Hi
>
> It might be that the signal is not the best possible for me as I can only
> scan about 500 channels with scan by using a command:
> ./scan -o vdr -a 1 Astra-19.2E
>
> In Astra-19.2E I have single line:
> #Astra 1KR (19.2E) - 10743.75 H - DVB-S (QPSK) - 22000 5/6 - NID:1 -
> TID:1051
> S 10743750 H 22000000 5/6
>
> However, once scanned the channels like eurosport, arte, skynews, cnn
> international shows up just fine with vdr-1.6.0.
>
> But if I try to use the same Astra-19.2E file with scan-s2, it can only
> find the channels from frequency 10743750 if I have stopped the "scan"
> after it had found those channels... If I let the scan to run in the end
> to other frequencies, then scan-s2 can not find anything...
>
> ./scan-s2 -a 1 -5 -n Astra-19.2E
>
> Propably Klaus Schmidinger reported something related with his TT-3200 in
> http://www.mail-archive.com/vdr@linuxtv.org/msg08493.html
> I have however hvr-4000.

As an owner of cx24116 device you should know that it doesn't allow any AUTO
settings, so you have to create an INI file with all parameters explicitly
specifed (FEC, modulation, rolloff).

I believe this is the main problem.

Also, please take the latest scan-s2, I've done some changes especily for
cx24116 cards.

[-- Attachment #1.2: Type: text/html, Size: 2032 bytes --]

[-- Attachment #2: Type: text/plain, Size: 228 bytes --]

_______________________________________________
linux-dvb users mailing list
For V4L/DVB development, please use instead linux-media@vger.kernel.org
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] How to use scan-s2?

[Mika Laitio]

> As an owner of cx24116 device you should know that it doesn't allow any AUTO
> settings, so you have to create an INI file with all parameters explicitly
> specifed (FEC, modulation, rolloff).
>
> I believe this is the main problem.
>
> Also, please take the latest scan-s2, I've done some changes especily for
> cx24116 cards.

Thanks for the hint, I will try to investigate this more.
I didn't know this because the old scan from dvb-apps have seemed to 
find channels even with this simpler Satellite scan data that comes 
withing dvb-apps for Astra.

Could you or somebody else give me an example from the satellite conf file 
where all those fields are filled in? I am little confused from those 
parameters.

How about the channel data generated by the scan-s2 or scan with "-o vdr" 
option. Should I also make some changes to those manually?

I think there must however be a bug either in scan-s2 or hvr-4000 S2API 
driver, if it's will start scanning even if the given input data is 
invalid. I mean that I think the driver and S2API should "hide away" the 
differences between different S/S2 chipsets in a way that same data given 
by the user space application should be acceptable for any card/s2-driver.

Is the bug in the scan-s2 not handling the error message from the driver 
about using "AUTO" values, or is the bug in the driver not "correctly" 
returning the error when all data needed is not set?

Mika

Re: [linux-dvb] How to use scan-s2?

[Alex Betis]

[-- Attachment #1.1: Type: text/plain, Size: 2584 bytes --]

On Mon, Jan 26, 2009 at 5:43 PM, Mika Laitio <lamikr@pilppa.org> wrote:

> > As an owner of cx24116 device you should know that it doesn't allow any
> AUTO
> > settings, so you have to create an INI file with all parameters
> explicitly
> > specifed (FEC, modulation, rolloff).
> >
> > I believe this is the main problem.
> >
> > Also, please take the latest scan-s2, I've done some changes especily for
> > cx24116 cards.
>
> Thanks for the hint, I will try to investigate this more.
> I didn't know this because the old scan from dvb-apps have seemed to
> find channels even with this simpler Satellite scan data that comes
> withing dvb-apps for Astra.

To make a long story short, scan utility set specific FEC and rolloff
parameters based on delivery type (DVB-S or S2) since the old interface (the
one before S2API) didn't support specifying delivery type. Since S2API do
support it, there is no need to play with other parameters, so AUTO
parameters are used by default. You can always override those in INI file
ofcause.

>
>
> Could you or somebody else give me an example from the satellite conf file
> where all those fields are filled in? I am little confused from those
> parameters.

I don't have a dish to 19.2E, so can't help with that.


>
>
> How about the channel data generated by the scan-s2 or scan with "-o vdr"
> option. Should I also make some changes to those manually?

you can use scan-s2 output as is for VDR. It has more information than scan
utility produce.

>
>
> I think there must however be a bug either in scan-s2 or hvr-4000 S2API
> driver, if it's will start scanning even if the given input data is
> invalid. I mean that I think the driver and S2API should "hide away" the
> differences between different S/S2 chipsets in a way that same data given
> by the user space application should be acceptable for any card/s2-driver.
>
> Is the bug in the scan-s2 not handling the error message from the driver
> about using "AUTO" values, or is the bug in the driver not "correctly"
> returning the error when all data needed is not set?

The bug is in S2API that doesn't return ANY error message at all :)
So the tuner is left locked on previous channel.

There are many things that can be done in driver to improve the situation,
but I'll leave it to someone who has card with cx24116 chips.


>
>
> Mika
>
> _______________________________________________
> linux-dvb users mailing list
> For V4L/DVB development, please use instead linux-media@vger.kernel.org
> linux-dvb@linuxtv.org
> http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
>

[-- Attachment #1.2: Type: text/html, Size: 3882 bytes --]

[-- Attachment #2: Type: text/plain, Size: 228 bytes --]

_______________________________________________
linux-dvb users mailing list
For V4L/DVB development, please use instead linux-media@vger.kernel.org
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] How to use scan-s2?

[Darron Broad]

In message <c74595dc0901260753x8b9185fu33f2a96ffbe13016@mail.gmail.com>, Alex Betis wrote:

lo

<snip>
>
>The bug is in S2API that doesn't return ANY error message at all :)
>So the tuner is left locked on previous channel.
>
>There are many things that can be done in driver to improve the situation,
>but I'll leave it to someone who has card with cx24116 chips.

When tuning the event status should change to 0 and if
it stays that way the tuning operation failed.

If you read the frontend status directly then you will
retrieve the state of the previous tuning operation
that suceeded. 

If this the above is not true then it needs investigation.

cya

Re: [linux-dvb] How to use scan-s2?

[Alex Betis]

[-- Attachment #1.1: Type: text/plain, Size: 974 bytes --]

On Mon, Jan 26, 2009 at 7:32 PM, Darron Broad <darron@kewl.org> wrote:

> In message <c74595dc0901260753x8b9185fu33f2a96ffbe13016@mail.gmail.com>,
> Alex Betis wrote:
>
> lo
>
> <snip>
> >
> >The bug is in S2API that doesn't return ANY error message at all :)
> >So the tuner is left locked on previous channel.
> >
> >There are many things that can be done in driver to improve the situation,
> >but I'll leave it to someone who has card with cx24116 chips.
>
> When tuning the event status should change to 0 and if
> it stays that way the tuning operation failed.
>
> If you read the frontend status directly then you will
> retrieve the state of the previous tuning operation
> that suceeded.

What do you call an event status and what direct status?

scan-s2 uses FE_READ_STATUS that always success and indicates channel lock,
even if cx24116 driver returned an error due to AUTO parameters.


>
> If this the above is not true then it needs investigation.
>
> cya
>
>

[-- Attachment #1.2: Type: text/html, Size: 1599 bytes --]

[-- Attachment #2: Type: text/plain, Size: 228 bytes --]

_______________________________________________
linux-dvb users mailing list
For V4L/DVB development, please use instead linux-media@vger.kernel.org
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] How to use scan-s2?

[Goga777]

> > As an owner of cx24116 device you should know that it doesn't allow any AUTO
> > settings, so you have to create an INI file with all parameters explicitly
> > specifed (FEC, modulation, rolloff).
> >
> > I believe this is the main problem.
> >
> > Also, please take the latest scan-s2, I've done some changes especily for
> > cx24116 cards.
> 
> Thanks for the hint, I will try to investigate this more.
> I didn't know this because the old scan from dvb-apps have seemed to 
> find channels even with this simpler Satellite scan data that comes 
> withing dvb-apps for Astra.
> 
> Could you or somebody else give me an example from the satellite conf file 
> where all those fields are filled in? I am little confused from those 
> parameters.

please use the latest scan-s2 with this ini files 
http://www.vdr-settings.com/download/channels/CLyngsatSP.tar.bz2
 
> How about the channel data generated by the scan-s2 or scan with "-o vdr" 
> option. Should I also make some changes to those manually?

no


> I think there must however be a bug either in scan-s2 or hvr-4000 S2API 
> driver, if it's will start scanning even if the given input data is 
> invalid. I mean that I think the driver and S2API should "hide away" the 
> differences between different S/S2 chipsets in a way that same data given 
> by the user space application should be acceptable for any card/s2-driver.

with hvr4000 and ini files from http://www.vdr-settings.com/download/channels/CLyngsatSP.tar.bz2 and with the latest
scan-s2 I could scan dvb-s transponders without any problem

I didn't try to scan dvb-s2 yet 


Goga

Re: [linux-dvb] How to use scan-s2?

[Darron Broad]

In message <c74595dc0901261130k6bdb6882lfb18c650cbca4abf@mail.gmail.com>, Alex 
Betis wrote:
>
>On Mon, Jan 26, 2009 at 7:32 PM, Darron Broad <darron@kewl.org> wrote:
>
>> In message <c74595dc0901260753x8b9185fu33f2a96ffbe13016@mail.gmail.com>,
>> Alex Betis wrote:
>>
>> lo
>>
>> <snip>
>> >
>> >The bug is in S2API that doesn't return ANY error message at all :)
>> >So the tuner is left locked on previous channel.
>> >
>> >There are many things that can be done in driver to improve the situation,
>> >but I'll leave it to someone who has card with cx24116 chips.
>>
>> When tuning the event status should change to 0 and if
>> it stays that way the tuning operation failed.
>>
>> If you read the frontend status directly then you will
>> retrieve the state of the previous tuning operation
>> that suceeded.
>
>What do you call an event status and what direct status?
>
>scan-s2 uses FE_READ_STATUS that always success and indicates channel lock,
>even if cx24116 driver returned an error due to AUTO parameters.

refer to

FE_SET_FRONTEND:
http://www.linuxtv.org/docs/dvbapi/DVB_Frontend_API.html#SECTION00328000000000000000

and,

FE_GET_EVENT
http://www.linuxtv.org/docs/dvbapi/DVB_Frontend_API.html#SECTION003210000000000000000

l8r

--

 // /
{:)==={ Darron Broad <darron@kewl.org>
 \\ \ 

Re: [linux-dvb] How to use scan-s2?

[Alex Betis]

[-- Attachment #1.1: Type: text/plain, Size: 1913 bytes --]

On Mon, Jan 26, 2009 at 10:20 PM, Darron Broad <darron@kewl.org> wrote:

> In message <c74595dc0901261130k6bdb6882lfb18c650cbca4abf@mail.gmail.com>,
> Alex
> Betis wrote:
> >
> >On Mon, Jan 26, 2009 at 7:32 PM, Darron Broad <darron@kewl.org> wrote:
> >
> >> In message <c74595dc0901260753x8b9185fu33f2a96ffbe13016@mail.gmail.com
> >,
> >> Alex Betis wrote:
> >>
> >> lo
> >>
> >> <snip>
> >> >
> >> >The bug is in S2API that doesn't return ANY error message at all :)
> >> >So the tuner is left locked on previous channel.
> >> >
> >> >There are many things that can be done in driver to improve the
> situation,
> >> >but I'll leave it to someone who has card with cx24116 chips.
> >>
> >> When tuning the event status should change to 0 and if
> >> it stays that way the tuning operation failed.
> >>
> >> If you read the frontend status directly then you will
> >> retrieve the state of the previous tuning operation
> >> that suceeded.
> >
> >What do you call an event status and what direct status?
> >
> >scan-s2 uses FE_READ_STATUS that always success and indicates channel
> lock,
> >even if cx24116 driver returned an error due to AUTO parameters.
>
> refer to
>
> FE_SET_FRONTEND:
>
> http://www.linuxtv.org/docs/dvbapi/DVB_Frontend_API.html#SECTION00328000000000000000
>
> and,
>
> FE_GET_EVENT
>
> http://www.linuxtv.org/docs/dvbapi/DVB_Frontend_API.html#SECTION003210000000000000000
>
Ohh, ok. So there is a solution for that after all. Thanks!
Unfortunately no one gave me a clear answer on that when I asked about it
last time.
Seems to work for stb0899, waiting for confirmation on cx24116.

Darron, looks you're the right person to ask:
How can I retrieve the REAL tuned parameters from the driver?
Looks like using FE_GET_PROPERTY returns cached properties that were issued
with FE_SET_PROPERTY before that.

Thanks.


> l8r
>
> --
>
>  // /
> {:)==={ Darron Broad <darron@kewl.org>
>  \\ \
>
>

[-- Attachment #1.2: Type: text/html, Size: 3213 bytes --]

[-- Attachment #2: Type: text/plain, Size: 228 bytes --]

_______________________________________________
linux-dvb users mailing list
For V4L/DVB development, please use instead linux-media@vger.kernel.org
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] How to use scan-s2?

[Andy Walls]

On Mon, 2009-01-26 at 22:31 +0200, Alex Betis wrote:
> 
> On Mon, Jan 26, 2009 at 10:20 PM, Darron Broad <darron@kewl.org>
> wrote:
>         In message
>         <c74595dc0901261130k6bdb6882lfb18c650cbca4abf@mail.gmail.com>,
>         Alex
>         Betis wrote:
>         >
>         >On Mon, Jan 26, 2009 at 7:32 PM, Darron Broad
>         <darron@kewl.org> wrote:
>         >
>         >> In message
>         <c74595dc0901260753x8b9185fu33f2a96ffbe13016@mail.gmail.com>,
>         >> Alex Betis wrote:
>         >>
>         >> lo
>         >>
>         >> <snip>
>         >> >
>         >> >The bug is in S2API that doesn't return ANY error message
>         at all :)

Aside from Darron's observation, doesn't the result field of any
particular S2API property return with a non-0 value on failure?

(Sorry, I missed the original thread on the S2API return values.)

Regards,
Andy

Re: [linux-dvb] How to use scan-s2?

[Alex Betis]

[-- Attachment #1.1: Type: text/plain, Size: 1586 bytes --]

On Tue, Jan 27, 2009 at 2:59 AM, Andy Walls <awalls@radix.net> wrote:

> On Mon, 2009-01-26 at 22:31 +0200, Alex Betis wrote:
> >
> > On Mon, Jan 26, 2009 at 10:20 PM, Darron Broad <darron@kewl.org>
> > wrote:
> >         In message
> >         <c74595dc0901261130k6bdb6882lfb18c650cbca4abf@mail.gmail.com>,
> >         Alex
> >         Betis wrote:
> >         >
> >         >On Mon, Jan 26, 2009 at 7:32 PM, Darron Broad
> >         <darron@kewl.org> wrote:
> >         >
> >         >> In message
> >         <c74595dc0901260753x8b9185fu33f2a96ffbe13016@mail.gmail.com>,
> >         >> Alex Betis wrote:
> >         >>
> >         >> lo
> >         >>
> >         >> <snip>
> >         >> >
> >         >> >The bug is in S2API that doesn't return ANY error message
> >         at all :)
>
> Aside from Darron's observation, doesn't the result field of any
> particular S2API property return with a non-0 value on failure?

Depends how you define the "failure".
If you order to tune, than for S2API failure would be something like "could
not initiate tune command" and not like "tuning failed".
Apparently the "tuning failed" failure should be checked with events and not
rely on return code from commands.

Correct me if I'm wrong with that.


>
>
> (Sorry, I missed the original thread on the S2API return values.)
>
> Regards,
> Andy
>
>
>
> _______________________________________________
> linux-dvb users mailing list
> For V4L/DVB development, please use instead linux-media@vger.kernel.org
> linux-dvb@linuxtv.org
> http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
>

[-- Attachment #1.2: Type: text/html, Size: 3139 bytes --]

[-- Attachment #2: Type: text/plain, Size: 228 bytes --]

_______________________________________________
linux-dvb users mailing list
For V4L/DVB development, please use instead linux-media@vger.kernel.org
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] How to use scan-s2?

[Darron Broad]

In message <c74595dc0901261231l4448f6cepfcb570557c54f60a@mail.gmail.com>, Alex Betis wrote:

hi

>On Mon, Jan 26, 2009 at 10:20 PM, Darron Broad <darron@kewl.org> wrote:
>
>> In message <c74595dc0901261130k6bdb6882lfb18c650cbca4abf@mail.gmail.com>,
>> Alex
>> Betis wrote:
>> >
>> >On Mon, Jan 26, 2009 at 7:32 PM, Darron Broad <darron@kewl.org> wrote:
>> >
>> >> In message <c74595dc0901260753x8b9185fu33f2a96ffbe13016@mail.gmail.com
>> >,
>> >> Alex Betis wrote:
>> >>
>> >> lo
>> >>
>> >> <snip>
>> >> >
>> >> >The bug is in S2API that doesn't return ANY error message at all :)
>> >> >So the tuner is left locked on previous channel.
>> >> >
>> >> >There are many things that can be done in driver to improve the
>> situation,
>> >> >but I'll leave it to someone who has card with cx24116 chips.
>> >>
>> >> When tuning the event status should change to 0 and if
>> >> it stays that way the tuning operation failed.
>> >>
>> >> If you read the frontend status directly then you will
>> >> retrieve the state of the previous tuning operation
>> >> that suceeded.
>> >
>> >What do you call an event status and what direct status?
>> >
>> >scan-s2 uses FE_READ_STATUS that always success and indicates channel
>> lock,
>> >even if cx24116 driver returned an error due to AUTO parameters.
>>
>> refer to
>>
>> FE_SET_FRONTEND:
>>
>> http://www.linuxtv.org/docs/dvbapi/DVB_Frontend_API.html#SECTION00328000000000000000
>>
>> and,
>>
>> FE_GET_EVENT
>>
>> http://www.linuxtv.org/docs/dvbapi/DVB_Frontend_API.html#SECTION003210000000000000000
>>
>Ohh, ok. So there is a solution for that after all. Thanks!
>Unfortunately no one gave me a clear answer on that when I asked about it
>last time.
>Seems to work for stb0899, waiting for confirmation on cx24116.

Okay. If there is a fault I will investigate.

>Darron, looks you're the right person to ask:
>How can I retrieve the REAL tuned parameters from the driver?
>Looks like using FE_GET_PROPERTY returns cached properties that were issued
>with FE_SET_PROPERTY before that.

At present that's all there is. With the cx24116 it is
actually possible to retrieve the actual FEC when requesting
FEC_AUTO for DVB-S but it's not implemented. Such a feature
though could be driver dependant in any case so probably
unreliable. I have not looked.

cya

--

 // /
{:)==={ Darron Broad <darron@kewl.org>
 \\ \ 

Re: [linux-dvb] How to use scan-s2?

[Darron Broad]

In message <1233017978.3061.2.camel@palomino.walls.org>, Andy Walls wrote:

LO

>On Mon, 2009-01-26 at 22:31 +0200, Alex Betis wrote:
>> 
>> On Mon, Jan 26, 2009 at 10:20 PM, Darron Broad <darron@kewl.org>
>> wrote:
>>         In message
>>         <c74595dc0901261130k6bdb6882lfb18c650cbca4abf@mail.gmail.com>,
>>         Alex
>>         Betis wrote:
>>         >
>>         >On Mon, Jan 26, 2009 at 7:32 PM, Darron Broad
>>         <darron@kewl.org> wrote:
>>         >
>>         >> In message
>>         <c74595dc0901260753x8b9185fu33f2a96ffbe13016@mail.gmail.com>,
>>         >> Alex Betis wrote:
>>         >>
>>         >> lo
>>         >>
>>         >> <snip>
>>         >> >
>>         >> >The bug is in S2API that doesn't return ANY error message
>>         at all :)
>
>Aside from Darron's observation, doesn't the result field of any
>particular S2API property return with a non-0 value on failure?
>
>(Sorry, I missed the original thread on the S2API return values.)

The actual tuning occurs within a thread and not when issuing
the tuning IOCTL. The only means to determine whether tuning
worked or not is inspection of the frontend events generated
within that thread. So, if the params are wrong, the IOCTL
can fail, but that's not the problem Alex is experiencing
where the params are correctly formed yet not supported in
the driver.

I did look at a means to expose supported params a while ago
but it's ugly so I haven't gone forward with it.

Bye


--

 // /
{:)==={ Darron Broad <darron@kewl.org>
 \\ \