Developer Challenge Submissions & Voting Now Available

[nuffink]

Can we please have an indicator if the plugin was created with Synthedit. It's important to some people and, in keeping with kvr practice, they deserve to be told.

[realisation]

Nothing to hide here, made in synthedit - AND proud of it, what a great piece of software.

Mine tells you on the credits section in the manual.

[Time Control]

nuffink
I think it speaks volumes that people need a little logo to tell them if it was made in Synthedit or not.
Ironic and even amusing considering how important it is to you.
It goes without saying that marking entries into 2 categories (SE / Non-SE) would impact the outcome of voters. Especially ones LIKE YOU!
I think it would be funnier to have everyone try to guess which ones were done in Synthedit and reveal it at the end. Too late for that now though as the documentation gives it away and the hardcore VST junkies already know which devs use SE.

[nuffink]

nuffink
I think it speaks volumes that people need a little logo to tell them if it was made in Synthedit or not.
Ironic and even amusing considering how important it is to you.
It goes without saying that marking entries into 2 categories (SE / Non-SE) would impact the outcome of voters. Especially ones LIKE YOU!
I think it would be funnier to have everyone try to guess which ones were done in Synthedit and reveal it at the end. Too late for that now though as the documentation gives it away and the hardcore VST junkies already know which devs use SE.

You're new here aren't you?

[Lagrange]

So many toys such little time to play...

[realisation]

nuffink
I think it speaks volumes that people need a little logo to tell them if it was made in Synthedit or not.
Ironic and even amusing considering how important it is to you.
It goes without saying that marking entries into 2 categories (SE / Non-SE) would impact the outcome of voters. Especially ones LIKE YOU!
I think it would be funnier to have everyone try to guess which ones were done in Synthedit and reveal it at the end. Too late for that now though as the documentation gives it away and the hardcore VST junkies already know which devs use SE.

You're new here aren't you?

heh, i think we have a misunderstanding here..

..I wonder if reaktor released a VST export function whether that would get the same treatment..

I don't think it matters, as long as the plugin works - its a freebie after all If i had more than 15 days to put my entry (say, a year) then i would have done it in c++ and had it cross platform. But then, would i have came up with the idea in the first place?

There ARE so many toys, and less than a month to try them..

[Time Control]

nuffink
I think it speaks volumes that people need a little logo to tell them if it was made in Synthedit or not.
Ironic and even amusing considering how important it is to you.
It goes without saying that marking entries into 2 categories (SE / Non-SE) would impact the outcome of voters. Especially ones LIKE YOU!
I think it would be funnier to have everyone try to guess which ones were done in Synthedit and reveal it at the end. Too late for that now though as the documentation gives it away and the hardcore VST junkies already know which devs use SE.

You're new here aren't you?

As a matter of fact I am, but I take it from your response that this is an ongoing "argument" here.
I'd wager that you are at the center of a lot of it- holding the torch high and keeping it alive.
It seems like another one of those- "what's better VSTi's or hardware. . ."
or "that's not industrial" to me.

[Vonbrucken]

nuffink
I think it speaks volumes that people need a little logo to tell them if it was made in Synthedit or not.
Ironic and even amusing considering how important it is to you.
It goes without saying that marking entries into 2 categories (SE / Non-SE) would impact the outcome of voters. Especially ones LIKE YOU!
I think it would be funnier to have everyone try to guess which ones were done in Synthedit and reveal it at the end. Too late for that now though as the documentation gives it away and the hardcore VST junkies already know which devs use SE.

i approve this message !
no label on plugins , because some people still have prejudices against SE whereas they don't have it with synthmaker wich is also on mac
but the last most buggy synths i have tried came from synthmaker

edit
but what we could do is to reveal it when the contest is over :hihi

[shamann]

I'd wager that you are at the center of a lot of it- holding the torch high and keeping it alive.

Nuffink often is at the centre, but on the side of SE (or rather on the side of judging on merit and not on lineage). I think you missed the humour in his above post.

[nuffink]

I'd wager that you are at the center of a lot of it- holding the torch high and keeping it alive.

Nuffink often is at the centre, but on the side of SE (or rather on the side of judging on merit and not on lineage). I think you missed the humour in his above post.

But don't worry about it, TC. You weren't to know and your response was, under the circumstances, spot on.

[stefancrs]

nuffink
I think it speaks volumes that people need a little logo to tell them if it was made in Synthedit or not.
Ironic and even amusing considering how important it is to you.
It goes without saying that marking entries into 2 categories (SE / Non-SE) would impact the outcome of voters. Especially ones LIKE YOU!
I think it would be funnier to have everyone try to guess which ones were done in Synthedit and reveal it at the end. Too late for that now though as the documentation gives it away and the hardcore VST junkies already know which devs use SE.

i approve this message !
no label on plugins , because some people still have prejudices against SE whereas they don't have it with synthmaker wich is also on mac
but the last most buggy synths i have tried came from synthmaker

edit
but what we could do is to reveal it when the contest is over :hihi

True when it comes to synths / effects in beta status atleast. The finished plugins made in SynthMaker aren't that buggy, are they? But we still have some bugs to fix in SynthMaker itself before we're at 1.0

[eidenk]

True when it comes to synths / effects in beta status atleast. The finished plugins made in SynthMaker aren't that buggy, are they? But we still have some bugs to fix in SynthMaker itself before we're at 1.0

Watch your PM Stefan, coming in 10-15 minutes. Just doing one last single randomize of all the parameters before I post it

[DWb]

I think it would be funnier to have everyone try to guess which ones were done in Synthedit and reveal it at the end. Too late for that now though as the documentation gives it away and the hardcore VST junkies already know which devs use SE.

It's easy anyway surely - we'll be able to tell because, as everybody knows, all Synthedit synths are near-identical 2-osc virtual analogues that sound exactly the same because all you can do with Synthedit is plug the same oscillators into the same filter and then maybe decide how many LFO's or envelopes you want to give it...

[RPH]

we'll be able to tell because, as everybody knows, all Synthedit synths are near-identical 2-osc virtual analogues that sound exactly the same because all you can do with Synthedit is plug the same oscillators into the same filter and then maybe decide how many LFO's or envelopes you want to give it...

Rofl That's not true, you are forgetting the many 3rd party modules that can be used

Cya,
Rob.

[Majken]

Oh it's very true, in fact.. I've heard that Jeff is planning a random button for 1.5 since every plugin sounds about the same anyway. Then we won't have to do all this connection, testing, tweaking, gui-making, bugfixing and such. We'll just press a button and move on with our lives. Oh how excellent it's gonna be!

/Majken