[music-dsp] Anyone want to help with my music program?

[Andrew Greenwood]

I'm open to suggestions and a lot of this project has been shaped by the
input of other people. One person was a guy who created a basic modular
synth program as part of his university course. At the time I just wanted to
create a VST host.

I used Reason for a while, and one of my college lecturers saw a program I'd
made previously and said "you should make something like Reason, but
better." At the time I shrugged it off as being impossible to do, and
continued blindly planning updates for my old project, which to be honest
hasn't been too successful. Mainly due to the fact I'd not really bothered
designing it before I started coding it!

I'm pretty certain of what I want the end application to look like and what
features it should have. But my design is probably not the most ideal one
and that's why I want some help designing it, so I can make it better.

The design has changed a lot over time.

I just wondered if anyone fancied giving me a hand with the design or
implementation. I'd really appreciate it.


----- Original Message ----- 
From: "nick" <nickcodemonkey at yahoo.co.uk>
To: "a list for musical digital signal processing"
<music-dsp at ceait.calarts.edu>
Sent: Thursday, September 23, 2004 5:08 PM
Subject: Re: [music-dsp] Anyone want to help with my music program?


While this stands for commercial software, where developers are paid,
I'm not sure that would help here.

The problem with designing and speccing the whole lot is that it then
becomes very hard to find people willing to work on it *for free*.

These kind of people will want to have their say in the decisions,
that's where the fun is and that's why they'll want to be involved!

Just my £0.02

Nick

On 23 Sep 2004, at 11:19, Dave Gamble wrote:

> You need a full user spec. Noone will know precisely what you mean
> unless you have one.
>
> Post a link to it (preferably as pdf) to the list, and you might get
> more constructive replies.
>
> What I mean by a spec is a complete list of the routes the user can
> take through using the software, from startup,
> editing, mixdown, the whole works.
>
> Having a spec basically guarantees your success. It will take a long
> long time to write.
>
> Not sure how to write such a spec? Look up the new book by Joel
> Spolsky (Joel Book 2).
>
> Dave.
>
>
> On 23 Sep 2004, at 02:54, Andrew Greenwood wrote:
>
>> I've posted stuff like this time and time again...
>>
>> But for some reason, whenever anyone is interested in my program, they
>> disappear off the face of the Earth shortly after they offer to help.
>>
>> Basic outline is as follows:
>> A music application based on the interface style adopted by
>> Propellerhead
>> Reason, with support for VST and other plugin formats, multiple
>> editing
>> styles for each data type, support for MIDI input and output, and
>> audio
>> input and output, and various other goodies.
>>
>> Target platform is Windows 98 to XP, with a view to porting the
>> program to
>> Linux in the future (and possibly Mac, if I ever get my hands on
>> one!) -
>> thus a cross-platform GUI toolkit, such as wxWindows, would come in
>> useful.
>>
>> The program will not be open-source, hence why Linux is not the
>> primary
>> target platform (although I'd love to use it on Linux.) I hope to
>> make some
>> money from creating this program, but if the program doesn't sell, I
>> will
>> have nothing to offer. If I had the money, I would've hired a team of
>> people
>> by now, but I don't.
>>
>> End product will comprise of a free version with restrictions (but no
>> nagging, just a basic program with basic functionality), and a
>> variety of
>> paid-for packages.
>>
>> But I'm stuck with things like making a simple widget/graphics API
>> that the
>> rack modules can use, and various key decisions such as supporting
>> XML for
>> defining visual layouts of plugin modules.
>>
>> I'd really appreciate any help that anyone can give to me, so if you
>> can
>> spare some time to discuss ideas and/or contribute code, please let
>> me know.
>>
>> Due to other commitments (ie, regular job) I haven't had much of a
>> chance to
>> get anything going with this project and it's just been sitting there
>> gathering dust for a year or so now.
>>
>> Thanks
>>
>>
>> Andrew Greenwood
>> Silver Blade
>>
>> --
>> dupswapdrop -- the music-dsp mailing list and website:
>> subscription info, FAQ, source code archive, list archive, book
>> reviews, dsp links
>> http://shoko.calarts.edu/musicdsp
>> http://ceait.calarts.edu/mailman/listinfo/music-dsp
>>
>
> --
> dupswapdrop -- the music-dsp mailing list and website: subscription
> info, FAQ, source code archive, list archive, book reviews, dsp links
> http://shoko.calarts.edu/musicdsp
> http://ceait.calarts.edu/mailman/listinfo/music-dsp
>
>
-- 
This message and any attachments are confidential to the user of the
e-mail address to which it was addressed. The sender does not accept
liability for any errors or omissions in the context of this message
which arise as a result of Internet transmission. Any opinions
contained in this message are those of the author and are not given or
endorsed by Focusrite or office through which this message is sent
unless otherwise clearly indicated in this message and the authority of
the author to so bind the Focusrite entity referred to is duly
verified.

--
dupswapdrop -- the music-dsp mailing list and website:
subscription info, FAQ, source code archive, list archive, book reviews, dsp
links
http://shoko.calarts.edu/musicdsp
http://ceait.calarts.edu/mailman/listinfo/music-dsp