Yeah i reported the parameter issue on GS. The dev didn't even understand what i was talking about. So i explained what the problem was in more detail, even linked to the VST3 SDK pages where it's explained for devs how to fix it (using 1 or 2 lines of code). But still silence.Yeah a few observations after testing:There sure are a lot of points of frustration and dissappointment with this synth.
Initially i was impressed with the sound, but after some hours of testing i ran into more and more issues. It's simply not reliable, lacks a lot of basic functionality, and overall feels unfinished.
-Crackles and spikes aren't great, however I've seen that the devs say they are addressing this soon, so looking forward to that.
-The control values exposed to the host aren't very useful. Most things are a range of 0 to 1. This is not how you do it. When you automate a waveform parameter that has 4 settings (se.g. sine/square/triangle/noise), you don't expect to see 0, 0.3333. 0.666 and 1. Use the actual words so we know what we are automating. If the fine tune goes from -10 to +10, use those values, not 0 to 1! I cant' believe any dev still does this and thinks it's ok. This isn't just about seeng the real value of the parameter when you are writing automation (although that's reason enough), most hardware also uses these value ranges, such as Ableton Push, Ni Maschine and Komplete Kontrol, Novation, Nektar etc.
-The sensitivity of the controls are inconsistent for trackpad scrolling. The upper slider type controls and the knobs aren't bad, but the jupiter hardware style sliders are very sensitive to trackpad scrolling. Would be good to calibrate for using on a laptop.
I'd need to see the first two fixed before paying, but if those were fixed I'd buy at the intro plus black Friday price. I would not pay full price.
Fixing the parameter issue would also fix Midi program change issues, as well as other Midi CC issues which are being reported all the time. It only shows how bad AA is at coding a synth.
The parameter issues have been reported many times before btw, as it's a ongoing issue with all their products. Still no fix after many years, and AA being the only one who still has these issues.
The crackles are due to cpu issues which are supposed to be fixed. I don't have high hopes for that tho.
The clicky behaviour is still not fixed, and that seems to be completely cpu unrelated. That one alone is reason enough for me to not buy this synth. Weird however, is that ppl reported this including sound examples, yet some fanbois and "beta-testers" don't even hear those clicks in the audio examples
The worst thing however (and i don't understand how that went through beta) is that offline rendering doesn't work ; automation and Midi control is not rendered correctly, unless you use real-time rendering/export. This means that anything you do can sound different after rendering, which is ofcourse a complete no-go.
There's many more issues btw. If i had more trust in the dev i would probably report them. But unfortunately my years long experience with AA, and the constant denial of issues by the dev, makes me simply not care. This post is already way too much attention for this trainwreck....
Statistics: Posted by dionenoid — Mon Dec 09, 2024 1:09 pm