Today in "I should not be allowed to operate a computer" I finally figured out why I couldn't get in_vgm running in wacup
It's a very silly reason.
Now, I had been using VGM_Play (the VGM playback executable) which is built in both 32-bit and 64-bit versions, and I was using the 64-bit version. It's a decent enough experience if what you want to do is play VGM files, but the interface is, well, basic and not suited to the sort of features one might expect out of a modern media player (like, say, a library). But hey, install the VC++ 2010 runtimes, drag a file onto the application, hear those lovely chippy tones. At least good for early days on my new-to-me laptop.
But, again, I want to have better organization of my music. So, of course, in_vgm.dll as a WACUP plugin is something I should get running. Obvious decision for improved media experience, right?
Well, if only it would actually get detected and fuckin work, y'know? I kept getting a message to the equivalent of "either a dependency is missing or you need to restart" and multiple restarts didn't solve the issue, and I didn't take the hint, and by now a bunch of you have guessed the issue if it wasn't immediately obvious.
Winamp plugins (this might not be true with plugins that are included in WACUP, mind, but in_vgm isn't one of them) are only 32-bit. So I can't use the 64-bit VC++ runtimes to get them working! I needed to also install the 32-bit runtimes and checking the big list of installed apps, it was immediately clear I hadn't.
Well, at least the story has a happy ending, even if it's an embarrassing one.
