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
We desperately need scopes. At least a scope for the master output, but the real game-changer would be adding "Scope" units in the synth, for displaying arbitrary signals in the scope.
The text was updated successfully, but these errors were encountered:
In addition to the oscilloscope and loudness/peak detections, this
commit refactors all the channels between components (i.e.
ModelMessages and PlayerMessages) etc. into a new class Broker. This
was done because now we have one more goroutine running: a Detector,
where the loudness / true peak detection is done in another thread.
The different threads/components are only aware of the Broker and
communicate through it. Currently, it's just a collection of
channels, so it's many-to-one communication, but in the future,
we could change Broker to have many-to-one-to-many communication.
Related to #61
Well, there's a rudimentary version there. I merged it as it was good enough, but not perfect. I will return to it to improve later, but I have a bunch of more urgent things to fix in the meanwhile. Still didn't want to leave this one completely out of master.
We desperately need scopes. At least a scope for the master output, but the real game-changer would be adding "Scope" units in the synth, for displaying arbitrary signals in the scope.
The text was updated successfully, but these errors were encountered: