@trainvids @bobbyrethwish @Kama11 there is actually one drawback to this method - rob won't be able to run my stuff at his place without duplicating the file path structure, because all the presets will be based on full filepaths

that's actually kind of a dealbreaker really, ugh

great for all you solo artists though :D

@sean_ae @bobbyrethwish @Kama11

hmm
bc you have different sample libraries?

@sean_ae @bobbyrethwish @Kama11

i see yeah but if the sample library is in the max search path wouldn't u just be able to get around this because the textedit only needs the name of the sample? e.g. drum.wav

and if that is in the search path, (which could be different on your diff machines), then it would still load correctly?

@trainvids @bobbyrethwish @Kama11 the umenus are outputting full paths to the textedit (which i could prob regexp into shape yeah)

@sean_ae @bobbyrethwish @Kama11

ah yes yes, cool. yeah im getting sample file from info~ so it's just the name, not path.

[strippath] ?

@trainvids @bobbyrethwish @Kama11 yeah you're right that should work

there's no reason to pay attention to the rest of the path apart from what the umenus are doing - right on

@sean_ae @bobbyrethwish @Kama11

yeah sick, i'm gonna try and get preview samples via umenus working next time i have a minute....

@trainvids @sean_ae @Kama11 love this thread, great work team 🥳

@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 @trainvids @bobbyrethwish @Kama11 a bit late to this , but looks interesting. I usually use polybuffer~ because I assumed loading samples from disk could cause glitches when changing presets. Do you preload presets into an unused voice or something or is it just a non issue?

@Glubhorn9 @trainvids @bobbyrethwish @Kama11 i keep buffers at global level and create/destroy as necessary, so they load when the system boots- and modules then just refer to them (when you browse it just checks to see if that buffer exists already and if not it creates it)

they're all separate

i don't think polybuffer existed when i built that, but it works so

@sean_ae @Glubhorn9 @trainvids @bobbyrethwish does this mean you have a defined number of buffers and if a check from a module comes back negative, it just renames the buffer in global to whatever the referenced buffer in the module is?

@Kama11 @Glubhorn9 @trainvids @bobbyrethwish no, it looks to see if a buffer exists with that name - if so it just points to it, and if not it makes a new one and points to that

and there's a destroy button that only works for the last created buffer, so if i'm browsing it's a kind of two finger affair (idk if i could figure out a better way of doing that.. probably, but i'm used to it)

@sean_ae @Glubhorn9 @trainvids @bobbyrethwish that’s deadly, had no idea you could do stuff like that. Definitely gonna try and dig into the idea seeing if I can come up with something along the lines. Cheers man..

“Two finger affair” lol 🤣🤣

@Kama11 @Glubhorn9 @trainvids @bobbyrethwish [thispatcher] help file should get you going