Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Separate Windows Installer Registry Entries for JACK and ASIO #3103

Open
pljones opened this issue Jul 12, 2023 · 2 comments
Open

Separate Windows Installer Registry Entries for JACK and ASIO #3103

pljones opened this issue Jul 12, 2023 · 2 comments
Labels
feature request Feature request

Comments

@pljones
Copy link
Collaborator

pljones commented Jul 12, 2023

What is the current behaviour and why should it be changed?

Currently the JACK and ASIO Jamulus installers for Windows share a registry key. This is not optimal where both versions are wanted as updates and uninstalls "get confused".

Describe possible approaches

  • We could keep things as they are now
  • We could add subkeys for JACK and ASIO
  • We could use separate keys for JACK and ASIO

For migration from the current approach, I think separate keys is probably easier although subkeys is probably the technically better approach.

Has this feature been discussed and generally agreed?

One of my off-topic ramblings kicked this off.

@ann0see
Copy link
Member

ann0see commented Jul 12, 2023

If subkeys are doable, we should use them.

@softins
Copy link
Member

softins commented Feb 13, 2024

It is more than just the registry. If you want ASIO and Jack versions to co-exist on one system, you will need also to either give them different app names or else have them install by default into different sub-directories too.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature request Feature request
Projects
Status: Triage
Development

No branches or pull requests

3 participants