All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stuart Naylor <stuartiannaylor@outlook.com>
To: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
	Hector Martin 'marcan' <marcan@marcan.st>
Subject: RE: USB audio cuts 2-3 secs at start
Date: Mon, 10 Aug 2020 23:45:31 +0000	[thread overview]
Message-ID: <DB7P191MB033205209A79C181EFB49C22A8440@DB7P191MB0332.EURP191.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <bcf009b2-9a35-8b2f-5629-2fb991c41ea0@marcan.st>

Thanks for the reply.

Windows it works with and a recent firmware fix solved that as its shipped with Windows behaving the same.
The Anker Power conf has a smartphone app that makes the firmware update a button click.
I don’t think they could make a secret update to windows and also I did originally think the same.
I used sox with the -n option to constantly send a null silent stream.
The unit doesn’t seem to like that as received some weird effects with recording.
Its almost like the unit prefers to switch modes and can do so quickly but not both at once.
I guess it operates in a similar manner to wideband Bluetooth as its both USB & Bluetooth but only one connected device and interface can be used at one time.

On X86 and I say X86 as the difference might be Pulseaudio not architecture just my Socs where quick tests with aplay.
I haven’t looked at the asound.conf of Ubuntu desktop but Alsa could be set to use the PA Server.
Again I was using aplay but onX86 Ubuntu only the very first play cuts and all subsequent are then like windows.
I am fairly sure PA doesn’t employ keepalive trickles but maybe it does?

I would of probably agreed with you until my sox hack produced such an array of problems.

Stuart

Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows 10

From: Hector Martin 'marcan'<mailto:marcan@marcan.st>
Sent: 10 August 2020 05:47
To: Stuart Naylor<mailto:stuartiannaylor@outlook.com>; alsa-devel@alsa-project.org<mailto:alsa-devel@alsa-project.org>
Subject: Re: USB audio cuts 2-3 secs at start

On 29/07/2020 02.08, Stuart Naylor wrote:
> http://alsa-project.org/db/?f=6b107178c9939f235a390c07cb5c1f71d6a6e0c0
>
> Its an Anker power conf and for some reason the first couple of seconds of aplay do not play via USB.
>
> Alsa-info above anyone and tips or ideas?

I bet this is just the way the hardware behaves. It probably takes a few
seconds to turn on its amplifiers and audio path when USB streaming starts.

If it doesn't happen in other OSes, then most likely those OSes
continuously stream audio to the device even when it is unused. The
workaround would be to do the same, e.g. use pulseaudio and disable
suspend-on-idle, or use JACK, or something along those lines that always
keeps the device running (with silence when no app is using it).

--
Hector Martin "marcan" (marcan@marcan.st)
Public Key: https://mrcn.st/pub


      reply	other threads:[~2020-08-10 23:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.12167.1595955329.5591.alsa-devel@alsa-project.org>
2020-07-28 17:08 ` USB audio cuts 2-3 secs at start Stuart Naylor
2020-08-10  4:47   ` Hector Martin 'marcan'
2020-08-10 23:45     ` Stuart Naylor [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=DB7P191MB033205209A79C181EFB49C22A8440@DB7P191MB0332.EURP191.PROD.OUTLOOK.COM \
    --to=stuartiannaylor@outlook.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=marcan@marcan.st \
    /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.