? patching feedback loops in GP3 not possible ? seems not

Hi there,
i tryed to patch a feedback loop. The idea would be to incloude some more VST-FX within that FB loop, ofcourse.
in fact my test patches had a gain control inclouded.

the results were mixed, but finally allways led to think that its not possible,
and something with GP3 is shuting down if i patch a FB.

first i had a audio signal going, but way weaker as thought,
iirc turned this patch automaticly to shut off.
I had in all three FB test patches finally shut downs of the whole audio,
until i removed the feedback patch.

so, there is no way or workaround to be able to patch a feedback loop in GP3 ?
( i finally can follow if this was programmed by purpose, for security reasons :wink: )

i finally had one moment where the patch immediately and with NO control begun to scream ! VERY load !!
luckily were my phones set to quite a low level…

( its one of the things i´m deeper into to patch feedbacks, hehe )

What does this mean? Could you please try to explain in more detail?

ahh, i see:

patch for example your audio signal to a mixer module,
and then feeding the audio back from the output of that mixer to another input of that same mixer,
with incorporating more VST-FX blocks inbetween that connections.
(just to create a picture ! don´t do it…or turn your speaker/HP Volume way down ! )
so: audio out of the mixer ----> patch into a FX, for example a BP filter, ----> then patch back into a another input of that same mixer.
now we have a “feedback-loop”.

Its a common “patch-technique” within modular synthesizers !
finnaly, do we deal in the FX world with many FXes that have such Feedback path incorporated within themself.
Filters, Delays, Flangers, just to name a few.
The parameter usually called: Feedback.

“patching” such feedback path yourself with the help of a mixer,
is from all i know and read, the same ( as FBs in FXes/Modules)
( though, working purely digitally difffers, than working in the analog realm )

Reason why i´d like to patch a “feedback loop” myself ?
it gives the user the ability to “patch” way more complicated feedback loops than you´d ever find in any common FX.

for example combine a BP Filter or filterbank with a Frequenzy shifter and even add another delay into that feedback loop.
I do this things in my modular synthesizer.
It allows to create your own resonating based synthsis models to say so. Or other wild things.
While donne the right way, does it become absolutely controllable and “workable”.

finally, will sofwtware never be the same ! thats a given fact.
but another fact is that we have in software way more function blocks at hand.
…for example are compressors absolutely common in VST land, but still not so much in modularsynth land

Meh - just use a virtual multi-channel audio interface - send stuff out of a VST to an output and then receive it back in on an input.

I don’t even want to think about what that will sound like.

thats an option i allready considered in regards to other uses, ( since my computer is old, but finally quad core)
but for creating feedbacks as such is it not an option !
(despite the fact that latencys would play here a role too)

my point here is still:
whats the situation within GP3 ? are there some limis programmed into the software by decission ?
i might mail them directly and ask :wink:

The virtual audio driver, Blackhole on Mac adds zero additional latency, for example. But in this digital world, there will always be latency. It’s not like using a eurorack system with control voltages.

No need to mail — I am one of “them”

Unfortunately, our internal implementation details are not public and they change from time to time as we do more optimizations.

1 Like

Oh nooo, really? :cold_face: (it is probably not that easy for keyboard solos)
image
image

1 Like

Touché

@dhj
Could you let “them” know that on Earth we say “deactivate” :wink:

Ha ha ha…the person who wrote that wasn’t on earth at the time!

David Vincent has perhaps seen it… but David H. J. not :stuck_out_tongue_winking_eye:

The Invaders was a great show.

The spelling error has been corrected

1 Like

Thank you ! thats interesting.
i´m not shure how far i can come with loopback which i have.

and wait, now i understand !
this type of woraround should do it.
i think i had a wrong picture in mind when i sayed it won´t.
( and i was under the impession that loopback would only provide two channels)

i will have to dive into this :wink:

yes, i´m aware :wink:
but patching with feedbacks is working within digital realm.
minimum latency is 1sample.
at least that was the doable with Clavias ( nord modular) G2

Thanks ! i´ll see where i land…:wink:

Also this is a very old topic, I just want to give a hint to anybody interested in feedbacking a signal that this IS possible via the global rackspace!

Although after trying out I will definitely NOT recommend to use this feature as it has to be set up very carefully and ALWAYS protect your gear and your ears when experiment with this:

If you route the plugin-output to global rackspace and there just connect this signal to 2 global returns, you can use the second one to refeed the signal to the same plugin.

Here my example screens to make things clearer:
Global Rackspace connection:
You can insert further plugins into the “3” path if desired…

Lokal rackspace:
I “replaced” inputs with the audiofileplayer.
As you can see I can use both (L+R) instances of the compressor in row (see different VU-Meters!) within the same instance!

I searched for a way to do something like this as I wanted to use an stereo vst-eq for mono instrument (bass) and double up the controllable bands in one GUI.
To be on the safe side I decided to load up the eq twice and use it the “normal” way as I think this feedback loops are way to dangerous to use (especially when you perform live)

So again, nearly everything is possible with GP but not everything is necessable!

2 Likes

interesting ! thanks for the heads up.

i use BlueCats “connect” plugin to do so.
It allows to create a feedback within a Rackspace, without “disturbing” GPs security feel. ( to put it this way, haha)

th enote you forgot to set:
ALLWAYS PLACE A LIMITER within a feedback path
:wink:

i must add, my results trying to create feedback “accelerated” FX patches was not so successful as hoped. Looking from a musical standpoint to it. No clue why.
since i was a modularsynth specialist, patching with feedbacks was nothing new to me