sync Live and Max perfectly

you can try midi beat clock,
or record midi in max and import into live.
is that Link sync so bad ?

Thanks Source Audio
yes i'm not really convinced by Link, but maybe I don't use exactly like I have to (but in a way, i don't see special functions I won't have seen)
no more modern system than midiclock do you think ? in this case, yes I will use this solution

I don't use Live at all, but remember users here complaining about Link sync not working reliably ...
Makes me wonder why do they advertise it as such ?
old good midi clock is what it is, I don't know how tight you need
your max output synced into live recording,
but as I suggested, you can allways record midi in max and import into Live.
You might also check if midi sync is different if max or live acts as clock master.

thanks !
my idea is to keep this link between the both softwares - Live is the score which controls my max patch.
The transport and the sequencer are in Max (driven by the transport) and I want to use Live to control my pattrstorage, that organise the change in my different patterns - the timeline provided by Live are easier to make musical scenarios.

FWIW, I worked on the same sort of thing for a while and ultimately switched to moving my Max into M4L devices. It is *much* easier to get super tight sync that way. I got it to decent with external Max, but now it's absolutely locked in. There are lots of things about M4L I don't love - the editing workflow is really annoying compared to standard Max, but overall it was worth it. I still prototype in stand-alone Max a lot though.

BTW, the key to getting great sync in M4L is to listen to the plugsync~ object.

Just figured I'd share in case that helps!

i would expect the best answer, as Iain wrote above, is to work within Live(using M4L), but just in case it helps:
Link sync, while it doesn't offer specific detailed control over position, can be nicely accurate/tight, but it's most robust when you run it on a completely private-network, ideally something like a personal hotspot with only the devices you require for working in the Link session, logged into that network
(if you run Link, even across applications on the same computer, but you're logged into regular wifi which accesses the larger world-wide-web, there are many different possible network services/interruptions that can cause Link to become unreliable... and also, some routers are setup by default to block specific ports it requires...)

if you're just looking for sync(and can work the Max-side of things around basic start/stop-control: for example, in Max, maybe you don't need to work by a specific point on a timeline tracked within Max alone, and in Live, you can always skip to the position you'd like then restart transport, this is how it would be using Live as the main timeline anyways), then Link can be great especially on a personal-hotspot-type connection(thinking about wireless sync in a performance-context, you would probably want to use a personal hotspot anyways: traveling venue to venue and expecting ideal wifi at every one wouldn't be feasible (also leaves you a bit exposed if you're an artist who becomes well-known for this, then hackers will be able to expect you to be logged into certain networks during specific showtimes.. but maybe i'm being paranoid there :D)).

Ha,ha, RAJA - it is not paranoid at all,
one can flood any kind of wifi network to bring it down,
being private or public, no mater if SSID is hidden or not.

Kids make this kind of things just for fun...
is Live Link not running on ethernet as well ?
would be a missery if one is bound to wifi only.

by the way, midi clock with SPP is just as well able to follow any DAW transport, and jumps in timeline.

Thank you for your messages.
unfortunately, also with the WIFI close, link doesn't seem really accurate.
So I decided to use midiclock with one of SourceAudio patch I found on an other post. But it's the version with the transport, because I use a lot of different quantified metro in my patch linked to the transport.

It works well but when I record the midi from Max in Ableton, it's not very accurate either (as you can see on the image attached on which I send some 1/16 notes). it looks like regular, but always with a bit of offset.

Do you know how I could fix that ?

Thanks,
M.

here few infos :

in max midi routed to - from IAC buss has latency of ± 33 𝔲s
same in any DAW, like Digital Performer.

in Live midi output from a track via IAC buss recorded to different track has ± 8.5 ms latency !?!?

latest live version 11.3.12, no audio tracks, effects or plugins.
that delay is same if midi comes from max,
and has nothing to do with midi clock.
next annoying detail is that IAC midi latency in Live is dependent on
audio buffer size - which is completely nonesense.
that 8.5 ms at 128 samples buffer drops to arround 4.6 ms at 32 samples buffer,
but what has audio buffer to do with midi ?

I don't see any options to "fix" that, Live seems not to be able to
use IAC buss properly.
I don't use Live and have no interest in it,
otherwise I would take time to measure it's midi clock, midi to - from
any external sources etc.