Lorenzo Lamasse

I'm using zl.stream to compute minimum and maximum value of an incoming set of data, but I face an issue where zl.stream seems to only be able to output 256 values at a time, though it accepts the "zlmaxsize" message to more than that... 

Not sure about the reason for that limitation (performance most likely) but if there's nothing one can do, I'd very much be grateful if someone can point me to another approach. 

Provided buffer~ operations don't seem to be able to output min and max value of their content so that would probably be some gendsp stuff. No big deal but a bit heavy, huh ?

Hi all, 

I'm using zl.stream to compute minimum and maximum value of an incoming set of data, but I face an issue where zl.stream seems to only be able to output 256 values at a time, though it accepts the "zlmaxsize" message to more than that... 
Not sure about the reason for that limitation (performance most likely) but if there's nothing one can do, I'd very much be grateful if someone can point me to another approach. 
Provided buffer~ operations don't seem to be able to output min and max value of their content so that would probably be some gendsp stuff. No big deal but a bit heavy, huh ?

Hi all, 

I'm using zl.stream to compute minimum and maximum value of an incoming set of data, but I face an issue where zl.stream seems to 

zl-stream-with-more-than-256-items

no problem here even in max 6 using old fashioned zl init

image.png

Facing the same problem. 
I'm using the Max 8.3.1.

zl objects need proper max list size set.

same applies to ALL zl objects like zl.len

Did you look at all at the screenshots ?
zl objects need proper max list size set.
in old objects using 
zl 1000 stream 1000
in new versions
zl.stream 1000 @zlmaxsize 1000

same applies to ALL zl objects like zl.len
otherwise enjoy 256 list items....
available size range is 1- 32767 ....


Weird, I thought I had used zlmaxsize properly by sending it as a message, but it doesn't seem to work.

- using the example inside zl.stream help

- sending [zlmaxsize 1000] to left inlet changes the attribute of the zl.stream object (new value properly reported at visualization)

- however, it keeps outputting 256 items nonthelesss

On the other hand, doing the max size setup at object creation works fine using [zl.stream 1000 @zlmaxsize 1000].

There may still be an issue there then...

Weird, I thought I had used zlmaxsize properly by sending it as a message, but it doesn't seem to work. 

So here is what I noticed:
- using the example inside zl.stream help
- sending [zlmaxsize 1000] to left inlet changes the attribute of the zl.stream object (new value properly reported at visualization)
- however, it keeps outputting 256 items nonthelesss
On the other hand, doing the max size setup at object creation works fine using [zl.stream 1000 @zlmaxsize 1000].
There may still be an issue there then...
Lorenzo


I did not notice that because I tend to set zl objects in old style.

That seems to be a bug, but in case you need a dynamic

max list length, sending int into right inlet of zl stream seems to work as expected.

in any case @zlmaxsize entered in zl objects seems to work too.

I did not notice that because I tend to set zl objects in old style.
That seems to be a bug, but in case you need a dynamic
max list length, sending int into right inlet of zl stream seems to work as expected.
in any case @zlmaxsize entered in zl objects  seems to work too.


zl.stream with more than 256 items ?