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

1.7.0 VST 3 Surge Instrument Does Not Appear in DAW but SurgeEffectsBank Does #2395

Closed
smilinggoat opened this issue Jul 30, 2020 · 1 comment
Labels
Bug Report Item submitted using the Bug Report template
Milestone

Comments

@smilinggoat
Copy link

Describe the bug
In macOS Mojave the VST 3 Surge instrument does not appear in DAW hosts even though the file exists in /Library/Audio/Plug-Ins/VST3/Surge.vst3 and the SurgeEffectsBank.vst3 does appear and load in hosts.

Tested with both Ableton Live 10 and Adobe Audition 2020.

I initially installed with brew, experienced the issue, then installed via the download DMG but the problem persisted. I attempted restarting after experiencing the issue.

Please let us know your surge version
1.7.0

  • Surge Version: 1.7.0
  • Plugin type: VST 3
  • Bits: 64

To Reproduce
Steps to reproduce the behavior:

  1. Install normally via brew or DMG
  2. Attempt to load plugin in host
  3. VST3 version does not show up in plugin list
  4. AU version does show up in plugin list
  5. VST3 SurgeEffectsBank does show up in plugin list

Expected behavior
The instrument should appear in the plugin menu

Screenshots
Screen Shot 2020-07-29 at 17 41 16

Desktop (please complete the following information):

  • OS: macOS Mojave 10.14.6
  • Host: Ableton Live 10, Adobe Audition 2020
@smilinggoat smilinggoat added the Bug Report Item submitted using the Bug Report template label Jul 30, 2020
@baconpaul
Copy link
Collaborator

Hi

I fixed this in the nightly install yesterday after other users reported it. The fix for live will be in Surge 1.7.1. Until then your options are use the AU; or install the nightly (https://surge-synthesizer.github.io/nightly).

Turns out Live places an extra signing constraint on your vst3 that no other host does; and our move to cmake and screwed up our no-op signing. But it's fixed in the nightly now. I'll close this but if the nightly doesn't work for you please do re-open it.

Thanks for the clear report!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Report Item submitted using the Bug Report template
Projects
None yet
Development

No branches or pull requests

3 participants