Anthony Palomba

I have been trying out the latest update and noticed 

that there were some rewire changes. The change list 

- clocksource support for transport external sync to ReWire

- ad_rewire: creates a clock source for transport sync

- transport: now has a clocksource attribute (currently set to internal / rewire)

So does this mean that when I start rewire, it should also 

start the global transport? Also if I set the clocksource attribute

to rewire, will it also start the global transport?

I tried a few tests and it seems that rewire activity has no 

on the global transport. Am I misunderstanding these changes?

I have been trying out the latest update and noticed 
that there were some rewire changes. The change list 
mentions the following changes:

- clocksource support for transport external sync to ReWire
- ad_rewire: creates a clock source for transport sync
- transport: now has a clocksource attribute (currently set to internal / rewire) 

So does this mean that when I start rewire, it should also 
start the global transport? Also if I set the clocksource attribute
to rewire, will it also start the global transport?

I tried a few tests and it seems that rewire activity has no 
on the global transport. Am I misunderstanding these changes?


max-5-05-and-rewire

Sorry, I was looking at the wrong thing...

My test patch was referring to rewire host sync. Is there any

possible way we can get the global transport to start when hostsync starts?

Sorry, I was looking at the wrong thing...
My test patch was referring to rewire host sync. Is there any
possible way we can get the global transport to start when hostsync starts?


When rewire is the clocksource for transport, the host's transport will control Max's global transport. Make sure you have audio on and that rewire is otherwise functioning correctly.

This is how I've been syncing transport between Max and ReWire hosts:

Is there a more elegant way to do this since 5.0.5?

Hostsync~ and hostcontrol~ etc. are still completely supported and are good patching.

In the interests of broadening the feature set of Max's own time management tools, we have introduced a way to slave the global transport in max to the rewire host. It's more or less as easy as

Andrew, there are a couple of things I noticed about your 

example. The locked metro does not seem to start when I start the 

hostcontrol~. I tried using the following metro as well:

[metro 4n @autostart 1 @autostarttime 0] this does not 

start either. I have to manually start it. Should it not 

The transport does not seem to pick up any rewire tempo changes. If 

I set the tempo to 90 in my rewire host (Sonar), [transport] still

says 120. Is there a way I can link them?

Also, hostsync~ reports the tempo in some strange format

how do I convert it into something meaningful?

Andrew, there are a couple of things I noticed about your 
example. The locked metro does not seem to start when I start the 
hostcontrol~. I tried using the following metro as well:
[metro 4n @autostart 1 @autostarttime 0] this does not 
start either. I have to manually start it. Should it not 
start on it's own?

The transport does not seem to pick up any rewire tempo changes. If 
I set the tempo to 90 in my rewire host (Sonar), [transport] still
says 120. Is there a way I can link them?

Also, hostsync~ reports the tempo in some strange format
how do I convert it into something meaningful?

It could be that Sonar doesn't send tempo changes over ReWire. We tested with Live (both Mac and Windows) and Logic, which do. Does the "useless" tempo number in hostsync~ change when you change the tempo in Sonar?

The number may be samples per beat, which is what ReWire uses for tempo I think.

Yes, the hostsync~ shows that the tempo has changed.

I guess I could calculate the tempo using the sample

rate and manually set the tempo for [transport].

Yes, the hostsync~ shows that the tempo has changed.
I guess I could calculate the tempo using the sample
rate and manually set the tempo for [transport].


It sorta works right for me in Sonar PE 7.

It seems like there may be some missing pieces here though. I'm not able to update Sonar's transport with the bpm message to hostcontrol~, and tempo changes within Sonar seem to require a transport restart in Sonar to register correctly with Max's global transport. But apart from that it locks.

Max 5.05 and rewire...