davids48 / pyata Goto Github PK

It'd be nice to have a basic step sequencer on the Python side so we can easily get musical results out of a basic combination of oscillators and envelopes.

We should try to avoid subpatch names clashing, either by adding a sconce of some sort to the provided name, or just using a randomly generated name anyway.

The order of inlets on a subpatch object is determined by the position of the inlets objects in the subpatch canvas. We should probably make sure that we do this in some sort of a predictable way, in order to make subpatching (and hence the use of abstractions) practical.

Slightly less typing for common connections.
dac << osc
should be equivalent to
dac.i0 << osc.o0

Work out how we want to be able to define re-usable sub-patches.

Ideally we want this to play nicely with both PureData's abstraction mechanisms and code re-use on the Python side

Create "dummy" mode for debugging - don't boot a pd server or send commands to it, but continue to write them to stdout / logs.

Automatically created mathematical operators should be created as signal operators or control operators depending on their inputs.

There's no real benefit to the "snd" object living on the Box / Connection classes - we might as well make it global, import it when we need it, and remove a bit of coupling from the subclasses to their parents.

Asking about the inputs and outputs of a given box at the command line should follow on through automatically created mathematical boxes and show their ultimate inputs and outputs.

Make imports explicit to avoid general horror.

It'd probably be good for instant hackability to have a library of common abstractions to start playing with. Eg vca with AD envelope, midi controlled oscillator, delay line with mix control etc.

It'd be nice if we could re-arrange the boxes in the PD window to provide a tidier patch. Particularly, we should be able to sort out the tree of objects feeding into a given box to be above it, relatively near it, and not overlapping.

It'd be good to have a script that will initialize PD and get us into an interpreter session, then quit PD again when we exit. This might turn into a more feature-rich live-coding environment, but for now it'd be enough just to save dealing with the boilerplate when we're testing stuff.

We should have a properly organized project structure with scripts and source directories, setup.py, requirements.txt etc.

We don't currently get any errors raised if we try to make an impossible connection. We ought to!

Sort out the redundancy between the different Pd Box classes and abstract box classes. Maybe by making the original Box subclasses also inherit from the API Box. We might also want to think about Replacing Inheritance With Composition for the Pd Box classes at the same time.

There should be a less verbose way of setting subpatch parameters. We should also be able to expose sub-subpatch parameters on the subpatch.

Use proper logging throughout old and new code.