Re: [microsound] algorithmic hardware

["Balazs, Gerofi" <kedli@xxxxxxxxxxx>]

i guess, everything what you are doing is an algorythm:)

On Thu, 5 May 2005, Alex Young wrote:

> If you program patterns on synths, which in turn trigger other synths
> in various ways, you can end up with some unpredictable results.
>
> This isn't really much different to programming an algorithm.  You're
> still dealing with chains of events - you could think of patterns on
> your step sequencers as subprograms, for example.  I love it when
> hardware/software sequencing becomes chaotic, you can draw chaos out of
> deterministic systems.
>
> On 5 May 2005, at 11:05, Kim Cascone wrote:
> >> there's no algorithmic use on it, it's all hardware sequencers.  no
> >> max/msp,etc.
> >
> > FYI: you CAN make algorithmic music on hardware sequencers...hardware
> > and algorithms are not mutually exclusive
> >
> --
> homepage: http://alexyoung.org
> music: http://noise.me.uk
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: microsound-unsubscribe@xxxxxxxxxxxxx
> For additional commands, e-mail: microsound-help@xxxxxxxxxxxxx
> website: http://www.microsound.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: microsound-unsubscribe@xxxxxxxxxxxxx
For additional commands, e-mail: microsound-help@xxxxxxxxxxxxx
website: http://www.microsound.org