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

Native Instruments Reactor5 plugins seem confused #313

Open
1 task done
miranda opened this issue Feb 21, 2024 · 0 comments
Open
1 task done

Native Instruments Reactor5 plugins seem confused #313

miranda opened this issue Feb 21, 2024 · 0 comments

Comments

@miranda
Copy link

miranda commented Feb 21, 2024

Thanks for giving yabridge a shot!

  • I read through both the troubleshooting and the known issues sections, and my issue wasn't listed there

Problem description

I'm not completely sure this is actually a yabridge bug, but it seems most likely the issue originates with the linking of the different VSTs. Reactor5 plugins seem wrongly assigned to their variations. If you install all of them, it seems you can't use the 2-channel base version because that one is somehow pointing to the 8-channel version. Using Ardour when creating a new track it does not give you the option to use the 2-channel version, however if you disable all the other variations it becomes clear that the 2-channel plugin just called reactor5.so is pointing to the 8-channel version.

What did you expect to happen?

Expected reactor5.so to be 2-channel version.

What actually happened?

reactor5.so points to the 8-channel VST.

Operating system

Garuda Linux KDE Dragonized Gaming Edition (Arch-based)

How did you install yabridge?

pacman

yabridge version

5.0.5-1

yabridgectl version

5.0.5-1

Wine version

wine-staging 8.21

Plugin

Native Instruments Reactor 5 (5.9)

Plugin type

VST2

Plugin architecture

64-bit

Host

Ardour 8

Desktop environment or WM

KDE Plasma 5.27.10 on X11

GPU model

Radeon 6950XT

GPU drivers and kernel

AMDGPU Linux Zen 6.7.5-zen1-1-zen

Debug log

No response

Anything else?

No response

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

1 participant