<br><br><div><span class="gmail_quote">On 12/6/06, <b class="gmail_sendername">Thomas Grill</b> <<a href="mailto:gr@grrrr.org">gr@grrrr.org</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi Eric,<br>i'm wondering how asynchronous DSP works in Max. As far as i know<br>only messaging can be deferred. </blockquote><div><br><br>Yes, but you can put DSP inside of a message too.<br> </div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Is the DSP operation done outside the<br>normal DSP chain</blockquote><div><br><br>Presumably. <br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
or is it some DSP operations on buffer data that you<br>are doing in message callbacks?</blockquote><div><br>I'm not doing callbacks, and am not even sure that's possible with what I'm doing, or at least not without a lot of programming pain and agony. Basically, I have two buffers with some sound in buffer #1. I'm planning at some time in the future to start playing from buffer #2. I copy the contents of buffer #1 to buffer #2 and then do all kinds of evil DSP to the contents of buffer #2, all done asynchronously from the main DSP perform loop. Hopefully by that time I'm ready to play buffer #2 the DSP is done. If not, I have to drop the playback of that event.
<br> <br>Best,<br>Eric<br><br></div><br></div><br>