Dear List,
I'm currently working on QOrchestra, and with some luck, the first
version might be available within 2 weeks. Be sure to keep an eye on
http://wendy.vub.ac.be/~bschiett/saol/
I'm under stress now, and I'm looking for people who want to contribute
one of the following, to speed up the development:
* SAOL syntax tree C++ classes
I found C code in saolc which I could use to build a
SAOL
syntax tree, but this would not go very well with the
current
code & design of QOrchestra, in many ways.
The code should be like this (more or less):
Class SAOLNode
{
public:
~SAOLNode();
virtual void print(ostream&) = 0;
protected:
SAOLNode();
}
Class SAOLProgram : public SAOLNode
{
public:
SAOLProgram();
~SAOLProgram();
void print(ostream& output)
{
// 0. print orchestra block
// 1. print all opcode definitions
// 2. print all instr definitions
}
void addOpcode(SAOLOpcodeNode*);
void addInstrument(SAOLInstrumentNode*);
private:
SAOLOrchestraNode* _orchestra;
list<SAOLOpcodeNode*> _opcodes;
list<SAOLInstrumentNode*> _instruments;
}
* SAOL opcodes for the following FlowML units:
delay (audio in, audio out, time in)
global audio in (audio out)
global audio out (audio in)
mixer (audio in 1, audio in 2, audio out)
control constant (control out)
addition (control in 1, control in 2, control out)
lfo (frequency in, variation in, control out)
time, frequency and variation are ofcourse control
signals.
The implementation in SAOL is probably just a few calls,
but I have no time to look into it right now, and I'm no
expert in signal processing.
I'm therefore looking for somebody who is willing to write any of this
code and release it under the GNU GPL, such that I can
use them in the development of QOrchestra. The copyright remains
with the original author, and he will be given full credit ofcourse.
I know this all sounds odd, but your contribution might make a
difference to the release date of QOrchestra.
Thanks in advance,
Bert Schiettecatte (stressed).
This archive was generated by hypermail 2b29 : Mon Jan 28 2002 - 11:46:38 EST