CIRCLE WITH A DOT

@Glubhorn9 @Nixtrove pretty sure this was the result when trying to sequence at audio rate

@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 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

@Nixtrove that sounds like a big positive to building a framework for your patches to exist in. I imagine it’s a a refreshing feedback loop to be in when you’re also constantly reiterating the system to benefit patches and vice versa . The one thing that stumps me seeing these sorts of environments is how cohesive 1 hour performances are done & how controller controller mapping is switching throughout a set , it’s wizardry to me

@Nixtrove right so poly would be the only way of having your patches lined up & ready to use without them being open somewhere in the patch eating up cpu? Have you implemented that same idea within the actual patches, my thinking moved towards it for that reason really , like you might have a synth/sampler etc. with features you know you’ll only use here or there or just taking up unnecessary space & it would be nice to open it up as a separate patch

@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

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