Editing "basic sampler" to be more than 2 seconds


Im not saying its ‘cheap’ , but I suspect expectations are bit high… an OP-1 is nearly double the price.

If you are planning to invest in Organelle, then download pd vanilla, and start experimenting with it, Organelle is ‘just’ pd running on a linux box, with some knobs/keyboard. its not a cut down form of pd.

being a ‘novice’ in PD is even more a reason to dive in…
its a win/win for you - you find you don’t like or can’t get to grips with PD - you save $500… you find you like it, then when your organelle arrives you already know some PD.

personally, I think if people start expecting others (including C&G) to start posting lots of patches, there going to get disappointed pretty quickly, there are just some many possibilities, to provide examples for all is going to be impossible.
(and theres a huge amount of PD resources available… online, and in books)

Id say there is one aspect though that C&G need to provide a bit more guidance on,
available resources (cpu/memory)… we know the specs, e.g. its a single core A9, but what does this actually mean how complex patches can be? this is something you cannot easily tell without having an organelle.
so patches demonstrating, how many voices (even simple oscillators)? how much ram for samples? is real time streaming practical (due to performance) from the usb or internal drive ?

currently, I’m still on the fence with organelle, as I think the single core A9 seems a little underpowered, I really wish it has been a dual core, and a bit more memory… but Id loved to be proven wrong.


I was/am a member of the monome community from some of the early days of their devices and online forums. the community they built was an amazing and supportive place which grew and grew despite the monome being difficult to explain, had a complex installation + implementation process and a device that primarily interfaced with max/msp (so not beginner friendly). Most of the flagship monome applications were first developed by brian + kelli (monome) themselves but the community really took ownership of creating the kind of applications that they wanted to see/use which was fantastic. Nobody was posting things like “why don’t monome create an application that does XYZ?!?” Instead people were asking help from the community at large.

"I would love to create an XYZ app… Could someone point me in the right direction?

“Here is my work in progress… I’m stuck… can someone help?”

Not everyone has the same needs or the same taste in music which is the beauty of an open-ended device. I hope that the community that pops up around the Organelle will be even a quarter as awesome as the one that grew around monome.


does pure data even benefit from something more than a single core?


I don’t think PD can use multiple cores (unlike Max which can via poly~)
but organelle is also running linux, so it would be nice to have a core ‘dedicated’ to PD, and the other for other stuff, include the linux OS. (device i/o, the osc server that organelle uses to communicate with PD etc).
( you can also port non-PD apps to organelle too, which could make use of multiple cores - though I accept this is ‘advance’ use :slight_smile: )

perhaps the cost differential between single and dual core was prohibitive, but seems surprising given the product price.

anyway, as I said, it would be interesting to see what is practical with the given specifications, even some statement on how much CPU is being used by the supplied patches might give us a better idea of whats available. (and also memory , the 512 is quite low…)
I love the concept of Organelle, and know enough Max to find it really an inviting proposition, but I’m just concerned, how quickly I’ll find I’m hitting resource limitations.


I just posted some more detailed info about CPU performance!


Hi @jessetal, I just uploaded a pair of patches that together demonstrate accessing sounds from a shared folder. They are actually slight modifications of two standard patches Sampler Style and Sampler Style REC. One allows you to record samples, and the other to sequence recorded samples. The samples are saved in a separate Sounds folder which lives next to the Patches folder on the USB drive.

you can grab it here:


The adjustments were made in the sampler-voice.pd sub patch to make this happen. Telling Pd to grab resources from different folders is pretty simple, and hopefully this sheds some light on the possibilities.

I should point out, however, that we don’t really consider the Organelle to be as much an all-in-one workstation as an all-in-one instrument. We generally think of the patches as stand alone instruments focused on translating human interaction to sound. While one could certainly build higher level functionality to support a multi-layer type workflow, it would take some wrangling because of the layout of the controls, which are setup more for playing than for editing. In other words, the Organelle paired with a dedicated multitrack recorder would then be a great all in-one studio!

New C&G Organelle Patches

That’s brilliant, Owen! I got the impression that you guys viewed the Organelle as more of an insteument. That’s certainly reflected in the patches. :slight_smile:

However, even though you may not have considered it as a more comprehensive music production device, it’s already achieved that potential through patches like those you’ve just mentioned.

There are certainly some limitations but there is still much power to be had! :-0


I’ve gotta bump this thread because I don’t want to make a new topic for this question:

