And here is a tutorial video showing some of what karma~ can do:
karma~, has been in somewhat active development since September 2014, when I first contacted raja to see if he would be interested in writing the C code for it. Thankfully, he was interested and able to. From that point we’ve exchanged hundreds of emails discussing the feature set, implementation, and bug fixery. I am eternally grateful for his programming wizardry and endless patience with me.
Before there was karma~, there was my desire to do any kind of live sampling in Max. I first started learning Max in 2003/2004, in the Max/MSP 4 era. Even back then, Max/MSP (as it was then known) was a mythical beast of a program. You could make a unicorn make-out with a hunter if you knew how to use it, and I desperately wanted to. Over the next few years I went through a cycle of drilling the tutorials hard, then getting frustrated because I couldn’t do anything with live audio, and then quitting. I did that 2-3 times.
Enter the Where’s The Party At 8-bit hardware sampler, a cool looking and sounding DIY hardware sampler that I found super intriguing. I’m a big fan of DIY stuff, and the lo-fi sound was right up my alley. I built a complex setup around the WTPA sampler, and used it in various contexts over the next couple of years. It was simple, it was streamlined, and it kicked ass. But I realized I wanted more. I wanted to be able to sample live audio, and not just the electronic instruments I was running through the sampler. So I started conceiving and planning a beast of a setup, originally based around the WTPA 2.0 sampler which was due to come out.
Here’s a page from my sketchbook showing the front/back/top/side panels of what I had in mind:
It was an elaborate setup based around the idea of having an Arduino controlling the WTPA 2.0 via MIDI. It was quite ambitious, as you can see from the sketch. It had an LCD screen, over a dozen buttons, and lots of audio I/O, including a built-in condenser microphone.
[During this last push I was lucky enough to be helped by some great programmers. There was a particularly exciting conversation with Pierre Alexandre Tremblay and Alex Harker (in which the term “Maxcho” was coined!) where Alex was popping in and out of the room every few minutes with recompiled versions of PA’s ipoke~ object in an attempt to do some of the varispeed dynamically lengthed looping that karma~ now does. Sam Freeman, Scott Hewitt, and Constantin Popp also provided some very helpful support/thoughts/code/time during this period of smashing-my-head-into-the-keyboard.]
Having something rigid to start building towards proved to be invaluable. It removed the “terror of the infinite” which can happen when working with an open programming environment. It also showed me that design was as much about what you don’t include as what you do. I designed with laser focused constraints, and made those work musically. What I built eventually turned into The Party Van, a monster of a program that I am very proud of. I’m endlessly humbled by seeing how, and how many, people use it. To this day, the main core modules of The Party Van are called the ‘WTPA modules’.
I initially released The Party Van at the end of 2011. It’s been through a dozen major updates and is currently sitting at a mature 1.1 release. I learned many things along the way while writing it, and developed a passionate belief in sharing things for free. I was only able to learn how to program because people (like the ever generous Pierre Alexandre Tremblay and Alex Harker) would share their patches/thoughts/time with me, so it was something I needed to do as well.
karma~ follows a long line: from initial experiments and frustrations with Max/MSP, through my hardware-based sampling days, to my rekindled passion for programming in Max. One of the things I found incredibly frustrating in Max was how difficult it was to do any kind of live sampling, or sampling of any kind. Declicking became a thankless, near endless chore, which got increasingly difficult the moment I wanted to dynamically change the size of a loop, or jump around the loop arbitrarily, or change the playback speed, etc…. Basically, looping is some of the hardest and unsexiest coding you can do in Max. A real shit show.
karma~ is born out of this really. This frustration. Why is it so hard to create a looper in Max?! Well, not anymore. karma~ is incredibly easy to use. It is super streamlined, while at the same time deep, with a powerful and esoteric feature set. It is, without a doubt, my dream looper. The accompanying helpfile and reference doc are super detailed, presenting each aspect of its functionality thoroughly, and includes a whole set of real-world applications, so that you can be up and running in no time at all.
karma~ is at the center of a massive patch that has been in development since before karma~ itself was conceived. I will post that soon enough, as soon as it is ready to roll out. In time, I will also replace the core ‘WTPA modules’ in The Party Van with karma~ modules. I will be sad to see that homage to my hardware days go from The Party Van, but digital art grieves for no one (Do androids dream of electric sheep? The answer is NO). The 1s and 0s are boot kicks to the ass of the past.
And with that I leave you with karma~. It is currently in its initial 1.0 release. There are 32/64bit versions for Mac and Windows (thanks to Barbara Cassatopo for compiling it for 32bit Windows and Alfonso Santimone for compiling it for 64bit Windows). karma~ was lovingly coded by raja, and I can’t thank him enough! And the linear interpolation used in the recording stage of karma~ is based on ipoke~ by Pierre Alexandre Tremblay.
Leave a comment
-makes music and art
-lives in Madrid/Manchester
-is a crazy person
Learn from me (for free!)
Want in on this?!
Read my PhD Thesis!
and Making Things,
sitting in a tree :