Aggressor - free VSTi - new version since Sep 6, 2006

[snooky]

why would you try to sell this synth??
Don't be so 'effin greedy mate, put it out there for free

because i'm young and need the money. seriously, i'm a very poor student and spent so much time on it - and even i can't live from air and love alone. and i see, that there are quite expensive commercial bass-synths out there, which offer less features than even the free demo of aggressor. actually i see it more as a kind of donation which gives the user some additional feature. take also into account, that i offer a lot of freebies on my website.

There are far easier ways to make money than software...your synth will end up being cracked and you'll feel depressed.

I'm telling you this so you don't get your hopes up.

Any kind of "art" shouldn't be created to earn money

You're just fooling yourself if you think your synth will pay the bills

[Music Engineer]

There are far easier ways to make money than software...

yes, i see. but when doing some stupid fulltime job, there will be not much time left to code new plugIns.

your synth will end up being cracked and you'll feel depressed.

no, i won't feel depressed. actually it does't need to be cracked, as i am not intending to waste my time in learning about and implementing a copy-protection for the full version - i'm a music and sound-design enthusiast, not a programming nerd. as already stated - i see the price (i'm targeting the range around 30 euros) more as donation

Any kind of "art" shouldn't be created to earn money

fully agreed. if money is the only motivation, than usually only shit comes out - we just need to take a look at the commercial music charts. i think sound-design and also instrument-design is certainly a kind of art, but doing all the labourious coding is - believe me that: WORK

[snooky]

OK, if you feel that the ~30 euros is more like a donation, I can agree that it's an ok way to get some in return for your work. It depends on how crippled the demo version of the synth is.

You seem like an honest guy, so good luck with your synth!

[original flipper]

HI

You should have an FXB loaded with your pre-sets, it is a real drag having to load up FXP's ...

The CPU hit will also make it hard to sell this - at this point I would see if you can trim something down as it is too hungry.

Flipper.

[Music Engineer]

It depends on how crippled the demo version of the synth is.

You seem like an honest guy, so good luck with your synth!

thanks. you can see, how crippled it is: it lacks the GUI-elements for the 3rd oscillator (the osc is still there, and if you load a preset which makes use of it, then it will play - you actually also can still access the parameters from the generic-gui or via automation-events).

maybe - if i implement user-sample-loading for the oscillators, i will leave that out in the demo, too

[Music Engineer]

HI

You should have an FXB loaded with your pre-sets, it is a real drag having to load up FXP's ...

yes, i still need to organize the presets and put them together to fxb's

The CPU hit will also make it hard to sell this - at this point I would see if you can trim something down as it is too hungry.

i already found some points, where i can trim the CPU-load down a little bit without sacrificing any quality. i'm not sure if it will be significant, we'll see.

[Music Engineer]

i just uploaded a new demo-version of my current synth-project aggressor. i implemented a few new things:

-anti-aliasing for the oscillators (multisampling)
-anti-aliasing for the distortion unit (oversampling)
-i could reduce the CPU-load (at least for sounds, which do not exploit all the features of the synth)
-i organized the .fxp presets to .fxb banks (but i'm not yet finished with that)

the links are as before:

www.braindoc.de/vst/AggressorDemo.zip

for the synth itself, and:

www.braindoc.de/manuals/AggressorEn.html
www.braindoc.de/manuals/AggressorGe.html

for the manuals (english and german)

...have fun again with this beast (now hopefully even more)

[sonicfire]

nice plugin @braindoc!
what are you using to code your plugins? just curious.

[lucasherrero]

Intellligent answers man. i can't test the synth yet, but i will do it today.

good luck!

[Music Engineer]

nice plugin @braindoc!
what are you using to code your plugins? just curious.

i'm using ms visual c++

edit:...ahh, and good old corel draw 7 for the GUI.

[linzatti]

I will give it a spin!

[jmh]

Sounds impressive from the specs, this will go into testing now

I wouldn't go on sacrificing the quality just because of "high" CPU utilisation - that's the price for quality and there are more users than just me who prefer quality over small CPU usage. Almost every VSTi that sounds great to me uses more CPU than the run-of-the-mill synths. And in a few of them, the difference with processing everything per sample as opposed to the usual way of doing things, is why. (Something like Sytrus with HQ envelopes turned on demonstrates rather well - with the disclaimer that I don't know whether this results in processing the envelopes per sample).

And not everybody prefers or even want a mod matrix, thought I'd give an opinion on that as well.

There's always other synths to try if mod matrices and low CPU usage is important. They're not be-all-end-all things for some of us

Regards,

JMH

[Music Engineer]

I wouldn't go on sacrificing the quality just because of "high" CPU utilisation - that's the price for quality and there are more users than just me who prefer quality over small CPU usage. Almost every VSTi that sounds great to me uses more CPU than the run-of-the-mill synths. And in a few of them, the difference with processing everything per sample as opposed to the usual way of doing things, is why. (Something like Sytrus with HQ envelopes turned on demonstrates rather well - with the disclaimer that I don't know whether this results in processing the envelopes per sample).

Regards,

JMH

this exactly my philosophy - first: doing it that way, how i think, it should be done right - may it cost what it costs. and then later let's see, where things can be done more efficiently without loosing quality. i don't know at the moment, if you are also following the development-forum, however - recently we discussed this enveloe-issue there in the context of alias free oscillators. i stated there, and i'll state it here again: imho, a very fast envelope has an impact on the sound in the time AND in the frequency domain, as it contains frequencies in the audible range (the faster it is, the more it approaches an impulse). so, for an amplitude envelope, amplitude modulation sidebands will appear. fast envelopes are audio-signals.

as for the cpu: i'm using an outdated compiler at the moment (from visual c++ 6.0 which is anno 98) - i hope, it will get better when i get the new version of visual c++ running (at the moment i have some problems with it).

BTW: the gui may flicker, when loading a .fxb-bank - the synth seems to be set to each preset once - this may look a little bit dangerous...also it ends up at the last patch #31 which is empty - the real presets are above.

[sonicfire]

nice plugin @braindoc!
what are you using to code your plugins? just curious.

i'm using ms visual c++

edit:...ahh, and good old corel draw 7 for the GUI.

Hut Ab!! Ich komme noch nichtmal mit Delphi + Tobybear VST Template wirklich zurecht!

[Music Engineer]

Hut Ab!! Ich komme noch nichtmal mit Delphi + Tobybear VST Template wirklich zurecht!

tja, also von delphi hab ich auch keine ahnung.