hey! I’ve incorporated a lot of kyma processing into my work, but after the initial “need” to use kyma only for the tools that set it apart from other environments, I’ve come to terms with the UX enough that I feel comfortable just doing “normal” stuff in it.
There’s this point where you start to just give in and think like Carla, and it all makes sense. I’ve found that my eurorack experiences over the last two years have been the perfect compliment to a deeper understanding of Kyma—and vice versa. I’d go so far as to say it’s the only visual dsp programming environment that I’ve felt i can intuitively just patch stuff together in a way similar to a modular and be pleasantly surprised.
I mean, yeah if I want to create hyperreal granular clouds I’d rather do it in kyma, where it’s almost effortless to create aggregate resynth patches that split sound apart into >256 individual grains. I’ve not uploaded anything to soundcloud that’s Kyma-specific as of late, and typically I’m using it in the context of sound design for work—so that doesn’t go up on my soundcloud. I’ve attended one kyma kata, and it was pretty badass—we essentially created a “basic” wavetable-based sequencer (very much similar to rossum’s control forge) in a few short hours.
I really would love to get to more katas—they’re very illuminating and useful!
in the meantime, i’ve been so caught up in the modular realm that I’ve just now updated Kyma and am trying to figure out what a damn Kyma Notebook is! assuming it’s some sort of place for capy/smalltalk snippets or text in general or something? browsing the totality that is Kyma’s documentation is a fragmented, but often entertaining, adventure—and i’ve not found any info in the latest kyma patch notes.