Forums > MaxMSP

buffer problems

January 31, 2006 | 5:52 pm

Im using about 4 buffers in a loop playing patch, loading them with relatively short wave files. For some reason the buffer sometimes will just cut a few seconds off the end of the loop. Is this a cpu issue? Are my loops too long? is my max just upitty? wass tha deal…


January 31, 2006 | 7:36 pm

Are you using replace instead of open? What I’m saying is: how are
you resizing your buffers? How are you playing your buffers?

_Mark


January 31, 2006 | 11:39 pm

i had a similar problem. i was constantly replacing waves into a buffer and after a few turns the groove~ i used to play them with started to cut the end of each file . After a while i found a simple solution: use the info~ object and connect it to the groove~ object

like this

max v2;
#N vpatcher 112 58 712 458;
#P window setfont "Sans Serif" 9.;
#P window linecount 1;
#P message 60 306 56 9109513 startwindow;
#P newex 170 339 28 9109513 dac~;
#P message 78 152 14 9109513 1;
#P newex 78 190 28 9109513 sig~;
#P message 140 60 38 9109513 replace;
#P newex 140 274 61 9109513 groove~ test;
#P newex 220 175 105 9109513 info~ test;
#P newex 146 124 81 9109513 buffer~ test 1000;
#P connect 5 0 4 0;
#P connect 4 0 2 0;
#P fasten 3 0 0 0 145 92;
#P connect 2 0 6 0;
#P connect 7 0 6 0;
#P connect 2 0 6 1;
#P connect 1 6 2 2;
#P connect 0 1 1 0;
#P pop;



f.e
February 1, 2006 | 7:56 am

Always use a [replace -1 2] (or -1 1 if mono) to load a new file. It
clears the previous size of the buffer~ which was relative to the
previous loaded file, and it replaces the size of the buffer~ with the
size of the new file.

best

f.e


Viewing 4 posts - 1 through 4 (of 4 total)