On 12/5/06, Mathieu Bouchard [EMAIL PROTECTED] wrote:
What is MAX
doing to keep JITTER from causing audio JITTER ?
I think there's some XML involved.
___
PD-dev mailing list
PD-dev@iem.at
http://lists.puredata.info/listinfo/pd-dev
Hallo!
currently there's no low-priority messaging in Miller's pd version, but
there is in the devel branch.
It's one of the features that have been there for some time and i'm
trying to provide a patch for Miller, so that it can make it into
vanilla PD some time in the future. Hopefully the
Hallo!
and oh, you can have priorities even without threads...
and how?
Do you mean a bigger blocksize ... ?
LG
Georg
___
PD-dev mailing list
PD-dev@iem.at
http://lists.puredata.info/listinfo/pd-dev
SourceForge.net wrote:
This also happens on Ubuntu, so its not OS-specific. I guess I forgot to
mention that. The above Dell Dimension is running Ubuntu Dapper.
Is there a certain set of ./configure options to try?
please check whether this is related to rectangle-textures (by using
Hi Eric,
i'm wondering how asynchronous DSP works in Max. As far as i know
only messaging can be deferred. Is the DSP operation done outside the
normal DSP chain or is it some DSP operations on buffer data that you
are doing in message callbacks?
greetings,
Thomas
Am 06.12.2006 um 11:37
Georg Holzmann wrote:
Hallo!
since pd-0.40 you can do DSP-on-demand, by banging the [switch~] object.
i have not tested, but it might be, that this DSP-operation is in the
message queue.
what do you mean by that ?
by what? there are 2 parts which might be problematic.
mfg.adr
IOhannes
- maybe you can also do it with vasp, which is a set of externals for
buffer calculation and I think they can do it also in a seperate thread
i guess the 'vanilla' way would be to downsample the 'evil DSP' ;)
Horrors! That would take the edge off the evil :-[=]
Eric
