External Sidechain, I got it working
-
@pluginboi Excellent ! will have to try this
-
Nice hack! However a more future-proof solution would not hardcode 4 channels, but let
NUM_PLUGIN_CHANNELSdo its magic, and use thesideChainproperty of thejuce::AudioBussesfor channels if desired. The cleanest option would probably another macro definition calledNUM_SIDECHAIN_CHANNELSwhich will then be subtracted from the total channel amount.I'll try to come up with something, but if it's as easy as just passing in the sidechain flag to juce, then it shouldn't take too much effort.
-
@Christoph-Hart Sidechain would be a gamechanger :)
-
@pluginboi How can you route the sidechain , will it appear in as an extra input in the routing manager ?
-
@lalalandsynth with the changes to the source code the routing manager should show 4 outputs now. I then add 2 more channels and connect each input to the corresponding output 1-4.
Then in scriptnode set it so the routing is enabled for all 4 channels and then using a multi node I separate channel 1 and 2 / 3 and 4. And then I use a send and receive node to send the 3/4 to 1/2.
Probably a much cleaner way of doing it but this was working for now haha
-
@lalalandsynth like this https://imgur.com/a/5bUDWAU
-
@Christoph-Hart oh hey i know your super busy but were you able to figure out a way to make sidechains with another macro NUM_SIDECHAIN_CHANNELS. you were right about in not being future proof haha i currently have to use two different hise builds cause protools only accepts mono sidechain
-
@pluginboi man I'm resurrecting a long gone thread but do you have any updates on your external sidechain journeys?? I'm working on following your original instructions right now but figured I'd ask if you had any new approaches or information in the last couple years!
-
@NEST-acoustics oh yea changed alot from this original post. I'll post an update later this week
-
@pluginboi absolute legend!!
