howdy, there's no help file for creb/ramp~
anybody ever used it?
thanks
ramp~ send it a number and it will generate a ramp~ - effectively a sample number to read arrays with something like a phasor~, but it just goes up and up. I just had a look in the C code. In all honesty it's one of those objects that is in Pd but could be easily dealt with in Pd without the external. No disrespect to Tom Schouten, but it's basically a line~ with an offset, and a fixed rate i.e. it just generates a signal ramp with the right characteristics to patch it into tabread4~ and playback samples at their original pitch. The only exception is that it always starts from a specific value sent to the inlet. There are quite a lot of externals like this (and some from me) where people coded something in C for convenience, but can be easily done in Pd without externals.
Here's a semi pddp formatted helpfile.It's boring.Cheers,Ed _-_-_-_-_-_-_-^-_-_-_-_-_-_-_
For Lone Shark releases, Pure Data software and published Research, go to http://sharktracks.co.uk
On Thursday, 19 January 2017, 0:38, Alexandre Torres Porres <porres@gmail.com> wrote:
howdy, there's no help file for creb/ramp~ anybody ever used it? thanks _______________________________________________ Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
Thanks, if I'm not mistaken, Fred is taking care of creb now, so maybe he could work on this help file and include it in a new deken release
cheers
2017-01-28 12:48 GMT-02:00 Ed Kelly morph_2016@yahoo.co.uk:
ramp~
send it a number and it will generate a ramp~ - effectively a sample number to read arrays with something like a phasor~, but it just goes up and up.
I just had a look in the C code. In all honesty it's one of those objects that is in Pd but could be easily dealt with in Pd without the external. No disrespect to Tom Schouten, but it's basically a line~ with an offset, and a fixed rate i.e. it just generates a signal ramp with the right characteristics to patch it into tabread4~ and playback samples at their original pitch. The only exception is that it always starts from a specific value sent to the inlet.
There are quite a lot of externals like this (and some from me) where people coded something in C for convenience, but can be easily done in Pd without externals.
Here's a semi pddp formatted helpfile. It's boring. Cheers, Ed
_-_-_-_-_-_-_-^-_-_-_-_-_-_-_
For *Lone Shark *releases, *Pure Data *software and published *Research*, go to http://sharktracks.co.uk
On Thursday, 19 January 2017, 0:38, Alexandre Torres Porres < porres@gmail.com> wrote:
howdy, there's no help file for creb/ramp~
anybody ever used it?
thanks
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/ listinfo/pd-list
it's one of those objects that is in Pd but could be easily dealt with in Pd without the external (...) but it's basically a line~ with an offset, and a fixed rate
looks like~ cyclone's count~ but much simpler
it just generates a signal ramp with the right characteristics to patch it
into tabread4~ and playback samples at their original pitch.
or using it with tabread~ then instead pf tabread4~
looks again like count~ as one of its applications is in conjunction with index~ (basically tabread~).
There are quite a lot of externals like this (and some from me) where
people coded something in C for convenience, but can be easily done in Pd without externals.
I know... Pd Extended is filled with things like that, and to make it more of a deal, documentation is sometimes bad, when simply non existing.
I'm willing to help this in the forth coming Purr Data, by reorganising it and making it better documented
cheers
Yes, I think the documentation is important (shame on me for never finishing all my docs). It's just a bit of a shame that we have to document some quite redundant functions, but if they make life easier for other patchers then that's great. I've made quite a few things in C that could be abstractions for example.
Also, there's an annoyance that comes from having to investigate C code from abandoned libs, although this is usually not so hard with things like ramp~. I think it could be a good idea and a lot of work to present at least some examples in the help files of how such externals could be modelled within Pd vanilla. Naively I think this could help both newbies and people learning to code externals. xEd _-_-_-_-_-_-_-^-_-_-_-_-_-_-_
For Lone Shark releases, Pure Data software and published Research, go to http://sharktracks.co.uk
On Saturday, 28 January 2017, 20:48, Alexandre Torres Porres <porres@gmail.com> wrote:
it's one of those objects that is in Pd but could be easily dealt with in Pd without the external (...) but it's basically a line~ with an offset, and a fixed rate
looks like~ cyclone's count~ but much simpler
it just generates a signal ramp with the right characteristics to patch it into tabread4~ and playback samples at their original pitch.
or using it with tabread~ then instead pf tabread4~ looks again like count~ as one of its applications is in conjunction with index~ (basically tabread~).
There are quite a lot of externals like this (and some from me) where people coded something in C for convenience, but can be easily done in Pd without externals.
I know... Pd Extended is filled with things like that, and to make it more of a deal, documentation is sometimes bad, when simply non existing. I'm willing to help this in the forth coming Purr Data, by reorganising it and making it better documented cheers