NixtroveBack on the maxpatching now, time for polyloadable subfolder rabbit holes
What’s great about that is that I get to patch more, poly the gift that keeps on giving. Loading up some weird patch in the middle of some other thing sounds kinda fun
What’s also perhaps a funny little con to poly is that I’m gonna have thousands of unfinished patches in a few years, but what doth “finishing a patch” even mean…
Will@Nixtrove how do the poly patches slot into your chain ? Is there a routing system set up that just allows you to mix in fx etc. I am veering towards setting up a little submenu folder for this in a sampler I’m working on but also intrigued how you have implemented this with sequencing data ?
@willjames25 Working off the specific architecture I conceived a few years ago and implemented, it’s really just a matter of mixing between what I had before and whatever can be hard-switched or slowly faded into the poly slot. It’s really just sprinkling that poly shit everywhere, where the stuff is already happening, so that particular gizmo I already have (where I put it pretty much) can just do more things. Because I do not want to overwrite my old messy system p much
@willjames25 Still a WIP but I’m thinking it being pretty easy, just to queue switches between the main sequencers I have and then the poly sequencers. Downbeats pretty much, slow fades between outputs maybe a bit of bleed of both, but yeah just imagine putting a poly right next to anything you have and then switch to the poly patch slot (whatever’s in there) whenever you want, that’s the kind of freedom I’m thinking of.
@willjames25 Like the difference between something you hard coded and something that’s swappable. I’m not getting rid of the hard-coded stuff (say it like the machine as it already is) I’m just adding the swappable stuff. I will be pretty much recycling audio channels and message/event cables and inserting poly~ hosted data and sounds into the same routing. I could run down the core architecture in a separate post or in PM
@Nixtrove I get you , it does sound refreshing having a framework laid out so you can easily access you’re patches & layer - have them meld together as a result of data being shared between them and so on. I normally work on patches in max as these contained projects / tools that become a sort of performance environment. Not knowing a lot about poly, is there particular features baked in that lend itself to it being more appropriate for building swappable chains of patches?
@Nixtrove I’m aware that you can create a umenu & send your patch names to poly for it to open but I’m probably missing a lot of its other useful features , especially when it comes to putting a framework in place for having changeable patches. I love what you mentioned about things only dropping in at the end of the bar, like I do that with speedlim a lot or latch in gen but I can imagine that being mental once it’s incorporated into the framework
Glubhorn@willjames25 @Nixtrove how is using latch in gen working for you? I was thinking about using that alot more to reduce glitches when preset switching , cause its on the audio thread rather than the scheduler
@Glubhorn9 @Nixtrove it's perfect for reducing glitches for what I'm doing which is mainly samplers in mc.gen. the first inlet will just be a click impulse and that will be resetting an internal phasor as well as param changes from outside, it's nice dialing in changes and knowing you have a set amount of time before those changes update, I rely on It heavily though, it's super smooth and find it cool for internal sequencing within synths too
@willjames25 @Nixtrove you mean audio rate sequencing?
@Glubhorn9 @Nixtrove i've tried audio rate sequencing where maybe the internal main pitches are doubling/halving at audio rate, for param changes though, a lot of the time I'll have internal delays changing certain params once a new pitch triggers a click within gen. there might be set params within gen that are being sequenced by chance using mix as well. have you tried audio rate sequencing ? I haven't delved into it too much. I'm a gen novice tbh when it comes to the technicalities
@Glubhorn9 @Nixtrove pretty sure this was the result when trying to sequence at audio rate
@willjames25 @Glubhorn9 love this