Maxim Cournoyer <[email protected]> writes:
> Hi Ian,
>
> Ian Eure <[email protected]> writes:
>
> [...]
>
>>> Confusingly, the home-pipewire-configuration record has an
>>> extra-content
>>> field, but that gets added to ~/.config/alsa/asoundrc, a file I
>>> can't
>>> see documented in pipewire's documentation (it seems it's an ALSA
>>> thing
>>> rather than a Pipewire one? Perhaps there's a more modern file to
>>> use
>>> in its place, like pipewire.conf?)
>>
>> I agree this seems odd. The service adds some ALSA configuration, I
>> do think PipeWire needs at least some of that to work, but it seems
>> much more useful to configure PW itself than ALSA in this instance.
>> Perhaps it was added because that’s the only service that touches
>> asoundrc at all, and if you have some other ALSA config you need,
>> that’s how you do it. Really seems like there should be an ALSA
>> service-type which pipewire extends to add its configs, though.
>
> Yeah, it'd be nice to have some fields to add drop-in configs for
> pipewire and wireplumber to extend it more easily, and maybe rename that
> extra-content field to something more descriptive (asoundrc?).
since i wrote it, i'll say that i probably made a mistake calling that
field ‘extra-content’, instead of ‘extra-asoundrc-content’. i think it
probably makes sense to create a field for pipewire and wireplumber
config extras.
maybe deprecate ‘extra-content’ to replace with ‘extra-asoundrc-content’
and add new fields for ‘extra-{pipewire,wireplumber}-content’?
wdyt?
> So my solution now looks like this:
>
> # file: ~/.config/pipewire/pipewire.conf.d/10-sample-rates.conf
should we have a mechanism in home-pipewire-config for this kind of
rc.d/udev configuration file types? my knee-jerk reaction would be that
it's not worth it, and we should be using
home-xdg-configuration-files-service-type.
> And then 'herd restart pipewire' (and sometimes I have to follow with
> 'herd restart wireplumber', as there seems to be a race) gives me a rate
> that goes to 192 kHz when using the analog output of the ALC4080 when
> playing hi-res FLAC or 96 kHz if using its SPDIF output instead.
there shouldn't be a race here, as wireplumber depends on pipewire,
shouldn't restarting pipewire auto-restart wireplumber? that's how it's
working for me.
i'll note that i have to restart wireplumber sessions after it restarts
for things like firefox which don't retry automatically.
-bjc
