Skip to main content ↑ ↓

Notice

Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
Topic: foo_audioscrobbler 1.4.7 (Read 926658 times) previous topic - next topic
0 Members and 3 Guests are viewing this topic.

foo_audioscrobbler 1.4.7

Reply #325 –
I want to suggest (once again) a cache only mode.  Now that the plugin attempts to reconnect t*2 seconds upon failure it is even more desirable for this to be officially supported rather than using an invalid proxy to trick it into caching.

This mode would only store tracks in the cache and allow the user to submit them when they want.

My suggestion so that you don't have to do any GUI programming is to implement some intelligent parsing of the proxy address field.

If the user prefixes the server address with a keyword ("DoNotSubmit*", "CacheOnly*", or something similar) then the plugin will only cache the tracks and not attempt to (re-)connect to the server.

To further extend this, it could be programmed such that the above occurs under normal conditions, but if the user clicks the submit cache button it would parse off the keyword and attempt to submit using the proxy if it exists.


EDIT: Alternately, if we could define the number of retries that could be used to accomplish the same thing.  Allow the user to enter -1 to never connect to server.

foo_audioscrobbler 1.4.7

Reply #326 –
Quote from: TheQwerty on
I want to suggest (once again) a cache only mode.  Now that the plugin attempts to reconnect t*2 seconds upon failure it is even more desirable for this to be officially supported rather than using an invalid proxy to trick it into caching.

This mode would only store tracks in the cache and allow the user to submit them when they want.


Why do we need or even want this feature again?

foo_audioscrobbler 1.4.7

Reply #327 –
Quote from: neothe0ne on
Quote from: TheQwerty on

I want to suggest (once again) a cache only mode.  Now that the plugin attempts to reconnect t*2 seconds upon failure it is even more desirable for this to be officially supported rather than using an invalid proxy to trick it into caching.

This mode would only store tracks in the cache and allow the user to submit them when they want.


Why do we need or even want this feature again?


more importantly: why would you need the feature at all.. the only reason that you give is that you want 'submission power'? it sounds like feature-bloat to me, anyway
if you don't have net access, it doesn't matter if it tries to submit.. if you do, there's no reason not to.

foo_audioscrobbler 1.4.7

Reply #328 –
Quote from: neothe0ne on
Why do we need or even want this feature again?

Quote from: boombaard on
more importantly: why would you need the feature at all.. the only reason that you give is that you want 'submission power'? it sounds like feature-bloat to me, anyway
if you don't have net access, it doesn't matter if it tries to submit.. if you do, there's no reason not to.
It's been explained three or four times already in this thread.  It's simply a matter of preference.

I don't want to submit from work.  I do however want it to cache so that when I get home I can perform the submission.  Why don't I want to submit from work?  For starters, IT policy would state that's not an appropriate use of the network.  With as small as the amount of data is it's a bit of a non-issue but it does break the policy and could be used as a reason for termination.  In addition, there's security and privacy concerns and with the work I'm doing I do have to monitor network connections, so it is a bit annoying to see a number of attempts throughout the day.

It's hardly feature-bloat if it is useful to a number of people, and if you read this thread such a feature has been requested many times. And I wouldn't exactly call a couple lines of parsing and some logic blocks bloat.


In the very least, some error checking needs to be introduced since the plugin will endlessly attempt to connect to a server with an invalid address or port and it should realize that a port greater than 65535 breaks spec.

foo_audioscrobbler 1.4.7

Reply #329 –
Quote from: neothe0ne on
Why do we need or even want this feature again?

Is he talking about you? Is he talking about anyone else but himself? Clearly HE has a wish for the feature, so HE´s asking about it. You´re the one talking about WE. In the end it´s up to the developer to determine if such a feature will be implemented.
Stop trying to stuff your own personal preference down other people´s throats.
I´m sorry for the rant but people can be really self centered around here. If I don´t need it why would anyone need it...

foo_audioscrobbler 1.4.7

Reply #330 –
Okay, I've read the suggestion about pausing the submission process and caching the items instead and kindly ask you to stop ranting on other users feature suggestions.

I'll definitely not implement it in the suggested way (using some dedicated strings in the proxy settings) but will think about a more accessible solution after I've finished some changes to the plugin that are more important at the moment.

Kind regards,
Florian

foo_audioscrobbler 1.4.7

