On Windows ARM, the installer does not install FlexASIO 64-bit

[dechamps]

In #205 @eguetta ran into an issue where the FlexASIO installer only installed the 32-bit version of FlexASIO, leaving out the 64-bit version. This results in FlexASIO being only usable in 32-bit apps and not showing up in the driver list of 64-bit apps.

The plot twist here is that @eguetta is running Windows ARM. This is very likely what triggered the issue. Most likely, FlexASIO's Inno Setup got confused and treated Windows ARM as 32-bit only.

This is a bug in FlexASIO's installer, perhaps even in Inno Setup itself.

As a workaround, Windows ARM users can manually register the 64-bit version of FlexASIO by following the procedure described at #205 (reply in thread).

[dechamps]

I took another look at this. I think a fix for this is going to have to wait, for the following reasons:

1. I don't have a Windows ARM device to test with, and it's not possible to set up an ARM VM on x86 hardware.
   • One way would be to set up a VM on Azure but that is less convenient, and potentially costs money.
   • On the other hand VAC did add support for ARM64 in its latest 4.70 version so it should be possible to use that for testing even in an isolated VM (assuming I get my hands on one) with no attached audio devices.
2. Inno Setup seems confused by the whole thing.
   • But the good news is, Inno Setup people seem aware of this and have fixes coming up in the next version (6.3.0).
   • The Inno Setup upcoming release notes even acknowledge precisely this issue:

     If you ship x86 and x64 versions of your app in the same installer, the 32-bit x86 version may be chosen instead of the expected x64 version when running on Arm64 Windows 11

A stretch goal here would be to not only have FlexASIO work properly on Windows ARM64 with x86/x64 apps, but also provide an ARM64 version of FlexASIO, such that native ARM64 ASIO Host Applications can use FlexASIO. This should be a fairly easy addition to the above. One caveat is that currently GitHub Actions would not be able to run ARM64 FlexASIOTest due to actions/runner-images#768, but it appears that is being worked on as well.

So, TL;DR: the ecosystem is almost there, but not quite. Let's check again in a few months.