Hi, Charles,
I think it is just the matter of WHERE the code goes.
My understanding (as for now) is that the method registered with
gensym("dsp") is called,
>> anytime when either the block size or sample rate changes or when the
>> signal graph is rebuilt.
so that running this check,
> i
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 "rela
On Sun, 15 Jun 2008 09:57:00 +0900
PSPunch <[EMAIL PROTECTED]> 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
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 i
Hallo,
Miller Puckette hat gesagt: // Miller Puckette wrote:
> (example: an abstraction in "lib/" has a table that you ask to open
> "foo.wav" in "snd/" -- should that mean "snd/" relative to the
> calling patch (the normal thing to expect) or relative to the
> abstraction?)
That's indeed a very
Bugs item #1993902, was opened at 2008-06-14 06:50
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=1993902&group_id=55736
Please note that this message will contain a full copy o
Hi David,
Am 14.06.2008 um 03:08 schrieb PSPunch:
=
== PROCESS BLOCK.2 ==
=
while (n--) {
// *out++ = *in++;
}
Remarks: Action is commented out but signal goes through.. Why?
that's because in and out can point to the same memory... signal
The libdir library format with namespace prefixes is a simpler
approach. You wouldn't need to change any of the code, just build
the internal objects as a libdir and it would work. People could
change the loading order, access multiple objectclasses with the same
base name, etc.
The onl
