- 20 Dec, 2020 2 commits
-
-
David Marzal authored
Part-of: <pulseaudio/pulseaudio!439>
-
David Marzal authored
Part-of: <pulseaudio/pulseaudio!439>
-
- 16 Dec, 2020 7 commits
-
-
Part-of: <pulseaudio/pulseaudio!360>
-
Part-of: <pulseaudio/pulseaudio!360>
-
Part-of: <pulseaudio/pulseaudio!360>
-
This is a temporary addition, until <afunix.h> ships with the MinGW toolchain. Part-of: <pulseaudio/pulseaudio!360>
-
Part-of: <pulseaudio/pulseaudio!360>
-
Part-of: <!360>
-
Part-of: <pulseaudio/pulseaudio!360>
-
- 14 Dec, 2020 7 commits
-
-
Some filters take parameters that effectively describe the hardware they're being applied to (like echo-cancel allowing to specify the mic array parameters for better noise filtering). This allows system integrators to set default parameters for such modules per-device, which will get used when the stream doesn't specify their own. Part-of: <!400>
-
The JACK sink and source priority was 0, but I believe the common case is that when a JACK sink or source is loaded, the user wants to make it the default device. Fixes: pulseaudio/pulseaudio#983 Part-of: <pulseaudio/pulseaudio!369>
-
Part-of: <pulseaudio/pulseaudio!437>
-
The old behaviour was such that if none of the normal mappings worked, we would probe ALL fallbacks. I don't think that makes sense, and it caused concrete issues: let's say we have a regular stereo mic device, but there's no "front" PCM defined for it. In this situation we would probe the stereo-fallback mapping (which uses "hw" instead of "front"), and it would work, but then we'd also probe the "multichannel-input" mapping, which would also work, so we end up with two mappings that don't have any difference in behaviour. I think it's better to simply pick the first working fallback and ignore the rest. Fixes: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/901 (issue is marked as confidential due to unreleased hardware) Part-of: <pulseaudio/pulseaudio!304>
-
Try $XDG_DATA_HOME, then $XDG_DATA_DIRS, and finally fall back to old behaviour (prefix-defined directory). core-util: Ignore non-absolute XDG base dirs These are invalid per the spec. Fixes: pulseaudio/pulseaudio#862 Part-of: <pulseaudio/pulseaudio!293>
-
If we do not manage to rewind at all because there is nothing to rewind any more, it means the latency is too small, and we let audio escape our control. We should thus increase the watermark to fix this. Fixes #871 Part-of: <pulseaudio/pulseaudio!287>
-
Igor Kovalenko authored
Allow adding module arguments using udev PULSE_MODARGS environment variable and fail module loading if there is a problem with PULSE_MODARGS This helps setting e.g. 'tsched=0' for specific devices without a need to create full load module entry in default.pa. Part-of: <pulseaudio/pulseaudio!436>
-
- 10 Dec, 2020 4 commits
-
-
With the Auto-Mute enabled, if the headphone jack is plugged, the alsa hda driver will mute the speaker and set pinctl of the speaker to Hi-Z state, after this happens, even the pulseaudio unmute the speaker, the speaker still couldn't output sound because the pinctl is in Hi-Z state. We found this issue on a Dell machine which has multi-function audio jack, after the headphone is plugged in, the speaker's availability is still unknown, users could select speaker from gnome-sound-setting, but even the speaker is selected to be the active device, it couldn't output sound. The Auto-Mute is not useful if the pulseaudio is running since pa could mute/unmute devices according to active port change, the ucm for sof+hda already disabled the Auto-Mute, let us disable it for hda audio if the machine has the internal speaker. Signed-off-by:
Hui Wang <hui.wang@canonical.com> Part-of: <!433>
-
Since there is now support for specifying the index of an Element, add the same config as is used for the output-mono variant, as they behave the same: One volume control with no support for adjustments to the left and right channels. Part-of: <pulseaudio/pulseaudio!274>
-
Some gaming sound cards have custom profiles with analog-game and analog-chat mappings that exist simultaneously. The game sink should have higher priority than the chat sink, but currently there's no way to affect the sink priorities from the profile-set configuration (the mapping priority is not propagated to the sink priority). I first thought about adding the mapping priority to the sink priority, but that could mess up the prioritization system in pa_device_init_priority(). I ended up checking for the intended roles property to reduce the chat sink priority. I also reduced the iec958 priority so that the chat and iec958 sinks don't end up with the same priority. Fixes: pulseaudio/pulseaudio#818 Part-of: <pulseaudio/pulseaudio!266>
-
Despite the ratelimiting, this error gets logged too much. I fixed a typo (Fallig -> Falling) while at it. Related: pulseaudio/pulseaudio#824 Part-of: <pulseaudio/pulseaudio!265>
-
- 09 Dec, 2020 7 commits
-
-
This same profile should also work for the GSX 1200, but I don't know the USB id for that. Part-of: <pulseaudio/pulseaudio!257>
-
Aids in tracking down exactly where in the chain underruns are happening. Signed-off-by:
Pierre Ossman <ossman@cendio.se>
-
In OpenEmbedded the PulseAudio recipe currently disables Valgrind support by passing "ac_cv_header_valgrind_memcheck_h=no" to the configure script (this was added to make it deterministic whether Valgrdind support gets enabled or not). I'm converting the PulseAudio recipe to use Meson, and I needed an option to disable Valgrind.
-
Since there's no stable API for modules, all modules need to be compiled together with the server. This version check tries to ensure that if a version mismatch happens, there will be an informative error message rather than a random crash.
-
Since commit ad447d14 (in 2009) pa_read and pa_write take care of handling EINTR error. So, pa_read, pa_write, pa_iochannel_read and pa_iochannel_write can not exit with errno set to EINTR, and testing it is useless.
-
module-jackdbus-detect now accepts sink_name, sink_properties, sink_client_name, sink_channel_map, source_name, source_properties, source_client_name, and source_channel_map arguments that will be passed through to module-jack-source and module-jack-sink (without the sink and source prefixes, except where needed).
-
This module uses 2 seconds for default max latency. If max_latency_msec is set, max_latency value will be changed. Part-of: <pulseaudio/pulseaudio!431>
-
- 08 Dec, 2020 2 commits
-
-
Tanu Kaskinen authored
Part-of: <pulseaudio/pulseaudio!432>
-
Currently translated at 76.0% (400 of 526 strings) Translation: pulseaudio/pulseaudio Translate-URL: https://translate.fedoraproject.org/projects/pulseaudio/pulseaudio/sk/ Part-of: <pulseaudio/pulseaudio!432>
-
- 07 Dec, 2020 4 commits
-
-
Sanchayan Maity authored
As long as modules use different keys, multiple loading of this module should be safe. Even in case of same keys, either the pa_proplist_update should correctly update the property list based on the mode or for the volume writable case, the last rule should win. Fixes: #942 Part-of: <!332>
-
-
-
It takes much time when starting to capture because max latency is set to 2 seconds as a initial value. null-source latency need to be set a lower value than initial value to improve latency.
-
- 03 Dec, 2020 7 commits
-
-
Part-of: <!51>
-
Part-of: <!51>
-
Tanu Kaskinen authored
Part-of: <pulseaudio/pulseaudio!51>
-
Tanu Kaskinen authored
These tests aren't directly related to modargs. I suppose these were first written for the modargs.h API and renaming was forgotten. Part-of: <!51>
-
Tanu Kaskinen authored
Part-of: <!51>
-
Tanu Kaskinen authored
I believe nobody needs to pass octal numbers to PulseAudio, and if we encounter integer strings starting with zeros, the intention is to use them in base 10. Hexadecimal numbers are more common, and they can't be interpreted in base 10 anyway, so they are still supported. Part-of: <!51>
-
Tanu Kaskinen authored
Part-of: <!51>
-