weird sync issue

[m4m]

since yesterday, i have an issue with sync between my ESX and ER1
for the last 5 years it worked flawlessly, but yesterday it sotped working when using the esx as master clock, the start is sent as the ER1 starts, but they drift appart

when i clock them both from live it's sync tho

also, why on earth does the plat/stop command IS NOT SENT when in external sync? i still want to use my esx as a control station, but its clock seems to be unreliable so i have to use ableton's but now i cant start stop with my tribe

[X-Trade]

also, why on earth does the plat/stop command IS NOT SENT when in external sync? i still want to use my esx as a control station, but its clock seems to be unreliable so i have to use ableton's but now i cant start stop with my tribe

prevents an infinite loop or MIDI data flood/overload. Imagine you have two devices connected together - hit play on A, sends it to B which sends play back to A again, which sends it back to B, ad infinitum.

[m4m]

i see, it's pretty logical as most device wont let you filter those messages like you can filter cc/sysex/pc/etc
i remember the mc505 did allow the use of the transport when sync'ed to cubase vst3.5 (shows my age lol), but again, it might have had a midi message filter on it that tribes don't