Abstracted Architecture

[meganindya]

Identified Requirements:

Engine	Client
State Management	Canvas Context
Scheduling	Audio Context
Block Framework	Block Tree
Feature API	Block Artwork
Export Algorithms	Block Interaction
	ADSR Envelope
	History
	Context Save Logic
	Widgets

[meganindya]

This is a very abstract representation of the requirements.

https://lucid.app/documents/view/cbb01bc9-9407-4aa9-8173-fccb64b1ee68

[walterbender]

What is going on with the ADSR envelop?

[meganindya]

Tone.js provides functionality to trigger an attack and a release separately, or at once with triggerAttackRelease, which works on precise musical time. There's also functionality for PolySynth which allows multiple voices to be managed together.

IG if we can process the required sound envelope properties in the "engine", perhaps a AudioContext wrapper in the "client" can effectively dispatch the events via the Tone.js API — separation of concerns.

[walterbender]

We use all of that functionality in musicsynths.js. But I think I see where you are going. It would also give us more direct control over sustaining notes and "bending" notes.

[meganindya]

My original idea was that the "engine" should be independent of Tone.js. But, I think it's best if we use Tone.Transport for timing and scheduling.

[walterbender]

I completely agree. Should help a great deal with performance and robustness.

[walterbender]

And it will make our code less complex.

[meganindya]

This has evolved to: