2013-01-09, 06:43
Hi guys - I see a few people talking about Pandora stopping. I have a similar issue, but I'm not sure its exactly the same. With mine, sometimes it just stops at the end of a track (although I think that may be due to me re-entering the add-in, see later), other times, it actually exits the add-in back to the music add-in's menu - the stream keeps playing until the end of that song, then stops. I can re-enter the add-in, and it sees the stream playing, but that is from a different session, so does not continue to the next song, and you can't use thumbs up/down.
Other times it plays several songs before stopping, about 30% of the time, it starts the first song, then immediately exits the add-in, but streams the song until its end. So for me, it doesn't seem like the screen saver is implicated in any way (or at least it definitely isn't for a minimum of 30% of the time!)
Caught this in the log just now - I wasn't watching the screen, but I think it played several tracks normally, then the add-in exited to the add-in's menu and the current song played out, then stopped:
The "Error: ClearBlock" would seem to be interesting, if that assumption is correct, as that happened immediately after the last track started playing. Then later (presumably at the end of that track) the message about no data packet being available is logged, presumably because the stream has long been closed at that point and there isn't a new track to play.
Does this mean anything to anyone?
XBMCbuntu 11.0 / script 1.2.10-git
EDIT: OK, I completely removed the script (deleted the script folder, and the add-in data folder) then reinstalled it from the .zip file (same version 1.2.10-git), the intermittent exiting may have gone away, that seemed different from the issues others are facing, except one person a few pages back that reported the same error (ClearBlock). That error now seems gone for me, I'm pretty sure that was what was causing the random exits for me.
I am now up to my 5th song and it hasn't stopped yet, so perhaps the 'stopping' issue that others are discussing here isn't impacting me. The only thing I configured differently after re-installing the add-in was going from mp3-hifi to mp3.
As for the 4 songs, that seems pretty straightforward - you can clearly see in the log file, when you first start a radio station, the script is actually queuing 4 songs - and you can actually see the names of the songs. Then it accesses a long URL which is clearly the CDN URL for the first song in that list of 4. In the log, when the 4th songs starts playing, you can see it requesting another set of 4 songs to add to the queue, which then start playing when that 4th song has finished. So its doing it in chunks of 4 songs.
You should monitor your log carefully when you start a station playing, check for these 4 songs at the beginning, then see if it logs anything about not being able to get 4 more songs, as soon as the 4th song of the initial playlist starts playing. It should definitely log something. If there is a failure at that point, then the error/warning should be directly related to why you are only able to play the first 4 songs before the 'stopping' issue occurs.
Other times it plays several songs before stopping, about 30% of the time, it starts the first song, then immediately exits the add-in, but streams the song until its end. So for me, it doesn't seem like the screen saver is implicated in any way (or at least it definitely isn't for a minimum of 30% of the time!)
Caught this in the log just now - I wasn't watching the screen, but I think it played several tracks normally, then the add-in exited to the add-in's menu and the current song played out, then stopped:
Code:
15:29:28 T:2891971440 NOTICE: PANDORA: onPlayBackStarted: http://t2-2.p-cdn.com
/access/5213302059239938114.mp4?version=4&lid=242550997&token=%2BEAtMf6cdbo8Oz4U
WHkI0fOiTEUsEaXZpLOOrI3yTx7ioxrSOJdFDHra2Q8ejxYNUUZCyN1ZUtmZndKhPhYp2hDR2xnvkSaA
KdqXxwtpMAC8GSCZ2QgyHWmqt3mQ4j25AD6keSmG%2FsYWj04smIDMAC89PoWiYiLdeTGUA2E4xwztYv
Yc5UAX9ro0rPkcNVvdOPQkemCJIHH3CF2pKO1XD6WtO%2FqhvOGvStUkTH6CRuUuJ3lznBHnTH9%2FFlQN3V8Aw%2BsgFO2UnCkQxN29KA4MwHWS5rEGYak%2BR5Fbbwytcj3ZhKm6WFm%2BS027iDdURi82OO1CCyKVtorSitpFN%2F%2BPbwTgCGyaqP%2BD
15:29:28 T:7674160 ERROR: ClearBlock: Trying to clear non existent block /home/colin/.xbmc/addons/script.xbmc.pandora
15:33:15 T:3032480624 WARNING: CDVDMessageQueue(audio)::Get - asked for new data packet, with nothing available
15:33:15 T:2744720240 NOTICE: CDVDPlayer::OnExit()
15:33:15 T:2744720240 NOTICE: DVDPlayer: eof, waiting for queues to empty
15:33:15 T:2744720240 NOTICE: DVDPlayer: closing audio stream
15:33:15 T:2744720240 NOTICE: Closing audio stream
15:33:15 T:2744720240 NOTICE: CDVDMessageQueue(audio)::WaitUntilEmpty
15:33:15 T:2744720240 NOTICE: Waiting for audio thread to exit
15:33:15 T:3032480624 NOTICE: thread end: CDVDPlayerAudio::OnExit()The "Error: ClearBlock" would seem to be interesting, if that assumption is correct, as that happened immediately after the last track started playing. Then later (presumably at the end of that track) the message about no data packet being available is logged, presumably because the stream has long been closed at that point and there isn't a new track to play.
Does this mean anything to anyone?
XBMCbuntu 11.0 / script 1.2.10-git
EDIT: OK, I completely removed the script (deleted the script folder, and the add-in data folder) then reinstalled it from the .zip file (same version 1.2.10-git), the intermittent exiting may have gone away, that seemed different from the issues others are facing, except one person a few pages back that reported the same error (ClearBlock). That error now seems gone for me, I'm pretty sure that was what was causing the random exits for me.
I am now up to my 5th song and it hasn't stopped yet, so perhaps the 'stopping' issue that others are discussing here isn't impacting me. The only thing I configured differently after re-installing the add-in was going from mp3-hifi to mp3.
As for the 4 songs, that seems pretty straightforward - you can clearly see in the log file, when you first start a radio station, the script is actually queuing 4 songs - and you can actually see the names of the songs. Then it accesses a long URL which is clearly the CDN URL for the first song in that list of 4. In the log, when the 4th songs starts playing, you can see it requesting another set of 4 songs to add to the queue, which then start playing when that 4th song has finished. So its doing it in chunks of 4 songs.
You should monitor your log carefully when you start a station playing, check for these 4 songs at the beginning, then see if it logs anything about not being able to get 4 more songs, as soon as the 4th song of the initial playlist starts playing. It should definitely log something. If there is a failure at that point, then the error/warning should be directly related to why you are only able to play the first 4 songs before the 'stopping' issue occurs.
