I initially had fluid.robustscale~ at the start of everything, but then it seemed weird to robustscale → umap → robustscale again.
Are MFCCs happy to just be chucked into UMAP ‘as is’?
I may expose that as a thing, but for the most part I was thinking to just bake in the settings I use and go with that all the time. I’ve not yet spent time with UMAPs settings to see what works best here, but @jamesbradbury offered up this handy resource:
https://umap-learn.readthedocs.io/en/latest/parameters.html
As I think I mention in the other thread, I want to have a set of analyses/processes that I can use on different corpora generically, so the corresponding realtime patch matches.
It would be great if the realtime analysis adapted/mirrored the settings from a corpus/dataset, but that’s not in the cards. So I’ve got to build everything twice+.
That being said, I’m working on a dict structure to save all the metadata, info, fits, etc… so that I have a single file that I can load. I only store some superficial settings info (fftsettings, numframes, etc…) so that I can remember and know what’s happening, but it would be great to have something more comprehensive that can just populate a corresponding realtime analysis path.
That should be fairly easy. I tried to name things somewhat generically (#0timbre_reduced as the dataset name). Would be curious your results with the MLP stuff as I still struggle to get that to be useful at all.