Reply #331 –
Quote from: Florian on
I'll definitely not implement it in the suggested way (using some dedicated strings in the proxy settings) but will think about a more accessible solution after I've finished some changes to the plugin that are more important at the moment.
That would be great.  I only suggested the dedicated strings because it would be a way of coding it without having to add to the user interface (earlier I believe you commented on disliking having to do that, or making the UI more complicated).

What honestly makes the most sense to me is having either a radio group or a drop down list and having three options. It could even replace the "Enable Audioscrobbler" check box.

I'm not sure on the wording but perhaps:
Audioscrobbler Mode:
-Disabled
-Scrobble Now
-Scrobble Later

or maybe:
Scrobble Tracks:
-Never
-Automatically
-Manually

Thanks again for the hard work coding this plugin!

foo_audioscrobbler 1.4.7

Reply #332 –
Hi, for some reason I cannot submit the tracks I've listened to since yesterday. Can't seem to connect, I tried another computer and it's the same. I already have the latest version.

Code: [Select]
Autoplaylists initialized in: 0:00.015551
Startup time : 0:01.179824
Audioscrobbler HTTP: User abort
Audioscrobbler: Cannot connect to server. Retrying in 60 seconds.
Audioscrobbler HTTP: User abort
Audioscrobbler: Cannot connect to server. Retrying in 120 seconds.
Audioscrobbler HTTP: User abort
Audioscrobbler: Cannot connect to server. Retrying in 240 seconds.
Audioscrobbler HTTP: User abort
Audioscrobbler: Cannot connect to server. Retrying in 480 seconds.

foo_audioscrobbler 1.4.7

Reply #333 –
last.fm/audioscobbler might change the API used for submissions at any time, so it's easier to just use their component instead of some third-party one that you never know if works or not.

I'm using the official last.fm component as it always seem to work. And the last.fm application is useful for getting extra info about artists I'm playing without having to copy/paste an artist's name into Google or whatever.

foo_audioscrobbler 1.4.7

Reply #334 –
Quote from: saivert on
last.fm/audioscobbler might change the API used for submissions at any time, so it's easier to just use their component instead of some third-party one that you never know if works or not.

Their submission protocol is well documented and even if they change the API, the last version will be supported (as you can now see with protocol v1.1 and v1.2).

So no reason to spread FUD here.


Quote
I'm using the official last.fm component as it always seem to work.

You seem to be a lucky person as this component is even listed as [a href='index.php?showtopic=44213']Known Problematic Component[/a] due to the many crashes it has produced.

foo_audioscrobbler 1.4.7

Reply #335 –
Quote from: Rain on
Code: [Select]
Audioscrobbler HTTP: User abort
Audioscrobbler: Cannot connect to server. Retrying in 60 seconds.

I've added further error logging to the v1.3.12 release and I admit that this error message is a little bit irritating

Whenever you get this, the component can't connect to the handshake/submission/notification server. Please refer to the official Last.fm System Status for detailed information.

This will be fixed in the next version.

foo_audioscrobbler 1.4.7

Reply #336 –
Thanks Florian for this great plugin!

Is there any chance that you could add a menu option to switch scrobbling on and off? That way, we could assign it to a keyboard shortcut or a toolbar button rather than having to go through the Preferences window.

foo_audioscrobbler 1.4.7

Reply #337 –
Quote from: Florian on
Whenever you get this, the component can't connect to the handshake/submission/notification server. Please refer to the official Last.fm System Status for detailed information.

This will be fixed in the next version.


I checked the Last.fm System Status and everything is fine but I still can't seem to scrobble these last few days. My username and password are correct, yet it can't connect to the server.

foo_audioscrobbler 1.4.7

Reply #338 –
Hi there,

I'm sorry if I'm just ignorant on how this works, but I think I may have set it up incorrectly.

I ran the installer after closing the player, then reopened.  In the prefs, I found the setup for it, so entered my last.fm info.

When I checked last.fm, no new songs were coming up.  I checked the prefs, and it stated that 21 songs were in the queue, to check the console.

Console shows nothing after the initial startup stuff(tree refreshed).

Once, I did click the submit button, which greyed it out, but when I opened the prefs later on, it was still counting up and no new songs showed up in last.fm.

I don't understand the queue.  My main computer uses Amarok, and during playing of each song, it submits the track to last.fm.  Is this plugin supposed to do the same and I have done something wrong, or is it supposed to just hold the cache until something that's supposed to happen, happens?

Again, I'm sorry for the stupid question, but didn't want to compound the problem by not trying to fix it.

thanks,
json

foo_audioscrobbler 1.4.7

