@Jack said:
Hi josh,
So when we record an 8 bar loop, GTL asks Link for the beat time to sync to. As it's 8 bars GTL gives Link an 8 bar "phase" to work with. Link then returns a beat time which conforms to this phase. Link has to synchronise phase across multiple apps so all apps start their 8 bar loop at the same time. This means that GTL has no control over the beat time over a particular phase so it could come in at any point through the sequence.
I'm really struggling to find a way to "predict" this behaviour. My requirement is that my Mozaic script can predict the point in time when all apps start this 8 bar loop at the same time. This is due to the fact that Mozaic will need to set up the inputs that are sent to GTL just before that point in time.
As Mozaic knows GTL's current clock length (I manage its state only through Mozaic so I can track it), there must be a way to talk either talk to Ableton Link somehow and retrieve the state, or that GTL itself would send some signal using MIDI that then could be received by Mozaic (for example, the signal could be sent 1 bar before the actual start, so my script would know that it can set up the inputs at the end of the current bar).
This is why you are seeing the unpredictable behaviour when cuing to record the 8 bar loop. If you turn Link off then GTL manages the phase and it becomes more predictable as GTL doesn't care what other apps are doing.
As I need GTL to be synced with AUM, turning Link off is not really an option. :frowning:
I think using GTL with CUE turned off is the only way to set exactly where you want the loops to start and stop recording.
I thought about doing that and renounce all the nice features that CUE offers. But this would mean a lot for me to handle in the background, which would probably be possible with Mozaic, but I fear that GTL and AUM would diverge in synchronicity after a while (e.g. due to "lags" or high CPU load). So having Link taking care of these very basic things is really good. But for my use case it's very bad that I just cannot predict this very moment described above.
