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
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
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.
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.
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:
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
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?
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).