TAL G-Verb

[Nug Wrangler]

Wow!^

[c_voltage]

Frankly initially was no special impress, but later observed some fun wild behaviors with feedback, that can make freeze pretty unstatic\interesting. (Despite it can be dangerous\uncontrolable a bit, but i hope it will not fix, let it keep as is pls).
Additionally, freeze body is seems "honest" here - texture depends from space size \ delays config. This imo big pros. (Todays can met opposite method unfortunataly, incl in popular rev's).
(And yes - need press apply button in edit area, stepped here too lol, actually possible palpable variation).
+ in the end tried above mentioned trick (using as pitch sequence) and liked too. Seems can grab.
UPD and grain' tunes automatable here.

[enCiphered]

Wow, after reading that, I think I might’ve accidentally opened a portal to another dimension. I swear my brain just did a hard reboot

[Aloysius]

YODA “You must unlearn what you have learned."

[kraster]

Nice video here.

That's mine. Thanks for posting

I wanted to see how far I could get with just a one note pattern.

[kraster]

Here's another one using Fors Chiral and Microtonic using the sidechain for ducking.

You can get cool rhythms using the bit rate reducer.

I love this thing.

[damstraversaz]

really like this one, some amazing texture. But CPU usage is very high compared to other sound tools.

[perpetual3]

I agree. This has quickly risen to one of my favorite effects.

Here's another one using Fors Chiral and Microtonic using the sidechain for ducking.

You can get cool rhythms using the bit rate reducer.

I love this thing.

[foosnark]

You can get some pretty wild results even just feeding it a droning sine wave. Honestly I feel like the reverb side of it could have been left out completely (fiddling with FDN parameters has never been my idea of a good time)... although the gate parameter works on grain feedback too and can be fun to mess with.

[kraster]

I agree. This has quickly risen to one of my favorite effects.

I just think it's a great combination of effects. It's well capable of doing the Strymon like shimmery stuff, more glitchy,/stuttery/staccoto stuff, interesting wobbly delays, glossy reverbs, dirty lo res reverbs, noisy washes. metallic comb filter sounds etc etc.

The interface is well laid out in general.

The gripes I'd have would be the same as others have mentioned.

I think programming the reverb algorithms is a little clunky/fiddly,. Being able to "paint" across the parameters would be cool.

Some more control over the modulation (colour) would be nice.

Exposing the EQ nodes to host automation would also be cool.

Some kind of numerical entry would be cool for the parameters.

I'd love to be able to route the bit reducer so it could happen before or in between the granular engine and the reverb.

Some kind of saturation control would be great.

These are all "nice to haves". As it stands it's a really fantastic product.

[jamcat]

Oh come on, the white noise is not that bad and it's not nearly as frequent as noise bursts/silences in a lot of other demos.

The white noise is the reverb.

This reverb needs reverb.

[audiojunkie]

We need more examples of the different types of reverb described. Unfortunately, I’m not convinced of all it can supposedly do. I don’t say that it can’t do these things, I’m just saying I need to hear more examples to be convinced of my need for it. That’s why I’m withholding any judgments for now.

[c_voltage]

really like this one, some amazing texture. But CPU usage is very high compared to other sound tools.

Hm, 6-8% for me (with middle 2018 cpu), that seems still in range yet (especially as for not just a reverb).

What regards possible requests, initially wanted to write about some simple management for grain tunes sequence, like saving and randomizing. But then I thought, maybe it's all because of laziness, and changed mind lol.

UPD oh sorry did not knew randomizing here already.

[pekbro]

It does use quite a bit of cpu at times. Still I bought it, since it's interesting and to support TAL...

Hmm, seems like unlocked it uses less cpu, tho I haven't really tried to test that...

[c_voltage]

Not sure if it important, just noted about installs included in zip: vst3 separate content (which supposed to be installed manually) and vst3 achieved thru included installer, give differ content. For example, in manual variant there is also folder "resources" (with file "moduleinfo.json"), what not exists after install. And vst3 file itself have differ size in both cases (6.63mb vs 6.62mb). Although version (displays on plug UI header) the same 126, and i did not see difference in work (incl cpu usage).
Anyway i still use vst2, just decided to check.
Win10

Upd
As request perhaps: noted that freeze become audo-disabled after DAW' transport restart. It seems that would better to make it optionally. For example we acidentally got interesting texture and need capture it "in place", but we stoping playback already (for prepare additional audio track in DAW for capturing). So it will lost.

Upd2 The same for reverb' tail \ transport behavior (well, popular request).