next »

[raina]

OMG, "Explorer bug", is this what made my system(s) so wonderfully unresponsive not too long ago? Great to find out there's a reason for it after all. Looking forward to that update.

[PollieXmas]

First of all thanks for taking the time to develop this plug-in!

I'm having trouble to get the plugin to work though.

I need to use a proxy at home which does not seem to work. (My proxy does not require a username and password.)

Then at work I do not need a proxy, but it also does not seem to work even after I have removed the proxy. (This is working now, but still causes Thunderbird and Firefox to crash when XMScrobbler is "on".)

I've attached the log file for you to have a look at.

Would it be possible for the plugin to try and use the browser setting w.r.t. proxy so you do not have to keep changing it in the player too?

Finally, I've noticed that my firefox started crashing after I started to use your plugin. (I'm using the foxy tunes extention in Firefox and Thunderbird.)

Thanks
Paul

[yagood]

I've just finished version 0.4. I was considering testing it for a couple of days locally on my PC, but I think I'll give it a shot and release it as is. Please read release notes (in the first post of this thread) very carefully.

"Include/exclude directories" feature will be available in the next version. I'll review my to-do list and last pages of this topic too in case I missed something.

If you see "Not all request variables are set" message in the log file and xmp-scrobbler doesn't want to submit songs anymore, you have to delete xmp-scrobbler.cache file. It turned out that fixing this cache bug is not such simple thing, but I'll do it as soon as possible and it should be in the next version.

[lingenfr]

I am still seeing similar behavior that once it pukes with a "Track is too short" it goes to la-la land and doesn't try again. I loaded the new version and followed the instructions. I played a track off my harddrive and it submitted fine. Then I opened my lastfmproxy and launched a radio station. It puked as you see at 21:28. I let it roll for awhile then skipped that track and let the next track play for awhile. It did nothing until I closed XMP at 21:44.

2006-06-15 21:27:41   [DEBUG] DSP_SetFormat( 1, 0, 0 )
2006-06-15 21:27:41   [DEBUG] DSP_StopTrack
2006-06-15 21:27:41   [DEBUG] XMP_KillTimer
2006-06-15 21:27:41   [DEBUG] DSP_NewTrack (CLOSE)
2006-06-15 21:27:42   [DEBUG] DSP_Free()
2006-06-15 21:27:50   [DEBUG] DSP_New()
2006-06-15 21:28:14   [DEBUG] DSP_NewTrack (OPEN)
2006-06-15 21:28:14   [LIBSCROBBLER] ...
2006-06-15 21:28:14   [DEBUG] DSP_SetFormat( 1, 44100, 2 )
2006-06-15 21:28:14   [DEBUG] XMP_SetTimer( 0 )
2006-06-15 21:28:14   [INFO] Track is too short to be submitted (must be at least 30 seconds long)
2006-06-15 21:28:15   [LIBSCROBBLER] Handshaking: Client up to date.
2006-06-15 21:28:15   [LIBSCROBBLER] Submit interval set to 1 second(s).
2006-06-15 21:28:15   [LIBSCROBBLER] Handshake successful.
2006-06-15 21:44:00   [DEBUG] DSP_SetFormat( 1, 0, 0 )
2006-06-15 21:44:00   [DEBUG] DSP_StopTrack
2006-06-15 21:44:00   [DEBUG] XMP_KillTimer
2006-06-15 21:44:00   [DEBUG] DSP_NewTrack (CLOSE)
2006-06-15 21:44:01   [DEBUG] DSP_Free()

Thanks for your continued efforts. Your plug-in is still more reliable than last.fm's site

[yagood]

I am still seeing similar behavior that once it pukes with a "Track is too short" it goes to la-la land and doesn't try again. I loaded the new version and followed the instructions. I played a track off my harddrive and it submitted fine. Then I opened my lastfmproxy and launched a radio station. It puked as you see at 21:28. I let it roll for awhile then skipped that track and let the next track play for awhile. It did nothing until I closed XMP at 21:44.

