All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Sakamoto <o-takashi@sakamocchi.jp>
To: Jaroslav Kysela <perex@perex.cz>
Cc: "M. Armsby" <m.armsby@gmx.de>,
	alsa-devel@alsa-project.org,
	Takashi Sakamoto <takaswie@kernel.org>
Subject: Re: ALSAfirewire broken / Pipewire 90ms delay
Date: Fri, 5 Sep 2025 05:44:50 +0900	[thread overview]
Message-ID: <20250904204450.GA221422@workstation.local> (raw)
In-Reply-To: <13e0868a-6528-42fa-ab9a-2b5e37e095f3@perex.cz>

On Thu, Sep 04, 2025 at 03:32:52PM +0200, Jaroslav Kysela wrote:
> It would be nice to check the buffer size / period size values using procfs
> for the problematic 2048 setup (see the referred thread), if there's a
> demand to fix this. Maybe there's a mismatch between GUI/sound server
> settings and driver settings.

Please suggest that all people involved in the discussion use strace(1)
to determine whether the failure originates from SNDRV_PCM_IOCTL_HW_PARAMS
or SNDRV_PCM_IOCTL_PREPARE, since the alsa-lib API, 'snd_pcm_hw_params()',
involves both and can be misleading.


Thanks

Takashi Sakamoto

  reply	other threads:[~2025-09-04 20:45 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-24 10:37 ALSAfirewire broken M. Armsby
2025-07-24 14:38 ` Takashi Sakamoto
2025-07-30 19:36   ` ALSAfirewire broken / Pipewire 90ms delay M. Armsby
2025-08-10 13:35     ` M. Armsby
2025-09-02  7:59     ` M. Armsby
2025-09-03  1:11       ` M. Armsby
2025-09-03  8:47         ` Jaroslav Kysela
2025-09-03 11:15           ` Takashi Sakamoto
2025-09-03 12:19             ` Jaroslav Kysela
2025-09-04 13:18               ` Takashi Sakamoto
2025-09-04 13:32                 ` Jaroslav Kysela
2025-09-04 20:44                   ` Takashi Sakamoto [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-08-06 10:57 Goran Kovac

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=20250904204450.GA221422@workstation.local \
    --to=o-takashi@sakamocchi.jp \
    --cc=alsa-devel@alsa-project.org \
    --cc=m.armsby@gmx.de \
    --cc=perex@perex.cz \
    --cc=takaswie@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.