Yeah, it would be a Cakewalk development or a virtual audio mixer like VoiceMeeter. I played around with this some time ago and it worked but was pretty finicky on my DAW. This is issue is similar to recording plug-ins live, which has been the subject of a few recent threads.

What I would like to see in Sidechain Mixer is the VST3 header updated to put the plug-in in the Tools folder.

scook
What I would like to see in Sidechain Mixer is the VST3 header updated to put the plug-in in the Tools folder.

OK try the new one, version 1.1 (same link in 1st post). It should now show up in the Tools folder if you sort by category. You might need to do a rescan, not sure. I did one anyway.

Yes, that works, it was picked up by the auto background scan
Thanks

Very cool little idea... Thanks Silktone. I'm not sure when I'll use this but it seems a handy tool to have "just in case"

I'll d/l it when I'm on my DAW...

In line with the people who would like to send signal to another track's input... What if a loopback could be somehow used to re-route signal? This way it would appear as a potential input to the front end of a track without Cakewalk needing to do anything?

...just a thought.

Keni

Thanks for this - always wanted an integrated bus in track folders.
 
One question arise - anything to look out for where PDC will not be properly calculated?
 
Thinking of the feeding bus back to a track that in turn may have sends etc.
At some point there are feedback loops - and a nono since any pdc cannot be reported correctly.
I already had some weird results in SA2015 with default routings.
 
Is there a don't list?
There are so many possibilities.
 
Thanks.

Keni & lfm...
 
From what I can tell, you cannot create an infinite loop since Sonar can detect this and prevent you from completing such a routing in the first place. See my comment in this post. This also implies that there should not be PDC issues since the signal path will never loop back on itself.
 
But this is just from my own observations. I don't really know how Sonar works internally but it seems that the correct checks and balances are already in place to prevent these kinds of issues.
 
If we are lucky, Noel might jump in and provide some details regarding Sonar's handling of this.

Thank you for this. I am eager to try this out when I get a chance to sit down later.

SilkTone
Keni & lfm...
 
From what I can tell, you cannot create an infinite loop since Sonar can detect this and prevent you from completing such a routing in the first place. See my comment in this post. This also implies that there should not be PDC issues since the signal path will never loop back on itself.
 
But this is just from my own observations. I don't really know how Sonar works internally but it seems that the correct checks and balances are already in place to prevent these kinds of issues.
 
If we are lucky, Noel might jump in and provide some details regarding Sonar's handling of this.

I'll check out the other thread too, thanks.
I know my brain loops at some point thinking over this - what you can do? 
 
Is anything violated when sidechain input does not just control something, but actually is fed through as audio and mixed?
 
If there is pdc not accounted for in this created chain?
If VST3 specs differentiate between input and sidechain in any way?
 
Easiest to put something rediculous like L3 with 3840 samples delay in there and see what happends. Anything going wrong will be heard I gather.
 
Would be neat if it works...

lfm
I'll check out the other thread too, thanks.
I know my brain loops at some point thinking over this - what you can do? 
 
Is anything violated when sidechain input does not just control something, but actually is fed through as audio and mixed?

 
Nothing is violated. Sonar doesn't know what the plugin does with the audio coming into the sidechain input (and doesn't really care). Mixing it in with the audio going through the plugin is perfectly valid.
 

If there is pdc not accounted for in this created chain?

 
The plugin reports 0 sample delay to the host and also doesn't introduce any delay itself.
 

If VST3 specs differentiate between input and sidechain in any way?

 
No, the plugin just needs more than 1 stereo input. It is Sonar that treats a plugin with more than 1 stereo input as having a sidechain input.
 

Easiest to put something rediculous like L3 with 3840 samples delay in there and see what happends. Anything going wrong will be heard I gather.
 
Would be neat if it works...

 
It should work correctly. The sidechain mixer is a very lightweight plugin that doesn't introduce any delay. It merely mixes two streams of stereo samples together into one stereo stream at sample accurate timing.
 
I believe someone did a PDC test in one of the initial threads and found it worked correctly. But you should do some testing yourself if you personally want to make sure you can trust it.