tsquillario / Jamstash

HTML5 Music Streamer for Subsonic
http://jamstash.com
273 stars 87 forks source link

Cannot play next song #36

Closed tpereira closed 12 years ago

tpereira commented 12 years ago

Hi,

I am having an issue in playing the next song from MiniSub, infact I cannot play any other song after I have played the first song. I have to refresh my firefox page to start another song. I dont see any error in the subsonic logs. I have been running my subsonic server on my Raspberry Pi for quite sometime now using the Raspbian distro. Its works fine on the standard subsonic page or when I play from the iSub application on my ipod touch. Only the MiniSub is having having problems.

I am running MiniSub 2.0.5 and its installed in /var/subsonic/jetty/3105/webapp/mini/. Access the MiniSub in Firefox 15.0.1 on Windows XP. Subsonic server is 4.7 (build 3105).

Cheers!

tsquillario commented 12 years ago

Check the "Debug Mode" in Settings. You can also install the Firebug addon for Firefox then hit F12 to bring it up. You will see any errors and the debug logs in the Console.

tpereira commented 12 years ago

I can see below, when I press the 'next' song button -

http://XXXXXX.subsonic.org/rest/getMusicDirectory.view?u=admin&p=enc:4170706c65313233&v=1.8.0&c=MyMini&f=jsonp&id=646

player.js (line 4)

SM HTML5 STATUS

player.js (line 58)

usingFlash: true

player.js (line 60)

m4a: false

player.js (line 60)

aac: false

player.js (line 60)

audio/ogg; codecs=vorbis: true

player.js (line 60)

audio/wav; codecs="1": true

player.js (line 60)

mp3: false

player.js (line 60)

audio/mp3: false

player.js (line 60)

mp4: false

player.js (line 60)

audio/mp4: false

player.js (line 60)

audio/m4a: false

player.js (line 60)

audio/aac: false

player.js (line 60)

ogg: true

player.js (line 60)

audio/ogg: true

player.js (line 60)

wav: true

player.js (line 60)

audio/wav: true

player.js (line 60)

canPlayType: function a(a) { var b, e, f = !1; if (!d || "function" !== typeof d.canPlayType) { return !1; } if (a instanceof Array) { for (b = 0, e = a.length; b < e && !f; b++) { if (c.html5[a[b]] || d.canPlayType(a[b]).match(c.html5Test)) { f = !0, c.html5[a[b]] = !0, c.flash[a[b]] = !(!c.preferFlash || !u || !a[b].match(Ua)); } } return f; } a = d && "function" === typeof d.canPlayType ? d.canPlayType(a) : !1; return !(!a || !a.match(c.html5Test)); } NowPlaying Delay: 30000

api.js (line 313)

NowPlaying Delay: 30000

api.js (line 313)

ChatMessages Delay: 291929.26025390625

chat.js (line 13)

NowPlaying Delay: 30000

api.js (line 313)

tsquillario commented 12 years ago

Just to make sure we are on the same page. The next song button only works with songs added to the Current Playlist. So you add songs there and when a song ends it switched to the next one automatically.

So if you add a whole album to the Current Playlist, start playing the first song, then click the Next button. Nothing happens? No errors in the Console?

tpereira commented 12 years ago

I wasnt adding the songs to the playlist specifically before, but I could see the whole album getting added there automatically. Now I have specifically added the album to the current playlist and still getting the same issue. You can see below the current song getting over, but it just gets stuck after that. Even the same song wont play again.

position:235964 duration:236434

player.js (line 75)

position:236121 duration:236434

player.js (line 75)

position:236225 duration:236434

player.js (line 75)

position:236356 duration:236434

player.js (line 75)

position:236434 duration:236434

player.js (line 75)

http://XXXXXX.subsonic.org/rest/getMusicDirectory.view?u=admin&p=enc:4170706c65313233&v=1.8.0&c=MyMini&f=jsonp&id=658

player.js (line 4)

SM HTML5 STATUS ...... ....... (same log contents as sent before)

tsquillario commented 12 years ago

Not sure what is going on. From that you can see that you are using the Flash player not HTML5. You might want to try using Chrome. Also, it could be related to the xxxx.subsonic.org hosting.

tpereira commented 12 years ago

Many thanks for getting back though. It works perfectly in chrome (though I had to use http instead of https). With https it was compaining that the https page was internally trying to access http link and hence getting blocked. Some chrome feature I guess. Anyway works like a charm after disabling it.