I have reverted back to v1.0.2.29. It works fine.

Can you please generate log and open new support ticket?dypsis wrote:I get a Runtime error 216 at 081E55F6 after closing MM since upgrading to Last.fm Scrobbler 1.1.0.41.
I have reverted back to v1.0.2.29. It works fine.
I'm actually still having the opposite problem as that. After reading your post, I went back and turned on Scrobbling from MM again. Threw a file from the MM Server into my Sonos queue and played it. And it shows up twice in Last.FM play history. The "Scrobble Time" is a couple minutes apart, but the song has only been played once, so it's submitting the track from both Sonos and MM. How do I fix this? Other than by disabling scrobbling on one or the other. If I disable it on Sonos, songs I play from Spotify won't be scrobbled. If I disable it on MM, nothing I play on my desktop gets scrobbled. I've been turning it off on the desktop and trying to remember to turn it back on (and subsequently back off) while I'm listening on the desktop, but that's obviously a pain. Any ideas?mcow wrote:I recently was experimenting with using MMA after using the "Choose player" function to pick a UPnP renderer. It played fine, but it did not scrobble nor update the stats in the library.
UPnP scrobbling was tweaked a while ago to leave scrobbling up to the UPnP client (such as MMA) when playing from the MMW server, which I think is fine. But that logic doesn't apply if MMW is the control point. If MMW is where I press the Play button, MMW is where the scrobble should take place. Especially since the renderer might be a hardware device (receiver) with no scrobble capability.