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.

Sign up for GitHub

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

Jump to bottom

Respect custom VST path only! #754

Open
Cris-- opened this issue Feb 25, 2024 · 0 comments
Open

Respect custom VST path only! #754

Cris-- opened this issue Feb 25, 2024 · 0 comments
Labels
bug Something isn't working
Milestone
1.0

Comments

@Cris--
Copy link

Cris-- commented Feb 25, 2024 •
edited by mfisher31

Hi,

my VST paths in Element are only:

"pluginScanPath64_VST" val="C:\Audio\VST2"
"pluginScanPath64_VST3" val="C:\Audio\VST3"

The problem Element detects also plugins under Unverified > VST3:
C:\Users\Xeno\AppData\Local\Programs\Common\VST3

Same with Unverified > VST:
C:\Program Files\VstPlugins

Both folder here (VST3 & VstPlugins) are symbolic links only to the paths in the elements.conf and sometime Element detects plugins doubled.

Why is Element searching plugins in Windows 11 via VST default paths?

Windows 11, Element 1.0.0 b219/b222
@Cris-- Cris-- added the bug Something isn't working label Feb 25, 2024
@mfisher31 mfisher31 added this to the 1.0 milestone Feb 25, 2024 — with Slack
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
1.0
Development

No branches or pull requests
2 participants
@mfisher31 @Cris--