[RELEASE] Grooveshark (Script) Music Addon

macf1an Wrote:maybe you could report back what I mentioned above?

I unpacked the zip for the fix and it worked and played several songs and when restating the grooveshark started and then when selecting a song it started spinning and then froze up and would not play the song.
any suggestion other than the one above.Using xbmc RC2

OK guys, that's what I did.

1 - Installed the script through repository. Run it -> doesn't work
2 - Deleted plugin folder ( script.audio.grooveshark )
3 - Unrar'd the patched one and renamed it as the original one ( script.audio.grooveshark-for-xbmc -> script.audio.grooveshark )

I didn't try to extract and copy the patched one only without installing the repository one at first, though I think it should works anyway.

macf1an, I don't know who wrote the patch, he didn't even sign his post, so I can't report back, sorry.

PS using RC2 on OSX

Not to blame any recent suggestion since I'm not sure exactly what change caused this, just a friendly warning; my WAN ip address was banned by Grooveshark somehow while trying to get this addon working.

This was pretty obvious since both http://listen.grooveshark.com and http://html5.grooveshark.com didn't work through any browser/device connected to my ISP's WAN ip (only that «Error playing song» message) - but worked ok using a 3G connection... Luckily I actually have more than one external ip included from my ISP so no waiting for any dhcp lease to expire here.

Agin Wrote:Not to blame any recent suggestion since I'm not sure exactly what change caused this, just a friendly warning; my WAN ip address was banned by Grooveshark somehow while trying to get this addon working.

This was pretty obvious since both http://listen.grooveshark.com and http://html5.grooveshark.com didn't work through any browser/device connected to my ISP's WAN ip (only that «Error playing song» message) - but worked ok using a 3G connection... Luckily I actually have more than one external ip included from my ISP so no waiting for any dhcp lease to expire here.

I fianally installed correctly from post above then released/renewed my Ip from command promp and all is running swell>
thanks for the assistance.

I copied the contents from the patched folder to the script.audio.grooveshark folder overwriting all files and now I dont have the id failure problem.

use this one

http://hub.gosub.dk/addons/script.audio....-fixed.zip


dont forget to delete everything with groove in the name in

../addons/

and

..userdata/addon_data

they acutally don't have to delete anything I made the zip so it overwrites the old one

macf1an Wrote:they acutally don't have to delete anything I made the zip so it overwrites the old one

Oddly, I tried to install it directly from .zip hub.gosub.dk and it didn't take, had to install it manually to get it to work. Works great, thanks.

Agin Wrote:Not to blame any recent suggestion since I'm not sure exactly what change caused this, just a friendly warning; my WAN ip address was banned by Grooveshark somehow while trying to get this addon working.

This was pretty obvious since both http://listen.grooveshark.com and http://html5.grooveshark.com didn't work through any browser/device connected to my ISP's WAN ip (only that «Error playing song» message) - but worked ok using a 3G connection... Luckily I actually have more than one external ip included from my ISP so no waiting for any dhcp lease to expire here.

Sadly same here. The fix works great if I play few songs but stops working if I want to listen more than a certain number of tracks. IP is somehow banned for a short time and I cannot stream anything neither by plugin nor on their website.
I saw in a thread from the Mediaportal's Rockstar plugin forum, that they had the same problem with their 2.1.3 version and they fixed the problem with 2.1.4 version.
Can someone with some programming skill take a look at this thread?

john.doe Wrote:Oddly, I tried to install it directly from .zip hub.gosub.dk and it didn't take, had to install it manually to get it to work. Works great, thanks.

they have timeouts sometimes that cause "wrong structure" error