Без кейворда

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

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?

Jens Krehbiel-Gräther 2009-01-25 09:49:16 UTC

Post by Artem MakhutovHello,I am wondering on how to use scan-s2.scan-s2 -a 2 -o zap /usr/share/dvb/dvb-s/Astra-19.2E > channels.confwhen runningscan-s2 -a 2 -n -o zap /usr/share/dvb/dvb-s/Astra-19.2E > channels.confthen I am getting 152 services.dvbscan -a 2 -o zap /usr/share/dvb/dvb-s/Astra-19.2E > channels.confHave I missed a parameter in scan-s2 or what else could be the problem?Thanks, Artem

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

the "-5" means:multiply all filter timeouts by factor 5 for non-DVB-compliant sectionrepitition 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?

Alex Betis 2009-01-25 13:25:59 UTC On Sun, Jan 25, 2009 at 11:49 AM, Jens Krehbiel-Gräther channels.confthen I am getting 152 services.dvbscan -a 2 -o zap /usr/share/dvb/dvb-s/Astra-19.2E > channels.confHave 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 fewservices.When I add the "-n" option I get some more services but all services Ionly get, when I am adding "-n -5".multiply all filter timeouts by factor 5 for non-DVB-compliant sectionrepitition ratesThe 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 Idon't trust them.I use a full frequency filled INI file.

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

Post by Jens Krehbiel-GrÃ¤therJens_______________________________________________linux-dvb users mailing listhttp://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Hans Werner 2009-01-25 14:41:12 UTC Post by Alex BetisIf 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 ?

--Release early, release often.

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

Alex Betis 2009-01-25 14:54:22 UTC Post by Alex BetisIf 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 notreset between tunnings.In that case messages from *previous* channel will arrive after the tunningto new channel is complete.Those messages will create a big mess in the results, such as channelswithout names, duplicate channels on different transponders.-k option specifies how many messages should be ignored before processingit. I couldn't think of a more elegant way to ignore messages frompreviously tuned channel. I use "-k 3" by myself, but after playing aroundwith "-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 aftertunning.Since I don't know how it can be done and how it will affect tunning ofchannels for viewing, I didn't want to go that way and solve it in scan-s2.

Post by Hans WernerThanks,Hans--Release early, release often.http://www.gmx.net/de/go/multimessenger_______________________________________________linux-dvb users mailing listhttp://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Hans Werner 2009-01-25 16:29:59 UTC Post by Alex BetisIf 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 ?

=20=20Since I've added it, I'll try to defend it :)=20stb0899 driver (or maybe the chip?) has some buffers inside that are =

Post by Alex Betisreset between tunnings.In that case messages from *previous* channel will arrive after the tunningto new channel is complete.Those messages will create a big mess in the results, such as channel=

Post by Alex Betiswithout names, duplicate channels on different transponders.-k option specifies how many messages should be ignored before proces=

Post by Alex Betisit. I couldn't think of a more elegant way to ignore messages frompreviously tuned channel. I use "-k 3" by myself, but after playing a=

Post by Alex Betiswith "-k 2" saw that its also working. "-k 1" was still not enough.=20The proper way is to have an option to reset that buffer in the drive=

Post by Alex Betisaftertunning.Since I don't know how it can be done and how it will affect tunning =

Post by Alex Betischannels for viewing, I didn't want to go that way and solve it in scan-s2.=20Regards,Alex.

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

Psssst! Schon vom neuen GMX MultiMessenger geh=F6rt? Der kann`s mit all=en: http://www.gmx.net/de/go/multimessenger--To unsubscribe from this list: send the line "unsubscribe linux-media" =inthe body of a message to ***@vger.kernel.orgMore majordomo info at http://vger.kernel.org/majordomo-info.html

Alex Betis 2009-01-25 16:56:05 UTC Post by Alex BetisIf 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 notreset between tunnings.In that case messages from *previous* channel will arrive after the tunningto new channel is complete.Those messages will create a big mess in the results, such as channelswithout names, duplicate channels on different transponders.-k option specifies how many messages should be ignored before processingit. I couldn't think of a more elegant way to ignore messages frompreviously tuned channel. I use "-k 3" by myself, but after playing

Post by Alex Betiswith "-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 aftertunning.Since I don't know how it can be done and how it will affect tunning ofchannels 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 havethe same problem.

Post by Alex Betis--Release early, release often.http://www.gmx.net/de/go/multimessenger_______________________________________________linux-dvb users mailing listhttp://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

BOUWSMA Barry 2009-01-26 03:24:14 UTC Post by Alex BetisIf 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 = reset between tunnings.In that case messages from *previous* channel will arrive after t= tunningto new channel is complete.Those messages will create a big mess in the results, such as cha=

without names, duplicate channels on different transponders.-k option specifies how many messages should be ignored before pr=

it. I couldn't think of a more elegant way to ignore messages fro= previously tuned channel. I use "-k 3" by myself, but after playi= with "-k 2" saw that its also working. "-k 1" was still not enoug=

Post by Alex BetisOK, 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. Bo= the same problem.

This may be going typically off-topic, but I do experiencesimilar artifacts with some STV0299 cards (looks superficiallyalike; 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, andI either experience `scan' difficulties or recording issues,or nothing.

