pechnatunk

I'm trying to sync max to an external clock - my path goes - rtin - select 248 250 252 (timing, start, stop)- counter 0 0 23 - bang - timer - 60000 / timer output - prepend set - flonum - tempo $1 - tempo.

This works but goes out of sync quite quickly - i know it is a bit long winded, but can't seem to work out a more efficient way.

This works but goes out of sync quite quickly  - i know it is a bit long winded, but can't seem to work out a more efficient way.

rtin-tempo

Have a look at [sync~] in conjunction with [rtin]. This may help.

On Feb 8, 2007, at 9:27 PM, pechnatunk wrote:

> I'm trying to sync max to an external clock - my path goes - rtin - 

> select 248 250 252 (timing, start, stop)- counter 0 0 23 - bang - 

> timer - 60000 / timer output - prepend set - flonum - tempo $1 - 

> This works but goes out of sync quite quickly - i know it is a bit 

> long winded, but can't seem to work out a more efficient way.

> I'm trying to sync max to an external clock - my path goes - rtin -  
> select 248 250 252 (timing, start, stop)- counter 0 0 23 - bang -  
> timer - 60000 / timer output - prepend set - flonum - tempo $1 -  
> tempo.
>
> This works but goes out of sync quite quickly  - i know it is a bit  
> long winded, but can't seem to work out a more efficient way.
>
> Can anyone help pls?

I've checked out sync~ and have made some progress - it stays in time long enough for what i need to do. But now when i press play it skips the first note and offsets the whole pattern - i'm sure this is due to the way I am triggering start/stop.

Also, sync~ outputs at 1/4 beats - i need 1/16 beats - i could use the midi beat out - but that seems no different to using rtin by itself.

I need the output to be ints counting from 0 - 16 at the rate of 1/16 of a bar.

Also, sync~ outputs at 1/4 beats - i need 1/16 beats - i could use the midi beat out -  but that seems no different to using rtin by itself.

I've found this suits my sequencer better since the bangs are faster, but i'm still having the same offset problem with start/stop of the pattern.

I've found this suits my sequencer better since the bangs are faster,  but i'm still having the same offset problem with start/stop of the pattern.

try this... do u still get the offset? works fine for me.

On Feb 11, 2007, at 1:53 AM, pechnatunk wrote:

> I've found this suits my sequencer better since the bangs are 

> faster, but i'm still having the same offset problem with start/ 

[sync~] itself responds to the midi start and stop real-time messages 

- perhaps this will suggest a method to you. Also, look at use of 

[rate~] on the output, as the example in the reference pages for 

[sync~] shows, in order to get the desired sync rate in relation to 

>
> Actually ,
>
> I've found this suits my sequencer better since the bangs are  
> faster,  but i'm still having the same offset problem with start/ 
> stop of the pattern.
>
>

[sync~] itself responds to the midi start and stop real-time messages  
- perhaps this will suggest a method to you. Also, look at use of  
[rate~] on the output, as the example in the reference pages for  
[sync~] shows, in order to get the desired sync rate in relation to  
the MIDI beat clock.

This is the patch i now have to edit and send CC values - it now starts to go out of time again (your patch didn't justin) but i only really need it to run for about 2 bars in order to record a motion seq into my electribe.

Thanks steven, i know i should start to understand the more accurate timing solution, i had a look at it but edge~ doesn't seem to pick up a 0 or 1 from neither a phasor~ or a sync~

Anyway here's what i did if you're curious.

Thanks steven,  i know i should start to understand the more accurate timing solution,  i had a look at it but edge~ doesn't seem to pick up a 0 or 1 from neither a phasor~ or a sync~ 

> i had a look at it but edge~ doesn't seem to pick up a 0 or 1 from

Unless the frequency isn't an exact division of the sample rate this is 

just very unlikely. You have to pass it through a comparison like [

0.01] or something like that before sending it into edge~...

pechnatunk wrote:
> i had a look at it but edge~ doesn't seem to pick up a 0 or 1 from
> neither a phasor~ or a sync~

Unless the frequency isn't an exact division of the sample rate this is 
just very unlikely. You have to pass it through a comparison like [
0.01] or something like that before sending it into edge~...

-- 
Stefan Tiedje------------x-------
--_____-----------|--------------
--(_|_ ----|-----|-----()-------
-- _|_)----|-----()--------------
----------()--------www.ccmix.com


I've now got it in time but there is a strange and inconsistant delay from when I press play on my external sequencer. 

It stays in time once it starts but doesn't start instantly. I thought this was due to the edge~ not picking up the initial 0 or 0 - non 0 , but the latency is irregualar.

I've tried putting different figures in the

I've now got it in time but there is a strange and inconsistant delay from when I press play on my external sequencer. 
It stays in time once it starts but doesn't start instantly.  I thought this was due to the edge~ not picking up the initial 0 or 0 - non 0 ,  but the latency is irregualar. 

I've tried putting different figures in the 

> I've now got it in time but there is a strange and inconsistant delay

> from when I press play on my external sequencer. It stays in time

> once it starts but doesn't start instantly.

Try to start it with [rtin]->[sel 250] and then only update with edge~...

pechnatunk wrote:
> Thanks stefan,
>
> I've now got it in time but there is a strange and inconsistant delay
> from when I press play on my external sequencer. It stays in time
> once it starts but doesn't start instantly.

rtin - tempo