Hey guys, i found out that some users cannot dowload patches applied (c'mon, it's been uploaded just 12 years ago! ) but i could download them with no issues. So i decided to reupload first and latest file in this thread.

Song_0000.zip

Cave_of_Creation.zip

It's not as if i've been enhancing this abstraction for 5 years. But here's the new version. I recently answered a question on [env~] object in Telegram/IRC Puredata chat and, as a result, slightly improved the recorder. Now it has more detailed meter scale and displays amplitude precisely. (Compared to Steinberg Wavelab, tested at 0, -6, -12, -18, -24 dB). recorder.pd

An example can be found here (i'll attach more demonstrative one if somehow manage to invent it). 123.pd

It may seem obvious, but anyways,

This:

|
[t b b]
|
[t b b]
|
[t b b]
|

etc., instead of this:

|
[t b b b b]

Makes consequent operations in Pd almost as easy as in scripting languages.

@EEight hey! I'm still on game, exploring various approaches to make truly realistic sound.. And yes, there will be new patches! For instance, that latest version of recorder.pd was made for a complex patch under construction, where i was exploring the way to use a sort of "particle system" to make realistic sounds which use more than 100% CPU (preview mode allows to hear sound in real time, render mode allows to record much more complicated sound to disc with small chunks).

P.s. To those who followed me outside this forum, - sorry for not having warned you personally before deleting all my accounts in all social networks. It was quite an impulsive act. I'm always open to communication anyways.

One more update:

• record button turns red (bug fixed: it turned red even if one cancelled "save file as" dialog)
• no mute button, volume slider instead (initial value is zero, it's suitable for me, but you may change it, just turn on "init" in slider properties and save abstraction with your own initial value)
• bug fixed: amplitude scopes weren't accurately synced with sample rate

recorder.pd

This abstraction is very simple but i use it so often that i thought it might seem useful to anyone else.

I use it instead of [dac~] as a master output, sending all audio to its inputs. When i need to record 32-bit stereo sound file from what i hear, i press record button, choose where to save file and its name (there's no need to add .wav extension). Recording starts immediately and goes on until stop button is pressed.

It is quite easy to modify for your needs. For instance, change "open -bytes 4 $1, start" message text to "open -bytes 2 $1, start" for 16-bit recording, or delete right inlet~ and change [writesf~ 2] to [writesf~ 1] for mono recording, etc. I think, most people use only one recording format in most cases, so it has no mono/stereo or 8/16/24/32-bit switches, but you can add your own ones.

http://www.pdpatchrepo.info/hurleur/recorder.pd

Open main.pd and just listen. If this patch uses more than 100% CPU on you computer, open [pd water_sound_generator], then [pd water] and delete as many [water.pd] instances as you need (but the more you delete them, the less realistic sound you hear).

See comments inside water.pd to understand how it works.

http://www.pdpatchrepo.info/hurleur/shore.zip

Just unpack an archive, open main.pd and enjoy. Warning: may start with quite loud short sound.

http://www.pdpatchrepo.info/hurleur/Song_0000.zip

Greetings,
This is my first post here. I made my first useful abstraction and thought it worth sharing. It's a mixer with volume, pan and stereo width controls, mute/solo mode, pre/postfader and 'learn' triggers. Just turn on any 'learn' trigger and move any knob/slider on you MIDI controller, - corresponding slider will follow its movement.

http://www.pdpatchrepo.info/hurleur/ch.pd

Glad you liked it! I slightly changed my version of recorder.pd - now it has amplitude scopes.

http://www.pdpatchrepo.info/hurleur/recorder.pd

Thanks for encouragement, austin_ep! I can share two ideas which, to my mind, helped me the most. The first one: before making this patch I listened various water streams and seashore sounds thoughtfully. Watched their waveforms and spectra, slowed down, listened again. This analysis took about 20 hours (80% of all time spent on this patch), until got clearly aware of what exactly I was going to recreate. It's impossible to make desired sound keeping your fingers crossed, not having clear understanding of it, but hoping that your dim ideas will take form during the process (mine didn't ). The second idea: I made a blank [water.pd], copied it many times, and then, listening to all copies at the same time, I improved [water.pd] step-by-step. I didn't listen what single [water.pd] sounded like, because it didn't matter how realistic single abstraction was (as far as complicated sounds are concerned).

As for your question: although this patch was a sort of training (I wanted to test myself if I was able to make any sound from scratch for 2-4 days) at the moment I'm trying to make accomplished track where all samples are generated in Pd. I'll share them here: https://soundcloud.com/freezemode Previously, I made music just like every electronic musician did - using synths, vst-plugins, etc. But the idea of making music not playing with synths (made by other people), but directly "transferring" sound from imagination into audio, made me studying Pd for several years.

Although, I (unintentionally) made one patch which could be considered to be a 'track'. It's called 'The Cave of Creation' and posted here: http://puredata.hurleur.com/sujet-5080-meditation-background-generator

@rafiki said:

i'm also very new in Pure Data......
your patch has shown me, what's possible with PD. that's exactly i wanna do with it.
thanks for the motivation. nice work.

I thought of motivational issue recently: how could i quite easily make this patch and why can't i just sit and make another one effortlessly? Then i remembered this was a sort of game - as if i was growing something, or inventing some machine, no matter, i mean the process itself was more interesting to me than that i aimed for. I just didn't notice how one simple abstraction making droplet sound grew into what you can see/hear. So, i'd recommend just to play, as if Pd was a game (isn't it, by the way? ), invent your own rules, change them, - enjoy the process, not thinking how much you've done already and what you've got ahead. As for technical issues - they all can easily be solved if you're enthusiastic about what you are doing at the moment.

So, this may seem banal, but i hope this approach may help: just playing the game and enjoying it, not thinking of how much remains to do, you won't notice how fast any complicated patch will be complete.

P.s. i spent 20-30 hours approximately to do this (with absolutely no experience in making large patches in Pd) divided into rather short periods during 2010 and 2011.

Thanks a lot, jobromedia! Hope next patches will be at least the same success. Now I use it as a "training ground", it is very useful for testing and experimenting without making complicated patches. So, this "Cave of Creation" is where new works are being created.

I made one more version recently. It has been optimized a bit, sounds also a bit different. Attached to this post.

http://www.pdpatchrepo.info/hurleur/Cave_of_Creation.zip

@Jonastikov said:

I like this patch. I am also working on generative sound patches this is something a bit similar I came up with. Not quite as complex though

Hope you like it!

My cat liked it the most - I had to grab her away from speakers several times listening to this patch. It's not her ordinary behaviour. So, "cat test" passed!

I've started working on next generative patch. Cannot say what it will sound like yet (something like summer forest sounds, perhaps, not sure yet). I'll try to optimize it initially, use comments everythere, and make its structure more sophisticated. Undoubtly, I'll share it at this forum.

I beg your pardon if this post is slightly offtopic and deals more with hardware than the patch itself, but it should take one more message for testing results to be complete:
@az said:

If PureData only uses 50% CPU, could it be the case, that you have a DualCore CPU?

Yes, all CPUs under consideration apparently had two cores, even Atom N280 on Eee - task manager shows two 1,66GHz cores. But I'm not sure its architecture has much in common with DualCore family. It looks slower than Core2Duo 1,66GHz. Well, anyway, it turns out that 50% CPU means 100% of one core under WinXP and Pd just can't distribute calculations between both cores to use more CPU in this case.

I just installed Ubuntu 10.10 NBR as 2nd OS on this Eee, and loaded this patch with Puredata Vanilla 0.42.6. It runs with no glitches at all with 44100Hz sample rate and 50ms audio buffer size! The same result with 48000Hz. But as I turned on 96000Hz, I even started hearing through glitches: "man, its just a netbook!" No matter what audio latency was set.

Task manager (named here "system monitor") showed 50-55% average usage of both cores (when 48kHz sample rate and 50 ms latency were set). Here it didn't mean that total usage was 100% (sometimes 80%-85% peaks appeared and again, no glitches). 50% CPU usage and no buffer underruns at all.

So, it's possible to use Eee with Atom N280 or later to make complicated patches, just under Linux. As for me, main problem is small screen, not Atom CPU, that's why I use it only for small abstractions and don't care what OS is installed. Also, if you'd use touchpad instead of mouse to work with Pd on Eee, I bet you'll say at least a couple of bad words in an hour of such torture.

@jamesmcn said:

I've been running this patch on Pd-Extended 0.42.5 on a Core2 Duo MacBook Pro with no trouble at all.

It is interesting to see that the Eee can't handle a patch like this - I've been thinking of getting a netbook for this sort of thing.

I'm going to install Ubuntu NBR on Eee to work with Pd - maybe it can handle this patch under Ubuntu. I'll post here if it can. It seems like Pd under 32bit Windows can use only 50% CPU power, maybe Linux kernel works better. I have to use WinXP just to communicate with sampler (Korg Microsampler), because its utility works only under Windows or MacOS (it requires special driver which Wine in Linux does not allow to install, and I'm not such a guru to write my own driver, unfortunately ).

Otherwise, making patches on slow computers encourages to optimize them! Being initially made on Eee it probably could work much faster. Also, small screen stimulates using subpatches, so it makes patch itself look more intelligible: compare this messy generator with that abstraction (made on Eee) http://puredata.hurleur.com/sujet-4261-midi-learnable-mixer-channel

Оk, and here are my test results:

1. Ubuntu Studio 64 bit, Pd-Vanilla 0.42-6, 2GB RAM, Core2Duo 2,66 GHz - all works well, 17% CPU approx. (96000Hz sample rate, 10ms buffer size! I love Linux )

2. WinXP 32 bit, Pd-Extended 0.42-5, Asus EEE 1000HE, 1 Gb RAM, Intel Atom 1,66 GHz. Works glitchy (no matter what audio buffer size is). 30-50% CPU. After changing freezeverb.pd to a simpler version with less delay lines (attached to this post) - 20-40% CPU and normal sound (48000Hz sample rate, 100ms buffer size). Rare glitches, CPU% jumps up to 50% at these moments.

3. WinXP 32 bit, Pd-Extended 0.42-5, 1GB RAM, Core2Duo 1,88 GHz. Works well, no buffer underruns, 20-30% CPU. (48000Hz sample rate, 100ms buffer size).

4. Vista 32 bit, Pd-Extended 0.42-5, 2GB RAM, Core2Duo 2,33 GHz. Couldn't open.

So, if you have difficulties with CPU consumption, try to change freezeverb.pd to a simpler version attached to this post. It sounds very close to original one.

http://www.pdpatchrepo.info/hurleur/freezeverb.pd