Quote:
|
No crazy 4 channel setups cuz the plugin allocates that for you when you load it.
|
Jesus Christ. You really are a moron aren't you?
The Reaper manual tells you to create a 4 channel track to sidechain. If you weren't so busy trying to engage in a stupid kiddie daw war maybe you'd have time to actually read that part of it.
To send anything to "3/4" you first have to HAVE a 3/4 on the Reaper audio channel.
The plugin does not create 3/4 on the Reaper audio channel.
Your "plugin loading allocation" above is pure bullshit.
Quote:
|
Explain to me how i need to make 4 channels in Reaper on the key track??
|
Not the key source track, the key target track with the comp that's being keyed. How do you think you send to 3/4? By making the track a four channel track. Otherwise, how would you send to 3/4 on that channel if it has no 3/4?
I'll let the person who wrote the software tell you. These are his words, not mine. Maybe you'll listen to him?
Quote:
| first make the track that it is in a 4 channel track (by setting it in the track I/O dialog).. then you can set the JS effect to sidechain input, then send another track to that track, and in the send you can specify to send to channels 3/4...
|
Before you can "...boom, send to the key input..." you have to have a second audio path to carry the key source audio. Your 3/4 on the channel is that second path. You can't just send audio directly to the plugin's 3/4 inputs from anywhere. You have to go
through the original track on a secondary audio path (it's 3/4) to hit the key input, the plug's "3/4.
Just like the
method used in Cubase SX I spoke of earlier that inspired you to call me a crackhead. A plugin inserted on a quad track or group using the second pair to carry the key audio signal to the plugin on that channel.
Go away.
They're both great daws. I love them both.