On Fri, 2010-12-24 at 08:51 +0100, Roman Haefeli wrote:
On Fri, 2010-12-24 at 00:52 +0100, Dietrich Pank wrote:
so is it correct to state that the workaround setting block~ size down to 1 for sample correct works is not existant for
most (maybe all, not sure) signal-to-message objects
besause they
have a minimum hard limit of 64 samples.
The good news is that there are still ways to create sample accurate signal-to-message converters that work at any blocksize (incl. 64).
Use [tabsend~] to write every block of the incoming signal to a [table] and perform the analysis in the message domain by iterating through the table. This approach might be a bit more expensive CPU-wise than a using a dedicated objectclass written in C, but for simple analysis like threshold and peak detection you probably won't notice it.
Please note that events created like this are exactly one block late since you can only start the analysis after the whole vector has been written.
This also applies to [vsnapshot~] and I don't even know if that works correctly at blocksizes < 64.
Roman