[PD] How does vline~ work under the hood?

[Frank Barknecht]

Hi,

On Sat, Sep 26, 2015 at 10:08:16PM +0000, Jonathan Wilkes wrote:
> Hi Frank,The [1, 0 50( message will almost always trigger different output
> when fed to [line~] and [vline~].  The only exceptionis when the ramp ends
> exactly on a block boundary--otherwise [line~] will stretch 

... or compress ...

> the final part of
> the ramp tothe block boundary.

You're right, I wasn't thinking of the line-endpoints in my explanation. In
fact, until now I believed, that these wouldn't be quantized with line~, but
indeed they are (see attachement). And it's pretty much what Miller writes in
the book: http://msp.ucsd.edu/techniques/latest/book-html/node43.html#fig03.05

Still in my view the quantization of endpoints is a bit counter-intuitive.
Whereas the actual firing of a message from the GUI is inherently vague and
shaky, the duration of the ramp (50 ms in the example) is written explicitely
in the control message. That [line~] changes it, "feels" like a bug, although
it isn't, and in the end it's the same way, [line~] deals with clock-delayed
messages.

For many applications the correct timing of start points musically is more
important (drums!), but one should be aware of possible quantization at
endpoints as well. 

Ciao
-- 
 Frank Barknecht                                     _ ______footils.org__
-------------- next part --------------
A non-text attachment was scrubbed...
Name: vlineline.pd
Type: application/puredata
Size: 1366 bytes
Desc: not available
URL: <http://lists.puredata.info/pipermail/pd-list/attachments/20150927/d0ad2536/attachment.bin>