Angry vline~s is the name of my next garage band :)
M
On Mon, Aug 17, 2020 at 02:52:28AM +0200, Christof Ressi wrote:
Hey,
but I still needed an example to see how to make this happen :)
Attached you find a simple example for recording N ms of sound to disk.
that's used n the help file of [samplerate~] but I agree it should also be included in this new documentaton section. Anyway, what else would you use it for?
It's useful for preventing "angry vline~s": if you accidentally keep sending messaes to a [vline~] while DSP is off, it will eventually bring Pd to its knees. The solution is to use a [spigot] which is opened on "pd-dsp-started" and closed on "pd-dsp-stopped".
Actually, the issue should be mentioned in vline~-help.pd, together with the possible solution.
Christof
On 17.08.2020 02:25, Alexandre Torres Porres wrote:
On 16.08.2020 05:52, Miller Puckette via Pd-list wrote: > An artificial example (for simplicity) - I want to apply a Pd effect to a > soundfile and write the result out to another file, without having to wait > for the length of the file to get the result.?? This could be done from the > command line using a batch command, but while you're developing the patch to > do it it's much easier to be able to set the process off with a button from > inside Pd.Great, kind of what I was expecting, but I still needed an example to see how to make this happen :)
Em dom., 16 de ago. de 2020 ??s 08:16, Christof Ressi <info@christofressi.com mailto:info@christofressi.com> escreveu:
My use case was that I had a patch which either produced some generative music or processed some soundfile and I wanted to record N seconds as fast as possible. It's basically like the render function in a DAW (usually you don't have to start the DAW from the command line to render your project :-).I also thought about that and I'm really excited to test both things. Hopefully I can have an example of this in my tutorial rght now and release an update. But my attempts here failed and froze Pd :)
Have you already messed with it, Christof?
But I agree that this needs to documented. Generally, there should be a section to document all (public) Pd messages, like [pd dsp(, [pd quit(, etc. (What can be considered "public"?)I opened an issue for that ( https://urldefense.com/v3/__https://github.com/pure-data/pure-data/issues/11... ??) and can take care of it as I'm usually handling documentation issues.
Also [r pd-dsp-started] and [r pd-dsp-stopped], which most people don't know about, I guess.that's used n the help file of [samplerate~] but I agree it should also be included in this new documentaton section. Anyway, what else would you use it for?
Porres
#N canvas 505 376 450 300 12; #X obj 31 202 noise~; #X obj 21 231 writesf~ 2; #X obj 89 202 noise~; #X msg 60 117 ; pd fast-forward $1; #X obj 83 39 nbx 5 14 -1e+037 1e+037 0 0 empty empty ms 0 -8 0 10 -262144 -1 -1 0 256; #X obj 37 62 f 10000; #X obj 37 38 bng 15 250 50 0 empty empty empty 17 7 0 10 -262144 -1 -1; #X obj 21 118 del; #X msg 21 173 stop; #X msg 83 166 open ./noise.wav , start; #X obj 37 86 t f f b; #X text 101 65 write N ms of stereo noise; #X text 35 14 go!; #X obj 21 150 bng 15 250 50 0 empty empty empty 17 7 0 10 -262144 -1 -1; #X text 40 148 done; #X obj 266 132 loadbang; #X msg 266 159 ; pd dsp 1; #X connect 0 0 1 0; #X connect 2 0 1 1; #X connect 4 0 5 1; #X connect 5 0 10 0; #X connect 6 0 5 0; #X connect 7 0 13 0; #X connect 8 0 1 0; #X connect 9 0 1 0; #X connect 10 0 7 0; #X connect 10 1 3 0; #X connect 10 2 9 0; #X connect 13 0 8 0; #X connect 15 0 16 0;
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://urldefense.com/v3/__https://lists.puredata.info/listinfo/pd-list__;!...