Skip to main content ↑ ↓

Notice

Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
Topic: wasapi VS processor architecture (Read 2407 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

wasapi VS processor architecture

Greetings,
I just switched to fb2k v2.0 [x64] and wanted to install my "common" components, yet the WASAPI.fb2k-component notifies me it cannot load Could not load component "WASAPI.fb2k-component": This component was built for a different processor architecture.

I have a x64 machine, though.

Any suggestions? Is there an alternative around?

THANK YOU
josz
 

Re: wasapi VS processor architecture

Reply #2 –
As @marc2k3 pointed out, the latest foobar2000 versions only have WASAPI outputs built-in (shared and exclusive), there's no more need for a component.
The error means you are trying to run a 32-bit component on a 64-bit app, old components were 32-bit only because foobar2000 used  to be 32-bit only. Now that there's a 64-bit version of foobar2000, components must be updated to include a 64-bit version.
(The old WASAPI component: Supported processor architecture: x86 32-bit.)