ANNOUNCEMENT: Pi Musicbox v0.7.0RC4

Are you using a wired or wireless connection? Can you look in /var/log/mopidy/mopidy.log for any errors, or maybe something in /var/log/dmesg ?

What audio output are you using? Analogue? Hifiberry DAC? HDMI?

The files are in /usr/local/lib/python2.7/dist-packages/mopidy_musicbox_webclient/static/

I think there was a change related to scrolling in the latest webclient release but it looks like it was something else. So no, be great if someone would give it (or any of the other issues) some love.

hi, my Musicbox is connected through WIFI (WPA2)

I found one (1) error in the dmesg file and it’s related to the wifi driver:

3.622586] usb 1-1.5: New USB device found, idVendor=0bda, idProduct=8176
[ 3.631938] usb 1-1.5: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 3.643574] usb 1-1.5: Product: 802.11nnWLAN Adapter
[ 3.650794] usb 1-1.5: Manufacturer: \x03ealtek
[ 3.650804] usb 1-1.5: SerialNumber: 00e04c000001
[ 4.080135] rtl8192cu: Chip version 0x10
[ 4.232003] rtl8192cu: Board Type 0
[ 4.237928] rtl_usb: rx_max_size 15360, rx_urb_num 8, in_ep 1
[ 4.246065] rtl8192cu: Loading firmware rtlwifi/rtl8192cufw_TMSC.bin
[ 4.278712] ieee80211 phy0: Selected rate control algorithm ‘rtl_rc’
[ 4.280493] usbcore: registered new interface driver rtl8192cu
[ 4.338731] Error: Driver ‘rtl8192cu’ is already registered, aborting…

