How to install the Last.fm scrobbler plug-in?

[King Mustard]

I downloaded the Last.fm program from www.last.fm/download/windows

Within Setup, I chose to install the Winamp plug-in.

I moved gen_wa2_scrobbler.dll from the newly created (by Setup) \\Program Files (x86)\Winamp\plugins to \\Program Files (x86)\WACUP\Plugins.

It is appearing within WACUP (Preferences > Plug-ins > General Purpose) but clicking on it then the 'Configure' button is not allowing me to configure it (no dialogue appear) - which I presume I would need to be able to log in to the service.

Any ideas?

[Eris Lund]

You can already scrobble through WACUP itself.

[King Mustard]

You can already scrobble through WACUP itself.

Oh yes, there it is!

I appreciate it.

[dro]

It is appearing within WACUP (Preferences > Plug-ins > General Purpose) but clicking on it then the 'Configure' button is not allowing me to configure it (no dialogue appear) - which I presume I would need to be able to log in to the service.

The config button being available to click just means the plug-in has reported there's a config method but there's nothing to indicate that it's not a dummy one (i.e. wouldn't do anything). iirc the last.fm provided plug-in didn't have a working config as it relied on their desktop client to handle it. The even older standalone last.fm plug-in did have a working config but iirc that won't show / crashes on modern versions of Windows since it was built in a manner that conflicts with security changes that have been applied to the OS since that time.

[King Mustard]

I have tried scrobbling my first song (a standard 5:07 MP3) but Preferences is saying, "Playing item is too short to be scrobbled."

Any idea why WACUP would think it is too short?

[dro]

Is the information for the file showing the correct length in the local library & alt+3 file information dialog?

I know of an issue with getting the length for files in un-mapped network shares but am not aware of that not working for anything else (local file or via mapped to a drive letter network share). Alternatively there's an option on the native scrobbler prefs page to mostly ignore the length but that's not ideal.

[King Mustard]

Is the information for the file showing the correct length in the local library & alt+3 file information dialog?

I know of an issue with getting the length for files in un-mapped network shares but am not aware of that not working for anything else (local file or via mapped to a drive letter network share). Alternatively there's an option on the native scrobbler prefs page to mostly ignore the length but that's not ideal.

I have attached a screenshot of ALT+3.

[dro]

That looks like an un-mapped network share from the path shown so I've got to assume you're having the issue I described. Looking for that file in the local library part of the media library window & there not being a length shown would confirm if that's the cause. It requires a new build to get the needed fix (not yet ready as a new preview build) & a refresh of the metadata in the local library after the newer build has been installed.

[King Mustard]

That looks like an un-mapped network share from the path shown so I've got to assume you're having the issue I described. Looking for that file in the local library part of the media library window & there not being a length shown would confirm if that's the cause. It requires a new build to get the needed fix (not yet ready as a new preview build) & a refresh of the metadata in the local library after the newer build has been installed.

It's just a standard Windows folder share from my other Windows 11 PC, if it helps.

[dro]

The nature of the share doesn't matter as it just has to be via an un-mapped location & the file metadata has to have also been cached within the local library db which is why I'd asked in both of the replies I've made about this problem for it to be checked.

[King Mustard]

Unfortunately, this is still occuring.

[dro]

As I cannot replicate this or it's potentially expected per my prior reply with network shares & items not already pre-cached into the local library then all I can I do is add what was internally obtained as the length & report that as part of the error message to try to diagnose it.

Alternatively for now you can trying checking the option on the scrobbler page to allow shorter durations to be sent & assuming network shares are still involved, go to preferences -> advanced -> options page 2 -> un-check the network file path checking option on there.

Also apply the post-release updates if not already done as the about|updates page showed there ones pending being applied.

[King Mustard]

My MP3s are on my internal network but there is no reason why that should affect anything. I don't know of any other software where it makes a difference (e.g. video players when playing videos).

[dro]

Neither do I hence adding in what length is reported to the error message to try to give me something to figure out why you keep saying it's broken for you. For reference I don't proactively use the scrobbler mode so there's a whole entirety that it's just shit / broken / never right.