Well, it makes sense. I've just tested LastFMProxy and it's just like I thought. XMPlay obviously sees LastFMProxy input as a stream so basically it's a single track with no length. Xmp-scrobbler tries to get track length at the start and it gets 0, so it refuses to submit it because "track is too short". What is more I think it's not xmp-scrobbler's job to submit Last.fm radio tracks to profile, I mean, there's "Record to profile" option in the Last.fm Player (and in LastFMProxy too) so it should take care of everything I guess... I didn't investigate how exactly Last.fm Player works but I imagine that track submitting is done on server side not on player side in this case - server knows what it's streaming and knows when to record it to user's profile. So correct me if I'm wrong, but I think Last.fm radio should work despite of xmp-scrobbler not wanting to submit anything.

In general I wrote about submitting streams in xmp-scrobbler couple of days (maybe weeks ) ago - xmp-scrobbler has no clear way to find out needed information about stream - XMPlay doesn't notify xmp-scrobbler when stream plays another song. I could do some dirty things and try to find out it on my own in xmp-scrobbler, but there's Audioscrobbler protocol specification too, which says that streams of any kind should not be submitted.

[yagood]

OK, so it's still a little buggy, after some time you may get "[DEBUG] XMP_SubmitProc -- XMP_GetChannelData failed, track not submitted!" message in the log file and xmp-scrobbler will not submit tracks anymore and you'll have to restart XMPlay. I'm investigating the cause right now, I'll release new version as soon as I fix it. Sorry for this, but hey, it's still experimental, right?

Eeeh, Explorer hangs are still occurring in some situations, this is not good... 

[Aux]

XMPlay doesn't notify xmp-scrobbler when stream plays another song.

Maybe You should talk to Ian a bit? Maybe he can make a fix to XMPlay or something? Anyway thanks for 0.4. I'll download it now!

P.S. Maybe You can share your source - I would like to take part in bug searching.

[yagood]

XMPlay doesn't notify xmp-scrobbler when stream plays another song.

Maybe You should talk to Ian a bit? Maybe he can make a fix to XMPlay or something? Anyway thanks for 0.4. I'll download it now!

There's nothing to fix I guess, this behavior is by design. Besides, even if Ian would decide to "fix" this, there still is not possibility to know the length of the track in stream. Stream is a single track with unspecified length, XMPlay can't break it into multiple tracks and say to xmp-scrobbler "OK, now it's track X of length 3:12, deal with it".

P.S. Maybe You can share your source - I would like to take part in bug searching.

Once again I think I've fixed it, at least it works for me, I'll test it more and probably release something like 0.4b today. About source code - I'm considering releasing it too, but first I would like to clean it up a little

[lingenfr]

What is more I think it's not xmp-scrobbler's job to submit Last.fm radio tracks to profile

Ouch. OK.

I could do some dirty things and try to find out it on my own in xmp-scrobbler, but there's Audioscrobbler protocol specification too, which says that streams of any kind should not be submitted.

Maybe, I don't get it, but if I was someone who colored inside the lines, I wouldn't be using xmplay in the first place. I would put my nose in the arse of the lemming in front of me, use WMP and run off the cliff.

I really appreciate what you are doing and I am glad to provide feedback to the degree it is useful to you in improving the plug-in. If we are now at some kind of impasse on a point of principle, I guess I am confused. Previously, I thought the plug-in was submitting tracks from lastfmproxy. I have the record to profile box checked, so maybe it was actually lastfmproxy. Regardless, I am interested in submitting the songs from the different streaming stations I listen to and will be glad to test and provide feedback to that end.If not, OK. Once again, I appreciate your contribution to making xmp more useful.

[yagood]

I could do some dirty things and try to find out it on my own in xmp-scrobbler, but there's Audioscrobbler protocol specification too, which says that streams of any kind should not be submitted.

Maybe, I don't get it, but if I was someone who colored inside the lines, I wouldn't be using xmplay in the first place. I would put my nose in the arse of the lemming in front of me, use WMP and run off the cliff.

I understand your point, but they wrote this specs for a reason - they don't want garbage in their databases. And don't get me wrong, I'm not saying that streaming radio stations play garbage Point is that with streams, I don't have enough data in xmp-scrobbler to handle it properly. Yes, I have some ideas, but I'm still unsure if it would make things reliable enough to consider submitting to Last.fm...

