decided against maintaining a separate 'presets' property in the ValueTree, since this is a view modelling concern that only the table cares about. instead, store as a tree. let the table component be responsible for maintaining a view over a subset of presets, instead of bothering the ValueTree with this. this is an effort to dial back the use of the store, and prefer to use it where it provides the most value rather than using it for everything.

Source/PluginProcessor.cpp

@@ -47,7 +47,7 @@ JuicySFAudioProcessor::JuicySFAudioProcessor()
         { "path", "" },
     }, {} }, nullptr);
     // no properties, no subtrees (yet)
-    valueTreeState.state.appendChild({ "presets", {}, {} }, nullptr);
+    // valueTreeState.state.appendChild({ "presets", {}, {} }, nullptr);
     // no properties, no subtrees (yet)
     valueTreeState.state.appendChild({ "banks", {}, {} }, nullptr);
     // valueTreeState.state.setProperty("soundFontPath", "", nullptr);