![]() ![]() RAM: I have assigned 1GB but it could do with far less (256MB/512MB). It is super lightweight as it turnes out: What I could not find are system requirements in terms of CPU/RAM/SSD Installing Avahi Daemon was required: sudo apt install avahi-daemon The configuration was super easy, however I couldn’t start Owntone as described - Avahi Daemon was missing on the above Ubuntu Distribution. I did mount a CIFS/SMB Share to the CT/Ubuntu (my music resides on a network share / NAS). Using the guide from Github ( ) was quite straight forward. I did set forked-daapd (new name: OwnTone) up on Promox as a CT with ubuntu-18.04 as a template-base. What I really need is Shairport-Sync to be AirPlay 2 compatible. Which is cool, but just doesn’t fit my use case. I originally posted in here because I was a bit unclear about what forked-daapd does but I understand now that it’s essentially a drop-in replacement iTunes. If Shairport-Sync was AP2 compatible, that could be done from the iOS AirPlay overlay, provided you have a device setup for each zone. As it is today, I can AirPlay from iOS to my single (Airplay 1 compatible) Shairport Sync device, but then I have to hop over to the Home Assistant app to activate specific zone speakers and control their volume. Shairport-Sync, if it were enhanced to support AirPlay 2, could do this (if I bought 6 Raspberry Pis). That’s why I’m trying to find some software or device that I can use to make my 6 zones around the house AirPlay 2 receivers. You can control it right from the AirPlay overlay in iOS. Yes, Apple Music can play to multiple AirPlay 2 endpoints (regardless of what the source of music is – library on the phone, streaming from Apple services, etc). What does storing the music locally have to do with it? Run_this_after_play_ends = "/scripts/vol.sh 33" Run_this_before_play_begins = "/scripts/vol.sh 100" chmod 775 /mnt/data/supervisor/share/shairport/scripts/vol.sh. ![]() Add a file /mnt/data/supervisor/share/shairport/scripts/vol.sh.So we resort to this cludgy but effective workaround. You could use the forked-daapd api to change the volume but Mike Brady’s image is built on busybox which doesn’t have curl. Unsure if it’s just something I didn’t get right but playing through the whole house airplay pipes my audio through two different sets of volume controls (phone & forked-daapd) resulting in cumbersome operation.mnt/data/supervisor/share/shairport/scripts:/scripts mnt/data/supervisor/share/shairport/nf:/etc/nf To - /mnt/data/supervisor/share/music:/music mnt/data/supervisor/share/shairport:/config mnt/data/supervisor/share/music:/music change volumes section of docker-compose from:.put it in /mnt/data/supervisor/share/shairport/nf.(Not a big deal but could save someone a lot of head scratching.) Some of your nf entries have no semicolons.Thank you! This solved an issue I’ve been wanting to take care of for years. Happy to work on something like this with you if you like.įantastic tutorial. In this setup we need to stream from mopidy to forked-dappd but I’m not sure the MPD clients or the remote iTunes app could mange changing streams / speakers.Īnother option is to build around the full forked-dappd installation as the music server and integrated Spotify somehow (any ideas how to?) and use the remote iTunes app as a client using this script (un-tested) One options is to use mopidy + Mopidy-Spotify as an spority + local integrated music server AND slimmed down version of owntone-server - without the iTunes library or mpd server. I’m trying to build a setup around Airplay, Spotify, local music files and a mobile front-end.ġ - Media server that can combine local files with Spotify (and possibly other streams / services)Ģ - forked-dappd (now owntone-server to stream to AirPlay speakersģ - A Mobile front end to control media and playing (an MPD client or apple’s remote iTunes app) ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |