MediaMonkey forum

Do you use MM Pre-3.1? This plugin doesn't work in the stable MM 3.0.

More fixes on the way. Changed status to "Better v1.0.2.4".

v1.0.2.5 released
http://www.mediamonkey.com/forum/viewto ... 32#p179102

V1.0.2.5 has been stable here since release.
Thanks Peke.

Just testing another function on a new empty database with 1202&1.0.2.5 to which I had added some podcast tracks via Re-Scan.

Getting 1 additional track after Play Now of single track via My Computer node.

Just rechecked the Auto-DJ options in Last.Fm Service(None), Last.FM Node(All Unchecked) and Player:Auto DJ/Now Playing(All Unchecked). Also checked Play Menu:Auto DJ(Unchecked as well).

DIIK.

Maybe another problem with v1.0.2.5. See
http://www.mediamonkey.com/forum/viewto ... =6&t=35010

Remind me not to say something looks stable again. It jinxes the process.

Owyn wrote:Maybe another problem with v1.0.2.5. See
http://www.mediamonkey.com/forum/viewto ... =6&t=35010

Remind me not to say something looks stable again. It jinxes the process.

I'm a little confused, in your other thread it seemed like you meant the Last.fm auto DJ and not the last.fm scrobbler. They're 2 separate plugins.

Yep. The SELECTs are coming from LastFmNode.vbs auto script, not the plugin.

Looks like all of it's option settings went MIA.

Removing it from my beta configuration for now.

To confirm, no bug report on the plugin.

You people really like to keep me in shape (running from one side of field to other and back forth)

Keep testing, so that we can make this stable and ready for new features.

Few Qs and test reports for them:
- Unicode (Japanese, Hebrew, German, Turkish, Israel, Cyrillic, ...) tracks Scrobbling
- Now Playing
- Time Zone
- Server Errors
- Caching

Peke wrote:Few Qs and test reports for them:
...
- Time Zone
...

I have one issue to report regarding time zone, but I tested only with the old version of this plugin (for MM v3.0), because I didn't install MM 3.1 yet.

I live in Time Zone GMT-3:00 and in 'normal' time, playtimes were scrobbled correctly. When I finished listening a bunch of songs and I opened my Last.FM profile, it would list the tracks as: But, right now we're in Daylight Saving Time here, so in fact our time currently is GMT-2:00. Now, when I finish listening the same bunch of songs and I open my Last.FM profile, it lists the tracks as: ... (like if the last songs were listened to in the future!)

P.S.: My OS is Windows XP and I use "Automatically adjust the clock to DLST" option in Date and Time properties.

Hi,

When activating the 1.0.2.5 scrobbler, i have the following problem:
At the end of the first track, the MediaMonkey.exe CPU usage jumps to 100% until (just after) the end of the following track. The CPU usage is than OK, until the end of that track, after which it jumps to 100% again (etc.)
Any idea? MM3.1 latest beta.

Regards,

Stephan

Ummm. If it was the Last.FM client, I would suggest disable fingerprinting, but....

Hmmm. What are your CPU/OS specs?

I can confirm that this behavior is still present in 3.1.0.1204. It happens when you let the track play completely. If you manually switch tracks or move the playback position slider forward (skip part of track) this doesn't seem to happen. On previous testing removing the last.fm plugin resolved the issue, which points to the plugin being the culprit.

OS: Windows XP Pro SP3
CPU: AMD Athlon Mobile 64 2800+
Memory: 2GB

Lowlander wrote:I can confirm that this behavior is still present in 3.1.0.1204. It happens when you let the track play completely. If you manually switch tracks or move the playback position slider forward (skip part of track) this doesn't seem to happen. On previous testing removing the last.fm plugin resolved the issue, which points to the plugin being the culprit.

OS: Windows XP Pro SP3
CPU: AMD Athlon Mobile 64 2800+
Memory: 2GB

Yep. I added a few tools from SysInternals since my last look at this. With luck I will get to re-testing it by Boxing Day.

Hmmmm. I think you reported approx 85% CPU peak on the track transition tests. Correct?

Yeah, it basically consumes 100% of available resources, which translates to 80%-90% normally. The problem is less bad then previous iterations of the last.fm plugin where my whole system became unusable, now my system remains responsive and the high CPU use is less prolonged.