You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Event abstraction (Probe abstraction - or maybe a probe is just a binary talking the same IPC/wire protocol)
What a probe should report? How much a probe should know about the systhesis, and vise versa?
Jen: They should be relatively indepedent of each other. Imagining each event as a tuple (quality, timestamp)
Network abstraction? (and/or make the sound synthesis a kinda “server”)
It might make sense to have this already, because probe may need to be run on a separate machine than where we want to play sound. Probe may need sudo to run, too.
Bincode-serialized events (or alike) over UDP?
The text was updated successfully, but these errors were encountered:
Implement the server as a "composer" crate for a (IMO) better fitting
name. In addition to the binary give it a library section that exposes
logic reused by probes as well as the possible event types.
Start with very basic sound effect of just playing a sample from a file.
This needs some improvements. But we gotta start somewhere.
Also implement a basic test probe that sends test events in a pulsating
frequency.
closes#9closes#4
The text was updated successfully, but these errors were encountered: