Add option to use persistence on the display_params

[pedrojg321]

No description provided.

[pedrojg321]

The idea is that I store the f{display_param} when I click on the encoder. However, I´m having an issue during Load, where I assign these f{display_param} with the stored values, but I think this would not work because setting these floats does not actually set the plugdata value, right?
Is it possible to set the hv_param on the plugdata side from the c++ world? I naively tried to use sendFloatToReceiver but did not work.

[dromer]

I don't think this is the right approach and it makes too many assumptions of the current hardware setup.
Is this reading/writing from sd-card somehow?

I am still working on a way to store data from the patch. While this will use [soundfiler] object and wav files, it will be able to store any value inside of these. This way the patch can decide to store or load values from sd-card and the wrapper can stay clean.

The display code will then only display data, not be involved with any storage or retrieval of data.

[dromer]

Ah, this post explains PersistentStorage a bit: https://forum.electro-smith.com/t/saving-values-to-flash-memory-using-persistentstorage-class-on-daisy-pod/4306

So it uses part of the flash memory. I still think it's not a good approach to put such logic outside of the patch.
I also don't see the use-case for the display parameters to be stored like this.

[sergiogf93]

Yes, that's the post I found as well and the implementation I added is based on that.

But are you saying that it's already possible to do store/load from the patch? I agree that would be better, but does it require an sd card? I will look into it

[dromer]

As I said: I'm still working on it.
It would use the sd-card but would be usable from within the patch and easier to test/reproduce etc.

See #288 for the PoC for DPF builds.