Ableton Forum

(found in Live version 6.0.1)

If you have two instances of Live sync'd together using midi-sync (clock-type: song) and the master instance changes the song position to a location greater than bar 1025, the slave instance song position pointer resets to bar 1.

This issue is reproducible every time.

It may be worth noting that we're using ipMIDI software over a 100Mbit LAN to sync the instances of Live together (instead of a traditional MIDI connection).

I have this same problem! It's what I'm trying to find a solution for... is there any solution to this, or does anyone even know what the problem is?

Me and a friend are having the same issue, only we're using MIDI connection through two firewire audio interfaces.

Has ANYONE got any advice on this one? I would really appreciate it.

Thanks,
Dwight.

Bump.

Any word on this one? Is this a recognised issue with Ableton or is it just a limitation of MIDI?


Thanks,
Dwight.

No particular idea of this is a limitation of MIDI. Maybe this will help out:

http://www.tweakheadz.com/sync_mmc_mtc_smpte.htm [/quote]

hi
I'm having the same problem. I'm syncing two mac book pro's both ableton.
it's working fine up until bar 1025 then it's not getting any info.
is this the limit on an ableton session?
any ideas?
cheers
james

Hello, sorry to dig up an old thread.. But I am currently using Live 8.2.5 and I'm still running into this issue. Is there a work-around for this? I need to be able to run sets longer than 1024 bars while syncing a slave computer via wireless MIDI network.

Change logs said this should have been fix in 7.0.7b1 but I'm still experiencing this issue:
"Sending of MIDI Song Position Pointer message beyond bar 1025 would lead to incorrect behavior and different behavior on Mac OS X and Windows. "

System Specs for both computers:
Macbook Pro (Non unibody)
Live 8.2.5
OSX 10.6.8

Thanks!

Jason