Bug 104781

Summary: Ability to choose/override the sample rate of a sink
Product: PulseAudio Reporter: Jérôme Carretero <cJ-X>
Component: coreAssignee: pulseaudio-bugs
Status: RESOLVED MOVED QA Contact: pulseaudio-bugs
Severity: enhancement    
Priority: medium CC: lennart
Version: unspecified   
Hardware: Other   
OS: All   
Whiteboard:
i915 platform: i915 features:

Description Jérôme Carretero 2018-01-25 03:18:45 UTC
While performing tests on a USB audio DAC, I wanted to select a specific sample rate, but noticed that the only way to do so was by disabling anything that might get plugged on the sink (eg. running pavucontrol creates peak-detect elements, and I've seen it affect the sample rate selection) and playing sounds having that particular sample rate.

Having the ability to force a sink sample rate (and sample type) would be quite practical in this particular (niche I admit) use case, I don't know if there are other relevant ones (testing of resamplers? defective sample rate on a device?).
Comment 1 Tanu Kaskinen 2018-01-26 01:50:46 UTC
You can force a particular sample rate on all sinks (no per-sink configuration support) by setting "default-sample-rate" and "alternate-sample-rate" to the same value in /etc/pulse/deamon.conf.

I suppose it would be nice to be able to do the configuration in pavucontrol or other GUI without restarting pulseaudio, and to configure the sample rate on per-sink basis. I don't expect that the feature will be implemented any time soon, unfortunately (unless you write the code yourself).
Comment 2 GitLab Migration User 2018-07-30 10:03:03 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/184.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.