All of lore.kernel.org
 help / color / mirror / Atom feed
From: Clemens Ladisch <clemens@ladisch.de>
To: alsa-devel@alsa-project.org
Subject: Re: VOIP xrun problem
Date: Tue, 23 Oct 2012 17:10:06 +0200	[thread overview]
Message-ID: <5086B34E.30400@ladisch.de> (raw)
In-Reply-To: <CAJqUV3_pp0upB_fV_TzK7PTJYQTatU=uGbgWG8cC899RBHXxqw@mail.gmail.com>

Jamey Drennan wrote:
> On Tue, Oct 23, 2012 at 2:35 AM, Clemens Ladisch <clemens@ladisch.de> wrote:
>> So the RTP stream is synchronized to the sender's clock.
>> How do you handle the differences between the stream's clock and
>> the playback device's clock?
>
> The client and server negotiate the connection parameters including packet
> interval, size, audio format, and rate.  The rtp library ensures that the
> packets arrive on time and accounts for initial time differences.  Maybe
> the timestamps of the stream packets aren't enough to keep the two clocks
> synchronized(or a frame is the same regardless if the two devices are set
> up the same)?

The sender's and receiver's clocks are determined by the crystals
soldered onto their sound cards.  You can try to configure them for
the same nominal sample rate, but you cannot avoid that they run fast
or slow relative to each other by some fraction of a percent.

> In testing, the two clocks are one and the same since I am
> running the client and server on the same device.

So the problem shows up even when testing?


Regards,
Clemens

  reply	other threads:[~2012-10-23 15:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-22 20:40 VOIP xrun problem Jamey Drennan
     [not found] ` <5085B04E.8040507@faberman.de>
2012-10-22 20:56   ` Jamey Drennan
2012-10-23  6:35     ` Clemens Ladisch
2012-10-23 15:00       ` Jamey Drennan
2012-10-23 15:10         ` Clemens Ladisch [this message]
2012-10-23 19:03         ` Jamey Drennan
2012-10-24 16:21           ` Jamey Drennan

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=5086B34E.30400@ladisch.de \
    --to=clemens@ladisch.de \
    --cc=alsa-devel@alsa-project.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.