Dev Competition-Now with its own forum!!

DSP, Plugin and Host development discussion.
Post Reply New Topic
RELATED
PRODUCTS

Post

depending on how the competition rules shape up, I'm in as well. I already have a perfect idea candidate for it as well.

Post

Sounds like fun, I'm in. :)

Post

Kingston wrote:depending on how the competition rules shape up, I'm in as well. I already have a perfect idea candidate for it as well.
you posted in the thread so according to the rules you're in. :p

Jack R wrote:Sounds like fun, I'm in. :)

thank you very much sir. :)
Image

Post

General, count me in!

Some rules suggestions:

1. Only new synths (no emulations)

2. Try to add something extra.

3. Open source encouraged. (Doesn't need to release the entire VST SDK but just the GUI and the Process routine.

4. At least 16 patches

5. 3rd party components allowed if you include the components (SE & SM) in your package.

6. Complete skin must be available in the released package for skinners.

That's for my rule suggestion.

Suggested start date: 1st June to make things easier to remember.

Now what do you say about this?
Best regards from Johan Brodd.
JoBroMedia since 1996.

Post

jobromedia wrote:General, count me in!

Some rules suggestions:

1. Only new synths (no emulations)

2. Try to add something extra.

3. Open source encouraged. (Doesn't need to release the entire VST SDK but just the GUI and the Process routine.

4. At least 16 patches

5. 3rd party components allowed if you include the components (SE & SM) in your package.

6. Complete skin must be available in the released package for skinners.

That's for my rule suggestion.

Suggested start date: 1st June to make things easier to remember.

Now what do you say about this?
i had already signed you up. :)

only new synths (previously unreleased) sounds good to me. as for no emulations, i really don't want to limit developers. that's why i think it should be a free for all, as long as it's musical. open source is cool with me. anybody's welcome to give the source of the plug. i really don't want to give a preset limit either. i mean, if someone decides to put out a plug with no presets, that's ok too, but i'm sure some people won't be able to see the possibilities of certain types of plugs. and of course, if it's something like milestone then you can't really have 16 presets. as for 3rd party components, skins and stuff, i'm not knowledgeable enough to comment.


anyway, i just wanted to say that so far i counted 15 kickass devs and arke. :p you can see them all in the first post. :)


june 1st is a nice date, but i can't really say for sure. i will have the complete rules by the end of this weekend. i promise. :)
Image

Post

Sounds sweet to me!
Best regards from Johan Brodd.
JoBroMedia since 1996.

Post

ive never released a plugin with over 8 presets. but then again, i have a random patch generator on every one.

lets keep the requirements more loose. rather than force numbers on people.

also.. as for the 3rd party modules. there are several i used that people would NOT want me to give out or pass around, so i'll probably end up keeping the modules, the patch, and the skin to myself..

Post

Urs wrote:
jtxx000 wrote:I say open source should be encouraged. I understand that some devs don't want to give away trade secrets but I think it'd be a great resource for other developers.
Hmmm... the VST SDK isn't open source... you simply can't open source VST plugins without breaching the license agreement... SynthEdit and SynthMaker aren't open source either. In the same way, you can't compile GPL'd code into a VST plugin, because a VST plugin can't inherit from GPL or one of both licenses would be broken.

It ain't easy.

;) Urs
True that, but I have no issues with releasing the schematic and will most likely do so :)


TO ALL:
All these extra rules some seem to want to add to the contest just makes it less fun, imho. Let's keep it simple and lets keep it a popularity contest. It shouldn't matter if I make a 8 preset TB-303 emulation, a 128 preset EQ, a zero preset randomizing drum machine or whatever. IMHO.

TO TUZ:
A theme might've been fun, but if not this time, maybe the next, eh? ;) A drum machine compo, or distortion/modulation effect compo etc, could kick some serious ass for the end users, and still would be fun for us devs :D

Post

tuz wrote:anyway, i just wanted to say that so far i counted 15 kickass devs and arke. :p you can see them all in the first post. :)
You don't know if I'm a good dev or not ;) ... well, yet.

It looks like this contest will be pretty big, so I think I'll dig out the old C++ compiler for this one instead of doing it in SE. I've never programmed for VST but I've got plenty of example code to draw from.

(...although I'll probably end up doing it in C and just having the C++ wrapper for the SDK :P)

(...or SE afterall...)

Post

If I had the slightest knowledge in C then I'd do the entry with it. But I haven't. + 2 months is far to short period for me to throw together a nice and confy Delphi plugin. But maybe I'll do it after all, well let's see what I can cook together.
Best regards from Johan Brodd.
JoBroMedia since 1996.

Post

Well, i'm working on some stuff i am going to release for free anyways so i might as well join the contest.
I don't expect to win but it's good for the old ego to be part of it. Hope i don't end up last though. :D

Post

jobromedia wrote:1. Only new synths (no emulations)
Are we not allowing effect plugins?

Post

Ooh my bad, Ofcourse are new effects welcome!
Best regards from Johan Brodd.
JoBroMedia since 1996.

Post

Urs wrote:Hmmm... the VST SDK isn't open source... you simply can't open source VST plugins without breaching the license agreement... SynthEdit and SynthMaker aren't open source either. In the same way, you can't compile GPL'd code into a VST plugin, because a VST plugin can't inherit from GPL or one of both licenses would be broken.
Um... Not to be pedantic, but the GPL isn't the only open source license out there - it's perfectly possible to still write open source plugins under a license that's compatible with Steinberg's stupid restrictions (see all of my recent plugins). Of course, you don't get the same kind of free software/community-based protections the GPL provides, but until Steinberg changes their license there's no way around that.

I would also want open source entries encouraged, btw :wink:.

- Niall.

Post

NiallM wrote:
Urs wrote:Hmmm... the VST SDK isn't open source... you simply can't open source VST plugins without breaching the license agreement... SynthEdit and SynthMaker aren't open source either. In the same way, you can't compile GPL'd code into a VST plugin, because a VST plugin can't inherit from GPL or one of both licenses would be broken.
Um... Not to be pedantic, but the GPL isn't the only open source license out there - it's perfectly possible to still write open source plugins under a license that's compatible with Steinberg's stupid restrictions (see all of my recent plugins). Of course, you don't get the same kind of free software/community-based protections the GPL provides, but until Steinberg changes their license there's no way around that.

I would also want open source entries encouraged, btw :wink:.

- Niall.
Agreed. I'll be releasing at least part of my source code for this project, but probably not any of the libraries that I use (since I'm trying to also sell them, heh).

Also, how does this effect SE plugs? Are these entries to be allowed? Will theey just release the SE documents or something?

Post Reply

Return to “DSP and Plugin Development”