Thank you for your post, It helped get another working version up and running.

I would also like to let you know for the streamkey retrival the client string differers, Here is a valid JSON request that I grabbed from the real client:

This differs from the htmlshark requests which are as follows:

As far as fixing unicode I simply made sure that I no longer converted to any ascii strings in the json requests.

I plan to push a update with a couple fixes and a proper download progress and playback bar. Sorry I haven't been working on this program as much as you all would like

For those who can't wait for the update in extras-devel I've attached a working build as of Jan 4th 2011

Did you use phonon with your windows version? I had issues getting phonon to properly adjust the buffer length during streaming playback on the windows platform

Yes I use Phonon with Qt and since there are bugs with a variable bitrate i have disabled the playback. (the download feature is the best one )


if anyone wants to try a windows client: (beta state) www.scharmentke.org/QGroovy.zip

Great, groove is now working again, and very useful to have a progress bar on downloads. I can now see that seeking back through played items requires re-download - which explains what I previously thought was the app becoming non-responsive (I had no idea that was how it worked, and when I skipped back and got silence I assumed it had hung!).

Hope you get more time soon to add more functionality, thanks again meantime :-)

Awesome program. Waiting update =)

in case this helps anyone else work out how Groove handles playlists, I've done some testing with the new version upliaded by dodblank earlier today, and my empirical conclusions are as follows:

a. you can add as many items as you wish to the playlist and they will download sequentially, even if many are added quickly whils others are still downloading

b. once a track "x" has downloaded and while player is still playing earlier tracks in the playlist, you can skip forward instantly to track "x" via multiple ">" presses

c. to skip back to track "x" after you have moved past it to track"y" or beyond) requires track "x" to be re-downloaded, even if you have only played a small part of the track (by skipping forward past it). Playback will still commence during download in this scenario however, so the delay is minimal.

d. skipping back and forward quickly so that each track needs to be re-downloaded, and without giving time for re-d/l to complete, will eventually cause the player to become silent, while showing a download in progress, and to stay silent once the d/l completes. Audio can be restarted by pressing ">" or "<" thereafter, but I think this is a bug/limitation of the client at present.

e. once the last song in the playlist has played to conclusion, you can no longer skip back/forward at all - you have to add more songs before the player will restart audio. I don't know if that is intentional or not (I'd have assumed that having got to the end of my playlist, I could still skip back into it if desired?)

This is (I suspect) identical to how the previous version - i.e. the one currently in the repos, which doesn't work with grooveshark any more - used to work, but it was quite hard to "see" it without the download progress bar to make sense of things.

There may have been a couple of bug fixes too in the new version which are making it more stable, but I am certainly finding it way more reliable now I know how I'm *supposed* to use it, and how the api forces the client to work in terms of downloading/skipping.

HTH

what is the command to run the groove attached file to update the older one to it, I forgot the command.

extract the new groove executable from the groove.tar.gz file (I used 7zip from x-terminal: 7z e groove.tar.gz, then 7z e groove.tar).

Then, save the current groove executable:
cd /opt/maemo/usr/bin
mv groove groove.orig

Then copy the newly extracted groove to same folder and ensure it has execute permissions (chmod ugo+x groove)

It should then run from command line or from desktop shortcut as before.

thanks i us openssh it's much more for faster

only if you can remember what to type

I have openssh too, with PK authentication (so no login overhead), but even then I still use the onboard x-term for most small tasks like this one. Personally, I think the n900 keyboard is pretty usable for day to day work at the command prompt.