constant delay of 500ms between two bangs ?!

Jun 19, 2006 at 3:10pm

constant delay of 500ms between two bangs ?!

Look at the patch below. There’s a constant 500ms between the first bang
and the one out of the counter… How is it possible to have such delay,
and how does it remain absolutely constant ?

f.e

#P window setfont “Sans Serif” 9.;
#P window linecount 1;
#P newex 158 331 19 9109513 t b;
#N counter 0 1 8;
#X flags 0 0;
#P newobj 158 294 151 9109513 counter 0 1 8;
#P flonum 49 419 69 9 0 0 0 139 0 0 0 221 221 221 222 222 222 0 0 0;
#P newex 49 384 29 9109513 timer;
#P toggle 49 77 29 0;
#P newex 49 238 19 9109513 t b;
#P newex 49 161 27 9109513 t i 1;
#P newex 49 211 68 9109513 tempo 120 2 8;
#B color 14;
#P connect 2 0 4 0;
#P fasten 2 0 6 0 54 275 163 275;
#P fasten 1 1 6 2 71 199 233 199;
#P connect 3 0 1 0;
#P connect 0 0 2 0;
#P connect 1 0 0 0;
#P connect 4 0 5 0;
#P fasten 7 0 4 1 163 367 73 367;
#P connect 6 0 7 0;
#P window clipboard copycount 8;


f.e chanfrault | aka | personal computer music
> >>>>>> http://www.personal-computer-music.com
> >>>>>> |sublime music for a desperate people|

#26480
Jun 19, 2006 at 3:32pm

it seems to me that you have put the quarter note at 120 metronome
speed,
that means 2 quarter notes every 1 second. so each of the quarter
notes comes every 500 mls.
the timer object measures how much time, after one bang, the
successive bang will come.
That’s not a delay between the 2 bangs, but the exact timing of the
tempo object.

:-)

#79229
Jun 19, 2006 at 3:37pm

ups,
i’ve realized now that you were sending a bang to the left inlet also.
well it seems that the problem is much more complicated than what i
thought… sorry for the wrong answer.

right now, im near to think that maybe the problem is about “the
refreshing feature” of the timer object, more than a specific delay
problem..

cheers

#79230
Jun 19, 2006 at 3:41pm

Am 19.06.2006 um 17:10 schrieb f.e:

> Look at the patch below. There’s a constant 500ms between the first
> bang and the one out of the counter… How is it possible to have such
> delay,

through the power of right-to-left order!

> and how does it remain absolutely constant ?

it’s tempo’s notorious timing accuracy ;)

(you are confusing timers inputs I think)

cheers, g.

#79231
Jun 19, 2006 at 3:43pm

for example…
i ‘ve been using a lot timer object in this manner:

and the timer is always giving the difference in time between two
successive events, that, in this case, they are the events triggered
by the tempo object.

a low explanation is for me that, when the bangs are simoultaneous,
“timer” consider them as a single bang on the right inlet, always
refreshing.
The high explaination is due to other more expert people…

:-)

#79232
Jun 19, 2006 at 3:45pm

hi,

it’s not a delay, it’s the interval of the tempo object
if you want consecutive bangs, use a uzi object.

in the help file, they say tempo is a “Metronome controllable in beats per minute”.
it also includes a counter starting at 0.

if you only want your count to go from 1 to 8 instead of 0 to 7, and that’s what I beleive
considering your patch, only add a [+ 1] after the [tempo 120 2 8].

peace.
//yac

#79233
Jun 19, 2006 at 4:01pm

about the timer object problem,
this object is one those few for which the right-to-left order rule is not valid.
its left inlet is cold: it causes no output but starts or restarts the timer.
and its right is hot: it causes the output of the elapsed time.
that’s all…

//yac

#79234
Jun 19, 2006 at 4:09pm

On 19-Jun-2006, at 17:10, f.e wrote:

> Look at the patch below. There’s a constant 500ms between the first
> bang and the one out of the counter… How is it possible to have
> such delay, and how does it remain absolutely constant ?

That’s how timer works. It’s not as strictly right-to-left as you may
have thought. You might want to trace through the following modified
version of your example.

#P window setfont “Sans Serif” 9.;
#P window linecount 4;
#P comment 70 176 273 196617 Hit the button once to get timer
initialized ; then turn trace on ; hit the button again and follow
the trace through ; Est-ce que tout est claire maintenant?;
#P button 49 210 15 0;
#P window linecount 1;
#P newex 158 331 19 196617 t b;
#N counter 0 1 8;
#X flags 0 0;
#P newobj 158 294 151 196617 counter 0 1 8;
#P flonum 49 419 69 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;
#P newex 49 384 43 196617 timer;
#P newex 49 238 19 196617 t b;
#P connect 5 0 0 0;
#P connect 0 0 1 0;
#P fasten 0 0 3 0 54 275 163 275;
#P connect 3 0 4 0;
#P fasten 4 0 1 1 163 367 87 367;
#P connect 1 0 2 0;
#P window clipboard copycount 7;

– P.

————– http://www.bek.no/~pcastine/Litter/ ————-
Peter Castine +–> Litter Power & Litter Bundle for Jitter

iCE: Sequencing, Recording & |home | chez nous|
Interface Building for |bei uns | i nostri|
Max/MSP Extremely cool http://www.castine.de

http://www.dspaudio.com/

#79235

You must be logged in to reply to this topic.