Not sure if this is a bug, or just all that the LOM provides, but I have a main-track with scenes that utilize follow-actions and clip groupings. ie scene3 either repeats, or triggers scene7-9. And scene9 always goes back to scene3.
The problem is that abletonSONG COMP’s channel ‘last_started_scene’ doesn’t correctly update to scene3, if after scene9, scene3 chooses to repeat.
I’ll try to say it another way, because its a somewhat particular use-case.
LOGIC:
scene 3 = 50/50 (scene3/scene7)
scene 7 = 100% (scene8)
scene 8 = 100% (scene9)
scene 9 = 100% (scene3)
If scene3 chooses to repeat, then last_started_scene remains at value 9 until scene7 is triggered, even though scene3 could repeat numerous times.
A problem this creates is that it becomes difficult to tell if scene9 has ended.
The LOM is a bit tricky with scene changes but I’ll look into this for the next round of TDAbleton development. For now, if follow actions aren’t working, you might try the technique where you include a track with a silent midi note that is unique to each scene, then track scene changes by looking for notes on that track.
The dummy-clips idea helped solve my issue. But just for clarity, follow-actions are working for me, just not detecting all changes inside of TDAbleton.
Also I tried using the abletonSong Callbacks, and the results are similar. The playing-clip or SceneStarted does not update in the instance I laid out previously.
Thanks for heads up. I totally understand the problem, it’s just going to take a bit of a deep dive to fix, but it’s in my todo! It may well be an issue with LOM, but I will try when I get back into some TDAbleton changes.