I’ve noticed a quirk in the buffer~ object. Steps to reproduce:
1. open patch below
2. load 22KHz audio file
Expected behaviour: buffer~ remains 1000 ms long, 1000 ms of audio
gets loaded in
Actual behaviour: buffer~ gets resized to 2000 ms long, only 1000 ms
of audio gets loaded in, last 1000 ms of buffer is empty.
Desired behaviour: buffer~ should always stay length defined by its
argument, unless replace or size messages are used, even when
soundfiles using different sample rates are loaded.
Version info: MaxMSP 4.5.5, MacOSX 10.3.9
Now I can probably guess WHY this happens, but that doesn’t mean I
LIKE that it happens :-P
Or am I being too finicky?
bless the little C74 elves.
#P window setfont "Sans Serif" 9.;
#P window linecount 2;
#P comment 220 153 198 196617 < -- buffer gets resized to 2000 ms ,
and only first 1000 ms of audio gets loaded.;
#P window linecount 1;
#P message 114 109 66 196617 read 0 1000;
#P newex 114 153 105 196617 buffer~ blahdie 1000;
#P comment 185 109 237 196617 < -- try reading in a file that's saved
as 22050 Hz.;
#P connect 2 0 1 0;
#P window clipboard copycount 4;
Log in to reply
Let us tell you about notable Max projects, obscure facts, and creative media artists of all kinds.