mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jamie Steele <steele.jamie1991@gmail.com>
To: Nicholas Johnson <nicholas.johnson-opensource@outlook.com.au>,
	Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>
Cc: Jonathan Corbet <corbet@lwn.net>,
	Shuah Khan <skhan@linuxfoundation.org>,
	linux-sound@vger.kernel.org, linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH 0/1] ALSA: add PreSonus Quantum PCI driver
Date: Sat, 24 Oct 2026 12:13:14 -0400	[thread overview]
Message-ID: <59ad0f62-dd4c-4d42-b50a-ab91bf469fb7@gmail.com> (raw)
In-Reply-To: <20260820083646.11383-1-nicholas.johnson-opensource@outlook.com.au>

On 8/20/26 4:36 AM, Nicholas Johnson wrote:

    The driver provides playback, capture, raw MIDI, sample-rate control,
    clock-source control, XRUN reporting, and surprise-removal handling.

Hi Nicholas,

I previously encountered sample-rate switching problems with this 
driver. Another Quantum 2626 tester has now reported similar behaviour 
using the August 20 RFC with Internal clock and direct ALSA hardware 
access, without PipeWire, JACK or a DAW.

His 15-minute 48 kHz duplex test completed without new xruns. At 
requested rates of 44.1, 88.2, 96 and 176.4 kHz, measured capture 
delivery remained around 48,000 frames/s. A nominal 10-second playback 
at 96 kHz took about 20 seconds. The actual hardware clock hasn’t been 
independently measured, so the cause is not yet isolated.

Full setup and results:
https://github.com/jamie-steele/presonus-quantum-linux/issues/34 
<https://github.com/jamie-steele/presonus-quantum-linux/issues/34>

Is this a known issue, and is anyone already working on a fix? Is there 
a newer patch series or development branch available to test? I’d like 
to avoid duplicating work if an update is already underway.

Thanks,
Jamie



      parent reply	other threads:[~2026-10-24 16:13 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-20  8:36 Nicholas Johnson
2026-08-20  8:36 ` [RFC PATCH 1/1] ALSA: pci: " Nicholas Johnson
2026-08-21 12:44   ` [RFC PATCH] " Markus Elfring
2026-08-21 13:00   ` Markus Elfring
2026-08-21 13:34   ` [RFC PATCH 1/1] " Markus Elfring
2026-08-21 14:24   ` [RFC PATCH] " Markus Elfring
2026-08-21 18:10   ` Markus Elfring
2026-08-22 14:20   ` Markus Elfring
2026-08-22 15:21   ` [RFC PATCH 1/1] " Matthew Wilcox
2026-09-18 18:34     ` [RFC] " Markus Elfring
2026-10-24 16:13 ` Jamie Steele [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=59ad0f62-dd4c-4d42-b50a-ab91bf469fb7@gmail.com \
    --to=steele.jamie1991@gmail.com \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=nicholas.johnson-opensource@outlook.com.au \
    --cc=perex@perex.cz \
    --cc=skhan@linuxfoundation.org \
    --cc=tiwai@suse.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®