On 02/28/2016 11:03 PM, Matt Barber wrote:
Just to confirm, this bug is only on patch load, right? Does it only happen when it's loading a table stored in a patch, or does it do the same if the table is loaded via soundfiler it generated algorithmically?
Is this fixable in partconv~ or is it a consequence of the design of the patch load sequence?
well there is one thing designed into [partconv~] and that is: it does not continuously update the IR from the table, but does so only at explicit points. one of these points is whenever it receives a "set" message. another of these points is when the DSP is turned on for the first time after the object was created (and still no "set" message has occured).
it's because of the latter that i currently don't think that there is a bug.
gamsrd IOhannes