Can't seem to play music without using the shuffle playlist button.

[ghost]

Directly clicking on music to play it doesn't seem to work.
Already ran Mopidy with the -v option, but it never gives any error messages.
Is this a current known bug? Or should i somehow provide more info?

EDIT: I noticed almost the same behaviour within other Mopidy webclients.

Using a Raspberry Pi 2 with latest Rasbian OS.
Tested on a iPhone 6 Safari/Chrome and on a Mac Safari/Chrome.

P.S I love the design!

[dirkgroenen]

Can you provide a bit more information on what happens with the client? Does it throw errors in the browser's console (Developer tools)?

I have seen this problem a few times at the office. Every time it happened it showed 'No connection' in the player. Does this also happen when you try to start the songs?

[ghost]

Yes it throws errors in the developer console. It does say 'No connection' when selecting only one song. When pressing 'Shuffle Playlist', it all works fine.

[dirkgroenen]

Are you using Mopidy 1.0.0? If so than Mopidy isn't compatible at the moment. I hope to release version 1.4.0, which is compatible with 1.0.0, today.

[ghost]

Ahh, yes I use Mopidy version 1.0.0. Do you recommend to downgrade mopidy for now? Or wait till next version? If yes, what Mopidy version is officially supported?

[dirkgroenen]

I've finished the last issues and are currently testing 1.4.0. If everything works it should be online somewhere in the next hour(s).

At the moment 0.19 is the last official supported Mopidy.

[ghost]

Okay, so it isn't worth it downgrading to 0.19 now. I'll wait patiently!
Thank you! / Enorm bedankt ;)

[dirkgroenen]

I have just released 1.4.1 and uploaded it. This should fix your problems. ;)

[ghost]

Unfortunately I ran into a similar error. Now it sometimes works, but when I sometimes select a song (double click, is that wanted behavior?) it won't play it.

EDIT: It seems to happen after i visited the 'SONGS' page, with as mentioned as a warning a lot of songs.
When selecting one of them, the raspberry pi doesn't seem able to comprehend this and this results in a frozen state for mopify until I refresh the browser. Then it gives an error, mentioned in the screenshot below:

P.S Also the volume selector seems to be unresponsive most of the time, only after adjusting the volume level several times it will change the real volume. Maybe I should add this as a separate issue?

[dirkgroenen]

Hmm that sucks. I will further invest the problem, but tonight we have to drink some beers and celebrate Easter Day ;)

[ghost]

Looking forward to it! Cheers!

[dirkgroenen]

Oh btw, can you enable debug mode in your config file and repost the error when it occurs? This will load the unminified version of Mopify which makes it a bit easier for me to identify the location of the problem.

You can enable it by adding the following line(s) in your config file:

[mopify]
enable = true
debug = true     # this line can be added as of 1.4.1

[dirkgroenen]

I think I've already found the problem causing these errors. I've changed the code in the development branch and will merge it somewhere in the next few days.

[ghost]

Again I'll wait patiently!
Thank you!

[dirkgroenen]

Just releases 1.4.2 which should fix this.

[ghost]

It seems like it is fixed! Thanks!

[dirkgroenen]

Great!