[Clam-devel] [PATCH] (working in progress) Harmonizer

[Hernán Ordiales]

On 7/5/07, Pau Arumi <parumi at iua.upf.edu> wrote:
> En/na Hernán Ordiales ha escrit:
> > hi all,
> > i'm sending the first aproach patch for SMSHarmonizer... no much time
> > for comments about it now because i'm leaving now (i'll add more
> > comments later)
> > summary:
> >     * SMSHarmonizer (test version with hardcoded 4 voices)[1]
> >     * Harmonizer Network
> >     * SMSSinusoidalGain bounds added
> >
> commited in revision 10357. Thanks!
> it sounds here.

good :-)

> not very well and with many artifacts but a good
> starting point. and it's a funny sound indeed :)

i'll post here another mail about that and looking for suggestions to improve it
take in account that by default residuals are ignored (maybe i'll
toggle default value, what do you think?)

> > [1] amount of voices maybe configurable with an InControl or
> > processing with configuration? Is this compatible to have a network
>
> #voices seems to fit more to a configuration than a in-control
> because it effects the number of in-controls.

ok

> > and a prototype for it? configuration approach i think yes... but
> > InControl one? (question: why networks doesn't remember InControl
>
> right. if the number of in-controls change during run-time then you
> cannot do the binding at prototype-loading time.

ok, for that reason i've started with a fixed InControlArray of 4
voices (i think is enough in mosts cases) because we need a prototype
of it

what to do?

- One fixed harmonizer processing with fixed amount of controls and protoype
- One harmonizer processing with dinamic amount of voices, but without
a prototype???
- Both (2 different processings)

> > values?)
> (please do one question per line next times :) )
>
> what do you mean exactly. what and when in-controls should be
> remembered?

For example if i want to remember 'gains' or frequencies and have a
saved network of that

In this case, have a network configured with specific voices and gains
ready to play...
In spectralnetwork, nice values of robotization, gains, filter, freq, etc...

ATM is always the mean value between min and max (for example in
robotization i think is bettter a '0' value by default)

-- 
Hernán
http://h.ordia.com.ar
GnuPG: 0xEE8A3FE9