Might be your *init preset* that have changed after well ... 'something has happened' . As I understand it, the real parameters values in your *init preset* dont reflect the knobs values, and when you move the knobs, they return to their actual state. A possible turnaround would be to change the values, so in a way return to normal behaviour, then save your own init preset. And relaunch it to see if it plays normally. It's the same thing for the delay I think - just an intuition- : Your init preset has been touched in some ways.ariston wrote:Oh, that's good! What about the strange behaviour of the init presets whenever I launch the plugin? Can you or anyone replicate that at all, or am I the only one with this bug? The sound is really loud, noise comes through even tho the level is turned down, and once I move Filter env knob or switch presets, it's back to normal.
And the FX section has something similar: I'll turn up the delay send on a sound and won't hear a thing (delay is of course turned on) UNTIL I move one of the delay config knobs... then it's there.
It's certainly not a showstopper, but kind of curious anyhow.
Hope I'm not bugging you too much with these bug reports.
One more question for today: are you considering improving on the distortion/bitcrush/SR module? I get that the distortion is really subtle, but I feel it needs to be more pronounced in order to be useful... maybe even include a few disto types. Otherwise, I'd just see myself disregarding this section and using secondary plugins. Oh, and some sort of compressor would be REALLY useful. Again, not some kind of subtle, delicate compression, but something pronounced, all-buttons-in so to speak.
Another way to confirm all that is to see if the delay etc behaviour is normal with any other factory presets.
Disto etc : As I said in another ancient post, there's now a legacy/compatibility problem with existing factory and user presets wich prevent us to totally change the behaviour of these modules. The only thing that might happen in the future is to mod it I think, ie add other disto types ( so the current one would be for example Disto A, but there could be disto B, C etc ) Tbh, we completely lack time to do this at the moment, but it *could* happen in the future.( though I cant guarantee that). This said, the disto (and filter drive) in their current incarnation are subtle, and some more violent ones might be desired I agree, (like in Largo that I enjoy a lot) but, still, they are imho usefull. I'm currently reviewing the Wave Alchemy samples, some of wich will later be included in StiX : There are very subtle variations of 'a 808 snare' for example. If you listen to them one by one in isolation, you might think ' well, not so much difference', but then if you actually use these different ones in a pattern, the overall sound of the pattern has a quite different *quality*, *character* etc, and you are surprised that, depending on whether you choose this or that *old 808 snare sample*, your groove will work wonders, or just average. I understood better a lot of things when listening to WA work : There's as much power in subtle things in the drum synthesis department than there is in global synth synthesis. Well, a very long way to simply say : Sometimes the devil, or angel, lies in details
Edit : Forgot the compressor part
It's something we have considered from the beginning. And it's related to cpu charge. In it's current incarnation, I think we have a very good ratio regarding uncompromised_audio_quality/CPU use. Adding N compressors would mean adding n*c cpu hit. Otoh, everydaw has now compressors, so the only thing to do is to insert one on stix bus(ses) in the daw. So if todays cpus were more powerfull, there are good chances that we would have added comps, but we feel we have to limit StiX to a fixed *raisonable* cpu print. Maybe in the -not near- future.
) and shows the saved settings
), or Kontakt.