Warnings in the [mopidy.log]
(https://docs.google.com/document/d/1LTovelbDpTcsgBj9n3crwuqTuc4KC9Vtpwo6ps9KA24/edit?usp=sharing)

I have cleaned the music library (deleted the Sony .sfk files and one wav ) which minimized the log and the remaining warnings are now

2017-04-05 14:58:52,114 - WARNING 404 GET /favicon.ico (192.168.1.252) 15.47ms
2017-04-05 15:17:56,420 - WARNING Element doesn’t implement handling of this stream. Please file a bug.
2017-04-05 15:23:21,252 - WARNING Element doesn’t implement handling of this stream. Please file a bug.
2017-04-05 15:28:47,667 - WARNING 404 GET /favicon.ico (192.168.1.227) 16.01ms
2017-04-05 15:29:25,552 - WARNING Element doesn’t implement handling of this stream. Please file a bug.
2017-04-05 15:35:21,230 - WARNING Element doesn’t implement handling of this stream. Please file a bug.
2017-04-05 15:40:13,389 - WARNING Element doesn’t implement handling of this stream. Please file a bug.
2017-04-05 15:44:27,228 - WARNING Element doesn’t implement handling of this stream. Please file a bug.
2017-04-05 15:50:43,360 - WARNING Element doesn’t implement handling of this stream. Please file a bug.
2017-04-05 15:54:01,817 - WARNING Element doesn’t implement handling of this stream. Please file a bug.
2017-04-05 21:06:02,084 - WARNING Element doesn’t implement handling of this stream. Please file a bug.
2017-04-05 21:06:55,083 - WARNING 404 GET /settings/js/mopidy.min.js (192.168.1.249) 15.64ms
2017-04-05 21:06:55,090 - WARNING 404 GET /settings/js/simple.js (192.168.1.249) 3.74ms
2017-04-05 21:06:55,307 - WARNING 404 GET /settings/js/mopidy.min.js (192.168.1.249) 3.97ms
2017-04-05 21:06:55,331 - WARNING 404 GET /settings/js/simple.js (192.168.1.249) 3.84ms
2017-04-05 21:06:55,828 - WARNING 404 GET /favicon.ico (192.168.1.249) 4.27ms
2017-04-05 21:11:26,937 - WARNING Element doesn’t implement handling of this stream. Please file a bug.
2017-04-05 21:17:31,248 - WARNING Element doesn’t implement handling of this stream. Please file a bug.
2017-04-05 21:23:26,935 - WARNING Element doesn’t implement handling of this stream. Please file a bug.
2017-04-05 21:28:19,105 - WARNING Element doesn’t implement handling of this stream. Please file a bug.
2017-04-05 21:32:32,965 - WARNING Element doesn’t implement handling of this stream. Please file a bug.
2017-04-05 21:38:49,091 - WARNING Element doesn’t implement handling of this stream. Please file a

Thanks - I’m away for a few days so will have a look when I get back.

Certainly, someone came already up with this question, but I cannot find it. :slight_smile:

What about plans to integrate the latest stable version of Mopidy which seems to be 2.1.x ?

See also:

Yea, that is still the plan. But not for v0.7. This is an incremental release adding support for new hardware.

Mopidy 2.x, Pyspotify 2.x and Jessie are all still coming in the next major release.

1 Like

That’s awesome. I was just asking in case you want to keep the current release cycle of one release every few years. :wink: Maybe we get more energy into the project with a bunch of people helping with pull requests.

No I don’t want to keep that, I had a busy couple of years.

We would undoubtedly get more done with some people helping. There are issues on GitHub tagged with the v0.7 milestone that once out the way would be a tremendous help.

yesterday, i tried to set up my new raspyberry pi zero w but got errors when i wanted to play a (local) song. after that i didn’t get any response from the webinterface. if you need any other logs, just tell me.
btw, 0.7RC4 works great on my RPi3! (with the same soundcard, a hifi dac)

Absolutely fabulous to see this project active again. Couldn’t be timed better with the recent release of the zero-W, which is the perfect Pi for this.

Very appreciative user.

Looking forward to getting to Jessie. If there is any way for the community to help just let us know.

Hi,

first of all thanks for your efforts to let this project live again (-;.

I want to use my Pi3 to use it with musicbox. I installed the image which has gone straight forward without any issue. I am trying to listen to podcast which does not work.
I use the web interface: Search -> SeachPodcast -> “ard radiofeature” and musicbox find the podcast feed ‘das ARD radiofeature’.
When i want to start one podcast this does not work.
I checked the log file here:
and find the following message: “ERROR Podcast lookup failed for podcast+http://www.ndr.de/info/podcast4292.xml#http://media.ndr.de/download/podcasts/podcast4292/AU-20170316-1542-4700.mp3: object of type ‘generator’ has no len()”

regards
Oliver

This sounds more like an issue with mopidy-podcast than with Music Box - I’ll look into this ASAP.

Turns out the problem was with me trying to play utube tracks. the log file says:

2017-04-16 15:50:09,523 - WARNING Could not find a audio/x-unknown decoder to handle media.
2017-04-16 15:50:09,524 - WARNING There is no codec present that can handle the stream’s type.
2017-04-16 15:50:09,525 - ERROR Your GStreamer installation is missing a plug-in.

Also, when trying to play a podcast, i get:
2017-04-16 15:41:51,644 - ERROR Podcast lookup failed for podcast+https://www.npr.org/rss/podcast.php?id=510298#https://play.podtrac.com/npr-510298/npr.mc.tritondigital.com/NPR_510298/media/anon.npr-mp3/npr/ted/2015/05/20150529_ted_animals.mp3?orgId=1&d=3265&p=510298&story=410046105&t=podcast&e=410046105&ft=pod&f=510298: object of type ‘generator’ has no len()

thanks a lot

Some youtube tracks require a codec that is not available in Raspbian Wheezy, there’s unfortunately nothing I can do about that with v0.7.

That podcast error I am not sure about. @tkem have you ever seen that one?

Indeed:

Sorry it took so long, was busy over the holidays.

This should be fixed with mopidy-podcast v1.1.2; I have to admit, I haven’t managed to have a look at MusicBox v0.7 yet, so I don’t know which version it currently uses…

I thought I had pulled in the latest but it seems I missed it out.

Thanks @aristo, good find.

And @Karl_Sapp, too :wink:

any help regarding my problem would be appreciated :slight_smile:
the original post is some posts above
thanks!