Closed parautenbach closed 4 years ago
Thanks for the post. It's always interesting to see what people are doing with Shairport Sync!
The directory is used if you have enabled the MQTT
, native D-Bus
or MPRIS
interfaces on the Shairport Sync build. It will be created automatically if it doesn't exist. You can check the build of Shairport Sync using:
$ shairport-sync -V
The resulting string will list MQTT
, D-Bus
and MPRIS
if they have been included in the build.
Let me also suggest that you ensure you're using a recent version of Shairport Sync.
Thanks, Mike!
I woke up this morning thinking I should really check my version (bit of a n00b mistake by me). I'm indeed running a fairly old version: 3.2RC8-OpenSSL-Avahi-ALSA-metadata-sysconfdir:/usr/local/etc
.
And apologies for not following the reporting issues readme.
I'll go do my homework now properly and give feedback here. I think I'll also enable the MQTT
option.
:-)
This now works as expected: 3.3.7rc1-alac-OpenSSL-Avahi-ALSA-pipe-soxr-metadata-mqtt-sysconfdir:/etc
.
I'm following the instructions of this topic on the Home Assistant forums.
It mentions a setting named
cover_art_cache_directory
in themetadata
section. I can't find any documentation on this here on the project and my question there hasn't been answered yet. I don't know if I'm missing some documentation, but taking a chance to set it doesn't seem to work.This is what I have:
The pipe exists and that I can read fine with the
shairport-sync-metadata-reader
.Is this indeed an allowed setting?
What are my other options? Should I write my own script to read the pipe based on what's in
shairport-sync-metadata-reader
?