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

Be able to specifiy each plugin's windows version (7/10/11) #366

Open
ywmaa opened this issue Sep 4, 2024 · 3 comments
Open

Be able to specifiy each plugin's windows version (7/10/11) #366

ywmaa opened this issue Sep 4, 2024 · 3 comments

Comments

@ywmaa
Copy link

ywmaa commented Sep 4, 2024

Feature description

Be able to specifiy each plugin's windows version (7/10/11)

Why ?
for some reason BBC Symphony works when winecfg is set to windows 7, meanwhile this breaks LABS! (gives unable to load their sample libraries (Error #X: Something went wrong)
if I set the windows version to 10 or 11, LABS works, but BBC Symphony gives the unable to load their sample libraries (Error #X: Something went wrong).

I think I can workaround this by doing two wine prefixes for each and setting windows version for each, but it would be awesome if I can just do it through yabridge config, and more cleaner.

also about BBC Symphony and LABS, I tried the solution in readme many times

If Spitfire Audio plugins like BBC Symphony Orchestra and LABS are unable to load their sample libraries (Error #X: Something went wrong), then you can try reinstalling those plugins to a new, clean Wine prefix. To avoid potential confusion, make sure to uninstall the Spitfire software along with the VST2 and VST3 plugins from your main Wine prefix first.

but the only solution for me for some reason is to change the windows version, which means I am unable to use both in the same project.

Anything else?

No response

@wastee
Copy link

wastee commented Sep 4, 2024

You can use multiple WINEPREFIX to install different sofeware and set different windows version.

@robbert-vdh
Copy link
Owner

That's indeed what Wine prefixes should be used for! While there are some environment variables that overlap some of the settings you can set through winecfg, plugins requiring bespoke configuration should just be using their own prefix so their configuration doesn't conflict with other plugin's setups.

@ywmaa
Copy link
Author

ywmaa commented Sep 4, 2024

Yeah, I am using wine prefixes for now and it is working, as also I mentioned in the issue that this workaround exists.

I don't actually insist on this feature and I don't mind closing the issue.

it is just a nice to have feature.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants