Forums > MaxMSP

Synchronising host to counter

March 21, 2006 | 8:32 pm

Hi there

This is causing me much frustration, so if any of you could help (again!) i’d be really grateful.

I’m having real trouble converting hostsync~ to get accurate sync information. Previously the counter object was controlling the position of everything, and the "step" increments were in semi-quavers (i.e. 16th steps). Unfortunately hostsync only reports beat changes, and I’ve tried linking this to the counter object but there is some latency. Can’t get my head round hostphasor~ either – do you think this could be converted to work with 16ths (semiquavers)? The metro object does not work at the same rate as hostphasor so it will always lag behind won’t it?

Many thanks, hope this makes sense!

Toby


March 21, 2006 | 11:46 pm

here a couple of suggestions…..

hope this helps….let me know if I got the question all wrong ….

#P window setfont "Sans Serif" 9.;
#P window linecount 1;
#P newex 587 96 48 196617 loadbang;
#P message 587 119 20 196617 16;
#P newex 437 136 68 196617 rate~ 4. lock;
#P newex 437 111 65 196617 hostphasor~;
#P number 437 311 35 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;
#P window linecount 2;
#P comment 623 142 68 196617 number of 16th "steps";
#P window linecount 1;
#P newex 507 174 33 196617 / 16.;
#P newex 437 283 48 196617 change 0;
#P number 587 141 35 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;
#P newex 437 198 80 196617 rate~ 0.25 lock;
#P newex 437 257 64 196617 snapshot~ 2;
#P comment 479 225 55 196617 # of steps;
#P newex 437 227 40 196617 *~ 16.;
#P newex 144 100 48 196617 loadbang;
#P button 41 314 15 0;
#P newex 41 282 36 196617 edge~;
#P newex 41 254 39 196617 < ~ 0.5;
#P message 99 123 14 196617 1;
#P message 114 123 14 196617 4;
#P message 129 123 14 196617 8;
#P message 144 123 20 196617 16;
#P flonum 99 199 35 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;
#P newex 99 179 31 196617 !/ 4.;
#P newex 41 222 68 196617 rate~ 1. lock;
#P newex 41 79 65 196617 hostphasor~;
#P comment 166 125 127 196617 Division of one bar;
#P fasten 17 0 13 1 592 219 472 219;
#P fasten 17 0 19 0 592 169 512 169;
#P connect 24 0 17 0;
#P connect 25 0 24 0;
#P connect 23 0 16 0;
#P connect 19 0 16 1;
#P connect 16 0 13 0;
#P connect 22 0 23 0;
#P connect 13 0 15 0;
#P connect 15 0 18 0;
#P connect 18 0 21 0;
#P connect 12 0 5 0;
#P connect 10 0 11 0;
#P connect 9 0 10 0;
#P connect 2 0 9 0;
#P connect 1 0 2 0;
#P connect 4 0 2 1;
#P connect 3 0 4 0;
#P connect 5 0 3 0;
#P connect 6 0 3 0;
#P connect 7 0 3 0;
#P connect 8 0 3 0;
#P window clipboard copycount 26;


March 22, 2006 | 12:04 am

Cheers, but how can I open the text you gave me, cos it’s missing the top two lines that are usually there? Thanks


March 22, 2006 | 12:39 am

Scrap that! Just discovered the ‘new from clipboard’ feature that I never knew existed. Just trying your patch now…


March 22, 2006 | 2:04 am

cheers spleef dude

You’ve sorted my problem out once and for all! Don’t think i was ever gonna get my head round the phasor issue, your help is really appreciated.

Toby


October 20, 2008 | 8:00 pm

This is great!
didn’t realize you could ‘lock’ the rate object!
sorted many problems out and opened many new max frontiers!
thanks


October 21, 2008 | 10:56 pm

One problem.

Can anyone tell me why the hostphasor~ starts at different times with the host?
sometimes it starts at the beginning and sometimes half way (or a division of the beat) through a cycle?

how could i stop this?

would i have to have some kind of reset trigger the rate or hostphasor~ every time i start and stop the host?


October 25, 2008 | 5:56 pm

yes, there’s an reset message to rate~

this message makes the output ramp restart when the input ramp is at 0.

Same as goto 0. 0. (goto 0. at time 0.)


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