To Pd-announce:
Pd version 0.51-1 is available on http://msp.ucsd.edu/software.htm or (source only) via github: https://github.com/pure-data/pure-data.
This contains bug fixes, notably fixing problems running on Macintoshes after dark or on system 11.
[OT] another announcement, but nothing to do with Pd: a new book that Kerry Hagan and I edited about electornic music pioneers, "Between the Tracks", comes out Sept. 1 from MIT Press.
cheers Miller
Pd-announce mailing list Pd-announce@lists.iem.at https://lists.puredata.info/listinfo/pd-announce
Awesome.
I wonder if anyone could work on an example about this new message to Pd so I can see if I get it. Also, this should be documented somewhere, right?
cheers
Em sáb., 15 de ago. de 2020 às 22:29, Miller Puckette via Pd-announce < pd-announce@lists.iem.at> escreveu:
To Pd-announce:
Pd version 0.51-1 is available on http://msp.ucsd.edu/software.htm or (source only) via github: https://github.com/pure-data/pure-data.
This contains bug fixes, notably fixing problems running on Macintoshes after dark or on system 11.
[OT] another announcement, but nothing to do with Pd: a new book that Kerry Hagan and I edited about electornic music pioneers, "Between the Tracks", comes out Sept. 1 from MIT Press.
cheers Miller
Pd-announce mailing list Pd-announce@lists.iem.at https://lists.puredata.info/listinfo/pd-announce _______________________________________________ Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
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.
cheers Miller
On Sun, Aug 16, 2020 at 12:38:55AM -0300, Alexandre Torres Porres wrote:
Awesome.
I wonder if anyone could work on an example about this new message to Pd so I can see if I get it. Also, this should be documented somewhere, right?
cheers
Em s??b., 15 de ago. de 2020 ??s 22:29, Miller Puckette via Pd-announce < pd-announce@lists.iem.at> escreveu:
To Pd-announce:
Pd version 0.51-1 is available on http://msp.ucsd.edu/software.htm or (source only) via github: https://urldefense.com/v3/__https://github.com/pure-data/pure-data__;!!Mih3w... .
This contains bug fixes, notably fixing problems running on Macintoshes after dark or on system 11.
[OT] another announcement, but nothing to do with Pd: a new book that Kerry Hagan and I edited about electornic music pioneers, "Between the Tracks", comes out Sept. 1 from MIT Press.
cheers Miller
Pd-announce mailing list Pd-announce@lists.iem.at https://urldefense.com/v3/__https://lists.puredata.info/listinfo/pd-announce... _______________________________________________ Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://urldefense.com/v3/__https://lists.puredata.info/listinfo/pd-list__;!...
I once made an external which does the same thing (https://git.iem.at/ressi/batchrecord) and it's cool that the same thing is now possible in the core!
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 :-).
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"?)
Also [r pd-dsp-started] and [r pd-dsp-stopped], which most people don't know about, I guess.
Christof
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.
cheers Miller
On Sun, Aug 16, 2020 at 12:38:55AM -0300, Alexandre Torres Porres wrote:
Awesome.
I wonder if anyone could work on an example about this new message to Pd so I can see if I get it. Also, this should be documented somewhere, right?
cheers
Em s??b., 15 de ago. de 2020 ??s 22:29, Miller Puckette via Pd-announce < pd-announce@lists.iem.at> escreveu:
To Pd-announce:
Pd version 0.51-1 is available on http://msp.ucsd.edu/software.htm or (source only) via github: https://urldefense.com/v3/__https://github.com/pure-data/pure-data__;!!Mih3w... .
This contains bug fixes, notably fixing problems running on Macintoshes after dark or on system 11.
[OT] another announcement, but nothing to do with Pd: a new book that Kerry Hagan and I edited about electornic music pioneers, "Between the Tracks", comes out Sept. 1 from MIT Press.
cheers Miller
Pd-announce mailing list Pd-announce@lists.iem.at https://urldefense.com/v3/__https://lists.puredata.info/listinfo/pd-announce... _______________________________________________ Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://urldefense.com/v3/__https://lists.puredata.info/listinfo/pd-list__;!...
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
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 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://github.com/pure-data/pure-data/issues/1125 ) 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
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://github.com/pure-data/pure-data/issues/1125%C2%A0) 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
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__;!...
I'm having a problem using 'fast-forward' in a patch loaded via [pd~].
I'm doing this to test if I don't get an audio dropout in the main patch by running the batch in a pd subprocess.
The patch runs fine and generates 10 min of white noise. This does cause an audio dropout (much shorter than I expected, wow), so yeah, time to test it inside [pd~]. What happens? No audio is generated at all, I get an audio with 0 seconds.
Perhaps this is something that got overlooked (allowing 'fast-forward' in [pd~])?
If so, clearly, this is something we'd all agree would be great to have, right? :)
Cheers
I'm doing this to test if I don't get an audio dropout in the main patch by running the batch in a pd subprocess.
With [pd~], the parent process "drives" the subprocess. If the subprocess blocks (beyond the given delay time), the parent process also blocks.
No audio is generated at all, I get an audio with 0 seconds.
I checked the code. "sched_fastforward" is only used in the polling scheduler. This means "fast-forward" has no effect in the callback scheduler or in a plugin scheduler (e.g. the one used by the [pd~] subprocess).
Open an issue on GitHub!
Christof
On 17.08.2020 16:52, Alexandre Torres Porres wrote:
I'm having a problem using 'fast-forward' in a patch loaded via [pd~].
I'm doing this to test if I don't get an audio dropout in the main patch by running the batch in a pd subprocess.
The patch runs fine and generates 10 min of white noise. This does cause an audio dropout (much shorter than I expected, wow), so yeah, time to test it inside [pd~]. What happens? No audio is generated at all, I get an audio with 0 seconds.
Perhaps this is something that got overlooked (allowing 'fast-forward' in [pd~])?
If so, clearly, this is something we'd all agree would be great to have, right? :)
Cheers
Em seg., 17 de ago. de 2020 às 12:02, Christof Ressi info@christofressi.com escreveu:
With [pd~], the parent process "drives" the subprocess. If the subprocess blocks (beyond the given delay time), the parent process also blocks.
so I see it's impossible to avoid dropouts :(
could this be improved and implemented somehow in the context of an 'offline' renderer? Like if it is possible to do all these audio computations without the 'dsp' on? I cannot elaborate this better and I hope you get what I mean.
Open an issue on GitHub!
Done!
Like if it is possible to do all these audio computations without the 'dsp' on?
No, it's not possible because "fast-forward" acts globally. It effectively makes the scheduler run as fast as possible for a given amount of time. This affects both DSP computation and clock timeouts!
If your audio computation is pure DSP (i.e. no messages), you can "render" it by repeatedly banging the [switch~] object at any rate you like. Global DSP still has to be on, but the canvas would be switched off.
Christof
On 17.08.2020 17:32, Alexandre Torres Porres wrote:
Em seg., 17 de ago. de 2020 às 12:02, Christof Ressi <info@christofressi.com mailto:info@christofressi.com> escreveu:
With [pd~], the parent process "drives" the subprocess. If the subprocess blocks (beyond the given delay time), the parent process also blocks.so I see it's impossible to avoid dropouts :(
could this be improved and implemented somehow in the context of an 'offline' renderer? Like if it is possible to do all these audio computations without the 'dsp' on? I cannot elaborate this better and I hope you get what I mean.
Open an issue on GitHub!Done!
Em seg., 17 de ago. de 2020 às 13:20, Christof Ressi info@christofressi.com escreveu:
If your audio computation is pure DSP (i.e. no messages), you can "render" it by repeatedly banging the [switch~] object at any rate you like. Global DSP still has to be on, but the canvas would be switched off.
hmm, please elaborate; thanks
Try attached patch. Note that this works fine with pure DSP objects, but it gives unexpected results once you add clocks (e.g. [metro], [del], etc.).
Sending a "bang" to [switch~] only advances DSP computation for the given canvas (and all its subcanvases), but it doesn't advance the message scheduler (which is global).
With this method, you can basically amortized DSP computations over a given period of time.
Christof
On 17.08.2020 19:27, Alexandre Torres Porres wrote:
Em seg., 17 de ago. de 2020 às 13:20, Christof Ressi <info@christofressi.com mailto:info@christofressi.com> escreveu:
If your audio computation is pure DSP (i.e. no messages), you can "render" it by repeatedly banging the [switch~] object at any rate you like. Global DSP still has to be on, but the canvas would be switched off.hmm, please elaborate; thanks
Yeah I think that would be a limitation that's unavoidable, because you're running at system clock rates vs audio clock rates. You'd have to spawn a new thread.
On Mon, Aug 17, 2020 at 10:40 AM Christof Ressi info@christofressi.com wrote:
Try attached patch. Note that this works fine with pure DSP objects, but it gives unexpected results once you add clocks (e.g. [metro], [del], etc.).
Sending a "bang" to [switch~] only advances DSP computation for the given canvas (and all its subcanvases), but it doesn't advance the message scheduler (which is global).
With this method, you can basically amortized DSP computations over a given period of time.
Christof On 17.08.2020 19:27, Alexandre Torres Porres wrote:
Em seg., 17 de ago. de 2020 às 13:20, Christof Ressi < info@christofressi.com> escreveu:
If your audio computation is pure DSP (i.e. no messages), you can "render" it by repeatedly banging the [switch~] object at any rate you like. Global DSP still has to be on, but the canvas would be switched off.
hmm, please elaborate; thanks
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
I wonder if having an embedded version of pdlib built to do that would work as you'd separate that from the scheduler, it would basically just run it's own scheduler but you wouldn't have to manage threads (and i think it took Csound quite a long time for them to get realtime with multiple threads working well).
On Mon, Aug 17, 2020 at 10:53 AM Josh Moore kh405.7h30ry@gmail.com wrote:
Yeah I think that would be a limitation that's unavoidable, because you're running at system clock rates vs audio clock rates. You'd have to spawn a new thread.
On Mon, Aug 17, 2020 at 10:40 AM Christof Ressi info@christofressi.com wrote:
Try attached patch. Note that this works fine with pure DSP objects, but it gives unexpected results once you add clocks (e.g. [metro], [del], etc.).
Sending a "bang" to [switch~] only advances DSP computation for the given canvas (and all its subcanvases), but it doesn't advance the message scheduler (which is global).
With this method, you can basically amortized DSP computations over a given period of time.
Christof On 17.08.2020 19:27, Alexandre Torres Porres wrote:
Em seg., 17 de ago. de 2020 às 13:20, Christof Ressi < info@christofressi.com> escreveu:
If your audio computation is pure DSP (i.e. no messages), you can "render" it by repeatedly banging the [switch~] object at any rate you like. Global DSP still has to be on, but the canvas would be switched off.
hmm, please elaborate; thanks
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
I'm having so much fun, thanks!
working on a "batch record" abstraction now :)
I'm only now frustrated I can't batch record myself playing live, for like, 5 minutes... maybe Miller will figure out a way of doing so in 0.52 :)
Em dom., 16 de ago. de 2020 às 21:54, Christof Ressi info@christofressi.com escreveu:
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> 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://github.com/pure-data/pure-data/issues/1125 ) 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
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
this sounds interesting. i've also successfully written to an array. i've always liked this idea, it makes no sense to compute something over and over again if you already know what's going to be computed. playing back a bit stream from RAM is always going to be faster.
i can have some fun with this and i know exactly the application to use it for as i've (ab)used this sort of "render to sample" feature in Renoise.
On Mon, Aug 17, 2020 at 12:48 AM Alexandre Torres Porres porres@gmail.com wrote:
I'm having so much fun, thanks!
working on a "batch record" abstraction now :)
I'm only now frustrated I can't batch record myself playing live, for like, 5 minutes... maybe Miller will figure out a way of doing so in 0.52 :)
Em dom., 16 de ago. de 2020 às 21:54, Christof Ressi < info@christofressi.com> escreveu:
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> 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://github.com/pure-data/pure-data/issues/1125 ) 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
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
In my click tracker I use [array set] to generate the resulting audio in 3 tracks (3 sources), and then zexy's [.] for amplitude scaling and iem_tab's [tab_add] to join all 3 tracks. iem_tab has also lots of other interesting things.
But that's all copy-paste, no audio processing (except with [.] )
this sounds interesting. i've also successfully written to an array. i've always liked this idea, it makes no sense to compute something over and over again if you already know what's going to be computed. playing back a bit stream from RAM is always going to be faster.
i can have some fun with this and i know exactly the application to use it for as i've (ab)used this sort of "render to sample" feature in Renoise.
On Mon, Aug 17, 2020 at 12:48 AM Alexandre Torres Porres <porres@gmail.com mailto:porres@gmail.com> wrote:
I'm having so much fun, thanks! working on a "batch record" abstraction now :) I'm only now frustrated I can't batch record myself playing live, for like, 5 minutes... maybe Miller will figure out a way of doing so in 0.52 :) Em dom., 16 de ago. de 2020 às 21:54, Christof Ressi <info@christofressi.com <mailto:info@christofressi.com>> escreveu: 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://github.com/pure-data/pure-data/issues/1125 ) 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
-
Alexandre Torres Porres -
Christof Ressi -
Josh Moore -
João Pais -
Miller Puckette -
Miller Puckette via Pd-announce