Reply #339 –
Quote from: schwim on
Again, I'm sorry for the stupid question, but didn't want to compound the problem by not trying to fix it.

Have you tried it today? The Last.fm servers had massive problems yesterday and it might be better today.

foo_audioscrobbler 1.4.7

Reply #340 –
Quote from: Florian on
Quote from: schwim on
Again, I'm sorry for the stupid question, but didn't want to compound the problem by not trying to fix it.

Have you tried it today? The Last.fm servers had massive problems yesterday and it might be better today.


Hi Florian,

I did try it today, and it is working perfectly.  Thanks very much for your reply!

thanks,
json

foo_audioscrobbler 1.4.7

Reply #341 –
Florian, is there any way to set up amount of time before 'scrobbling' of track?

Now, as i can see from console, it always happens at the end of track. How about some preference, so we can determine that ourselves (like in Last.FM component)?

for example:
Code: [Select]
$puts(half_length, $div(%length%, 2))
$ifgreater($get(half_length), 240, 240, $get(half_length))

--

P.S.: my apologies if there is already an asnwer.

---
Update: also i would suggest to 'populate' some audioscrobbler 'playtime info', such as 'where track scrobbled?' & 'how many time till scrobbling?', if it possible.

foo_audioscrobbler 1.4.7

Reply #342 –
Quote from: seigert on
Florian, is there any way to set up amount of time before 'scrobbling' of track?

Quote from the specification of the Audioscrobbler Realtime Submission Protocol v1.2
Quote
1. The track must be submitted once it has finished playing. Whether it has finished playing naturally or has been manually stopped by the user is irrelevant.
2. The track must have been played for a duration of at least 240 seconds or half the track's total length, whichever comes first. Skipping or pausing the track is irrelevant as long as the appropriate amount has been played.

Due to this very clear guideline I'll not offer any settings for submission time.

I'll also not introduce any Audioscrobbler-related titleformatting placeholders, because titleformatting is not intended for such global data. There is no way of updating global data on all items and using it for global data might even result in funny repaint glitches.
 

foo_audioscrobbler 1.4.7

Reply #343 –
Quote from: Florian on
Due to this very clear guideline I'll not offer any settings for submission time.

Aw, thanks! Now process is perfectly clear to me. Didn't realize for a first time that 'marked for submission' (guideline #2) is not equals to 'submitted' (guideline #1).

Quote from: Florian on
I'll also not introduce any Audioscrobbler-related titleformatting placeholders, because titleformatting is not intended for such global data.

May be i'm misunderstanding you - what do you mean by 'global data': audioscrobbler submittion data or available tracks data? In my proposal i've suggested data only about one 'now playing' track, if it exists. So, such scrobbling data should be available only in contexts when placeholders like %playback_time% are available.

foo_audioscrobbler 1.4.7

Reply #344 –
Quote from: seigert on
So, such scrobbling data should be available only in contexts when placeholders like %playback_time% are available.

As I said before, I won't add any Audioscrobbler-specific titleformatting placeholders. I was flamed for doing that before and don't want to run in this situation again. However, I'm quite aware of the fact that other component authors are very generous with creating component-specific titleformatting placeholders.

Anyway, you can use existing placeholders to display Audioscrobbler-related information, like time till point of scrobble (but not e.g. size of cache).

foo_audioscrobbler 1.4.7

Reply #345 –
Quote from: Florian on
Anyway, you can use existing placeholders to display Audioscrobbler-related information, like time till point of scrobble (but not e.g. size of cache).

Yeah, i'm doing it this way now. Well, thanks anyway -- great component!

foo_audioscrobbler 1.4.7

Reply #346 –
@Florian

Would you be interested in making use of newly implemented foo_dop API for receiving play counts from Ipod?
Foo_dop is great component for managing iPod maintained by musicmusic, and it would greatly cooperate with foo_audioscrobbler if submitting play count could be possible

foo_audioscrobbler 1.4.7

Reply #347 –
Hi Audioscrobblers,

I've just released foo_audioscrobbler 1.3.14 which
  • adds support for importing tracks played from an iPod via foo_dop! foo_dop version 0.5.3 and above is required. The import can be triggered using 'iPod > Rewrite iPod database'.
  • adds a workaround for proxy servers that omit required trailing sequence in chunked mode (which resulted in duplicate entries on Last.fm profile page)
Thanks to musicmusic for providing the API to access playback data via foo_dop!

Happy scrobbling!

Cheers,
Florian

foo_audioscrobbler 1.4.7

Reply #348 –
very nice release, appreciate it