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

Surge: In Cubase cannot route audio into Surge. #379

Closed
itsmedavep opened this issue Jan 22, 2019 · 4 comments · Fixed by #1394
Closed

Surge: In Cubase cannot route audio into Surge. #379

itsmedavep opened this issue Jan 22, 2019 · 4 comments · Fixed by #1394
Labels
Host Specific Issues related to specific host(s) or host features

Comments

@itsmedavep
Copy link
Contributor

itsmedavep commented Jan 22, 2019

I believe that given @baconpaul stated (and this is bore out in other Hosts) Surge can have audio routed to it, this is a bug.

Using either VSTi 2.4 or VST3 does not allow for side chaining. Meaning, that it does not show up in the GUI in the plug in window chrome. Additionally, Cubase does not show Surge as an audio plug in. As evidenced by these screens:

screen shot 2019-01-22 at 12 13 55 pm

screen shot 2019-01-22 at 12 14 45 pm

Showing Surge VST3. No side chain button along plug in window chrome. It should be showing up right next to the black drop list window but its not.

screen shot 2019-01-22 at 12 30 33 pm

This video leads me to believe that there is work to be done to get this happening (at least) in the case of VST 3.

https://www.youtube.com/watch?v=PBQr-PnI6Yw

To Reproduce
Steps to reproduce the behavior:

  1. Open Cubase project.
  2. Insert a VSTi
  3. Look at VSTi plug in window chrome for side chain button
  4. Notice it's missing.

It should be here:

screen shot 2019-01-22 at 12 44 11 pm

Desktop (please complete the following information):

  • OS: [macOS 10.14.2]
  • Host [Cubase]
  • Version [9.5]
@sense-amr
Copy link
Contributor

I believe that given @baconpaul stated (and this is bore out in other Hosts) Surge can have audio routed to it, this is a bug.

maybe it should be Surge can NOT have audio routed to it :)
@itsmedavep

@baconpaul baconpaul added the Host Specific Issues related to specific host(s) or host features label Jan 26, 2019
@esaruoho esaruoho added this to the 1.6.n milestone Mar 1, 2019
@baconpaul
Copy link
Collaborator

Linking this to #1005

@baconpaul baconpaul modified the milestones: 1.6.n, Currently Unscheduled Oct 4, 2019
@baconpaul baconpaul modified the milestones: Currently Unscheduled, 1.6.5 Dec 3, 2019
@baconpaul
Copy link
Collaborator

Hey @itsmedavep I bet you thought I forgot about this one?

Well:

Screen Shot 2019-12-03 at 5 50 43 PM

Lemme get it pushed and maybe you can do a test for me in cubase beyond the test I did (which is: it showed up).

baconpaul added a commit to baconpaul/surge that referenced this issue Dec 3, 2019
SideChains in Cubase require the VST3 to show a "kAux" input.
This does that.

Closes surge-synthesizer#379
@baconpaul
Copy link
Collaborator

Requires the VST3 of course.

baconpaul added a commit that referenced this issue Dec 3, 2019
SideChains in Cubase require the VST3 to show a "kAux" input.
This does that.

Closes #379
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Host Specific Issues related to specific host(s) or host features
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants