MUX + Studio One - sidechain?
-
- KVRAF
- Topic Starter
- 1906 posts since 15 Oct, 2008 from Germany
Hi,
I'd like to send audio from one track in Studio One into an instance of MUX (effect version) on another track. Normally, plugins with multiple inputs expose these as sidechain inputs which can then be selected as a send target. But the MUX instance doesn't appear as a sidechain target.
Does anybody know how to send audio from track to a MUX on another track in Studio One 2.5?
Here's an example: on track 1 there's an instance of Melda's MDynamics. On track 2 I can add a send from that track to the MDynamics instance. The audio is then available as the sidechain input. But as you can see, MUX does not appear in the sidechain list.
Thanks in advance,
Andre
I'd like to send audio from one track in Studio One into an instance of MUX (effect version) on another track. Normally, plugins with multiple inputs expose these as sidechain inputs which can then be selected as a send target. But the MUX instance doesn't appear as a sidechain target.
Does anybody know how to send audio from track to a MUX on another track in Studio One 2.5?
Here's an example: on track 1 there's an instance of Melda's MDynamics. On track 2 I can add a send from that track to the MDynamics instance. The audio is then available as the sidechain input. But as you can see, MUX does not appear in the sidechain list.
Thanks in advance,
Andre
- KVRAF
- 12739 posts since 24 Jun, 2008 from Europe
I think it's especially a S1 question. I'm not a S1 expert myself. Did you also post this question in a S1 support forum?
-
- KVRAF
- 4470 posts since 27 Jul, 2004
It seems to be not possible atm...
Jo, if I load a fx plugin into S1 V2, which does have multiple inputs, a "sidechain" button appears automatically on the top of the plugin "wrapper"...
Doesn't happen, if I load MUX into it... to me it seems, that MUX only reports the one audio in from the Basic Effect patch and can not change it, if another one is loaded into the deep editor...
But that's necessary to work with sidechaining in S1... perhaps it's better to let it report all available, even if only one is "active" in most presets
Good time to have a new beta... (you know, what I mean )
Jo, if I load a fx plugin into S1 V2, which does have multiple inputs, a "sidechain" button appears automatically on the top of the plugin "wrapper"...
Doesn't happen, if I load MUX into it... to me it seems, that MUX only reports the one audio in from the Basic Effect patch and can not change it, if another one is loaded into the deep editor...
But that's necessary to work with sidechaining in S1... perhaps it's better to let it report all available, even if only one is "active" in most presets
Good time to have a new beta... (you know, what I mean )
Last edited by Trancit on Sun Feb 24, 2013 8:12 am, edited 1 time in total.
-
- KVRAF
- Topic Starter
- 1906 posts since 15 Oct, 2008 from Germany
No I haven't, but I'll try it there as well.mutools wrote:I think it's especially a S1 question. I'm not a S1 expert myself. Did you also post this question in a S1 support forum?
I suppose the plugin needs to report to the host that it supports external sidechaining. Other plugins do this successfully, so I suppose this is something that has to be done on the plugin side.
Examples of plugins that appear as sidechain destinations in S1:
- all Melda plugins that accept external sidechains
- ArtsAcoustic CL-1
- FXpansion DCAM BusComp+CrossComp and Etch
- Klanghelm DC8C
- KV331 SynthMaster FX
- DNR MixControl Pro
- KVRAF
- 12739 posts since 24 Jun, 2008 from Europe
No, MUX Vst has 2 fixed stereo audio inputs (=4 mono inputs) which are reported to the host. When i load MUX Vst in MuLab they are visible. So i don't know why S1 does not recognize these inputs.Trancit wrote:Jo, if I load a fx plugin into S1 V2, which does have multiple inputs, a "sidechain" button appears automatically on the top of the plugin "wrapper"...
Doesn't happen, if I load MUX into it... to me it seems, that MUX only reports the one audio in from the Basic Effect patch and can not change it, if another one is loaded into the deep editor...
-
- KVRAF
- 4502 posts since 3 Oct, 2013 from Budapest
and after some years ...
this is how it looks when it's working, would be nice if you able to solve it You do not have the required permissions to view the files attached to this post.
"Where we're workarounding, we don't NEED features." - powermat
- KVRist
- 100 posts since 21 Nov, 2017 from India
-
- KVRist
- 30 posts since 1 May, 2018
- The only VSTs I've tried showing this problem in Studio One are MUX and Reaktor 6 FX. I've reported the issue to the PreSonus forum as well.
- The only VST host I have this problem with is Studio One.
While I have the impression that it's "more" a Studio One issue, it should also be fixable on MUX side.
- The only VST host I have this problem with is Studio One.
While I have the impression that it's "more" a Studio One issue, it should also be fixable on MUX side.
- KVRAF
- 12739 posts since 24 Jun, 2008 from Europe