No, it does not look stupid,
it was just a suggestion that the programming could technically be
done more clear by re-using code where possible.

(The same sort of simplification could be done with some of the Python
code, for example the ri(), ga(), ma(), pa(), da, and ni() methods of
the Song1 class are also very similar. Maybe the use of arguments
could allow you to only have one method definition, and still have the
same flexibility.

But, now, these are just technical suggestions.

The musical algorithm you are using, is it based on some sort of
traditional (folk) scheme ? I'm not familiar with the words/syllables
(sa ri ga ma pa da ni), but it "looks" like traditional music somehow
(?)
Also, it reminds me of another person that used to be here a few years
back, by the name of buyo-buyo-igor.

best
Oeyvind

2008/8/13, '2+ <electriclightheads@gmail.com>:
> thanx
> and yes my oil.orc look totally stupid
> maybe i was sticking too much to use as few p-fields as possible
> and maybe that have somethang to do with it
>
> well
>
> On Tue, Aug 12, 2008 at 09:23:35AM +0200, Oeyvind Brandtsegg wrote:
> > But, from looking at your orchestra, it seems like most of the
> > instruments only differ in parameter settings (ftable/waveform
> > selection, and harmonic ratios), so you might be able to make the
> > orchestra a lot simpler by only using one instrument and supplying
> > these parameters via p-fields.
>
> i still want to capsule thangs and
> keep the structure look simple when i pass those ps to the orchestra
> i tend to forget the meaning of each couple of months later ;-D
> and wanting to make all orc to use the same p-field structure ... is
> another reason
>
> hmmm
>
> but yes .. too many instruments in a file is ugly and maybe even dangerous
> even if i change a small thang
>
> so i came up with this idea:
>
> putting a lot of meaning to an exact value of a parameter
> can help me not increasing the member of p-field?
>
> i mean
> 2000 and 2001 and 2002 doesn't have a big difference as a value
> but the if the 4th digit 0 or 1 or 2 can take an effect on
> which ratio to use in the instrument
> i can built in that kinda calc to my sing.py script
>
> had someone already tried things like that?
>
> oh the fact that value might become int rather than float
> can bring me some trouble?
>
> > You don't tell anything about the python processes involved in making
> > the music, it might be interesting to hear about that too.
>
> oh they are @:
>
> http://sarigama.namaste.jp/oil/sing1.py
> http://sarigama.namaste.jp/oil/overtones
> http://sarigama.namaste.jp/oil/song1/song1.py
>
> sing1.py makes the instance of song1 to sa.sing()
> and i want to keep most of the logics to calc the freq capsuled in a
> class
> so that the whole thang could become a bit like an imoprovisation done  by some instances of song1.class
>
> --
> '2+
> http://sarigama.namaste.jp/buyobuyo.html
>
>
> Send bugs reports to this list.
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>