Ah_Dziz
Well ok after additional exploration my initial "complaints" were changed a bit.I'd guess it has something to do with the "counter" used for the parameter that stops the same sample from playing over and over (don't have it in front of me).Well, need say, initially personally me was afraid about cpu usage, but by fact this is pretty not high, and very depends just by two parameters - polyphony and particles amount (as mention already). So, if take default values (8 and 200, resp.) - it's just about 3-4% eating. (If even less values - near to zero usage).
Also should note that during idle state (no loaded samples, or no playbak/processing) it's zero eating too.
That good.
From first catches - won't load mp3 (although flac for example load ok).
UPD: also there is some relation with host' transport by some reason - seems plugin give different result with during playback and with stopped transport state. Although i not see obvious reason for this. (this is with empty mod section). Not sure if this by design (?)
UPD2 As well, transport restart can change sound character of one and the same setting pretty noticeable.
Resuming, i would say this is thing for rendering "in place", in current state at least.
Edit: variation is the parameter
(looking ahead - no, this is not because Variation param)
Instead, it is turned out that there is some specify in work of "Spect Weight" parameter in 0 value.
Here I think could limit to a few phrases, but i already prepared info anyway, so, that it doesn't go to waste, better also post it here that anyone can explore this behavior and decide if it important (I would put this paragraph in a spoiler to reduce the size, but I can't find how to do it):
[spoiler]
Spect Weight "zero" behavior, successful reproduction variant:
1) Load plugin (default state patch)
2) Import single wav (let's it will be speech sample about 15 sec length) to corpus.
3) Let's use the same sample in DAW' track (as incoming audio for processing resp)
4) Set "Polyphony" to 1 (and ok, Variation to 0)
5) Now run transport, and during processing (transport playback) if we set (in realtime) "Spect Weight" parameter to minimum (zero), we will get not so big changes
6) whereas if now we - first stop playback (by DAW transport), and then run again (not necessary from start, even just continue) - changes will be drastically.
Better reproduce exactly with 1 polyphony, and with single\the same wav (in corpus and for processing).
Hovever, later i found, that button "Particle reset" (in the upper left UI corner) make the same effect as transport restarting (with Spect Weight at 0 resp).
"Particle Reset" button explanation (from user manual):
So, yes, here mentions zero value of Spect Weight, but with no transport relation.The particle reset button can be used to randomise the states of each active particle, which forc-
es the plugin to choose new sounds. Experiment with this while using a high stickiness and a low
spectral weight to hear the effect. You can trigger a particle reset by clicking the particle reset
button, or by pressing ‘R’ on your keyboard while the plugin interface is focused.
Note: If Spect Weight is set to 0.0 when the particle reset button is pressed, you will experience
‘grain splattering’ where the algorithm is rapidly switching between random grains. To fix this,
simply increase Spect Weight to a non-zero value.
Although yes, the assumption is that restarting transport produces the "Particle Resetting" effect seems pretty logic lol, but nonetheless, being non documented, such implementation of this relation may be non obvious for user.
[/spoiler]
======================================
Next behavior example (transport related too) - already not so conditional as before, but rather obvious issue. This is when we want use plugin in, so to speak, modular manner. Ie with no transport playback at all, by using generated incoming audio.
Agree that this is not an exotic scenario at all, given the aesthetics of such plug.
And this time without Spect Weight "zero" factor (this is will be at normal default, 10.00 value).
And no rules about incoming material \ imported to corpus material, difference will be noticeable in any case i believe. Ok, let it be again the same single sample in corpus. (but regards incoming ie generated signal - can be any sort of..synth etc, as you convenient).
Now values set (simple all to minimum, except Spect Weight):
- Polyphony 1
- Variation 0
- Particles 10
- Stickiness 0.1
- Amp Weight 0
- Spect Weight 10
And now just hear difference of result' processing With and Without transport playback.
(Fun thing that often i find more interesting result in stopped state, well with described config at least)
==============================================
Like summarizing (if no time to read) - there is probability to get completely different sound from one and the same saved preset, depend from DAW' transport state. (Despite lack of obvious\documented reasons for this).
Statistics: Posted by c_voltage — Sat Feb 08, 2025 4:27 am