I’m loading parameter state using
ValueTree::fromXml(). The range of a given parameter_used_ to be 0 - 1 but changed to 0.001 - 1. Because said parameter is stored as 0, the load turns it into a NaN. All sorts of problems arise with slider attachments and more.
Is it an idea a parameter makes a choice by either clipping within the range (preferred) or changing to default? I don’t think NaN is the way to go.
Obviously, the range shouldn’t change and have been decided on from the get-go, but reality says so otherwise and our client wouldn’t want to throw away all their old presets.