On Fri, 2007-10-26 at 19:35 -0400, Mathieu Bouchard wrote:
On Fri, 26 Oct 2007, Roman Haefeli wrote:
that is what i do in netpd since last change. whenever a patch is loaded, it is not openen per message anymore but created dynamically as an abstraction. i found out, that it takes _much_ less time, if dsp is turned off before and turned on after creating it.
The problem with that is that there is no way to figure out beforehand that the dsp was on, so you can't know for sure that it wasn't meant to be off, and I usually have it off.
true, but i found a way in netpd to come around this problem. every netpd session starts with chat, chat sets dsp to 1 and also chats stays open until the end of the session. it is not possible to request the actual dsp state, but it is possible to track all changes of state and this is what chat does. other netpd patches can just ask chat about the actual dsp state. so even if you turn dsp off, it won't get turned on by loading a netpd-patch.
there is no way in pd to tell how much behind schedule pd is with computing, or is there?
Yes, use [realtime] and [timer] and [-].
ah ok. interesting. with that you could construct a 'dynamic patcher' that just does NOT cause a drop-out, right?
roman
___________________________________________________________ Der frühe Vogel fängt den Wurm. Hier gelangen Sie zum neuen Yahoo! Mail: http://mail.yahoo.de