I am currently making a track with a huge bass that needs chaining to the kick.
I managed to “sidechain” the bass by just entering a string of volume adjustments on the bass channel every time the kick occurs…
On my screen, everytime the kick occurs, I make the bass duck by entering a volume command which returns back to the standard volume. The amount of steps that it takes to return is obviously my choice, and is sort of like tuning the release.
If anyone can find fault with this method PLEASE let me know.
The only thing I can see at the moment is that it is time consuming, not automatic, and maybe not reach the resolution of a dedicated plug in unless you are running at speed 1 (can someone tell me about this please!?)
I think the problem here is that few people know what sidechaining is… due to so many false “sidechaining is just ducking the bass to the kick” definitions that float around the net. In reality, sidechaining is the ability to route the incoming signal to any parameter… and until we have proper routing or a sidechain metadevice (preferably both ) the sidechain issue can not be considered resolved. It’s generally annoying though, when I see many threads proclaiming to solve the sidechaining issue that are simply tutorials on how to do curve automations.
One workaround. (And I’m sorry if I have not understood the functioning of this feature correctly) Would be to disable the input of midi cc to a track when the record midi controllers is selected in the midi menu. (Now it disables the recording only, but not the “step” input of CC’s.)
We already have a sidechaining that functions with 128 instances, but the only problem is that the CC’s get recorded everytime the user presses space when using these midi workarounds.
So finetuning this disable recording feature would make it possible. (If it is a bug, then just bugfixing this will solve situation. I have not reported this though because I think it might be that I have not understood the functioning of this correctly)
One workaround. (And I’m sorry if I have not understood the functioning of this feature correctly) Would be to disable the input of midi cc to a track when the record midi controllers is selected in the midi menu. (Now it disables the recording only, but not the “step” input of CC’s.)
We already have a sidechaining that functions with 128 instances, but the only problem is that the CC’s get recorded everytime the user presses space when using these midi workarounds.
So finetuning this disable recording feature would make it possible. (If it is a bug, then just bugfixing this will solve situation. I have not reported this though because I think it might be that I have not understood the functioning of this correctly) [/quote]
May this be related to the part where pattern follow mode affects meta devices in automation or effect column? It sounds a bit fuzzy to me because i cannot really relate pressing spacebar with an external device affecting input cc’s so here’s just my idea that may be of help but if i understood incorrectly then apologise for that:
Try changing this button into and see if this makes a difference when using the space bar.</0x000056284eed4e60>
Hi yeah I will try this (altough I think I tried everything possible already)
To clarify: I’m using the space mode of FT2.
Will post results back later. If this works I’ll post an e-z tutorial also… [/quote]
Weirdest stuff… Now it works
hmmhmmhmm…
Last time I checked it recorded the notes randomly, but gotta say this might be my bad aswell.
Using jUltram it seems that you can really have a non latency sidechain. I think this needs few more evenings of testing before posting a tutorial, but those who want to try, might wanna do so.
Download jUltram
Install MIDIYOKE
Go to windows control panel and set MIDIYOKE 1 as your default midi output
(IMPORTANT. this way you will avoid the built in bug of jUltram to resetting the values to the main midi output when a song is saved.
Put jUltram into a send channel
Send your KICK to that channel
Set MIDIYOKE 1 - CHANNEL 1 as the output of jUltram (it should be that by default. I haven’t checked this, but: You might want to use channel 1 just to make sure it does not reset this aswell)
Insert GAINER plug-in to bass track
Select gainer and press Ctrl+M to assign the controller sent by jUltram to the GAIN slider - REMEMBER: 2 USE INVERSE.
note: also you must use MIDIYOKE 1 as the main input of renoise. Also check that record controllers is off.
EDIT: One more step Important to note:
Allways, set MIDI output in jUltram to “TRUE” =)
Also when recording the CC’s for multiple instances, Mute every other send devices except the one you are recording. Or add the CC to control the values manually.
Okay…
Latency free sidechain with 128 instances…
Have fun an I hope this works.
I’m not sure what fixed the midi recording bug for me this time, but use the tip provided by vV. Seemed to fix it for me…
Actually I use the same spacebar mode - but twiddling that button seemed to do something to fix the “recording” of CC when space is pressed… or perhaps I had a midi loopback
Anyhow… Everyone should check this out.
Sidechain (for any parameter on any plug-in) without latency =)
Don’t hold your breath SNS…native sidechaining, done properly, is fairly complex stuff that involves routing of audio signals. Also, sidechaining is in fact several things - compressor ducking, gating, and with extreme settings, the effect known from Call On Me (but I’d bet that Eric Prydz actually handcrafted that, and often, real hardware compressors have MIDI inputs for that extra control - which is essentially the same as the LFO controlling the volume with a custom envelope).
This post made me think. I draw my ‘side-chain’ manually. Good enough for now. But how about this:
Create a meta device with audio input.
Set a minimum and maximum volume threshold in dB.
The meta device will create an LFO based on the audio input between the min and max thresholds.
You can narrow the lfo’s range with a percentage button or whatever to increase it’s flexibility.
The generated lfo can be assigned to a certain parameter as the regular lfo can.
And an invert LFO button would be nice too to create the opposite effect .
Such a feature would most definately have a LOT of creative purposes. Volume controlled filters, side chaining, pitch. Whatever!!
And compared to regular side chain vst’s this would probably be very CPU efficient as well
) the sidechain issue can not be considered resolved. It’s generally annoying though, when I see many threads proclaiming to solve the sidechaining issue that are simply tutorials on how to do curve automations.
into 
and see if this makes a difference when using the space bar.</0x000056284eed4e60>
.