Describe the bug

The latest Jamulus builds for Windows are 64 bit, the previous versions were 32 bit. I think ASIO4ALL maintains customized settings per-exe file path and the install location is different for 32 vs 64 bit programs. This means the previously working settings for the old 32 bit version are not carried over to the new 64 bit version. Furthermore, the installer strongly recommends removing the older 32 bit version (this makes sense, because otherwise you end up with 2 sets of shortcuts, and things get kind of confusing).

To Reproduce

Have Jamulus working with ASIO4ALL on the old 32 bit version. Install a new 64 bit version, and click yes when installer strongly recommends removing old 32 bit version. Realize that ASIO4ALL is using the default settings now, and you don't remember what the good settings were. Reinstall the old Jamulus version to get the old settings, take a screenshot and get copy over the working settings to the 64 bit version.

I spent about an hour and a half talking someone through this over the phone yesterday.

Expected behavior

I don't think it's feasible for Jamulus to avoid this outright, but at the point where the installer recommends removing the old 32 bit Jamulus, it would be good to have a warning about it.

Operating system

This applies to Windows only.

Jamulus version

3.7.0, 64 bit builds.