From: "Roman Jarosz" <roman.jarosz@gmail.com>
To: linux-dvb@linuxtv.org
Subject: Re: [linux-dvb] DVB-S Channel searching problem
Date: Sun, 04 Jan 2009 14:11:33 +0100 [thread overview]
Message-ID: <op.um8hljd6rj95b0@localhost> (raw)
In-Reply-To: <Pine.LNX.4.64.0901041435090.1668@shogun.pilppa.org>
On Sun, 04 Jan 2009 13:42:06 +0100, Mika Laitio <lamikr@pilppa.org> wrote:
>> http://mercurial.intuxication.org/hg/s2-liplianin (yesterday Igor
>> synchronized it with current v4l-dvb)
>> +
>> http://hg.kewl.org/dvb2010/ - new dvb scaner
>>
>> for me everything is working without any problem with my hvr4000. Also
>> patched vdr 170 works well with s2api
>
> Can you test whether channel switching works for you with
> following
> - vdr-1.7.2
> -
> vdr-1.7.2-h264-syncearly-framespersec-audioindexer-fielddetection-speedup.diff
> - vdr172_v4ldvb_2g_modulation_support.patch (attached)
> - streamdev plugin
>
> I can only watch those channels that I have previously tuned with szap or
> szap2 or vdr.1.6.0? If it works for you, what other cards than hvr-4000
> you have simultaneously connected and does the hvr-4000 be
> /dev/dvb/adapter0 or 1? (for me it's adapter1)
>
I've tried clean vdr 1.7.2 (without patches) and it doesn't work (works sometimes).
When I try to change channels in vdr 1.7.2 I see in log:
Jan 4 13:57:43 blackbox vdr: [3250] frontend 0 lost lock on channel 437, tp 110743
Jan 4 13:57:45 blackbox vdr: [3250] frontend 0 timed out while tuning to channel 437, tp 110743
Btw I don't use hvr-4000 I have only one TeVii S460 DVB-S/S2 card.
But vdr 1.6 works
Roman
_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
next prev parent reply other threads:[~2009-01-04 13:10 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-03 16:42 [linux-dvb] DVB-S Channel searching problem Roman Jarosz
2009-01-03 17:01 ` Brice DUBOST
2009-01-03 17:14 ` BOUWSMA Barry
2009-01-03 17:15 ` Roman Jarosz
2009-01-03 17:28 ` Alex Betis
2009-01-03 18:11 ` Roman Jarosz
2009-01-03 18:58 ` Alex Betis
2009-01-03 19:37 ` Gregoire Favre
2009-01-04 8:14 ` Goga777
2009-01-04 8:29 ` hermann pitton
2009-01-04 10:37 ` Gregoire Favre
2009-01-04 16:06 ` hermann pitton
2009-01-04 16:37 ` Gregoire Favre
2009-01-04 17:15 ` hermann pitton
2009-01-04 18:24 ` Gregoire Favre
2009-01-08 2:20 ` hermann pitton
2009-01-04 10:35 ` Gregoire Favre
2009-01-04 10:58 ` Roman Jarosz
2009-01-04 12:42 ` Mika Laitio
2009-01-04 13:11 ` Roman Jarosz [this message]
2009-01-04 14:56 ` Goga777
2009-01-04 20:47 ` Roman Jarosz
2009-01-04 21:24 ` Goga777
2009-01-05 17:43 ` Roman Jarosz
2009-01-05 17:58 ` Roman Jarosz
2009-01-05 19:00 ` Goga777
2009-01-06 14:58 ` Mika Laitio
2009-01-03 19:39 ` Roman Jarosz
2009-01-03 20:48 ` Alex Betis
2009-01-03 20:59 ` Roman Jarosz
2009-01-03 21:01 ` Alex Betis
2009-01-04 3:52 ` BOUWSMA Barry
-- strict thread matches above, loose matches on Subject: below --
2009-01-04 19:46 Eduard Huguet
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=op.um8hljd6rj95b0@localhost \
--to=roman.jarosz@gmail.com \
--cc=kedgedev@centrum.cz \
--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