New PD release

Would this make a lot of present And previous user patches unusable without changes too, or just a few? Or is there something particular in the early c&g patches?

1 Like

Yeah lets get that PD update, its like patching in the dark ages, using that ooooold version of PD. For the new versions, there are both 32 bit and 64 bit to choose from. I mean both could run on organelle right? So its mostly about backwards compatibility, I guess.

As @oweno said , only thing I found was an issue with sending out midi clock as the patch was starting - so it’s a small cahnge and quite specific.
3rd party patches might have this if they copied metro but can be easily fixed.

Of course not tested all other patches, but ones I’ve tried were ok on 48, and of course mine are fine :slight_smile:

1 Like

ok, so Ive got PD 0.49.0 compiled and running on my Organelle :fireworks:

a quick test indicate no issues with C&G patches or Orac, audio and midi seem fine.
(even incompatibility issue introduced in 48 seems to have been fixed :crossed_fingers: )

I need to do some more tests (on my vanilla organelle), to check that the CPU load has not increased, or anything else odd is happening either due to PD 0.49 or my build of it.
but so far its looking positive.

Ive provided the build to C&G so they can also take a look on a spare Organelle, and check they are happy with it.

I guess if tests are positive then we can :
a) release it as a package, either on the C&G website, or patchstorage (TBD)
b) later release as part of an OS update.

if we do (a) then if you use newer features of PD in a patch you’d have to let your users know.

if you dont use new objects etc, e.g. you just use editing features, then a PD 0.49 patch should still run on the old PD e.g. I used PD 0.48 for all Orac development, despite the user’s organelle being on pd 0.46.7
so bearing this in mind, you can already use Pd 0.49 on your desktops (pc/mac) for the new editing features, I know i am :wink:

I guess we should also keep an eye on the PD dev lists, incase they decide to release a minor update, though its very quick/easy for me to rebuild an updated pd package if needed.


Alwys hard at work :wink:
Thanks for pushing forward!! Fingers crossed for new stuff…

Hey man.

Just a big thanks you for all your amazing work on the Organelle OS and patches. Your work, and this community’s work, is one of the reasons I bought an Organelle to begin with. :slight_smile:

Quick question: Its been a while since there have been an OS update and therefore and update of PD.
PD is now version 0.49.1 and has some nice new features. I know you’re not working for C&G but I thought you might have an inside scope on things to come? :slight_smile:

1 Like

Ive supplied a 0.49 build and it does look good… (I use it all the time without issue)

but really needs an OS release, as we don’t want to get into a situation where to get some patches working you have to do PD upgrade… it’ll be confusing to users.
(but saying you have to be on OS 3.5 (or whatever) would be ok, and we could even build this check into the patch)

But i agree its a useful upgrade, mainly because of the clone object which makes polyphonic patches much easier/flexible.


Pd 0.50 just dropped.


change list

------------------ 0.50-0 ------------------------------

new pdcontrol object allows getting patch's owning directory and calling arguments, and opening files in web browser under patch control (useful in help files).

new nonlinear low-pass filter, slop~, for use in designing envelope followers and dynamics processors.

attempted to fix limitations on incoming MIDI and network packets. Things seem to be improved but the improvements aren't exhaustively tested yet.

improved HTML style in documentation and more info on writing externs.

updates to Iohannes's smart patching features

sort method for text object. Also text searching can deal with restricted range of lines (so that, for instance, you can iteratively get all the matches, not just the first one).

internal changes to improve scheduler behavior and memory management.

"zoom" feature updates to handle data structs better.

busy at the moment, but in a few weeks - I’ll compile it, and check compatibility etc
I’m mainly interest in the midi, scheduler and memory management changes.

however, its likely it will be better to wait for 0.50-1 or 2, let it settle down - as 0.49 seems very stable to me… and there are a few comments around, that things are a little incomplete in 0.50.
(besides ive got a whole load of change in 0.49 that i want to start getting into my patches!)


I was patching away on my mac, but when I transferred the patch to my Organelle-M I was missing the [slop~] object.

  1. How about we update PD now? My mac is on 0.51-3, Organelle-M is on 0.49.0.
  2. If anyone want to guide me in the direction of how to actually do this myself that would also be cool as I am slooooowly dipping my toes in the direction of Linux as macs are getting more and more locked down.

@chrisk @oweno @thetechnobear :man_shrugging:? :slightly_smiling_face:

We should look into this for next OS update… The Organelle OS is old enough that you can’t just run an update to grab Pd 0.51, so you would have to build it from source. Not impossible but you might run into dependency problems. We have an experimental OS build based on the newer version of Debian (10 aka buster) and it looks like there is a backport package available for Pd 0.51. We can try this out and maybe post a beta disk image.


Awesome! Since it is pretty cheap and easy to just have a couple of cards it would be fantastic if you would post betas. We wouldn’t run to big of a risk of messing something up as we can just put it on a separate card.

1 Like

Hey Oweno !

Just curious - is that update planned for the original Organelle too ? ( An update from the older Arch ?)

@KristofferLislegaard we uplodaed a new disk image for the Organelle M. It is based on the newest Debian version and includes the latest Pd (0.51). You can burn it onto an SD card following the same instructions in the manual.

The first time it boots up it takes about a minute because it resizes the file system to match the size of the SD card. This is useful if you burn it onto a large SD card. Previously the disk image was static 8GB even if burned onto a larger card.

We don’t have plans to update the original Organelle right now. It is theoretically possible but would take a bunch of work to get everything up to date. (probably build new disk image from scratch would be the best way).


That is great news!

But I have a hickup. I burned the image to a new card with BalenaEtcher and it looks to have booted fine.
I got it on wifi and started VNC.
There is a folder called usbdrive which is the default patchfolder even if I have no usbdrive mounted. It has a folder called patches inside it that is impossible to edit. So I am unable to launch my own patches (on the sd card) on the Organelle itself.
I also tried running the script to make the system not read only, but that doesn’t seem to affect the usbdrive folder. So I am unable to add my own patches.

Am I doing something wrong or is this simply a bug with the new image?

Hah yeah I had a crack at building from the latest base ARM-ARCH … that was a few weeks ago :sweat_smile:

I’ll start a new thread with progress updates if I make any worth cheering about

Ahh yeah, sounds like a bug. Removing everything in /usbdrive maybe will fix it. Does this work?

mount / -o remount,rw
rm -fr /usbdrive/*

That sounds interesting!

1 Like

Yes that worked indeed! Now I can use it. Thanks for the quick fix :smiley:
Looking forward to learning more Linux myself. It’s a slow process.

Two small not important comments:

  • Every time I want to open the sdcard folder or usbdrive folder (that is now working correctly) I have to manually select that I want to execute the scripts. Is this also a super easy fix?

  • There are some icons that seem to be missing its picture file.

I guess you can just put it on the list :slight_smile:

Skjermbilde 2021-06-22 kl. 18.13.34

Edit: Deken seems to be not working.
Edit 2: It started working. Not totally sure what I did different, hehe!