Where exactly in basic sampler is all of this stuff happening? I have been cramming this pd stuff for a few days but let’s just say I smoke weed all day and am busy as a line cook… I’m not exactly a student and like, I haven’t had a good method of trying to learn this.

Pd tutorials aren’t seeming to help me because I would like a concept of what is happening on the organelle’s patches and pd seems to go in a lot of other directions I don’t want to fill up my aspergers with

So, like, where within basic sampler is the time getting limited?
And additionally how do I like, read these patches, on that patch storage site? I’m at prob a 8% understanding and I kind of know how to think of it like modular but I come from hardware and not computer biz… So when I look at that picture of Analog Style, where is the command to the aux? Why are some things not represented is what is throwing me off

i wish someone here was into making viddies lol I’m kinda stumped and learning a lot of new words

implying I’m learning at all


Yes! It would be great if we could learn Pd together on this forum. Explain the screen caps of patches and walk through all the “left out” info…


Thought It might be better to re-live this thread than to create a new one. I saw a new patch today Loop Jam Rec but there is a 2 second limitation recording time. I’d love to have a slightly larger buffer. I’ve been trying all morning to fiddle with arguments and values trying to edit the patch in PD with no result. Any point in the right direction would be awesome. Thank you :slight_smile:


I think someone should assemble what @josephbranciforte has already developed, which is a functional asynchronous multitrack looper. I guess it should be a trivial task for someone with some knowledge of pd.

*Pardon my English-


Sounds cool! You could achieve some asynchronous looping of samples in ‘samplenest’. Not sure what the sample recording time limit is in that patch but it well exceeds 2 seconds. It is not quiteloop pedal-like though, if that is what you need. Could be worth checking that out though.
Btw your written English seems advanced and can’t notice a single mistake.


@Jacobino - we haven’t tried any other lengths in Loop Jam Rec so there’s no guarantees longer recordings will work. You have to change two parameters.

The first is in the jam-loop-voice.pd file. The ‘2000’ in the circled object sets the length at 2000 milliseconds:

Change it to your desired length (ex: ‘5000’, for 5 seconds)
Then in the cg-rec-array subpatch (just click into that object above), you need to change the properties (right click) of the circled array:

The ‘88200’ size is the length of your recording in samples (44100 samples/sec for 2 seconds). So if you wanted 5 seconds, you would change this number to ‘220500’ (44100 samples/sec * 5 seconds).


Thank you so much for such a detailed and easy-to-follow explanation! Will give it a try once i get home :slight_smile:

Edit: I just tried it, had to also change the samplerate on the cg-load-array for it to work. Thank you so much, this thing is insane :blue_heart::musical_note::musical_note::musical_note


i woudl try with 5 seconds first that seems do-able!


Can you please share you edited version of the patch? I would also love to use it :smiley:


Damn, I think these simple changes aren’t enough for ready-made wav files dropped in the sound repertory.
I did all of these changes in loop jam rec, and all I get are 2 seconds of loop, and sometimes even 1 second, even though I set the “rec” and “load” array to the correct sizes.
I really don’t get it, there must be some other “size” parameter that changes when you record, which isn’t changed when you simply load wav files.
I looked over the all patch and subpatches, read the helpfile of every object I didn’t already knew, my wav files are mono 44,1kHz.
I give up, all this sample loading/reading/looping in pure data is too complicated for me :exploding_head::flushed:


OK I think I’m starting to figure out what’s going on in Loop Jam Rec.

What I want to do is make a loop jam rec patch without the “rec” feature. Instead, I want it to playback samples such as loops and fills that I would be able te play live. So I put wav samples in the “sounds” file.

The problem is : the loop playback length seems to be determined by the recording duration, and that happens in the “record guts” subpatch and in the cg-rec-array abstraction.

So I guess need to figure how to get rid of the record features in the patch, and tell pd to match the loops playback length with the actual size of the pre-loaded wav files.
To sum up: transform “Loop jam rec” into “Loop jam”.
Easy, isn’t it?


Before deleting the ‘Rec’ parts of the patch, did you try:

…in addition to changing the jam-loop-voice.pd file & cg-rec-array subpatch?


Hi Chrisk, thank you for your answer,

I did try to edit the “load” part as well, but I guess it worked for Jacobino because he used the rec feature to make his sample bank, whereas I want to import mine via usb. And I guess the recording duration sets the playback duration, somehow.
I guess my own samples were looped exactly the same way as the default ones were (for instance, almost 2 seconds for key 23, and 1 sec for key 24).