=46irst off, for reference: a PCI SkyStar2 card that getspriority for recordings, using a 2.6.14-ish kernel that I'min the long slow process of planning to update on thatproduction machine.

When making two recordings separated by time from the sametransponder, often the second recording will have a fewvideo frames left over from the previous recording. Thisappears in my quality-control as video frames with differingtimestamps 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 flawlesspartial transport stream).

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

I've never noticed that this affects `scan' which changestransponders; that in itself seems to be enough to losethe buffered data. This is only a minor concern as thefirst few frames of confused data are almost certainlydisposable, as a fraction of a second in the paddingleading up to the content of interest.

As exhibit number two, where I have had problems withregular `scan' seeing data from the previous transponderand causing problems getting current data, anotherstv0299-based device, the Opera-1 USB-connected tuner.I have *never* seen any recordings made from thisdevice contain frames from an earlier tuning session,though.

As far as `scan' tuning goes, I would regularly seeprevious ``phantom'' channels appearing, combined withzero-value PIDs for channels on the intended currenttransponder. At least until recently; my latest scanshave been flawless, either due to hacks I added tothat `scan' or to kernel updates on that test machine.

Exhibit C, m'lud, will be -- again on the 2.6.14-ishkernel machine, but this time connected via USB 1.1 --an early Nova-S device. Apart from bandwidth issuesdue to the usb1 interface, I've never noticed problemswith stale packets when recording from either the sameor a different transponder. I do have other issueswhich 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 tothose experienced with leftover packets, but whichappear to be compounded by the internal mangling ofthe transport stream components into a proprietary-yet-open delivery stream. This device is the ttusb-dec DEC3000-s, of unknown-based-on-kernel-codeheritage, though I may have taken it apart long agoand written the results on a long-since hidden drive.

This device is connected via USB1, and is incapableof delivering more than an MPEG2 video and mp2 audiostream to a recording, making it useless for multipleaudio, teletext, AC3, H.264, or PMT tables to start.

It also internally converts the transport streaminto the PVA format, with side-effects such as thatthe timestamps do not match the original transportstream components, cycling after some 40 000 secsrather than the 90 000-ish seconds delivered in thestreams from other devices.

Recordings from this device all-too-often would havetiming problems as well as leftover data from aprevious recording. (Whether from same or differenttransponder, I cannot say. I added a hack-workaroundto my recordings to tune briefly a different txp,then tune back. Sometimes it worked. Often withhigh load, nothing could help.) Sometimes the timingwould be based on the leftover video data and wouldincrease linearly from that, being well out-of-stepwith the audio timing. Other times the video datatiming would be stuck at a non-increasing value.Obviously this caused major problems with utilitieslike `mplayer' which try to skew the presentation ofthe data until the timestamps match; other applicationscould better (though not perfectly) handle some datawith botched timestamps and at least display awatchable video with consistent sub-second audiooffset.

Yet, a few recordings from this device would havethe video data totally corrupt and unrecoverablewithout great and pointless effort. Anyway, thetiming issues even when correctly recorded aspartial transport streams cause problems seekingwith `mplayer' at times, so basically I limit anyuse of this device nowadays to audio recordingswhere timing doesn't matter after being stripped toa simple mp2 file, and even then, often this devicecan'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 thedistant past; I neither remember blatant problemsnor obvious successes other than issues with oneparticular device with the BSkyB Open-dedicatedtransponders. It generally works recording radiounless it's somehow half-bricked itself needing apower-off, but due to the timing issues andoccasional botched video recording, I've avoidedusing it for anything else for quite a few monthsnow.

This device is used regularly to record audio, anddue to the nature of its tuning, I generally needto 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 tothe recording. Not so much an issue since I'veavoided it for video recordings.

