All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gerrit Renker <gerrit@erg.abdn.ac.uk>
To: dccp@vger.kernel.org
Subject: Re: Gstreamer e DCCP: issues related to ccid-3
Date: Thu, 25 Oct 2007 10:17:14 +0000	[thread overview]
Message-ID: <200710251117.14404@strip-the-willow> (raw)
In-Reply-To: <5bc4c4570710242047h1d9b1c64k6381ba5c3a421355@mail.gmail.com>

|   I'm implementing the dccp plugin for gstreamer and everything goes
|  very well, I can transmit an mp3 sound using ccid-2, but when I try to
|  use ccid-3, I can just send very little via send function and after
|  the function returns 11 (EAGAIN). Is there any different parameter
|  that I should set? I think that the problem that you had in VLC should
|  be the same
This problem (or "feature") is well-known, Ian has also repeatedly pointed out
to this. Basically, what your code needs to be able to do is cope with EAGAIN,
i.e. when the TX buffer is full and CCID3 decides to throttle the sending speed,
the write call needs to be repeated.

I haven't checked the VLC code lately (it will have such a test), but I know that 
Andre Noll developed a very clever way of handling this, by using a "generic chunk queue" 
for audio chunks which could currently not be sent. He implemented this in paraslash
(file dccp_send.c), the sources are on http://www.systemlinux.org/~maan/paraslash/

For this most recent feature, it is best to use his git tarball:

  http://www.systemlinux.org/~maan/paraslash/versions/paraslash-git.tar.bz2


I also 

  reply	other threads:[~2007-10-25 10:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-25  3:47 Gstreamer e DCCP: issues related to ccid-3 Łeandro Sales
2007-10-25 10:17 ` Gerrit Renker [this message]
2007-10-25 10:29 ` Gerrit Renker
2007-10-25 17:14 ` Ian McDonald
2007-11-01  4:13 ` Łeandro Sales
2007-11-01  9:48 ` Gerrit Renker

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=200710251117.14404@strip-the-willow \
    --to=gerrit@erg.abdn.ac.uk \
    --cc=dccp@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 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.