AudioProcessorValueTreeState - Possible additions?

Just out of interest. Are people handling the lack of explicit atomicity in the parameters (the value member) by just never reading the parameter value directly in another thread ? i.e. in the processBlock ?

So would the preferred approach be to respond to a parameter change (via a listener callback etc.) by always setting the related object/widgets value.

In other words with a parameter like filterCutoff you would avoid calling filterCutoff.getValue() in the processBlock ? Instead you would only ever read the param value directly in the listener callback and then update a filter object or whatever.

Say:

myFilter.setCutoff(state.getParameterRange().convertFrom0To1(filterCutoff.getValue()));

Then only ever read/process values from the myFilter object in the processBlock ?

I’m just interested to hear how people are handling these kind of things.