[PD-dev] block~-overlapped canvases: samplerate wrong for dsp objects

2008-06-27 Thread Thomas Grill
Hi, i just stumbled over a strange behavior in canvases with overlapped blocks without resampling (e.g. set with [block~ 1024 2]). In such canvases e.g. [osc~ 440] delivers a cosine wave with an actual frequency of 220 Hz, because of the double overlap. This is because dsp signal vectors carry

Re: [PD-dev] bang [block~] to query current blocksize

2008-06-27 Thread Mathieu Bouchard
On Fri, 23 May 2008, Hans-Christoph Steiner wrote: It seems that adding an outlet to block~/switch~ seems to be the most obvious interface for getting the data. Perhaps just a message then? sending a "get blocksize" message to either object could output "blocksize $1" through the last outle

Re: [PD-dev] [range] from maxlib

2008-06-27 Thread Mathieu Bouchard
On Tue, 24 Jun 2008, Roman Haefeli wrote: anyway, it seems that it has been years ago, so nevermind. i was confused when trying to help someone with a patch, that uses [range], which i found in /deprecated (this person was using pd-0.38.4-extended, irrc). obviously, i had to think, that the orig