[pulseaudio-discuss] Using module-combine-sink with intermittent devices

Hi there. Thanks for the fantastic PA; I'm enjoying its elegance and power, and have been for years. I've been trying to search the web and the mailing list for answers to my questions, but the docs are few and the mailing list is hard to search. ... Lately, I'm setting up a sort of a

Re: [pulseaudio-discuss] Using module-combine-sink with intermittent devices

On Mon, Jan 18, 2016 at 8:25 PM, Arun Raghavan wrote: > > 2. I want to use module-combine-sink to play through several sound sinks > at > > the same time. It works, but things break down when one of the sinks > > disappears, which it does because it's a USB interface to a DAC

Re: [pulseaudio-discuss] Using module-combine-sink with intermittent devices

On Mon, Jan 18, 2016 at 8:25 PM, Arun Raghavan wrote: > > In short, I have two run-states: one with one soundcard, one with two; I > > want to support both transparently, playing the same source streams, > without > > having to log into the server and run pacmd. Is this

Re: [pulseaudio-discuss] Using module-combine-sink with intermittent devices

On Tue, Jan 19, 2016 at 6:50 PM, Matt Feifarek <matt.feifa...@gmail.com> wrote: > But I'll try it tonight. Thanks. > I have had great luck starting over from scratch... thanks to everyone for the help. In short, I'm using system mode, starting from systemd (with a re-launch

[pulseaudio-discuss] PA 8.0 -- what happened to soxr- resamplers

I updated my Ubuntu box to 16.04, where I was running PA7, and now with PA8, I get: W: [pulseaudio] resampler.c: Support for resampler 'soxr-vhq' not compiled in, reverting to 'auto'. Any insight? Thanks! ___ pulseaudio-discuss mailing list

Re: [pulseaudio-discuss] PA 8.0 -- what happened to soxr- resamplers

But the 7.0 deb DID include the soxr resamplers... just to clarify. On Wed, May 11, 2016 at 4:50 PM, Luke Yelavich <luke.yelav...@canonical.com> wrote: > On Thu, May 12, 2016 at 03:35:47AM AEST, Matt Feifarek wrote: > > Thanks, Luke. How is the PPA configured? > > Apart

Re: [pulseaudio-discuss] PA 8.0 -- what happened to soxr- resamplers

On Tue, May 10, 2016 at 11:47 PM, Luke Yelavich wrote: > We would have to get libsoxr into Ubuntu's main repository, which requires > commitment from Canonical to keep the package up to date, keep an eye on > bugs, etc. Given that pulse has to be built against

[pulseaudio-discuss] LADSPA on MacOS

I was pleased to see that module-ladspa-sink is present in the 9.0 compile of PA for MacOS (via Homebrew). But, there are no actual LADSPA things compiled for it or installed for it. In my Debian-derived world, I know what to do, but not here. I want to capture some streams on MacOS and route

Re: [pulseaudio-discuss] Delayed muting of studio speakers

I'm not following everything that you're writing (including the file you mentioned... which I've never messed with, but I find on my system as /usr/share/pulseaudio/alsa-mixer/paths/analog-output.conf.common) I think, though, that the file you mention might have to do with the alsa mixer labels

Re: [pulseaudio-discuss] Delayed muting of studio speakers

That'd be something to try; another device plugged into the same analog out, see if the muting behavior persists. Perhaps you thought of that already? On Tue, Dec 22, 2020 at 12:45 PM Chris Mayes wrote: > Speaking of Spotify, I remembered that I'd selected "quiet" for the volume > level under

Re: [pulseaudio-discuss] Networking and volume control

duplicate your problems, let me know. On Fri, Nov 6, 2020 at 4:27 PM Matt Feifarek wrote: > I think your theory is right; a tunnel sink isn't just a network proxy... > but I'd have to read up as to why. It might make sense that the volumes are > different in that regard... given the desi

Re: [pulseaudio-discuss] Tunnel vs direct connect to remote PA server - tunnel unreliable

Wow! Good find! I'll see if I can duplicate this result by installed some kind of time sync in the virtualbox machine that I mentioned. As far as controlling the volume remotely, I think you're right in thinking that the tunnel isn't a remote control onto the remote sink, it's a "virtual" sort

Re: [pulseaudio-discuss] Networking and volume control

just using the PA settings to allow tcp connections, and loading the remote sink by the "tunnel sink" module, but I don't think this has any benefits over zeroconf. I hope this helps. Sorry this has been so hard; I've been there! On Fri, Nov 6, 2020 at 3:54 PM Matt Garman wrote: >

Re: [pulseaudio-discuss] Networking and volume control

Perhaps this might help: when you set the PULSE_SERVER env variable, all the commands you run will be run against the Rpi, basically going around the local machine configuration. That's why you're seeing different sink configurations when you do pactl... it's effectively the same as you logging

Re: [pulseaudio-discuss] Latency/lag with tcp tunnel

> > Thanks! > ___ > pulseaudio-discuss mailing list > pulseaudio-discuss@lists.freedesktop.org > https://lists.freedesktop.org/mailman/listinfo/pulseaudio-discuss > -- *Matt Feifarek* +1.608.403.5432 phone / SMS / Signal / WhatsApp mattfeifarek.com ___ pulseaudio-discuss mailing list pulseaudio-discuss@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/pulseaudio-discuss

Re: [pulseaudio-discuss] Latency/lag with tcp tunnel

On Tue, Jan 26, 2021 at 2:09 PM Matt Garman wrote: > > The ma12070p is a newish digital input (I2S) class D amplifier > (essentially, a "power DAC" or a DAC and amplifier in one chip). > Between the RPI and amp is an Allo Kali I2S reclocker. I don't think > the Kali adds any meaningful latency,

Re: [pulseaudio-discuss] Latency/lag with tcp tunnel

> > From what you've reported above, a direct network client (e.g. > PULSE_SERVER=hostname mplayer /path/to/file ) should not have any more > latency than an on-device player. > And, using the zeroconf client makes that easy, since it's already on the server; Matt, if you load up that module on