From: Maxim Doumkine <maxd@coregears.com>
To: "sox-users@lists.sourceforge.net"
<sox-users@lists.sourceforge.net>,
sox-users@lists.sourceforge.net
Subject: Re: Loopback latency issue
Date: Sat, 11 Jul 2020 19:04:19 +0300 [thread overview]
Message-ID: <b8870be5-e817-41f9-b4be-bcfa1e50f959@Spark> (raw)
In-Reply-To: <DA8BA049-F866-4805-8C5B-9F645653E437@unsw.edu.au>
[-- Attachment #1.1: Type: text/plain, Size: 1411 bytes --]
Yes it is an exact clone.
On 10 Jul 2020, 21:09 +0300, Darryl Lewis <darryl.lewis@unsw.edu.au>, wrote:
>
> Is your virtual machine exactly the same (OS version) as your physical PC?
> It might be a driver issue with different versions.
>
>
> From: Maxim Doumkine <maxd@coregears.com>
> Reply to: "sox-users@lists.sourceforge.net" <sox-users@lists.sourceforge.net>
> Date: Saturday, 11 July 2020 at 3:58 am
> To: "sox-users@lists.sourceforge.net" <sox-users@lists.sourceforge.net>
> Subject: [SoX-users] Loopback latency issue
>
> 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.
>
> We’d appreciate an advice or any input but would be equally glad to hire a consultant for a fee to get this resolved.
>
> Thank you.
> _______________________________________________
> Sox-users mailing list
> Sox-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/sox-users
[-- Attachment #1.2: Type: text/html, Size: 3008 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
[-- Attachment #3: Type: text/plain, Size: 158 bytes --]
_______________________________________________
Sox-users mailing list
Sox-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sox-users
next prev parent reply other threads:[~2020-07-11 16:04 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 [this message]
2020-07-11 13:12 ` Måns Rullgård
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=b8870be5-e817-41f9-b4be-bcfa1e50f959@Spark \
--to=sox-users@lists.sourceforge.net \
/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).