Routing Matrix issue - no signal when returning send from an effect [solved]
andioak last edited by andioak
Hello there HISE:rs. I got a little issue that might be a misconception of the construct of the audio paths on my part, but let me explain.
I want a normal send-return to and from a Reverb plugin. So I got a few plugins going first, then I do this:
1: first a few plugins...
2: Routing Matrix #1 -- send (extra blue channels) from 1-2 to 3-4
3: reverb plugin gets the signal by tapping into channels 3-4, so far so good.
(since sending or "returning" the output of the reverb does not work, and we cannot route any channel to any other channel, via send or direct, I instead add the next plugin)
4: Routing Matrix #2 -- this sends a parallel send back to cannel 1-2 from the 3-4, after the reverb is done giving it´s thing.
5: No signal. Nothing is going into the channel 1-2 chain again. I want the output of the Reverb to go back into my channel 1-2 chain for summing through a limiter and final gain stage. Like any normal mixer procedure.
Image of the scheme:
The image shows the first routing matrix sending using a "send", blue lines, from 1-2 to 3-4. Then "Reverb1" is using the channels 3-4 for adding reverb. But the return via the next Routing Matrix is not audible and does not give sound.
Is it not possible to return the signal using my second Routing Matrix plugin?
andioak last edited by
I found the solution to the issue. The returning signal did not have anything to hook into, as I was using only a send. That apparently does not hook into anything. You need the 3-4 from the Matrix plugin to go out to 3-4 of the container/bus/output too. Or there is nothing to tap into for the send:
Now I´m getting sound and can set up a send FX contra "dry signal" path, without leaving the container I´m in.
Lindon last edited by
andioak last edited by
Yes, lets. But to redesign this one, the Routing Matrix, would be a good idea. The clarity of "taking from one stream" and "putting it into another stream" is lacking. My preference in routing is a origin and a destination. This case would be this to me, using 3 rows of connections instead of 2:
- input stream - choose a stream to tap into.
- routing matrix interconnection slot.
- destination output slot.
- Connect "Container 1-2" to "Routing Matrix plugin input 1-2".
- direct / redirect "Routing Matrix plugin input 1-2" to output, for example "Container 3-4".
We now directed the sound in one "beginning to end" path. Easy to understand. The current one is mysical and in that sense, dangerous for the listener of both hise and it´s intended output product.