On 2017-01-15 22:58, Miller Puckette wrote:
> I can't understand what is wrong... if you 'stop' a line~ and then later
> give it a new target, it ramps form the position it had stoped at. I think
> this is the most reasonable behavior. Or is it doing something different
> somehow?
it starts
On Mon, 2017-01-09 at 17:59 -0200, Alexandre Torres Porres wrote:
> > Is this an intended design?
> I think so
This seems odd to me. Once you hit 'stop', there is no way to avoid a
jump. The point of using a ramp generator is exactly to avoid jumps. I
only noticed now that [line~ ] continues
>
> Is this an intended design?
I think so
btw, cyclone/line~ has stop and resume methods
___
Pd-list@lists.iem.at mailing list
UNSUBSCRIBE and account-management ->
https://lists.puredata.info/listinfo/pd-list
Hey all
I found that a 'stop' message to [line] doesn't make it store the
current position. A subsequent ' ' message starts from
the last targeted position instead of the position when the 'stop'
message occurred.
Is this an intended design?
See attached patch that tries to illustrate the
