Just made a recording I’m really proud of. I’m really enjoying being able to explore the analog inputs that the #ObliquePalette gives me in #plugdata .
I haven’t hooked them up to external modular gear yet. That’s next.
Still gotta optimize for sample rate, but it’s already fun to play with!
Shown: me playing it with #westernmasselectronics last week! Recording is coming, but the track I just did is basically the same as my set that night, but 3x the length and with a few refinements.
10 days of using #asahi daily.
It's been a really smooth experience so far.
Been playing mostly with #supercollider and doing some recreational programming.
I want to get more into #plugdata as my #maxmsp alternative for when I am on Linux, but the current version has some visual issues.
Using #puredata vanialla with the touchpad is just awful though.
Feels like the "hot zone" around node connections spans just a couple pixels and makes the entire patching experience kinda unpleasant.
Today, I got past the mysterious technical problem I’ve been having with the #ObliquePalette and I’m back to building a creative technology out of and for the propagation of hope.
The Oblique Palette asserts that computers are for you to explore new regions of human creativity.
Livepatch in #plugdata. Control with weird controllers or
#eurorack modules.
Send out sound or CV from your patch to other modules and your mad science electronics.
Make it dance with the servo outputs.
I can have PlugData running *inside* of Bespoke Synth.
Takumi Ogata just published this #daisysynth patch for #plugdata and its Heavy compiler to build a hardware granular
synthesizer.
I’ve been wanting to build a live looping instrument that does this.
But I’ve also been thinking of granularizing a wavetable in case that project was going to be simple enough that I’d just finish it.
Gonna try to do the easy, simple thing first, like I tell my students.
@lislegaard Puredata / Plugdata (newbie) user here. It feels pretty active in development: both softwares had updates pretty recently and have active communities on Discord.
#plugdata #puredata
I went to take a picture of the back of the #ObliquePalette prototype 0.5.5 and it came out like this. So I gotta share.
The front, in the second image shows the inputs & outputs. Analog knobs, 3.5mm jacks for Eurorack, pin headers for Arduino (or other electronics) & servos.
(It's for turning computers into machines for making art, fucking around, and falling in love. You talk with it using the extremely powerful graphical language, #plugdata.)
#modularsynt #synthdiy #eurorack #computerart #
Do you wish computers were for you to make art with, and not just to make money for your boss's boss?
Then you probably want in on the Oblique Palette project. Make a computer that's part of a #modularsynth that has #robot parts and is programmed with #plugdata
Let's make the future we wanted.
PlugData is a concatenation of several related projects, and allows a user to include objects from any of these projects.
It can also compile to a plugin by means of an included project called Heavy.
But Heavy doesn't support all of the included objects. It doesn't even support all of vanilla PD. So if you want to use delay~, well, you can't.
So what's the advantage of writing your Heavy patch in an IDE that will allow you to build, prototype and test a bunch of stuff that will never compile? There's a way to build a patch in "Compile Mode" which will tell you if your objects won't work, but turning on that mode after you've built a patch is too late. It does not appear to generate a report.
tl;dr If you want flexibility in terms of compiled output type, use Faust
Hoolleee shitballs. The #ObliquePalette might be feature complete.
8 analog in.
8 analog out.
A hardware #plugdata object you program graphically.
(thanks to @ArchiteuthisFlux& the Jumperless krewe for finding the hardware bug!)
I can now control #plugdata software patches with #modularsynth CV or by twisting a knob — and the patch can control hardware with control voltages or by twisting a servo!
Computers are for making art, fucking around, and falling in love.
Ok, so I have a panning algorithm I could port to #plugData. It was one audio inlets and one data inlet (the pan knob) and two audio outlets.
I want to use this with #ardour, so ideally, it would replace the built-in panning on the tracks that used it.
Is this complicated?
(Is there a more modular DAW I could use? I just want to scoot audio regions back and forth in a multi track system and automate faders and plugins and be able to bounce to disk.)
Prototype 0.5.5 of the #ObliquePalette is in! I’m 75% sure it’ll work, though I’m hunting a comms bug in the firmware.
The honorary bit portrait on this one is Susan Kare, the original graphic designer of the Macintosh, creator of the I-beam and finger cursors, little house for representing “home” in HyperCard — the direct ancestor of the Web —and so many icons we take for granted now.
It’s just barely possible that I will have voltage control of and by #plugdata this weekend!
#plugdata is good. It have a lot of good ui ideas implemented nicely but when it comes to performance #puredata vinilla wins. I using Linux with realtime kernel and when it comes to processing resources I become really greedy. The downside of vanilla is that you have to dig into tcl plugins to make UX better but there is really nothing even close to how pure data performing (MAX map, #bitwig etc all bloated).
