public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Kjeld Flarup <kjeld.flarup@liberalismen.dk>
To: Michael Riepe <michael.riepe@googlemail.com>
Cc: linux-media@vger.kernel.org
Subject: Re: dvbd
Date: Mon, 20 Apr 2009 00:29:26 +0200	[thread overview]
Message-ID: <49EBA5C6.5060808@liberalismen.dk> (raw)
In-Reply-To: <49EAF472.9010702@googlemail.com>

Hi Michael

Thanks for your reply. Tweaking the scheduling is ususally easy to fix. 
I might want to look at the buffering too. It ought to be a system thing.
I never got VDR working properly, and currently I use mplayer/mencoder 
to record.

But one thing which I would like to do is to use dvbd together with VLC, 
because VLC can handle the DVB subtitles used in Denmark. But VLC does 
not seem to like connecting to the dvbd socket. If anyone have success 
with that, I sure would like to know.

Also at some time soon I would need to stream some DVB signals. But I do 
not like the way this is done by most tools, they seems to be using up 
CPU cycles even if nobody is listening.

  Regards Kjeld

Michael Riepe wrote:
> Hi!
>
> Kjeld Flarup wrote:
>
>   
>> I've taken some interest in a small piece of software called dvbd.
>> http://dvbd.sourceforge.net/
>> I really like the concept of this software, because it could be used for
>> sharing one DVB card among several different applications.
>>     
>
> That's right.
>
>   
>> BUT the software have not been developed since 2004.
>>     
>
> And it needs a few tweaks when you're using a more recent C++ compiler
> like gcc 4.3.x.
>
>   
>> Is this because it is not so smart anyway, or are there some better
>> programs out there?
>>     
>
> There is VDR, of course. But I don't like the way it does things.
> Therefore, I've been using dvbd for years to handle my small zoo of
> DVB-T receivers (I've got four of them running at the moment). It easily
> handles several recordings in parallel without using many resources - a
> few megabytes of RAM and a few percent of CPU time on an old (2005)
> Athlon64. I currently consider moving it to an Intel Atom based system.
>
> dvbd does sometimes have issues with disk writes, though. It doesn't do
> much buffering, and if another process is blocking the disk it's writing
> to for too long, you may encounter drop-outs. It's best to give it a
> disk of its own. Similarly, if dvbd doesn't get scheduled for a while,
> it will lose data from the receivers. On a single-core machine that also
> does other things (like mine), I recommend to raise its priority with
> nice --20, or maybe use a realtime priority level.
>
>   


-- 
-------------------- Med Liberalistiske Hilsner ----------------------
  Civilingeniør, Kjeld Flarup - Mit sind er mere åbent end min tegnebog
  Forssavej 49, 7600 Struer, Tlf: 40 29 41 49
  Den ikke akademiske hjemmeside for liberalismen - www.liberalismen.dk



  reply	other threads:[~2009-04-19 22:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-19  1:31 dvbd Kjeld Flarup
2009-04-19  9:52 ` dvbd Michael Riepe
2009-04-19 22:29   ` Kjeld Flarup [this message]
2009-04-20 16:51     ` dvbd Michael Riepe

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=49EBA5C6.5060808@liberalismen.dk \
    --to=kjeld.flarup@liberalismen.dk \
    --cc=linux-media@vger.kernel.org \
    --cc=michael.riepe@googlemail.com \
    /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