I've had a few cases recently where due to whateverreason (power failure, use of `kill'), the previousrecording from this device has not been closedcleanly. The next recording made, then has severalseconds worth of leftover audio. Often this willprecede the desired audio at a different bitrate.In order to skip the stale data, I'll need to `dd'the file with a `skip=3D' parameter, else my playerwill fail to detect the change. For audio recordingsthe last few which have had this problem have beencoarsely ``fixed'' by a value of `skip=3D1200', withtransport stream frame blocksize `bs=3D188'.

Whether this value transfers to video, I cannotsay. Generally I prefer to lob off the minutesworth of padding I provide to accommodate programmeover-/under-running and similar last-minute changes,than to worry about an uninteresting stream. Thelower bandwidth of audio makes a tweak of 100 TSframes more meaningful and easier to handle.

As a side note that eventually, as part of my slowprogress in updating the 2.6.14-ish machine to therequirements of today's Real World (use of flashstorage via USB for the entire OS has successfullypassed the one-month-without-panic mark and is nowpoised for widespread adoption), I've also noticedthat at least with the .14-ish kernel, and perhapson the test machine with .18-era, I have not beenable to get this plus the other USB1 device toco=C3=ABxist and simultaneously function via the samebus, getting a panic when using both devicessimultaneously. I intend to verify this with afar-more-recent kernel before complaining loudly.

Note that in general, shared use of a USB1 portshould not cause me problems, as I've pretty muchlimited use of my USB1 devices to lower-bandwidthradio streams, or to a handful of channels whosebandwidth never approaches that of DVD-quality;that is, generally non-german-public-broadcasters.

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

barry bouwsmascum--To unsubscribe from this list: send the line "unsubscribe linux-media" =inthe body of a message to ***@vger.kernel.orgMore majordomo info at http://vger.kernel.org/majordomo-info.html

Mika Laitio 2009-01-25 23:48:19 UTC

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

It might be that the signal is not the best possible for me as I can onlyscan 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:1051S 10743750 H 22000000 5/6

However, once scanned the channels like eurosport, arte, skynews, cnninternational 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 onlyfind 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 endto 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 inhttp://www.mail-archive.com/***@linuxtv.org/msg08493.htmlI 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 tuningchannels from 106437502) scan-s2 run after that (no channels found)3) scan when stopping it immediately after it has found channels from106437504) scan-s2 after that (now it found correctly all 5 channels that arerepoted to be in 10543750, but failed to tune from other freqs)

1)[***@tinka scan]$ ./scan -a 1 Astra-19.2Escanning Astra-19.2Eusing '/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 9937500x0000 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 20922500x045d 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) [***@tinka scan-s2]$ ./scan-s2 -a 1/home/lamikr/dvb/apps/dvb-apps_20090126/util/scan/Astra-19.2EAPI major 5, minor 0scanning /home/lamikr/dvb/apps/dvb-apps_20090126/util/scan/Astra-19.2Eusing '/dev/dvb/adapter1/frontend0' and '/dev/dvb/adapter1/demux0'initial transponder DVB-S2 10743750 H 22000000 5/6 AUTO AUTOinitial transponder DVB-S 10743750 H 22000000 5/6 AUTO AUTO----------------------------------> Using DVB-S2DVB-S IF freq is 993750WARNING: >>> tuning failed.

tune to: 10743:hC56S1:S0.0W:22000: (tuning failed)

DVB-S IF freq is 993750WARNING: >>> tuning failed. ----------------------------------> Using DVB-SDVB-S IF freq is 993750WARNING: >>> tuning failed.

tune to: 10743:hC56S0:S0.0W:22000: (tuning failed)

DVB-S IF freq is 993750WARNING: >>> tuning failed. ERROR: initial tuning faileddumping lists (0 services)Done.

3) [***@tinka scan]$ ./scan -a 1 Astra-19.2Escanning Astra-19.2Eusing '/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 9937500x0000 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:28721EinsFestival:10743:h:0:22000:201:202:28722EinsPlus:10743:h:0:22000:301:302:28723arte:10743:h:0:22000:401:402:28724Phoenix:10743:h:0:22000:501:502:28725Done.

4) [***@tinka scan-s2]$ ./scan-s2 -a 1/home/lamikr/dvb/apps/dvb-apps_20090126/util/scan/Astra-19.2EAPI major 5, minor 0scanning /home/lamikr/dvb/apps/dvb-apps_20090126/util/scan/Astra-19.2Eusing '/dev/dvb/adapter1/frontend0' and '/dev/dvb/adapter1/demux0'initial transponder DVB-S2 10743750 H 22000000 5/6 AUTO AUTOinitial transponder DVB-S 10743750 H 22000000 5/6 AUTO AUTO----------------------------------> Using DVB-S2DVB-S IF freq is 993750