Hi João I can't add more info to this issue, but to me it looks like bug. It seems in re-blocked (< 64?) subpatches the ramp starts too early. But why this happens, I don't have the slightest idea.
I think, you provided enough info to file a bug report. Roman On Sun, 2012-11-04 at 17:27 +0100, João Pais wrote: > (according to the pd-list server this message came attached to thread of > another mail, I try to send it here again to create a new thread) > > > Hello, > > a friend noticed that vline~ behaves differently with different block > sizes - namely that the smaller the block size is, the less precision it > has. Besides the numbers being different with each block size, the latest > values go slightly over the border of the desired range. > Is this a bug, a feature, or an unavoidable behavior of the vline~ > algorithms? > > Attached is a patch which explains the situation. I think it should be > clearly enough explained. > > The bottom line is: in the patch I am working, block size is 1 (sample > rate 48KHz, in case it matters). Which choices are there to improve > vline~'s precision, so that I get the results I am expecting? > > Thanks, > > João > _______________________________________________ [email protected] mailing list > UNSUBSCRIBE and account-management -> > http://lists.puredata.info/listinfo/pd-list _______________________________________________ [email protected] mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
