[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [sc-dev] Towards SC 4




On 12 November 2013 01:06, Josh Parmenter <josh@xxxxxxxxxxxxxxxxx> wrote:
So, with the current state if things being what they are, what are the major changes / major things we want to keep from SC 3 going forward to SC 4?

Breaking backward compat is of course more in the table then not, though anything that does (I think) should be done with good reason. I think a new project should aim to-

- Cleanly deal with future bit changes (64 bit compatibility, and thinking ahead to things we can do to make any future changes easier)
- Would like to keep the basic language and class structure
- build the language as a set if language plugins
- retain Qt and the IDE

As for the overall architecture, I personally could think of reasons to keep the lang / server divide, but also reasons to bring them closer together as SC 2 did... Thoughts?

Also, what strategies can we use to start and grow as cross platform, rather then working it in after the fact?

No time lines yet, but I seriously want to open this can of worms. I would be interested in hearing who might be up for this project, planning it together and setting some timelines and mapping out tasks.

Go!

Just a couple of tiny suggestions if breaking backwards compatibility is on the cards. They've been discussed before, but they're worth saying again:

Firstly, how about removing UGens' mul and add arguments, in favour of .madd? That frees up the possibility of adding new arguments to old UGens, at the end of the argument list, without breaking old SC4 code.

Similarly but perhaps more contentiously, how about removing UGen:if, which has always been a source of confusion for new users. It could be replaced with a UGen called If (i.e. If.ar and If.kr), which would make its server-side nature much more obvious.

In terms of big ideas, I add a very large +1 to the single-sample feedback loops suggestion.

Nathaniel


--
Nathaniel Virgo
http://nathanielvirgo.com