Wusikstation Open Source kvr buyout

[kisuw]

I've come to the sad conclusion that the least bad option is for WilliamK to sell Wusik.com lock, stock and barrel to a software company.

[kara]

ok, I would be in, but doubt that open source would be a solution.
Problem with open source is that it becomes very fact chaos if it is not well managed.
To have a good open source project, you need a good project manager. One that can direct, accept or refuse code modifications, new features,....
So one of my questions would be : Who would do this and who has the skills to do this.
I would be willing to host the synth, soundpatches, etc...


Rony

[cptgone]

- be careful people...
- why bother at all? there are many WS like synths already.
I would have sold mine months ago if it hadn't been for a misplaced desire to support the dev.

[kara]

ok, perhaps that's a point to.
So, why not form a development community and build one then ?
It wouldn't be mandatory to make it open soucre, it could be a product that is sold.

[Glassback]

You'll have to forgive me as I've just woken up...
but do you mind if I ask who this was for, if anybody, and why?

[griels]

ok for the people wondering how the readability / documentation of the code is william sent an example:

Code: Select all

extern float Wavetable_Output[99999];
extern float Wavetable_Output2[99999];
extern float Wavetable_Amplitude[99999];
extern float *Wavetable_Sample[99999];
extern float Wavetable_Time[99999];
extern float Wavetable_TimeF[99999];
extern float Wavetable_Rate[99999];
extern float Wavetable_RateF[99999];
extern float Wavetable_LoopEnd[99999];
extern float Wavetable_LoopSize[99999];
extern float Wavetable_Position[99999];
extern bool Envelope_StateQuad[99999];
extern float Envelope_Output[99999];
extern unsigned int RemoveSign[999];

Nice, as Borogrove stated, vast global static arrays... I wonder what the significance of 99999 is?

Looks like this code is going to need some serious restructuring...

I myself would favour the Open Source approach.. At least it would allow people to port their soundsets to a different platform without changing sound quality (with the right licensing).

[spaceman]

ok for the people wondering how the readability / documentation of the code is william sent an example:

Code: Select all

extern float Wavetable_Output[99999];
extern float Wavetable_Output2[99999];
extern float Wavetable_Amplitude[99999];
extern float *Wavetable_Sample[99999];
extern float Wavetable_Time[99999];
extern float Wavetable_TimeF[99999];
extern float Wavetable_Rate[99999];
extern float Wavetable_RateF[99999];
extern float Wavetable_LoopEnd[99999];
extern float Wavetable_LoopSize[99999];
extern float Wavetable_Position[99999];
extern bool Envelope_StateQuad[99999];
extern float Envelope_Output[99999];
extern unsigned int RemoveSign[999];

Nice, as Borogrove stated, vast global static arrays... I wonder what the significance of 99999 is?

Looks like this code is going to need some serious restructuring...

I myself would favour the Open Source approach.. At least it would allow people to port their soundsets to a different platform without changing sound quality (with the right licensing).

14 lines of god nows how many.. yeah it is SOOOOOO obvious. You guys should use your amazing skills to predict the stockmarket and heck.. why not.. the whole future

could make you a buck or two

[griels]

14 lines of god nows how many.. yeah it is SOOOOOO obvious. You guys should use your amazing skills to predict the stockmarket and heck.. why not.. the whole future

could make you a buck or two

Seriously, that's some ugly code... And it's in one of the key sections of the app.. Who knows what lurks elsewhere...

If it is to be developed by other programmers it would seem better to rewrite the whole engine from scratch or port features to another one than develop an idiosyncratic and undocumented engine further.

[Glooper]

griels...

admitidely it's not the best code...but trust me, it's better than a lot of open source code...

one of the problems with open source is that people don't follow conventions and generally people who program at home are crap at commenting/ documenting (Maybe I'm making a sweeping statement there, and I'm sure that's not always the rule). But having delved into the code of several open source projects now, they are generally uglier.

Ben

[haydxn]

my commenting is supreme

[griels]

of open source code...

one of the problems with open source is that people don't follow conventions and generally people who program at home are crap at commenting/ documenting (Maybe I'm making a sweeping statement there, and I'm sure that's not always the rule). But having delved into the code of several open source projects now, they are generally uglier.

Ben

Wow, fair enuff.. For the sake of the soundset developers, we've got to think of how we can maintain the longevity of Wusikstation functionality in whatever way... Maybe someone would be willing to pick up the mantle in developing it in the OSS domain, but whoever it is should be good at maintainence and commenting.

It might be a nice idea to port some of the functionality to LinuxSampler which is slated for a windows implementation.

[M'Snah]

my commenting is supreme

It's not about your comments in this thread, it's about commenting your code

[haydxn]

[Seus Hawkins]

I may be in as well. - Having second thoughts though(I usually stop at the first) ;)

[Caleb]

Of course another option might be to start a collection to try and romance Glenn into upgrading Crystal to take on the user waveform wavesequencing and maybe add another oscillator while he's at it.

I was always hoping Crystal would go this path anyway as it's such a fantastic engine and the import of soundfonts makes it even handier.

Of course it may not be as low-CPU as WusikStation is....

I'm not bagging WusikStation. It's one of my favourite synths - but just throwing it out there.

Glenn - I'd give you $100 to put in wavesequencing of sf2s into Crystal.

Caleb