Re: [pulseaudio-discuss] PATCH 3/3: RAOP: Add latency value for Shairport RAOP server

On 08 October 2017 at 21h21, Tanu Kaskinen wrote: Hi, > > +} else if (pa_streq(model, "ShairportSync")) { > > +/* Shairport - software AirPort server */ > > +default_latency = 2352; > > } > > > > pa_log_debug("Default latency is %u ms for device model %s.", > >

Re: [pulseaudio-discuss] PATCH 3/3: RAOP: Add latency value for Shairport RAOP server

On Sat, 2017-10-07 at 20:20 +0200, Colin Leroy wrote: > From 5882bd15c528a0e9987a02f9ddcdd093087ae548 Mon Sep 17 00:00:00 2001 > From: Colin Leroy > Date: Sat, 7 Oct 2017 20:11:49 +0200 > Subject: [PATCH 3/3] RAOP: Add latency value for Shairport RAOP server > > After testing,

Re: [pulseaudio-discuss] PATCH 1/3: RAOP: Show device codename in sink properties

On Sat, 2017-10-07 at 20:19 +0200, Colin Leroy wrote: > This will make it easier for testers to report latency offset for their > specific hardware. > > Also, remove the IP:port part from the device description; it will go > in the pa_device_port description in the next commit. To me it would

Re: [pulseaudio-discuss] PATCH 2/3: RAOP: Init dummy port and card for latency change

On Sat, 2017-10-07 at 20:20 +0200, Colin Leroy wrote: > From bd815a400ad280627083cbce3ef9b927f669faa0 Mon Sep 17 00:00:00 2001 > From: Colin Leroy > Date: Sat, 7 Oct 2017 20:10:21 +0200 > Subject: [PATCH 2/3] RAOP: Init dummy port and card for latency change > > This adds a

Re: [pulseaudio-discuss] [PATCH] pavucontrol: Set latency offset's maximum to 5000ms

On Fri, 2017-10-06 at 20:22 +0200, Colin Leroy wrote: > Hi, > > Airplay hardware has a inherent latency of at least 2 seconds, with > 2350ms being a common value. Thanks! Applied. -- Tanu https://www.patreon.com/tanuk ___ pulseaudio-discuss mailing

Re: [pulseaudio-discuss] [PATCH v2 0/3] Fix Intel HDMI LPE problems

On Sun, 2017-10-08 at 19:48 +0300, Tanu Kaskinen wrote: > The Intel HDMI LPE driver uses hw:0 for HDMI, which is different from > the HDA device numbering scheme. Our jack detection and ELD code assumed > the HDA numbering, these patches remove the assumption. > > If PulseAudio tries to play

[pulseaudio-discuss] [PATCH v2 1/3] alsa-mixer: add hw_device_index to pa_alsa_mapping

We have so far assumed that HDMI always uses device indexes 3, 7, 8, 9, 10, 11, 12 and 13. These values are hardcoded in the path configuration. The Intel HDMI LPE driver, however, uses different device numbering scheme. Since the indexes aren't always the same, we need to query the hw device

[pulseaudio-discuss] [PATCH v2 2/3] alsa-mixer: autodetect the HDMI jack PCM device

This removes the need to hardcode the PCM device index in the HDMI jack names. The hardcoded values don't work with the Intel HDMI LPE driver. BugLink: https://bugs.freedesktop.org/show_bug.cgi?id=100488 --- src/modules/alsa/alsa-mixer.c | 53 --

[pulseaudio-discuss] [PATCH v2 3/3] alsa-mixer: autodetect the ELD device

This removes the need to hardcode the ELD device index in the path configuration. The hardcoded values don't work with the Intel HDMI LPE driver. BugLink: https://bugs.freedesktop.org/show_bug.cgi?id=100488 --- src/modules/alsa/alsa-mixer.c | 28 --

[pulseaudio-discuss] [PATCH v2 0/3] Fix Intel HDMI LPE problems

The Intel HDMI LPE driver uses hw:0 for HDMI, which is different from the HDA device numbering scheme. Our jack detection and ELD code assumed the HDA numbering, these patches remove the assumption. If PulseAudio tries to play audio while the monitor is not plugged in, the HDMI LPE driver will

Re: [pulseaudio-discuss] RAOP, pavucontrol and general "Latency offset"

On Fri, 2017-10-06 at 14:51 -0400, Chris Billington wrote: > Hi Colin, > > A while ago I wanted to set the latency offset of a null sink, and I wrote > some patches to be able to do this, not by adding a port, but by adding the > ability to set the latency offset on a sink. I'm sure you can find