New Recirculate plugin by Eventide/Newfangled Audio

[Funky40]

We .......

ahh, the coder.

i have some critics or suggestions, as you like.
=> this is solely vs. explicitly jamm-related setups.

The time parameter scaling vs. CC mapping is a f.ck. i´m sorry to say.
Refering vs. small time values !
( to create a jammable setup that incloudes smallest times vs. bigger ones)
(i refer +- to both time values, first tap, the later tapps)
I patch in gigPerformer (Host)
There i can compensate for unideal or screwed up parameter scalings.
But with your recirculate, i had to take it into the extreme. And its still not perfect.
Thats seldom to see such unrefined parameter scalings.

Also are the parameter-names on the listing vs. the CC mappping dialog all over the place.
....and i think i dealt with some other problems vs. CC mapping vs. the time parameters.....plus the *initial* hassle with that fresh plugin vs. new names, linked, unlinked, etc. .
The amount of time spent to just CC map both time parameters was insanely high.

The related (time related) names are spread all over the place.
That added alots to make the whole CC mapping immensly time consuming. ( in a situation of a allready given confusion)
some nice shuffling of the listing vs. the parameter names would make this work quite a bit easier! Anyway for first-timers.

The sound is great ! the capabilitys vs. jam-specific setups would be great.
But the parameter scaling would need to see some rework for such uses.
Anyway for everybody who would want to do so, using a DAW, and not GigPerformer.

while GP has a freely drawable curvature feature. its still hard to get such extremly flat curves out. And Recirculate is still not optimised to 100% -even with my curvatures- vs. the finger-feel vs. jammin

here, a screenshot of my drawn correction curvature:
(this is extremly flat vs. the first 1/3 of the travel)

Recirculate_time.png

i like the sound, i like the capabilitys.
It´s a great work otherwise !


This all might not play a role for traditional static uses in a DAW, though.

[DGillespie]

That's an 1/8th note first hit, with a 5 repeats in a half note on the right channel and 7 notes in a half note on the left channel. You can easily do this by grabbing the 5 or 7th stem and snapping that to the half note division. (Placing 5 notes in a half note is called a 5:2 polyrhythm).

Thank you for replying. I don't understand.

Which part is confusing?

[_leras]

That's an 1/8th note first hit, with a 5 repeats in a half note on the right channel and 7 notes in a half note on the left channel. You can easily do this by grabbing the 5 or 7th stem and snapping that to the half note division. (Placing 5 notes in a half note is called a 5:2 polyrhythm).

Thank you for replying. I don't understand.

After the initial delay 1/8 here, you can then have different delay times on L and R.

The gui imahe has 0.4 and 0.29, which make 5 and 7 delay repeats over the full whole note in total. (Well two divided by these numbers is 5, 7)

So each side of the delay has a different timing.

You may be thinking polyrhythms differently e.g. in something like Tremor, where you may have kick looping 4 notes, but HH looping 5, making an overall unique pattern only looping every 20.

[elxsound]

That's an 1/8th note first hit, with a 5 repeats in a half note on the right channel and 7 notes in a half note on the left channel. You can easily do this by grabbing the 5 or 7th stem and snapping that to the half note division. (Placing 5 notes in a half note is called a 5:2 polyrhythm).

Thank you for replying. I don't understand.

After the initial delay 1/8 here, you can then have different delay times on L and R.

The gui imahe has 0.4 and 0.29, which make 5 and 7 delay repeats over the full whole note in total. (Well two divided by these numbers is 5, 7)

So each side of the delay has a different timing.

You may be thinking polyrhythms differently e.g. in something like Tremor, where you may have kick looping 4 notes, but HH looping 5, making an overall unique pattern only looping every 20.

I think he means, why is this different than multitaps.

At best I could see describing it as having the ability to create polyrhythms using per channel multitaps.

[elxsound]

By the way, nice job on the delay. There’s obviously tons of delays but the included features are fairly nice.
I only used it a bit yesterday, but so far finding the drive and noise a bit tame at max. I’m hoping it’s just not enough sleep and user error.

[Uncle E]

I think he means, why is this different than multitaps.

At best I could see describing it as having the ability to create polyrhythms using per channel multitaps.

Yes. I feel like there's something really amazing going on yet all I'm seeing is multi-taps.

@_leras, I wasn't thinking of Tremor polyrhythms but now I want that!

[DGillespie]

I think he means, why is this different than multitaps.

At best I could see describing it as having the ability to create polyrhythms using per channel multitaps.

Yes. I feel like there's something really amazing going on yet all I'm seeing is multi-taps.

@_leras, I wasn't thinking of Tremor polyrhythms but now I want that!

Ah, yeah, so there's two things really.
1. The big difference between multitap and feedback delays are that multitap delays are all feedfoward, so you can add some filtering and distortion to the audio once, then put it in the delay line and pull it out at various times and mix them together. This way everything gets hit with the effects just once. A feedback delay, on the other hand has one set of effects, but they're in the loop, so each repeat gets mixed into the signal and run through the effects again and again. So, for instance, the tails get darker and more distorted each go around. That's the magic of feedback delays (imho)>

2. The difference here was that we unrolled the first echo so it can have it's own time before sending it to the feedback delay. We did this because we found that the timing of that first delay was really important to your sense of tempo in the song, and that once you'd grounded that first echo, you could have more fun with the following repeats. That said, because it's a feedback delay they all have to be the same as one another (at least per channel). Which is more restrictive than a multitap, but I think in a way that works out pretty well.

[Uncle E]

A feedback delay, on the other hand has one set of effects, but they're in the loop, so each repeat gets mixed into the signal and run through the effects again and again. So, for instance, the tails get darker and more distorted each go around. That's the magic of feedback delays (imho)>

Great! Yes, that’s why people love the Deluxe Memory Man. Every time the delay feeds back, it gets more filtered and distorted.

The difference here was that we unrolled the first echo so it can have it's own time before sending it to the feedback delay.

Got it! So it’s 2 delays per side, where the 2nd delay is off the 1st and has the repeats. The Hughes & Kettner Replex did that and it was lovely.

Thanks for answering and for being here!

[Zoopy]

I'm a newfangled fanboy and I cannot use this UI at all

[plexuss]

I'm a newfangled fanboy and I cannot use this UI at all

Poor you.

[martinjuenke]

I'm a newfangled fanboy and I cannot use this UI at all

That's a realy pity.

[DCrown]

After demoing I think it's a very good plugin, but cpu usage is even higher than Avenger (!), so fun factor and usage limited.

[martinjuenke]

After demoing I think it's a very good plugin, but cpu usage is even higher than Avenger (!), so fun factor and usage limited.

Buy new CPU now

[DCrown]

After demoing I think it's a very good plugin, but cpu usage is even higher than Avenger (!), so fun factor and usage limited.

Buy new CPU now

Of course, I will, for one plugin only haha
But suprisingly there's no latency, you can track with plugin engaged

[Rickskii]

I have replaced a couple of different delays in projects with no change in CPU on my M1. Nice flexible delay, thanks.