hostsync~ vs. transport

[gato.rui]

hi,

i'm porting a max 5 patch to MFL, a sequencer built by Lo-Fi Massahkah called Instamatic

it uses hostsync~ to get the timming info from Live, and now i want to use the transport object, witch i think is the most correct object to get tempo information from live.

the problem is that the hostsync~ raw ticks output is different from the transport raw ticks output

any clues how to make the adaptation?

thanks!

[pukunui]

Use a

phasor~ @frequency 1 0 0 bars.beats.units @lock 1

To get an audio ramp over the length of one bar, then subdivide it as you need to.


-A

[gato.rui]

thank you for the fast reply pukunui,

seems out that the raw ticks sent by the transport object differ from the hostsync~ because they needed to be divided by the resolution (in this case /480)

problem solved, port done! really tight sync now

[Machinate]

@gato.rui
could you post the code here?

cheers

[gato.rui]

No problem, do you want the full instamatic port or just the transport section?

[Machinate]

the whole shebang

For some reason I can't find my instamatic files round here.

[gato.rui]

here goes:

http://www.how.pt/gato/insta.zip

it contains my lemur template, and the m4L patch

i have my OSC target 1 settings pointing to 10.0.0.11 9000

and my lemur on static ip 10.0.0.12


i'm testing the sync by recording to another live midi track, and i get a little offset of about :

1/4096 with the fireface buffer size of 128 samples

1/8192 with the fireface buffer size of 96 samples

cheers

[Lo-Fi Massahkah]

Oooohhh... Sharing!

.m