xoxos Effects Suite 2010

[xoxos]

when you have seven beta testers and only one says that

I found most of the fx to be a little noisy and it seemed a ringing sound was consistant with the pluggins

and describes a biquad filter as "weak and plastic" (do you know anything about biquad filter algorithms? how about noise > digital signal chains??) then yes, i didn't really feel the need to further elicit your opinions, and decided my time was better spent engaged in more productive activities.

if you wish to interpret this as an offense, you know you are entitled to your opinion, even if it does sound weak and plastic, a little noisy and it seems to have a consistent ringing sound, i pretended i was shocked coming from someone i blah blah blah.

it just goes to show i have no tolerance for well-thought out criticism

and the regular kvr bullshit is on.

[thoshu]

Yes, kvr's thread's recently become more and more bullshit-liitered.

But btt: beautiful guis alone, just bought 'em.

Good luck with everything, Rurik!

[CinningBao]

.. i should be c++ and steinberg vst sdk after that ..

even though it's quite unrealistic, i hugely misinterpret this as a step closer to writing for cross platform! (ssh, I turned to mac a few years ago)

they _do_ look great though

[Hink]

when you have seven beta testers and only one says that

I found most of the fx to be a little noisy and it seemed a ringing sound was consistant with the pluggins

and describes a biquad filter as "weak and plastic" (do you know anything about biquad filter algorithms? how about noise > digital signal chains??) then yes, i didn't really feel the need to further elicit your opinions, and decided my time was better spent engaged in more productive activities.

if you wish to interpret this as an offense, you know you are entitled to your opinion, even if it does sound weak and plastic, a little noisy and it seems to have a consistent ringing sound, i pretended i was shocked coming from someone i blah blah blah.

it just goes to show i have no tolerance for well-thought out criticism

and the regular kvr bullshit is on.

no regular KvR bullshit because I'm not about that, I wish you the best with your pluggins...we'll just leave it at it worked on my system.

[trimph1]

I have to wait until the end of the month when I get paid---my paypal account is be drained!!!

I love how they work here

[xoxos]

cheers hink, and thank you.

CB - i was prompted to use iplug yesterday, and successfully compiled the gui-less effect example, i understand that it compiles AU as well, so who knows. i'd prefer to use the least number of resources. after the sitar (and relevancies) i'll be doing some non-vst programming in order to pay the bills. the objective is to be writing fourier functions, or something like them, in 2011.

[CinningBao]

CB - i was prompted to use iplug yesterday, and successfully compiled the gui-less effect example, i understand that it compiles AU as well, so who knows. i'd prefer to use the least number of resources. after the sitar (and relevancies) i'll be doing some non-vst programming in order to pay the bills. the objective is to be writing fourier functions, or something like them, in 2011.

'uck me, xoxos, fft plugins, on mac? INCEPTION!
good luck on the bill paying front, in a similar situation myself.. (bill payment necessities)

[Mister Natural]

hada chance to really play with them last night :

the mod/delay thing is TITS - really interesting & subtle sounds inside there, can't wait to play with further

the 'verb sounds terrific, as well

the delay is very "big" sounding - I can't describe it differently, has a really nice flavor

nice work Rurik - thanks

[Ulrik Sander]

Great job with Effects Suite 2010! I've tested the demos - which I liked - however for example the reverb and phaser plugins were a bit too "ordinary" (don't misunderstand me: they ARE quality products) and that I already have those effects in just as good/better plugins.

So before I buy this suite I have a question:

Will you be updating this (semi) regularly with bugfixes and - most importantly - improvements and new functions?

If the answer is yes, then consider me a buyer. I see great potential in this suite if you improve it slowly over time. I know it's a bit rude asking for updates already, but I hope you understand its relevance for me.

PS: While I'm at it - I absolutely adore your freeware VSTs. Many of them I have no use for or don't understand, but your plugins are always stable, creative, experimental and have nice GUIs. Generally they are just plain nice! Keep up the good work!

PPS: You, xoxos, and de la Mancha are IMO the most interesting and innovative SynthEdit coders.

'Nuff ass-kissing!

Peace!

[xoxos]

i try to do as-is for recallability, it depends if there's a good reason. eg. if i ported all of these to vst sdk (who knows..) i'd be inclined to at least offer a discount to license holders for this set. i used to offer discounts, bundles, and send freebies.. i haven't had much overlap in commercial products yet "but my intentions are good" :p

i'm going to fiddle with multiq and see if i can get a wider Q out of it.. i thought i had it at the lowest setting the alg could take (rbj peak filter A is a common algorithm). before release i'd tested it on white noise in a frequency analyser and used it on percussion sounds. two days ago i used it on a pitched part and realised the lowest setting was, as one beta tester observed, much too narrow.

(also.. reluctant to squeeze in a rate meter above the first param on the mod delay.. and people keep asking for a simpler version of the static, but that would be free.)

i completely appreciate what you're saying about ordinary.. i try to avoid product overlap but felt drawn to doing standards. i try to document my subjective views on a product in the documentation so that prospective buyers or users have a more objective impression of the worth of something

and thanks - synthedit has done a lot of people good by giving people a stable environment, catalytic to the art and society in general.

[xoxos]

introducing the story of a poor development choice...

as indicated in the literature, one or two of these plugins have a finite set of relative merits the eq is counted amongst them.. lower cpu solutions are referenced in the included pdf

i had been using a vst wrapping a single instance of the rbj peak filter with narrow q and found it very useful, so the idea was to reduce the vst count for me.. the problem was i translated my Q routine form that code, which was my first shot at them. there's no recipe for the Q coefficient in the rbj biquad paper, so one is left to one's own devices.

i've just put my paying customers through the wringer, sending out two updates for it.. the first with a wider q, the second with a yet wider q.. and a third update will be issued tonight or tomorrow, basically realising that my method was daft (scaling a pow function with a convenient value instead of thinking about it for a minute longer and using an unscaled coeff in the pow function.. cpu difference is negligible but it's the principle of having tidy bits..) the demo will be update das well, though i've advised people to use other eqs.. :p anyway, sorry for bother and fuss.

[xoxos]

the demo file has also been updated now,

multiq's Q has been sensibly recalibrated as 2^-2 to 2^8, which gives it a significantly more useful wide range while still potentiating the extremely narrow Q settings from the first build.

same URL,
http://www.xoxos.net/vst/DEMOeffects2010.zip

[ravasb]

xoxos, I love these plugins. You underestimate how good they are. Your definition of ordinary is far too modest. They sound huge and alive.

[xoxos]

you're very gracious

thank you! though i think i have a denormal to find in one of them that hadn't evinced itself earlier

[brok landers]

rurik, haven't tried them, but again i have to say it: you made biiiig steps in gui design, the look really nice, respect!