Notes on KitsilanoBot & SScapeSynth

jan 06 2017

///////////////////
Changes
jan 1
- removed variation in duration: always full section
- only one voice possible (removed poly)
- removed vitality/density tests: only one voice can play

dec 31
- changed most loadbangs to loadmess, due to newComposition
- in [receiving_OSC_and_setting_variables] added onebang to s newComposition

dec 29
- receiving internal params from Orchestrator (p receiving_OSC_and_setting_variables)
- [p update_notepool_for_synth]
- [p total_activity]
- deleted display pitch stuff
- deleted self analysis
- deleted matching other bot
- altered poly~ Droney

///////////////////
TO DO

• synthdata (SScapeSynth envelope, Resonators Dry/Wet) only sent @ load. Should these be
varied @newComposition? (Send latter in [send_synthData]

//////////////////
EXPLANATION

@load 
- create a new track in Live

@spectrum (from ParamBOT)
- load SScapeSynth into that track
- load Resonators effects device into track
- transmit note & pitch settings (originally read from script, but updated via notepool message)
to Resonators device via device_loader

in SScapeSynth
- when it receives beat info, will adjust envelope data based upon tempo


@new_composition
- not sure yet

@new_section
- not sure yet


//////////////////
BUGS

- why is ACTIVE button on in KitsilanoBOT?

//////////////////
QUESTIONS



Reminders

impatience: how willing is agent to become active

persistence: how willing is agent to remain active

vitality: how much an agent is willing to do once active (hdensity)

consistency: how often agent will vary its playing

compliance: how strict will it interpret requests