Hi,
great. What was exactly the problem? And also, how is it possible to get
to the corrected version? Will it be part of any nightly builds? Will it
be integrated into pd extended automatically?
João
OK... I think I have this fixed in git
(git clone
git://pure-data.git.sourceforge.net/gitroot/pure-data/pure-data)
cheers
Miller
On Fri, Nov 02, 2012 at 08:29:52PM +0100, João Pais wrote:
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
_______________________________________________
Pd-list@iem.at mailing list
UNSUBSCRIBE and account-management ->
http://lists.puredata.info/listinfo/pd-list
_______________________________________________
Pd-list@iem.at mailing list
UNSUBSCRIBE and account-management ->
http://lists.puredata.info/listinfo/pd-list
