public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Goga777 <goga777@bk.ru>
To: Mika Laitio <lamikr@pilppa.org>
Cc: linux-media@vger.kernel.org, linux-dvb@linuxtv.org
Subject: Re: [linux-dvb] How to use scan-s2?
Date: Mon, 26 Jan 2009 22:44:40 +0300	[thread overview]
Message-ID: <20090126224440.3c642d94@bk.ru> (raw)
In-Reply-To: <Pine.LNX.4.64.0901261729280.19881@shogun.pilppa.org>

> > 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

  parent reply	other threads:[~2009-01-26 19:35 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-25 10:29 [linux-dvb] How to use scan-s2? Artem Makhutov
2009-01-25  9:49 ` Jens Krehbiel-Gräther
2009-01-25 13:25   ` Alex Betis
2009-01-25 14:41     ` Hans Werner
2009-01-25 14:54       ` Alex Betis
2009-01-25 16:29         ` Hans Werner
2009-01-25 16:56           ` Alex Betis
2009-01-26  3:24             ` BOUWSMA Barry
2009-01-25 23:48     ` Mika Laitio
2009-01-26  9:35       ` Alex Betis
2009-01-26 15:43         ` Mika Laitio
2009-01-26 15:53           ` Alex Betis
2009-01-26 17:32             ` Darron Broad
2009-01-26 19:30               ` Alex Betis
2009-01-26 20:20                 ` Darron Broad
2009-01-26 20:31                   ` Alex Betis
2009-01-27  0:59                     ` Andy Walls
2009-01-27  7:48                       ` Alex Betis
2009-01-27 14:11                       ` Darron Broad
2009-01-27 14:07                     ` Darron Broad
2009-01-26 19:44           ` Goga777 [this message]
2009-01-25 14:25   ` Artem Makhutov
2009-01-25 17:48     ` Goga777

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=20090126224440.3c642d94@bk.ru \
    --to=goga777@bk.ru \
    --cc=lamikr@pilppa.org \
    --cc=linux-dvb@linuxtv.org \
    --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