just_one_minute_i_just_cant_stop

(|| how not to be taken seriously as a programmer)*

http://www.jwm-art.net/art/audio/just_one_minute_i_just_cant_stop.mp3

//------------------------------------------------------------------------
// wcnt and ladspa up a tree, k-i-s-s-i-n-g.

// wav composer not toilet
// :-> non realtime modular synthesis sequencing and sampling (4 linux)

a number of years after releasing    wcnt,  i  have finally  let go of the
notion that  the program must only   use my own code. the next release, to
occur by the  end of the year will    be  dependant   on  
mega-nerd.com's
libsoundfile  audio file IO library.  not only this,  but  there will be a
number of new  modules which interface with selected LADSPA plugins - from
the swh plugin set, and the caps plugin set.
___________________________________________!YES_EVEN_MORE!________________
using ladspa has brought me to see further ^shortcomings^ of wcnt, and the
way modules are written out within a .wc file for wcnt to process.

currently,  (and with the next release and the minor  releases  which  may
follow it) there is no way that parameters or inputs within modules can be
optional.

for instance, if you  wish  to use  a clock  module  running at a constant
unchanging frequency, you obviously want to specify the frequency, but you
don't want to be forced to say the input for modulation is  off,  and
that
the amount of modulation is to be none - u shood b abull to leevitaaaat
an the code finks 2 itslef that it must be off an non.

further,  the  clock  module  has  only  one input and parameter for which
modulation is  to occur by,  what if you  want more - then you must use  a
more complex module such as  the  lfo_clock - which may have other  things
you must specify but don't wish to use.

so not only must certain parameters and corresponding  inputs be optional,
but there should be freedom to have as many as needed.

and  then,  there  are  different  ways  of calculating modulation, ie for
amplitude:

 amp_level = level * envelope_input
 amp_level = level + modulation_input * amount (ie an LFO generated sine)
 amp_level = level * (1 - amount) + level * amount * modulation_input

woteva...

ass_You/Me level is between 0.0 and 1.0, amount will be the same.
but what if level is specified in decibels?

the user is like a mushroom - kept in the dark and fed on horseshit.

require groupage of parameter wiv input _OR_ groupage of in with param.

sum params R2 simpl 4 this tho. but we wont2 say 2 user sum help 2oo.

and we wont to say 2 user this is dual shaped adsr and the velocity
input partnered with the up_thresh and lo_thresh parameters control which
of the two envelope shapes the adsr outputs.

an fings like that innit.

so what in (col' chillin' in) effect we R talkin''aboot is da like
sub-modules of modules or somink. i dunno i qant cwite worky tout.
//------------------------------------------------------------------------

http://www.jwm-art.net/art/audio/just_one_minute_i_just_cant_stop.mp3

*or anything else for that matter

_______________________________________________
NetBehaviour mailing list
[email protected]
http://www.netbehaviour.org/mailman/listinfo/netbehaviour

Reply via email to