Hi Fred, I'll answer you here

> What do you mean by setting samples in the delay line?
> I tried understanding what fexpr~ does with [set ...( but failed miserable :-(

first, I mean that regarding [z~], [delay~] in max doesn't have this.

What it does is you can set the values of the previous samples, in fexpr you can set values for any delay line in it, both inputs ($x1[-1], $x3[-4]) and outputs ($y2[-2] etc). You can also clear it (0 everywhere).

I think it's another cool feature to add to [z~] besides clearing it.

say you have a constant signal = 1 into your delay line and it is 5 samples long (1 1 1 1 1) - the leftmost being the first samples of the delay line

you can go and set different values for them like this, lets set $x1[-1] and $x1[-2] to 0 and 0.5

now it's 0 0.5 1 1 1

and the samples we've set will quickly be overwritten by the constant signal of "1"

hope this does it. 

cheers

2015-12-13 8:06 GMT-02:00 Fred Jan Kraan <fjkraan@xs4all.nl>:
Hi Alexandre,

Cool, works, and if your planing on doing something, besides a clear
message you could also think of a "set" message where it receives a list
of numbers setting the samples in the delay line (max list size = delay
size).

The [clear( message is as simple as DSP can get; just zero the entire buffer. Most other operations are more complex. What do you mean by setting samples in the delay line? Trying to set more than a few will get very inefficient, and from the message domain it will be hard to control where they be placed in the signal stream.

The "set" message would really make it much more powerful ;) - reminding
that delay~ and delwrite~ don't have this, only fexpr~

I tried understanding what fexpr~ does with [set ...( but failed miserable :-(.

Let me know how you feel about the suggestion, and when you could do
that if you're considering adding such features.

About the feature requests, maybe you could try to make a persistent overview (web page or in the http://puredata.info wiki)? Trying to find them in this list later is no fun, and it will be useful when I or some future cyclone maintainer might find the time to implement them. It allows for some extra explanation and maybe an abstraction to demonstrate the feature.

I just managed to install the Max/MSP 4.6 help patches and counted 470 objects there. Count 100 for vanilla Pd and 150 for cyclone, there are 220 to go...

cheers

Greetings,

Fred Jan

2015-12-11 20:08 GMT-02:00 IOhannes m zmölnig <zmoelnig@iem.at
<mailto:zmoelnig@iem.at>>:

    On 12/11/2015 11:01 PM, Alexandre Torres Porres wrote:
    > 2015-12-08 17:16 GMT-02:00 Christof Ressi <christof.ressi@gmx.at <mailto:christof.ressi@gmx.at>>:
    >
    >> Actually, [z~] is cleared everytime you change the right inlet
    >
    >
    > Although it serves well for the mean filter, I just came across the need to
    > clear the buffer for the same delay size, so I can't use [z~] or [delay~]
    > or [delwrite~]/[delread~]...
    >
    > so only option is [fexpr~] - which has a block limit but suits me
    >
    > anyway, not a bad idea to add a clear method to [z~] anyway

    how about giving [z~] a dummy delay (e.g. 'required+1') to trigger the
    clearing, and then set it back to the original value ('required')?
    not very elegant, but works *now*.

    fmadsr
    IOhannes


    _______________________________________________
    Pd-list@lists.iem.at <mailto:Pd-list@lists.iem.at> mailing list
    UNSUBSCRIBE and account-management ->
    http://lists.puredata.info/listinfo/pd-list




_______________________________________________
Pd-list@lists.iem.at mailing list
UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list