# LTEp demo patch

**URL:** https://discourse.flucoma.org/t/ltep-demo-patch/821
**Category:** Pre-Release Toolbox2 Code Sharing
**Created:** [March 10, 2021, 4:22pm UTC](https://discourse.flucoma.org/t/ltep-demo-patch/821 "2021-03-10T16:22:53Z")
**Posts on this page:** 1
**Showing post:** 7

<div class="post-metadata">

### Author: ![rodrigo.constanzo](https://discourse.flucoma.org/user_avatar/discourse.flucoma.org/rodrigo.constanzo/32/12_2.png) [@rodrigo.constanzo](https://discourse.flucoma.org/u/rodrigo.constanzo)
#### Post date: [March 11, 2021, 1:16pm UTC](https://discourse.flucoma.org/t/ltep-demo-patch/821/7 "2021-03-11T13:16:27Z")

</div>

> [@tremblap](#):
>
> the first thing I wanted to know is why you used standardisation before the UMAP in the timbral space. Did you try directly, or with RS instead?

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’?

> [@tremblap](#):
>
> UMAP has a lot of parameters to tweak and the number of iterations is quite low so I get a lot of varience in my case so exposing those at the top would be fun too…

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](https://umap-learn.readthedocs.io/en/latest/parameters.html)

As I think I mention in [the other thread](https://discourse.flucoma.org/t/lte-an-alternative-to-lpt-for-people-who-dont-care-about-pitch/605/17), 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.

> [@tremblap](#):
>
> and then in line with our paper I wanted to replace UMAP by PCA and MLP-autoencoding just for shits and giggle…

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.

---

_[View the full topic](https://discourse.flucoma.org/t/ltep-demo-patch/821)._