yes i also asked this myself when the term rompler came up. but at the same time i asked myself how other synths do it? e.g. let's tale sylenth1, it has also stored the sine, saw etc. somewhere. so is it a VA synth or not?BBFG# wrote:Well, I wasn't dismissing it. I would call it a rompler with more than one engine though. Simplicity in discussing would be calling it a rompler though, but it unfortunately doesn't set a common ground so that further discussion happens (as it should). It took me months to get past the rhetoric to find out more about the product. Mostly because questioning can be seen as offensive with the same stock of immunized answers being levied against them.Caine123 wrote:and sadly you dont reply to me directly and dont reply to my question instead making some overall statementBBFG# wrote:And I never to my recollection called it a ROMpler ONLY
I can't think of one rompler I've had that didn't have synth capabilities.
But it never stopped anyone from calling it a rompler.
And why does it matter?
Except in some oversensitive reaction that claims it an ad hominem that's its not.i expected more now and a direct discussion.... seems you dont wanna educate me and tell me why it's no VA Synth....
As far as a VA. I have no problem with the term as a set of being virtual. One however could ask, "what is producing that sine?" and then the term breaks down also, except by being a virtual representation more than analog itself. Where are those sines stored?
my take is that VSTs with set sine/saw etc. have this somewhere stored the info in the code compressed or whatever, unlike wavetable synths which have WAVs etc. which are open normally to see.

