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

[Matt Barber]

It's because of the linear interpolation, which always sounds warmer. :)

On Sat, Sep 26, 2015 at 8:23 PM, Jonathan Wilkes <jancsika at yahoo.com> wrote:

> I tend to use [vline~] in those cases because-- to my ears-- it sounds
> warmer.
>
> (I so wanted to click send, but I have to come clean and say I'm just
> kidding.)
>
> -Jonathan
>
>
>
> On Saturday, September 26, 2015 7:46 PM, Matt Barber <brbrofsvl at gmail.com>
> wrote:
>
>
> Well, obviously it depends on what you want to use the lines for. If it's
> just to fade something in or out over 10-50 ms to avoid a discontinuity,
> it's not that big a deal. Moreover sometimes it's great to have the ends
> and beginnings of ramps happen at block boundaries; e.g. when [switch~]ing
> off a subpatch or abstraction in a synth bank at the end of a quick fade,
> it's nice to know that you can target things to boundaries without having
> to try too hard.
>
> On Sat, Sep 26, 2015 at 6:08 PM, Jonathan Wilkes via Pd-list <
> pd-list at lists.iem.at> wrote:
>
> Hi Frank,
> The [1, 0 50( message will almost always trigger different
> output when fed to [line~] and [vline~].  The only exception
> is when the ramp ends exactly on a block boundary--
> otherwise [line~] will stretch the final part of the ramp to
> the block boundary.
>
> In fact, I'm willing to bet that if visualized this [line~]
> quantization to new users at the outset they'd almost
> always use [vline~].  After all, who wants imperfect lines? :)
>
> -Jonathan
>
>
>
>
>
> On Saturday, September 26, 2015 12:57 PM, Frank Barknecht <
> fbar at footils.org> wrote:
>
>
> Hi,
>
> On Sat, Sep 26, 2015 at 11:24:40PM +0900, i go bananas wrote:
> > In that case, maybe an even simpler question:
> >
> > What is the difference between sending a [1, 0 50(  message to vline as
> > opposed to line ?
>
> There will only be a difference in how line~ and vline~ react to this
> message
> when the message was triggered by something with a "clock" inside. These
> kinds
> of messages are called clock-delayed messages.
>
> Clock-delayed messages originate in objects like [metro] or [delay] or
> [qlist].
> Messages that originate for example in mouse clicks are not clock-delayed
> (i.e.
> if you click a [bng] or move a slider).
>
> vline~ evaluates clock delayed message with high, sub-sample timing
> accuracy.
> line~ quantizes even clock delayed messages to block-boundaries or to 64
> samples, I'm not sure ATM which it is. But line~ quantizes.
>
> So depending on when the message was issued any by what, the ramp
> generators
> may act the same or different.
>
> Try delaying the message:
>
> [bang(
> |
> [delay 0.3]
>
> |
> [1. 0 50(
>
> |
> [line~ or vline~]
> |
> [print~]
>
> Ciao
> --
> Frank Barknecht                                    _ ______footils.org__
>
> _______________________________________________
> Pd-list at lists.iem.at mailing list
> UNSUBSCRIBE and account-management ->
> http://lists.puredata.info/listinfo/pd-list
>
>
>
>
> _______________________________________________
> Pd-list at lists.iem.at mailing list
> UNSUBSCRIBE and account-management ->
> http://lists.puredata.info/listinfo/pd-list
>
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.puredata.info/pipermail/pd-list/attachments/20150926/43af4899/attachment.html>