[PD-dev] [ pure-data-Patches-2290495 ] [feature] grain message for "line" to set time grain

SourceForge.net noreply at sourceforge.net
Wed Sep 29 20:59:28 CEST 2010

Patches item #2290495, was opened at 2008-11-15 11:29
Message generated for change (Comment added) made by sf-robot
You can respond by visiting: 

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: puredata
Group: None
>Status: Closed
Resolution: Fixed
Priority: 5
Private: No
Submitted By: Frank Barknecht (fbar)
Assigned to: Miller Puckette (millerpuckette)
Summary: [feature] grain message for "line" to set time grain

Initial Comment:
Attached patch for x_time.c adds a "grain $1" method to the [line] object which allows setting the update rate/time grain of a line object dynamicall after it was created. So far the only way to change the time grain is with a creation argument.

Maybe "grain" isn't such a good name, "rate" could be better. I didn't change the help file yet.


>Comment By: SourceForge Robot (sf-robot)
Date: 2010-09-29 18:59

This Tracker item was closed automatically by the system. It was
previously set to a Pending status, and the original submitter
did not respond within 14 days (the time period specified by
the administrator of this Tracker).


Comment By: Miller Puckette (millerpuckette)
Date: 2010-08-03 03:25

I ended up making an inlet so it's more nearly compatible with Max.  the
line object is badly designed anyway (why does the second inlet reset


Comment By: Frank Barknecht (fbar)
Date: 2008-11-16 21:26

I thought of a third inlet as well, but this would be a bit in conflict
with the arguments that line accepts: line takes the initial value as first
and the time grain as second argument and there is no argument for initial
duration. OTOH the first inlet is for the new target value and the second
inlet for the line duration. So the second argument (grain) clashes with
the second inlet (duration) already, adding another inlet would be even
more confusing IMO because of the "hole in the middle" of the argument
list. Also line would look more like vline~, while it should rather
continue to look like line~ IMO. 

In the end I couldn't figure out a nice solution that doesn't break old
patches, so I thought a new method would be the easiest approach.

OTOH a third inlet could use list-distribution to change the update rate
with a single message like "10 1000 5" for: "go to 10 in 1000 ms and update
every 5ms"

I'll let Miller decide about this, I just needed a quick way to change the
grain dynamically.


Comment By: Hans-Christoph Steiner (eighthave)
Date: 2008-11-16 20:33

what about making a third inlet to set the grain size?  Then it would line
up nicely with the 2nd argument.


You can respond by visiting: 

More information about the Pd-dev mailing list