I really appreciate what you are doing and I am glad to provide feedback to the degree it is useful to you in improving the plug-in. If we are now at some kind of impasse on a point of principle, I guess I am confused. Previously, I thought the plug-in was submitting tracks from lastfmproxy. I have the record to profile box checked, so maybe it was actually lastfmproxy. Regardless, I am interested in submitting the songs from the different streaming stations I listen to and will be glad to test and provide feedback to that end.If not, OK. Once again, I appreciate your contribution to making xmp more useful.

There is no way that xmp-scrobbler actually submitted something from LastFMProxy. I wrote about it in my post above - it's a pure stream. Last.fm Radio is handled by Last.fm streaming server. About other streaming stations - could you give me some stream examples you use? And again, it's not like there's a war in my head and I'm not sleeping at nights still wondering whether I should support streams I would love to do this (I hope that Last.fm folks are not reading this ) if things were the same as with normal tracks. For now, I would like to test some streams to see what options do we have. And thank you for your contribution, I really enjoy it when people care!

[yagood]

Version 0.4b is available. Please attach log file to problem reports.

[PollieXmas]

Hi Yagood

Version 0.4b seems to have done the trick.

I can now submit from work and home and it no longer makes my FF and TB crash.

Well done and thanks again.

Cheers
Paul

[yagood]

Version 0.4b seems to have done the trick.

I can now submit from work and home and it no longer makes my FF and TB crash.

Well done and thanks again.

Good to know, thanks!

[nemo]

have you thought about adding a button to the scrobbler options to either clear or delete the cache file? It would be useful to me because it seems like I have to periodically delete the cache file for submissions to work.

[yagood]

have you thought about adding a button to the scrobbler options to either clear or delete the cache file? It would be useful to me because it seems like I have to periodically delete the cache file for submissions to work.

I would rather spend time on fixing this cache bug than adding such button This will be my priority now, because it is indeed very annoying...

[Rah'Dick]

I've put version 0.4b up on the support site.

I know this is a bit off-topic but I just saw a comment on the Support site that was a bit like a phishing try. Have a look here, it's the long comment on the bottom.

[Buda]

Well.. i have found a bug in the last version of the plugin. I heard about 10 or 13 complete songs, but when i go into last.fm it says that only i have played the songs for an average between 40-50 seconds.

Thanks.

If you want i upload the log here: http://jairmoreno.googlepages.com/Log.txt

Thanks

[yagood]

Well.. i have found a bug in the last version of the plugin. I heard about 10 or 13 complete songs, but when i go into last.fm it says that only i have played the songs for an average between 40-50 seconds.

I'm not sure that I understand. Your log looks fine, all songs between 16:43 and 20:10 were submitted successfully. Maybe there's some bug, but I don't know what exactly do you mean by "played the songs for an average between 40-50 seconds" - could you be more specific? Also note that sometimes there's a delay before tracks appear on your profile page after being submitted - that's Last.fm issue. You could try observing "tracks played" counter on your profile page, but that's not too reliable either recently. Please write more about problem.

[Dotpitch]

When using wav-writer or another encoder, xmp-scrobbler obviously sends the info to Last.fm. Is there any way to avoid this behavoir? (And I mean other than manually removing the plugin from the DSP-section ). Or is there no way for the plugin to determine the output-device? In the latter case, perhaps a request to Ian ?

BTW, thanks for developing this plugin! It's working very good over here .

[yagood]

When using wav-writer or another encoder, xmp-scrobbler obviously sends the info to Last.fm. Is there any way to avoid this behavoir? (And I mean other than manually removing the plugin from the DSP-section ). Or is there no way for the plugin to determine the output-device? In the latter case, perhaps a request to Ian ?

Hm, I don't see a simple way of determining output device in xmp-scrobbler. But instead of removing the plugin, you can just disable it - it'll prevent any data from being sent to Last.fm.

BTW, thanks for developing this plugin! It's working very good over here .

Thanks. More updates to come - I've already finished cache manager module, which will hopefully fix any issues with cached submissions, I'm now testing it, so far works OK and it'll be included in 0.5. Next thing on to-do list is "include/exclude directories" feature. Xmp-scrobbler is a simple piece of software, it has a simple task to accomplish, but if anyone would want to see any more features - I'm opened to suggestions.