Sorry for accidentally sending the previous note to pd-list.
Thomas,
I hear that malloc is a "relatively" expensive task. Is it bad practice to run this each cycle, or is a kilobyte or two not a bid deal?
That's definitely bad practice. Instead of that you can do the allocation in the "dsp" callback, that's where you add your dsp processing to the signal chain. This callback will be called anytime when either the block size or sample rate changes or when the signal graph is rebuilt.
Many thanks to you again, I know have it working with the way you suggest.
Being fairly new to C and Pd source, I am still at the stage where I code with out understanding 100% of what I am really doing. This weekend has been very adventurous so far.
Would you mind giving me directions to where I can find descriptions on the concept "signal graph" and where I shall look in the code to see it in action? It has nothing to do with the GUI object "graph" does it?
-- David Shimamoto
On Sun, 15 Jun 2008 09:57:00 +0900 PSPunch shima@pspunch.com wrote:
Sorry for accidentally sending the previous note to pd-list.
I'd love to hear this stay on list. David is asking all the right questions, and the answers (Thomas and Iohannes) are the kind of thing it takes weeks or months to discover in the code.
andy
Thomas,
I hear that malloc is a "relatively" expensive task. Is it bad practice to run this each cycle, or is a kilobyte or two not a bid deal?
That's definitely bad practice. Instead of that you can do the allocation in the "dsp" callback, that's where you add your dsp processing to the signal chain. This callback will be called anytime when either the block size or sample rate changes or when the signal graph is rebuilt.
Many thanks to you again, I know have it working with the way you suggest.
Being fairly new to C and Pd source, I am still at the stage where I code with out understanding 100% of what I am really doing. This weekend has been very adventurous so far.
Would you mind giving me directions to where I can find descriptions on the concept "signal graph" and where I shall look in the code to see it in action? It has nothing to do with the GUI object "graph" does it?
-- David Shimamoto
Pd-dev mailing list Pd-dev@iem.at http://lists.puredata.info/listinfo/pd-dev
Hallo, Andy Farnell hat gesagt: // Andy Farnell wrote:
On Sun, 15 Jun 2008 09:57:00 +0900 PSPunch shima@pspunch.com wrote:
Sorry for accidentally sending the previous note to pd-list.
I'd love to hear this stay on list.
I think, David was referring to pd-list vs. pd-dev for this topic. It's more appropriate for -dev of course.
Ciao
There's a rather hard-to-understand description on
http://crca.ucsd.edu/~msp/Publications/cmj91-max.ps
cheers Miller
On Sun, Jun 15, 2008 at 09:57:00AM +0900, PSPunch wrote:
Sorry for accidentally sending the previous note to pd-list.
Thomas,
I hear that malloc is a "relatively" expensive task. Is it bad practice to run this each cycle, or is a kilobyte or two not a bid deal?
That's definitely bad practice. Instead of that you can do the allocation in the "dsp" callback, that's where you add your dsp processing to the signal chain. This callback will be called anytime when either the block size or sample rate changes or when the signal graph is rebuilt.
Many thanks to you again, I know have it working with the way you suggest.
Being fairly new to C and Pd source, I am still at the stage where I code with out understanding 100% of what I am really doing. This weekend has been very adventurous so far.
Would you mind giving me directions to where I can find descriptions on the concept "signal graph" and where I shall look in the code to see it in action? It has nothing to do with the GUI object "graph" does it?
-- David Shimamoto
Pd-dev mailing list Pd-dev@iem.at http://lists.puredata.info/listinfo/pd-dev
-
Andy Farnell -
Frank Barknecht -
Miller Puckette -
PSPunch