Forums > MaxMSP

metro having trouble keeping up with the beat

January 23, 2006 | 2:10 pm

dear max list members,

below is a simple patch to cross-fade or cut between two stereo
playback subpatches (left out to reduce email size).

if i type a value in the metro object speed box, say 64, then the
rhythm becomes very uneven. is this a fault inherent of my patch
design, or is metro unstable, or could it be to much for my computer?
i’m playing back two 10 minute stereo soundfiles using sfplay objects,
on a 1ghz g4 powerbook with 512 mb of ram.

could someone offer a suggestion why my "chopping" patch can’t keep a
tight rhythm?

best,
martin

max v2;
#N vpatcher 10 59 610 459;
#P window setfont "Sans Serif" 9.;
#P window linecount 1;
#N vpatcher 1107 154 1235 296;
#P origin 91 77;
#P outlet 34 112 15 0;
#P toggle 34 78 15 0;
#P window setfont "Sans Serif" 9.;
#P newex 34 94 56 196617 metro 500;
#B color 5;
#P slider 80 1 13 51 0 1;
#P newex 80 60 32 196617 * 10;
#P number 80 78 33 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;
#P connect 4 0 3 0;
#P connect 3 0 5 0;
#P connect 2 0 1 0;
#P connect 1 0 0 0;
#P connect 0 0 3 1;
#P pop;
#P newobj 377 96 44 196617 patcher;
#P hidden newex 422 112 38 196617 * 127;
#P toggle 422 96 15 0;
#P user hslider 232 96 18 128 128 1 0 0;
#N vpatcher 506 355 1106 755;
#P inlet 224 278 15 0;
#P inlet 264 266 15 0;
#P outlet 223 331 15 0;
#P outlet 257 328 15 0;
#P window setfont "Sans Serif" 9.;
#P newex 224 297 27 196617 *~;
#P newex 255 297 27 196617 *~;
#P inlet 295 260 15 0;
#P inlet 346 259 15 0;
#P outlet 305 324 15 0;
#P outlet 339 321 15 0;
#P inlet 50 70 15 0;
#P newex 111 132 39 196617 / 127.;
#P newex 48 122 39 196617 / 127.;
#P newex 101 183 41 196617 line~ 1;
#P newex 48 183 41 196617 line~ 1;
#P newex 306 290 27 196617 *~;
#P newex 337 290 27 196617 *~;
#P newex 48 141 29 196617 – 1.;
#P connect 7 0 5 0;
#P connect 5 0 0 0;
#P connect 0 0 3 0;
#P connect 6 0 4 0;
#P connect 7 0 6 0;
#P connect 13 0 15 0;
#P connect 17 0 13 0;
#P connect 3 0 13 1;
#P connect 16 0 12 0;
#P connect 12 0 14 0;
#P connect 3 0 12 1;
#P connect 2 0 9 0;
#P connect 11 0 2 0;
#P connect 4 0 2 1;
#P connect 10 0 1 0;
#P connect 1 0 8 0;
#P connect 4 0 1 1;
#P pop;
#P newobj 232 115 66 196617 p crossfade;
#P toggle 246 150 15 0;
#P newex 262 150 31 196617 dac~;
#P hidden connect 5 0 3 0;
#P hidden connect 3 0 2 0;
#P hidden connect 2 2 0 0;
#P hidden connect 2 0 0 0;
#P hidden connect 1 0 0 0;
#P hidden connect 2 3 0 1;
#P hidden connect 2 1 0 1;
#P hidden connect 6 0 4 0;
#P hidden connect 4 0 5 0;
#P pop;


January 23, 2006 | 3:40 pm


January 24, 2006 | 6:28 pm

yes, overdrive is and was on, but my metro’s are still terribly out of
tempo. i’ll try using square wave audio instead as control signals,
thank you for the hint!

and i’ll check the new archives…

martin haanstra


January 24, 2006 | 6:44 pm

I think you might be better served to
look at using the phasor~ object for
tighter timing – not least because it’s
particularly powerful when used alongside
the rate~ object to produce multiple
subdivisions of a single clock.

The examples folder has some resources
for audio-rate sequencing you may find
of use.


January 24, 2006 | 8:33 pm

You could check out tl.metro to see if that helps from the tl.objects:

http://www.bek.no/~lossius/download

It is driven by phasor~ whenever audio is running.

Best,
Trond


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