Forum » Last.fm Client Support

PLUGIN NEEDED: Media Player 12 x64 Support

 
    • pupkick said...
    • User
    • 5 Jun 2009, 22:30

    PLUGIN NEEDED: Media Player 12 x64 Support

    Forcing wmp to 32bit each reboot is both frustrating and excessive.

    There needs to be a plugin for what is going to be a very popular player once win 7 is released. I think it's a reasonable request to ask that this be developed prior to Windows 7's release in October. Please please feel free to contact me to assist with testing.

    All users of x64bit Vista or Win 7 please respond with support.

    • pupkick said...
    • User
    • 5 Jun 2009, 22:33
    Also, iTunes 64bit for Windows needs a working plugin.

    Thank you

    • pupkick said...
    • User
    • 6 Jun 2009, 17:58
    Plugin started working properly for iTunes 64 with an install of the new version (8.2), and forcing that install to the \Program Files\ directory instead of the default \Program Files (x86)\

    WMP 64 still desperately needed. :(

    • pupkick said...
    • User
    • 13 Jun 2009, 16:26
    nothing?

  • I have no experience using 64bit software (yet), but have you tried manually selecting the wmp.exe in \program files (x86)\?
    I know that when I installed all my programs on another drive than the default C:, which contained my Windows-install, browsing to the correct folder made every plugin work, despite the fact that the client only looks in C:\program files\

    And staff has until somewhen in october, that is when W7 hits the shelfs ;)

    Remember to say "thank you" for the things you haven't had
  • It's not just a question of Windows 7.

    64 bit WMP has been about at least since Vista was released so a 64 bit WMP plugin is long overdue.

    Stupid thing is, it's probably just a matter of recompiling the wmp_scrobbler.dll for 64 bit, it's not exactly going to be complicated.

    Never argue with a fool. Onlookers may not be able to tell the difference....
  • Im having the same issue. switched over all my home Computers to Win7. Now I can only scrobble from work.

  • Any result? I did give a suggestion...

    Remember to say "thank you" for the things you haven't had
  • No, forcing the plugin directory doesn't work.

    Even if you manually place the plugin in C:\Program Files\Windows Media Player\Plugins as opposed to C:\Program Files (x86)\Windows Media Player\Plugins it does not work.

    This is due to wmp_scrobbler.dll being a 32 bit dll and the 64 bit WMP will not load it.

    wmp_scrobbler.dll needs recompiled as 64 bit, it is the only solution unfortunately.

    Never argue with a fool. Onlookers may not be able to tell the difference....
  • I was wondering why Last.fm's "search for available plugins" thing wasn't seeing iTunes, but now I realise.

    A 64-bit iTunes plugin is sorely needed, especially once Windows 7 is released.

    • pupkick said...
    • User
    • 22 Jun 2009, 03:40
    It works no problem with 64bit itunes, which can operate with 32bit plugins. WMP 64 however, cannot. As said above, you can't manually switch the plugin, and the issue has been around not just with Windows 7, but with Windows Vista 64. Forcing windows to use the 32bit version of WMP is a pain in the ass, and a process that generally needs to be redone each reboot. It's not a possible/simple workaround for the average user.

    The issue is absolutely with WMP 64bit and the WMP plugin.

  • WMP 64bit Last.FM Client Plugin

    Hi guys,
    I had been experiencing the same issues like you, so I've downloaded the WMP plugin source from Audioscrobbler's SVN and recompiled it as 64bit DLL. Here is the result:
    http://rapidshare.com/files/249016164/wmp_scrobbler.dll
    Works OK for me thanks to some presetted post-build actions defined in the VisualStudio project and I can scrobble now from the 64bit WMP too, but because of the lacking documentation of WMP plugins registering, I'm not exactly sure how to do it on other machines. If you are interested, I would recommend placing it in the 64bit WMP Plugins directory and then running from the CMD (with admin privileges) this:
    regsvr32 /s /c "c:\path\to\dll"
    (where is the "c:\path\to\dll" supposed to be replaced by the path to the DLL).
    Please let me eventually know whether it works for you or not.

    PS: I hope I'm not breaking some license of that orinal WMP plugin source by placing it recompiled here in such way, because I haven't found any licensing terms of it. If I do, let me also please know, I would remove/eidt in that case.

    Edited by RedDragCZ on 5 May 2010, 19:24
    • pupkick said...
    • User
    • 5 Jul 2009, 02:30
    RedDragCZ's hack works just fine. last.fm, give the guy some credit and ask him to use his .dll seeing as you can't recompile your own despite 64bit wmp being out for years.

  • I thought RedDragCZ's version was working on my Vista Ult 64 Version but no longer, maybe I mixed up the versions and was scrobbling on the 32 bit version after all. Not happening now.

    • pupkick said...
    • User
    • 11 Jul 2009, 18:17
    I have actually found a problem with the RedDragCZ workaround. You have to re-enable the plug-in every time you start WMP. Not terrible.. but not perfect.

    Edit: I think this may be because in Windows 7, WMP wants to stay resident even if you exit/close the player, rather than being a problem with the dll. This manifests itself as the last song played being stuck on my Logitech G15 keyboard's LCD display. So I end up killing the wmp process, which I'm guessing makes wmp forget the plug-in was enabled. Any way to cleanly exit wmp fully, or is this something that is normal, that WMP is always running? I dislike that because the wmpslideshow process is also running and consumes a LOT of resources.

  • Yes, I've came after this issue too, it is really annoying if I use sometimes more media players and then the mediakeys on my G15 control more than one player at once. Unfortunately, I think it is currently considered 'normal' on W7 that the WMP process just runs residently even after closing it, for me it seems to be most probably because of some additional library indexing (I can see it in WMP's statusbar when I re-run it), some people say it is caused by library sharing when you are in a home network (to be more specific, i found it here: http://www.windows7taskforce.com/view/2480 , hovewer, disabling it hasn't done the trick for me).
    Hope they will recognize it as a bug and fix it until the RTM is released ...

    • pupkick said...
    • User
    • 12 Jul 2009, 20:39
    yeah that's definitely it. I agree completely it needs to close properly.

  • Thanks RedDragCZ !

    Your Plugin is working great in WMP 11 x64 at my Vista ^^

    Already thought I had to go back to x86-Version...

  • Thanks RedDragCZ, this has been annoying the hell out of me since I started using Windows Media Center!

    Can confirm it works on x64 windows 7 RC playing through Windows Media Center (which uses x64 Windows Media Player).

    • lozzd said...
    • Alumni
    • 22 Sep 2009, 16:46
    Out of interest, why are you guys using the 64bit version of Windows Media Player? By default, even in Windows 7 the default WMP is still the 32bit version for plugin compatibility.

    Thanks pupkick for re-compiling it as 64bit.. I suspect on the next release we will do this too just for compatibility.

    Can confirm it works on x64 windows 7 RC playing through Windows Media Center (which uses x64 Windows Media Player).

    I just tested this and this does not seem to be correct either. I see eshell.exe running as 64bit, but wmplayer.exe * 32 was launched. it also scrobbled correctly straight out of the box. No changes performed here on my fresh Windows 7 machine, first time I'd launched both MCE and WMP.


    Want a fully customisable sig (like above?) CLICK HERE!
    Insert disclaimer here.
  • lozzd said:
    Out of interest, why are you guys using the 64bit version of Windows Media Player? By default, even in Windows 7 the default WMP is still the 32bit version for plugin compatibility.

    I was needing the 64bit version plugin because my W7 (even after clean reinstall!) was still starting for some strange reason by default the 64bit version of WMP and I was just not able to force it in any way to use the 32bit one (tried really many ways with no success at all).

    And by the way, it doesn't matter much, but it was me who recompiled the plugin, not pupkick. ;)

    • lozzd said...
    • Alumni
    • 24 Sep 2009, 21:36
    Oops, sorry about that!

    That's really weird that your is definitely launching the 64bit version. As I said, my clean installed version from a couple of weeks ago launches the 32bit one. At least you can fix your own problem! :)


    Want a fully customisable sig (like above?) CLICK HERE!
    Insert disclaimer here.
    • pupkick said...
    • User
    • 8 Nov 2009, 17:30
    months later, Red's recompiled .dll is still working perfectly for me. How it does it I could care less.. scrobbles are working, that's all that matters :)

  • I tried registering the x64 WMP plugin and now it shows up in the 64 bit version, however it doesn't do anything, and clicking on "properties" for it in the plugins page does nothing either :(

    • WinSrev said...
    • User
    • 31 Dec 2009, 08:39
    What's the point in have a 64bit OS and us using 32bit software, heavily defeats the point. Either way, last.fm is making is difficult for everyone really considering how easy this fix is for them. I mean, 64bit is becoming more and more supported.

Anonymous users may not post messages. Please log in or create an account to post in the forums.