Commit b70ad87f authored by Bob Ham's avatar Bob Ham

base-defaults: Add PulseAudio daemon.conf.d snippet to change default sample rate

This fixes call audio on the devkit.  The stock default sample rate is
44.1 kHz and PulseAudio wants a multiple of 8 kHz due to Haegtesse.
Confusion ensues because the hardware restricts the available sample
rate in either the ADC or DAC once the other side is opened.
PulseAudio assumes that the list of available sample rates never
changes.  We work around this by making the default sample rate 48
kHz, a multiple of 8 kHz.
parent 602154a7
Pipeline #4391 passed with stage
in 52 seconds
......@@ -3,3 +3,4 @@ default/09_librem5.gschema.override usr/share/glib-2.0/schemas/
default/blackboard-1920.jpg usr/share/librem5/default-theme/
default/85-librem5-evk-sgtl5000.rules etc/udev/rules.d/
default/librem5-evk.conf usr/share/pulseaudio/alsa-mixer/profile-sets/
default/75-librem5-evk-sgtl5000.conf etc/pulse/daemon.conf.d
# Call audio uses 8 kHz by default. PulseAudio tries to minimise
# resampling efforts by setting the sample rate of a source/sink to a
# multiple of the input/output's sample rate. In the case of
# Haegtesse, it tries 48 kHz over 44.1 kHz. However, the sample rates
# on the SGTL5000 must be the same for both the ADC and DAC. When
# PulseAudio starts, it queries the SGTL5000's supported sample rates
# for playback and recording separately and then opens the playback
# and record devices with the default sample rate of 44.1 kHz.
# When Haegtesse comes along, it tries to change the sample rate of
# one of the streams to 48 kHz while the other is still open. This
# fails and causes a lot problems (made worse by the fact that
# PulseAudio "successfully" sets the sample rate on the configuration
# and only later changes the sample rate on the hardware). To work
# around this, we simply set the default sample rate to 48 kHz so that
# no sample rate change is needed.
default-sample-rate = 48000
alternate-sample-rate = 44100
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment