Oh that’s what you mean… I stumbled into this one some time ago:

Does anyone know if anyone has released ‘helper’ patches for using the ableton push with puredata? I poked around online for a bit, but couldn’t really find anything and I don’t really want to try and write my own scaling to make the keyboard isomorphic.

I am glad this thread has had a bump. Playing a lot with automatonism (just on pc) and adding my own custom bits onto it. really enjoying getting into something new. Not sure how to go about making my own patches into automatonism modules. Also plan to get a bela shield and make some kind of noise machine. though i do have a half built axoloti machine on my bench that i should make something of.

Any links to any resources appreciated.

I think this is the starting point you’re looking for, explains how to surface controls at the parent of a re-usable subpatch:
http://write.flossmanuals.net/pure-data/graph-on-parent/

1 Like

Ah yeah, I was looking for someone that already had made a subpatcher. Ableton has pretty great docs here https://github.com/Ableton/push-interface/blob/master/doc/AbletonPush2MIDIDisplayInterface.asc I just don’t have enough free time to actually do the leg work right now.

the display cannot be accessed from midi, basically you have to write a C/C++ external so that you can communicate at the USB level.

I’m doing some work in this area at the moment, so you can keep an eye on this.

note: not quite sure which platform your using, my priorities are Mac and Linux (ARM and x86), so whilst I’ll no doubt do windows, its not really a priority.

if your just after lighting up the pads/and getting notes, that can all be done via CC/note on/note off messages - and is pretty straightforward.

developing isomorphic layouts is pretty trivial, you just convert the note # into x, y, then the new note number = base + (x * row offset) + y … if you want to add scales (rather than chromatic), that gets a bit more complex as you need to use the new note number to index into a scale array.

anyway, i’ll be doing this all in the ‘system’ I’m developing, but just can’t commit to when it will be available.
(my approach is to run a separate app, which is communicating with a PD external, this is because I personally don’t want the USB code to run inside the pd process… though no technical reason it can’t)

2 Likes

Yeah, I’m decent enough at C/C++ but not super super interested in writing a C external for wiring up the display (this would be using a Push 1 anyway). I appreciate all the suggestions, my initial question was out of sheer laziness. I’ve already got a few things that work with an m64 to do isomorphic things with puredata/whitewhile, it was more a “if this exists, I would use it” type of problem. Your organelle project looks dope! I’ll definitely keep an eye on it.

oh, you referenced the Push 2 spec in your post above… so I assumed you were talking about the Push 2.

the Push 1 is completely different (and that spec does not cover it) , the Push 1 uses Sysex for driving its display, so you can do that from within PD… you can find the details of the sysex with a simple bit of googlefu
No idea if anyone has done anything for the Push 1 and PD… I know there was something available for Max.

oh, you referenced the Push 2 spec in your post above… so I assumed you were talking about the Push 2.

My bad I should’ve been a bit more clear on that. Going off of https://github.com/Ableton/push-interface/issues/5 looks like a spec similar to the push2 one won’t be happening. http://pushmod.blogspot.com/ has some stuff, I’ll search around for a sysex helper. I feel like there must be some prior art for puredata that’s push1 specific.

Is there any way to use deken from the command line?

I think it compiles to an LV2 plugin, which would mean it can be loaded into Jalv or mod-host.

Oh wait, I was thinking of Dexed, which is a DX7 editor.

deken is a package manager for pd-vanilla. I guess there’s only a TCL implementation, so I suppose that means headless Pd users on RaspberryPi will need to either use their distro package manager, or compile/install manually.

1 Like

Found this puredata manual during some searches - hadn’t seen it before, and I’ve had a lot of issues finding puredata docs that I like. It seems really up to date and organized in a way that makes sense to me. I couldn’t find a link to it in this thread, so figured I’d drop it in.

http://write.flossmanuals.net/pure-data/introduction2/

1 Like

Oh yes, that’s of the best manuals for Pd I have found so far.
This book is also very good imho: http://www.pd-tutorial.com/english/

You could just remote into the machine using VNC or something. I’ve been using that for my pisound box. Works pretty well.

Then you have to install graphics packages. I don’t want to.

I came to the conclusion that supercollider is more aligned to my goals for this box.

1 Like

have 2 images (different SD cards)… one for headless, one not… then just transfer binaries across from one to the other (via card reader or whatever)

I quite like having different images for development /release… partly because its useful to have all sorts of tools including X for dev/debugging etc… (i do similar with virtual machines) , also means you have a backup of sorts.

Are you concerned about system resources being taken up by graphics? That’s interesting I hadn’t considered that. I wonder are those resources allocated and in use even when a monitor or Remote Desktop isn’t in use?

Honestly? It’s because this SD card I happen to be using is on the small side.

But it’s also an objection on principle that a package manager should not require a GUI.

isn’t it really just a small front end to :
http://deken.puredata.info/search?name=

so you dont have to use the tool…

you can quickly create throw together a script to do wget | grep | tar … which’ll do the same thing - no?

if you don’t need to automate it, basically the wget tells you what you what you need to know anyway and you can just cut n paste the url you need

or is deken smarter than that?