sox-users@lists.sourceforge.net unofficial mirror
 help / color / mirror / code / Atom feed
From: "Måns Rullgård" <mans@mansr.com>
To: Maxim Doumkine <maxd@coregears.com>
Cc: sox-users@lists.sourceforge.net
Subject: Re: Loopback latency issue
Date: Sat, 11 Jul 2020 14:12:13 +0100	[thread overview]
Message-ID: <yw1x7dvap55e.fsf@mansr.com> (raw)
In-Reply-To: <9148e80a-8af7-4545-af62-bf4f3512aace@Spark> (Maxim Doumkine's message of "Fri, 10 Jul 2020 20:40:09 +0300")

Maxim Doumkine <maxd@coregears.com> writes:

> Hello everyone,
>
> We are trying to build a Sox based real-time sound altering app, and we’ve
> got everything working on our LUbuntu 16.04 stations except for an issue w
> latency.
>
> When we test it on actual hardware, we are having a latency of about 2
> seconds, when we test it on our virtual machine the latency is more like
> 250ms.
>
> sox -t pusleaudio default -t pulseaudio null pitch n
> Whenever we add the null loopback or aloop, we experience a delay. No amount
> of config tinkering seems to affect this latency on an actual workstation.

The first thing I'd do is get rid of pulseaudio and access the ALSA
device directly.  Even then, however, there are several places where
latency is added.  You can find the ALSA buffer sizes currently uses by
examining /proc/asound/card0/pcm0p/sub0/hw_params (or whatever numbers
your system uses).  The size (in bytes) of the main buffer in SoX is set
with the --buffer option.  Some effects have additional internal buffers.

-- 
Måns Rullgård


_______________________________________________
Sox-users mailing list
Sox-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sox-users

  parent reply	other threads:[~2020-07-11 13:30 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <0713c9d8-7bdf-4b97-99b4-12e219e94d45@Spark>
2020-07-10 17:40 ` Loopback latency issue Maxim Doumkine
2020-07-10 18:08   ` Darryl Lewis
2020-07-11 16:04     ` Maxim Doumkine
2020-07-11 13:12   ` Måns Rullgård [this message]
2020-07-11 15:59     ` Maxim Doumkine
2020-07-11 16:12     ` Steve Masters
2020-07-13 11:49   ` Jan Stary
2020-07-13 12:05     ` Jan Stary
2020-07-13 15:09     ` Maxim Doumkine
2020-07-13 20:52     ` Måns Rullgård
2020-07-13 22:20       ` Rafal Maszkowski

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-list from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://lists.sourceforge.net/lists/listinfo/sox-users

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=yw1x7dvap55e.fsf@mansr.com \
    --to=sox-users@lists.sourceforge.net \
    --cc=maxd@coregears.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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/sox.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).