looper input : as it is on my grid i.e. getting the sound processed of the input 1, the input 1 processed is going then on output 1/2 (with some more processing)
sending this loop to a new row with some other processing dedicated only to loop material and sending it to out 3/4
Here is a picture to explain it :
Is it possible to do with quadcortex ? I’m trying to figure out the routing mode of the looperX to solve it… but it’s very confusing and the actual documentation is quite lean about this subject.
You can use the transparent blend from the utility blocks for this.
Place it on row 3, select Looper X as input source and blend to 100%. You should see little indicators on the right of the looper and on the left of the transparent blend which tell you they are connected.
Thanks a lot derdoe!
Unfortunately, I was looking for a solution with a looper not playing the input signal, only the recorded one (think about the ableton live looper if you know it). I was hoping that the routing option of the looper could be the solution, but it’s quite hard to understand and the documentation is not clear at all about this.
But I’ve discovered with your help the “Transparent blend” (no entry about that in the documentation ), it can be handy. I’ve to figure out a solution with that…
Ah I see. I was so distracted by the red arrow that I missed the “dedicated only to loop”
I think it would need a way to disable playback of the input signal, but as far as I know that isn’t possible.
If it was possible, you could use the transparent blend or splits to tap into the signal before the looper and have the looper only play back the recorded loop.
I found a feature request for this, but it didn’t really gather a lot of votes:
Thanks for this new feature request! It’s exactly what I’m looking for actually (besides other things). Not a lot of votes, but I’m pretty sure it’s really easy to implement.
Moreover, have you guess what’s the point of the routing mode of the looper ? I was wondering if it could be the solution. But for the moment, with some tests, it keeps being quite hard to understand the usage… If someone has a ressource about that, I’m really interested!
I also fiddled around with the routing mode and found it confusing (and poorly documented).
My best guess is that you can switch to either one input which skips all the blocks before the looper in the grid, or one output, which skips the blocks after the looper and sends directly to the output.
I don’t really see why you would do this and if you do, why it’s better than just directly routing the in/out on the grid, but maybe others can comment on that.
My hope to find a solution made me thing that it could be with a smart usage of the routing option. But my experiments led me to the same conclusions as you. So I will wait to have the dry volume feature implemented !
), it can be handy. I’ve to figure out a solution with that…
!