From: "Hans Werner" <HWerner4@gmx.de>
To: Christophe Thommeret <hftom@free.fr>, linux-dvb@linuxtv.org
Cc: linux-dvb@linuxtv.org
Subject: Re: [linux-dvb] hvr4000-s2api + QAM_AUTO
Date: Tue, 23 Sep 2008 18:27:57 +0200 [thread overview]
Message-ID: <20080923162757.282370@gmx.net> (raw)
In-Reply-To: <200809221201.26115.hftom@free.fr>
> > >
> > > Hi Steve,
> > >
> > > I've managed to add S2 support to kaffeine, so it can scan and zap.
> > > However, i have a little problem with DVB-S:
> > > Before tuning to S2, S channels tune well with QAM_AUTO.
> > > But after having tuned to S2 channels, i can no more lock on S ones
> until
> > > i
> > > set modulation to QPSK insteed of QAM_AUTO for these S channels.
> > > Is this known?
> > >
> > > --
> > > Christophe Thommeret
> >
> > Hi Christophe,
...
>
> > I'd be very happy to try out your patch for Kaffeine and give feedback
> if
> > you are ready to share it.
>
> Sure, here it is (patch against current svn
> http://websvn.kde.org/branches/extragear/kde3/multimedia/)
>
> Atm, s2api is only used for S/S2.
>
> P.S.
> In order to play H264/HD with kaffeine/xine, you need a fairly recent
> ffmpeg
> and xine compiled with --with-external-ffmpeg configure option. (and of
> course a quite strong cpu, unlike my old athlon-xp-2600 :)
> However, you can still record and/or broadcast without this update.
Success! Many thanks Christophe.
With the following:
HVR4000 card
S2API + multifrontend patch (hg clone http://linuxtv.org/hg/~stoth/s2-mfe)
ffmpeg from SVN
xine-lib from mercurial (compiled with --with-external-ffmpeg)
Kaffeine from SVN + Christophe's S2API patch
Scanning to find channels and tuning are working in Kaffeine for DVB-T, DVB-S and DVB-S2.
S/S2 tuning and scanning is with S2API.
My CPU (3ghz core 2 quad) is fast enough to show live HD video so I can watch HD channels
live inside Kaffeine, or record to disk and watch afterwards. ASTRA HD+ and ANIXE HD are
good. ARTE HD throws some errors and stutters a bit. Simul HD can crash Kaffeine.
I enabled the two lines in dvbstream.cpp which set modulation to QPSK instead of
QAM_AUTO for DVB-S.
Settings: number of xine threads >= 4, de-interlacing(CTRL-I) at minimum (is it useful for HD ?
I don't know). The load isn't always distributed well across the 4 cpus -- it can max out one
of them sometimes, with the others almost idle. Perhaps this can be improved.
Regards,
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 mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
next prev parent reply other threads:[~2008-09-23 16:28 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-21 17:05 [linux-dvb] hvr4000-s2api + QAM_AUTO Christophe Thommeret
2008-09-21 23:54 ` Hans Werner
2008-09-22 10:01 ` Christophe Thommeret
2008-09-23 16:27 ` Hans Werner [this message]
2008-09-23 16:39 ` Steven Toth
2008-09-23 16:59 ` BOUWSMA Barry
2008-09-23 17:43 ` Hans Werner
2008-09-23 17:49 ` Goga777
2008-09-25 17:22 ` Goga777
2008-09-24 13:38 ` Christophe Thommeret
2008-09-24 14:08 ` Hans Werner
2008-09-24 14:16 ` Christophe Thommeret
2008-09-24 14:31 ` Darron Broad
2008-09-24 15:44 ` Christophe Thommeret
2008-09-22 2:17 ` Steven Toth
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=20080923162757.282370@gmx.net \
--to=hwerner4@gmx.de \
--cc=hftom@free.fr \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.