@bobbyrethwish @sean_ae @Kama11

yeah cool this is working for me. see screenshot. so if im making sounds i can load umenus and then quickly preview / try stuff in context, which is great. i'm not use to using umenus this way so it's kind of a mess rn but will refine that somehow...

@trainvids @bobbyrethwish @Kama11 beauty yeah, works well here in individual tests but the real test happens when they’re all done and I go thru the whole set

Apt meme for this tbh

I started rolling it out last night but it’s a bit of a slow one cos I have to resave all the presets in each module (I automate that part but I have to do the edit in stages cos once the old unenu pattrs are gone there’s no going back)

I’m gonna be issuing Rob with some strict protocol lol

Also - I should prob mention that umenu’s types attribute is useful for filtering

eg in that case you mentioned earlier with the json files, it occurred to me I could use that (I won’t though cos our settings have to live in a special place for portability)

@sean_ae @bobbyrethwish @Kama11

yeah using types with .wav to get rid of folder names showing up as an entry in the menu but it's still annoying to see part of the path displayed for every .wav

e.g. "folder/file.wav"

@bobbyrethwish was texting me last night just about doing one menu for the folder and then one menu for the file, which is a good idea but need to see if it works for me

@trainvids @bobbyrethwish @Kama11 oh that's weird, i hadn't noticed, but yeah i see it now

hm, mine doesn't do that(?)

unless - ur scanning subfolders?

@sean_ae @bobbyrethwish @Kama11

yeah my sample library is organized in just two layers of folders. i will probably lazily just dump all the files into one big folder...

@trainvids @bobbyrethwish @Kama11 right yeah

i've been doing it like pic related

rob's always tryna get more subfolders going and i'm always resisting lol, one level's alright (lot of stuff in each one though, sometimes wish there was a search/filter thing)

imagining a little file browser like the one in Live, would be super ideal

(you could prob do that with js right? (i'm shit at js))

@sean_ae @bobbyrethwish @Kama11

this is looking great man - i think the two umenu thing is gonna be the way for me.

@sean_ae @bobbyrethwish @Kama11

that instrument looks cool too, auto slicer module ?

@trainvids @bobbyrethwish @Kama11 ah no that's just the bottom of an amp pattern/envelope thing

idk why i used the word slices lol (just means grid steps there)

@sean_ae @bobbyrethwish @Kama11

aight check it -
this is working cool so far.
folder menu, then sample menu.
leave mouse over the sample menu to use arrow keys to scroll through samples in a folder. you have to give the sample menu a script name for use with [hover] so then make sure to deselect it in the pattrstorage client window...

this was the main thing i missed from using the finder dialog - quickly checking stuff with arrow keys - now i can do this in context of the patch!!

@trainvids @bobbyrethwish @Kama11 ah right, idk if i ever used that hover thing, interesting

i just use a number (click it and voila, arrow keys)

@sean_ae @bobbyrethwish @Kama11

oh right duh that's way easier lol

@sean_ae @bobbyrethwish @Kama11

yeah [hover] is great.

tangent but:
i use it for a large portion of parameter automation via [mtr]. i think we were talking about this during a soundcheck in oct but i didn't quite explain it right.

basically: hover mouse over any UI object. hit R on the keyboard, record controller input on that param, hit R again, starts playback as looping. mtr -> dict saves it with pattr.

i sort of think of it like having an eno style tape loop system but for params.

@Kama11 @trainvids @bobbyrethwish never actually looked at mtr before, seems pretty cool

i have capturing/looping in ours but i went via a totally diff route (often the way eh)