Is there any performance drawbacks from using a ChangeBroadcaster to notify editor elements that a change has occurred almost every processor callback? Being that the processor is called many, many times per second (or could be), I wonder if there is any performance issues with that.
My reason for this is to replace the need of using the Timer class to refresh the editor every update, for example in use of an amplitude meter. Though this — in best practice — is capped to 60 hz, so unfortunately monitors with a greater refresh rate do not benefit. My thoughts is sending a change every processor can make the motion smooth for any monitor.