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

Hi Kjeld,

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

you can access a particular stream with dvbcat and pipe it into a media
player (xine works fine). I usually do it differently, though: write the
stream to disk and let the player read the file. That way you also get
time shifting (which doesn't work when you use a pipe). And if you use a
low priority for live viewing, scheduled recordings will take precedence.

Writing a plug-in based on dvbcat would be another option. That might
also allow you to switch channels on the fly (if the other channel is
accessible, that is - one of the reasons why I use multiple receivers).

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

If they use UDP multicast (the standard way of media streaming), they
never know who's listening.

-- 
Michael "Tired" Riepe <michael.riepe@googlemail.com>
X-Tired: Each morning I get up I die a little

      reply	other threads:[~2009-04-20 16:51 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   ` dvbd Kjeld Flarup
2009-04-20 16:51     ` Michael Riepe [this message]

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=49ECA808.50309@googlemail.com \
    --to=michael.riepe@googlemail.com \
    --cc=kjeld.flarup@liberalismen.dk \
    --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