ejurgensen wrote:@cdlenfert, another possible cause of the issue could be this.
Here is a build you can test that has the modification for slow system timers.
Let me know if this fixes the problem, then I will look into a proper way of supporting these kind of timers.
Code: Select all
[2017-05-11 06:03:35] [ LOG] player: The AirPlay device 'Kitchen' FAILED
[2017-05-11 06:03:36] [ LOG] player: Bug! Input metadata item_id does not match anything in queue
[2017-05-11 06:08:09] [ LOG] player: Source is not providing sufficient data, temporarily suspending playback
Just watching the CPU monitor that comes installed by default in the top right bar on Raspbian during active streaming to multiple airplay speakers (also connected via a VNC session) the Pi ZeroW is showing between 30-40% and when it switches tracks (I think) it spikes up to around 70% and 100% on occasion. Maybe that explains the drop out after a track is completed. Please let me know if there's a better way to monitor this.ejurgensen wrote:Did you get to check the cpu use?
Code: Select all
***
Code: Select all
*** Somewhere below the connection to the kitchen speaker stopped, but playback to the office speaker continued ***
[2017-05-19 09:25:41] [DEBUG] raop: Got retransmit request, seq_start 3293 len 1
[2017-05-19 09:25:49] [DEBUG] player: Input buffer has 176896 bytes
Hi RobP, is there any chance you ever got this up and running on Rasbian Jessie Lite? Forked-daapd is failing to start for me. Thanks_RobP wrote:At any rate, I noted every step and put them across three blog posts here: http://robpope.co.uk/blog/post/multi-ro ... -bluetooth
@Marioscube - Any chance you can get Jessie Lite running on a fresh SD Card and follow the instructions to see if it works for you?
.
I dont know your setup. In case you are using FHEM for home automation, then it is very easy to use alexa (ha-bridge) and control mpd/forked-daapd via custom skills. However I would not install FHEM if this is the only use-case.liminal wrote:Hi guys,
Coming back to my Alexa Spotify project
(Play Spotify from Echo Dot output though Forked-daapd using named pipes and controlling airplay speaker connect and disconnect/ volume though MPC using HTTP requests from HA-Bridge
Just wanted to know if anyone had any documentation/ how to ect for controlling MPC though http requests?
Thanks in advance!
Code: Select all
sudo sh pairinghelper.sh
This script will help you pair Remote with forked-daapd
Please verify that these paths are correct:
Log file: '/var/log/forked-daapd.log'
Library: '/home/pi/Music'
Confirm? [Y/n] y
Please start the pairing process in Remote by selecting Add library
Press ENTER when ready...
Looking in /var/log/forked-daapd.log for Remote announcement...found
Ready to pair Remote 'Alex's iPhone', please enter PIN: 4207
Writing pair.remote to /home/pi/Music...
Waiting for pairing to complete (up to 20 secs)...
forked-daap doesn't appear to be finding /home/pi/Music/pair.remote...
Check /var/log/forked-daapd.log, removing pair.remote
Code: Select all
remote: Discovered remote 'Alex's iPhone' (id 7398AA3C-8A13-4A45-97D4-75E2D86077BC) at 10.0.1.13:63827, paircode 17B38C13569A934D
remote: Invalid Remote pairing file /home/pi/Music/pair.remote: device name too long or missing pin
remote: Empty Remote pairing file /home/pi/Music/pair.remote
Code: Select all
forked-daap doesn't appear to be finding /home/pi/Music/pair.remote...
Support of AppleMuic (MusicKit) would be great (similar to Spotify). Since MusicKit has access to the the music uploaded into the iCloud Music Lib, network shares might not be needed anymore.ejurgensen wrote:No, I haven't tried it. Right now forked-daapd doesn't really have any interaction with iOS, so not sure what you are thinking of? Airplay2 could be interesting on the speaker side, but I haven't looked into that either.
Users browsing this forum: No registered users and 9 guests