Some patches run great at lower buffer/latency settings, others can only run at higher buffer settings. Could be nice to have a way to specify ‘ideal buffer/rate setting’ within the yml of a patch that temporarily changes the system settings right when that patch is loaded, so that if anybody tries out a shared new a hoggy patch that runs best on 128-512, they won’t ever have any issue just loading and running it. Or they won’t have to go to their system settings and change the buffer manually to something other than what they normally leave it set on, just to be able to run a single patch, and then have to change their system setting back to whatever their normal preferred buffer/rate setting is when they are done with the patch. An override setting like this would really come in handy down the road once a plethora of patches are shared, to ensure things should run ok across the board for everyone.
One idea: perhaps on the metamodule in vcv there could be a right-click setting to specify the ideal override buffer/sample rate to be saved within the yml (with a default ‘none’ option that just uses main system setting on mm)?
Another (maybe easier?) idea: perhaps a way(system pref?) for the mm to just automatically temporarily adjust the buffer to 512 if it detects that a patch is hoggy