[music-dsp] Modelling of analogue synthesizer circuits

Ian Lewis ILewis at acclaim.com
Mon Nov 12 18:01:33 EST 2001


It would probably be less confusing to say that the code is "linked" at
runtime. Does that accurately describe the process?
Ian

> -----Original Message-----
> From: Jan Marguc [mailto:jm at kampsax.dtu.dk]
> Sent: Monday, November 12, 2001 2:51 PM
> To: music-dsp at shoko.calarts.edu
> Subject: Re: [music-dsp] Modelling of analogue synthesizer circuits
> 
> 
> 
> ----- Original Message -----
> From: "piter pasma ..ritz" <ritz_rvl at yahoo.com>
> To: <music-dsp at shoko.calarts.edu>
> Sent: Monday, November 12, 2001 5:12 PM
> Subject: Re: [music-dsp] Modelling of analogue synthesizer circuits
> 
> 
> > --- Jan Marguc <jm at kampsax.dtu.dk> wrote:
> > > > does anybodyhere have some tips on how to make the structure of
> > > > a modular (or perhaps not modular) softsynth.. that is
> > > > 1) flexible
> > > > 2) fast
> > > > 3) very very small :) [preferable the pattern data]
> > > you might want to check out the source code of freestyle's
> > > stoerfall ost 4k
> > > intro. i saw it on cfxweb.net a while ago.
> >
> > i already looked at that one yes.. nice piece.
> >
> > > it features a modular
> > > synth
> > > setup, whose code is assembled just-in-time when the 
> program starts
> > > up.
> >
> > i don't think it is assembled just-in-time at runtime.. at least
> > if i understand the source correctly, it generated the code using
> > MASM's macro-language.. [which still is rather small, because it's
> > just assembler :) ]
> > but i'll look at the code again, if you are right, it might be
> > very interesting..
> 
> in fact, it *is* assembled at runtime. the thing is, they 
> create code for
> the basic modules, then
> have a couple of simple instructions telling how this code is to be
> assembled.
> read "assembled" here: all code has already been converted into intel
> bytecode by masm, so
> it is only a matter of copying this bytecode from the various 
> places into a
> single bytestream
> constituting the soundcode itself. i tried this out myself 
> and it seems to
> work out very well, but i
> never found time to finish it. the key to minimizing code 
> size of the synth
> is afaics to let your
> module editor do all the calculations about data flow, 
> recursive paths etc.
> take a look at their code,
> the assembly function takes almost no space. nice, indeed.
> 
> >
> > > that
> > > way, the whole synth structure can be kept small and the 
> controller
> > > data can
> > > be directly passed to the inputs of the modules in the network.
> > > oh yeah, btw: the sound of this thing is absolutely great!
> >
> > dunno, it kind of skipped on my PII350 .. [i intend my softsynth
> > to be better :) but maybe that's just that i have a different taste
> > for music :) ] ..
> > oh and the latest (?) 4k intro from freestyle, which was released
> > at mekka&symposium2001 has even better sound.. but i don't think
> > they released the source yet.
> 
> heh, do you really want to know how they did it? ;)
> i was laughing my ass off when i found out, that they just 
> read samples
> from the soundfont file c:\windows\system32\drivers\gm.dls
> this is a 3 mb soundbank that comes with any soundblaster 
> pciXXX or live
> card and contains a complete gm sound set.
> some may call it cheating -- i'd rather call it a pretty 
> creative way of
> making use
> of the resources available! ;)
> 
> >
> > > anyhow, i think that if you want really good sound for your 4k,
> > > it's
> > > probably a better idea not to choose a modular design 
> (although the
> > > idea of
> > > assembling the soundcode just-in-time is somewhat intriguing). i
> > > personally
> > > find it easier to work with (that is, make it do what i expect it
> > > to) a
> > > fixed-architecture synth. it is a bit more limited, sure, but from
> > > a
> > > perceptional and musical point of view it is easier to understand.
> >
> > fixed architecture.. i did that in my 4k called 'meuk' (downloadable
> > @ my site) ..
> 
> yeah, noticed it, but unable to run it under w2k (even with 
> the emulator
> you suggest)
> 
> > problem with a fixed architecture is that it doesn't leave much
> > room for the musician [i really suck at composing, so i intend
> > on letting someone else do it.. lucky for me, most 
> musicians/trackers
> > i know are quite familiar with buzz, so modular should be no prob
> > for them..]
> 
> ok, i should probably explain, what i meant with fixed architecture:
> i don't mean custom code for 3o3's, hihats or the like, but 
> rather a simple,
> yet flexible synth controlled by patches.
> having one and only one architecture to work with is easier 
> for a musician
> (since that's exactly the kind of equipment they are used to 
> work with every
> day)
> + you can focus on making this one architecture really good 
> wrt. code size
> and most
> importantly sound quality.
> consider having 3 independent envelope generators in your 
> fixed-architecture
> synth.
> not less, not more: always 3 envelopes. this setup can still be very
> flexible, if you can
> allow them to control pitch, vcf, vca freely.
> 
> >
> > somehow, a modular synth sounds like a good idea to me.. also for
> > size.. .. or at least a fixed architecture, that is modular, but
> > fixed or something..
> >
> > - piter
> 
> looking forward to see your next windoze 4k ;)
> cheers,
> 
> jan marguc
> 
> >
> > =====
> > . piter pasma                   ....
> > .. ritz[nd-44-zh]                ...
> > ... ritz_rvl(at)yahoo(dot)com     ..
> > .... http://www.ritz.nd-44-zh.net  .
> >
> > __________________________________________________
> > Do You Yahoo!?
> > Find a job, post your resume.
> > http://careers.yahoo.com
> >
> > dupswapdrop -- the music-dsp mailing list and website: 
> subscription info,
> > FAQ, source code archive, list archive, book reviews, dsp links
> > http://shoko.calarts.edu/musicdsp/
> >
> >
> 
> 
> dupswapdrop -- the music-dsp mailing list and website: 
> subscription info,
> FAQ, source code archive, list archive, book reviews, dsp links
> http://shoko.calarts.edu/musicdsp/
> 

dupswapdrop -- the music-dsp mailing list and website: subscription info,
FAQ, source code archive, list archive, book reviews, dsp links
http://shoko.calarts.edu/musicdsp/




More information about the music-dsp mailing list