Another user reported this on my Github. I’m asking what version he’s on so maybe I can reproduce it and see what’s going on…
3.015 rpi4/4 mpd 21.50 tested … same cut off
3.010 rpi4/4 mpd 21.50 tested … same cut off
2.861 rpi2/? mpd 20.18 tested … same cut off
I reported the issue via github today.
I’m on Volumio v. 2.861, no MPD modification, Raspberry pi 2.
Investigating volumio logs, the cut off occurs on a MPD update:
info: ---------------------------- MPD announces state update: player info: ControllerMpd::getState � � info: ControllerMpd::pushState info: CoreCommandRouter::servicePushState info: CoreStateMachine::pushState info: CoreCommandRouter::volumioPushState info: CoreCommandRouter::executeOnPlugin: volumiodiscovery , saveDeviceInfo info: CorePlayQueue::getTrack 0 � � info: CoreStateMachine::syncState stateService stop info: CoreStateMachine::syncState currentStatus play info: CoreCommandRouter::volumioPushState info: CoreCommandRouter::executeOnPlugin: volumiodiscovery , saveDeviceInfo info: CoreStateMachine::stPlaybackTimer info: ------------------------------ 15ms
what is your mpd version? oke mpd 0.21.5 i have on both …
volumio@volumio:~$ mpd -V Music Player Daemon 0.20.18 (128d910-dirty)
I’ve tested using the stock MPD 0.20.18 that came with Volumio and experienced the cut-off as well. Here’s what I get in MPD’s log:
$ cat /var/log/mpd.log Mar 09 13:47 : ffmpeg/aac: Input buffer exhausted before END element found Mar 09 13:47 : ffmpeg: decoding failed, frame skipped: Invalid data found when processing input Mar 09 13:47 : ffmpeg/mov,mp4,m4a,3gp,3g2,mj2: stream 0, offset 0x38c560: partial file Mar 09 13:47 : exception: CURL failed: GnuTLS recv error (-9): A TLS packet with unexpected length was received. Mar 09 13:47 : player: played "<Stream URL>"
(I hid the stream URL because I don’t want to expose it here)
To put it simply, the cut-off was due to the connection closing unexpectedly due to a bug in a library used by MPD.
Could you guys confirm that you’re seeing this too in your MPD’s log?
The custom MPD 0.21.16, which I have been using, works because it was compiled with libraries slightly more recent than those provided by Buster (and many versions ahead of those in Volumio 2.x). But I would like to see this plugin working without the need to update MPD. A simple change to the code should do the trick but let me test it first for an hour or so.
testing on 3.015 don’t get a error : cat /var/log/mpd.log
volumio@volumio:~$ cat /var/log/mpd.log
Mar 09 14:20 : zeroconf: No global port, disabling zeroconf
Mar 09 14:20 : client:  opened from local
Mar 09 14:20 : exception: No such directory
Mar 09 14:20 : client:  opened from 127.0.0.1:38768
Mar 09 14:20 : client:  opened from 127.0.0.1:38786
Mar 09 14:21 : ffmpeg/aac: Could not update timestamps for skipped samples.
Mar 09 15:48 : client:  closed
Mar 09 15:50 : client:  opened from 127.0.0.1:39002
now test the same on the 3.010
volumio@music:~$ cat /var/log/mpd.log
Mar 09 14:18 : zeroconf: No global port, disabling zeroconf
Mar 09 14:18 : client:  opened from local
Mar 09 14:18 : exception: No such directory
Mar 09 14:18 : client:  opened from 127.0.0.1:54936
Mar 09 14:18 : ffmpeg/aac: Could not update timestamps for skipped samples.
Mar 09 14:19 : client:  closed
Could you update the plugin (follow instructions at the Github link) and try again?
Please report back if this improves anything. Thanks.
3.015 looking good past the 11min mark and still have sound… after update
gonna let it run for a while brb… sleep tide don’t let the bed bugs bite …
OK, thanks. Going to sleep now. Will check back tomorrow. Goodnight!
I still have the issue after update. mpd log shows this curl/GnuTLS error on recv. Do you want me to update to newer volumio version?
run the update section of the plugin … and after all i rebooted …
i’m testing 2 in the same time now… both are already past the 60min and 85 min mark
and still playing…
volumio:~$ cd ~/mixcloud-plugin/volumio-mixcloud/ volumio:~/mixcloud-plugin/volumio-mixcloud$ git pull ... volumio:~/mixcloud-plugin/volumio-mixcloud$ volumio plugin update This command will update the plugin on your device ... Progress: 100 Status :Successfully updated plugin // If the process appears to hang at this point, just press Ctrl-C to return to the terminal. volumio:~/mixcloud-plugin/volumio-mixcloud$ sudo systemctl restart volumio
after this reboot
3.010 2x tested Successfully 3,0 hrs test 2 different songs full
3.015 2x tested Successfully 2,5 hrs test 2 different songs full
it seems that Marcin’s
2.861 rpi2/? mpd 20.18 tested … still got the same cut off ( i didn’t test this )
It should not be necessary to update to a newer Volumio version. Did you encounter any error message when updating the plugin (
git pull +
volumio plugin update) and did you restart Volumio or reboot the device? Would you mind showing the console output when you update the plugin?
I did not reboot volumio yesterday after updating the plugin.
After suggestions in this thread I did it today morning and it seems to be working. 30+ minutes into a mixcloud show right now without issues.
I’ll test it throughout the day and report if I encounter any errors. For now I believe it is resolved.
OK, I’ll close the Github issue tonight if I do not receive further error reports on this.
and again great work patrick
I just installed the Mixcloud plugin on the latest Buster Beta for RPi… pretty straight forward, well done!
I am listening right now to one of my favorite mix, no issues to report so far!
Is it possible to add, login account in the future?
No, to do that would require an API key from Mixcloud. I don’t think Mixcloud will give one for this plugin because their T&C prohibits direct streaming (you need to use a widget they provide but this can’t be done in Volumio).