[PD] Array display Limit (was Re: [tabread4~] bug???)

Alexandre Torres Porres porres at gmail.com
Thu Jul 26 05:37:07 CEST 2012


2012/7/24 i go bananas <hard.off at gmail.com>

> There is some inbuilt limit to array sizes that needs to be overridden by
> using the -maxsize tag when loading a file from soundfiler.
>
> I have a feeling it might mess things up with GOP arrays if you use that.
>

The same thing happens when we place arrays and give them sizes over 2ˆ24,
so I don't see how [soundfiler] should be blamed. There is something else
that prevents it from displaying, which really bums me out, because we can
even actually play it, but not see it.

Why does this happen? Any chance on removing this display limitation out?

Thanks.  And thanks to Iohannes for the onset tip and Llorenzo for the
sample rate tables about the [tabread4~] limit.

All I can think of is that the same kind of limitation ruins the displaying
of the arrays, so maybe a higher bit resolution version of it can make it
happen, isn't that right?


Now, I made a parallel to the phase vocoder bug I reported and realized
that the 47.5 seconds limit I had is 8 times smaller than 380 seconds. Not
sure why, but the block size of 512 is 8 times bigger, maybe there's some
relationship... who knows? Anybody?

check here for more info:
http://lists.puredata.info/pipermail/pd-list/2012-07/097071.html

But anyway, I'm working around with the onset tweak.

Thanks
Alex
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.puredata.info/pipermail/pd-list/attachments/20120726/adcfbd27/attachment.htm>


More information about the Pd-list mailing list