It all depends on what you consider "minor tweaks." I can almost guarantee you that envelope shapes and so forth are configurable elements within the code. It would be insane to "hard code" such things.bonch wrote: Tue Apr 29, 2025 3:16 am If you mean there is shared core functionality such as sample playback, some of the filters, and some of the modulation sources and effects, then that's most likely true and is common sense. However, to claim that these as well as Jup-8000 in particular are "based on Pigments" in the context of the statements made earlier implying that they simply made a new GUI on top of Pigments with a few minor tweaks and gave it a new name is a silly conspiracy theory.
TAE is most likely a component-modeling framework similar to that used by other companies, such as Softube (there was an article about theirs years ago) and probably every other major plug-in maker, in which common infrastructure and algorithms are shared. If you implement an anti-aliasing algorithm or a modulation source or a diode behavior or whatever once, it makes sense to make it modular and reuse it. That's not the same thing as plopping a new GUI onto Pigments, tweaking the filter a little, and calling it a JP-8000 emulation.
So if the supersaw waveform had already been coded for Pigments that would leave the JP8000 filter model, which is likely new, and a few additional bits and bobs. The bottom line is that by building on the Pigments codebase, Arturia almost certainly saved themselves considerable time and effort. Was it simply a matter of "tweaking a few things" under the hood and slapping a new GUI on top? No, of course not. I assume a fair amount of work went into adjusting the Pigments engine to better mimic the behavior (envelope times, velocity response, etc.) of the JP8000. But this is absolutely not a brand new synth. Given the number of synth emulations they need to support, Arturia would go out of business if they took that approach.

