KamaIt’s quite hard to consistently “compose” and build tracks with a system that constantly informs or hints to new features “it wants” me to integrate. But I’ve been messing with this sound pallet for a minute and it’s slowly shaping up into something you might call a track. I get a bit anxious when it’s time to edit down large chunks of audio, but I tend to remind myself of some of the advice given to me by @sdem and @sean_ae … it’s all about curation and versions 🙏
urner / isaac@Kama11 I've been experimenting with organizing my setup into tabbed subpatchers, so was curious: do you have all 3 tabs running at the same time as parts of one system, or are the different tabs more like different tracks/independent systems that only get run one at a time?
@isaacpearl It's actually something in-between. All the patches communicate with one another to some degree. There is also a “hub" which controls aspects like tempo, tuning and some other bits that let me influence all the tabbed patches at once. If your patches don't depend on being opened within a single instance, I would actually advise to have separate patchers entirely as it's way more CPU friendly due to threading.
@isaacpearl Enabling “mixer parallel processing" in the mixer settings in Max has done wonders for my CPU. But it requires the patches to run as separate patches, not as part of a larger one. Shoutout to @tomhallsonics for sharing this "trick" recently.
I’m actually working on having everything separate. @sean_ae also talked about this a lot - afaik their rig has each track module open as its own patch instead of a giant singular patch. This is obv excluding the poly~ stuff.
I’m actually working on having everything separate. @sean_ae also talked about this a lot - afaik their rig has each track module open as its own patch instead of a giant singular patch. This is obv excluding the poly~ stuff.