I ran into a problem, think I figured it out, and if so it's a reasonable operational mode (not a bug), but might require some explaining to not have it confuse other people?

I was running into a problem where mobius wasn't in sync with ableton as master. I had set the (new groovy session settings) as directed in a thread I initiated in Feb where the first track is host-sync'ed on a bar basis, and the subsequent tracks are driven by the first track with loop granularity. v41 .

I think what was happening was the plugin initializes, picks up at some point a start point and a speed. If the host starts and stops - even with no tracks recorded - I suspect Mobius is keeping the old timings. This happens at startup, as far as I can tell.

I guess I expect that if the host starts and stops or changes tempo with no tracks recorded, then mobius will pick up the new values.

The answer appears to be always global reset after starting the host's time the way you like it. Global Reset will certainly pick up the new timing.

Is there some setting about when to pick up new time, or how to deal with time changes? I understand that host timing changes could be handled a lot of ways - stretch, reset start, etc. That seems like a hard problem and maybe there are a lot of config settings I haven't found / don't understand.

At first I'd like the simple thing - if no tracks, always go with new.

If my diagnosis is correct, I would request:

Pick up new timing if there are no tracks recorded (including the "sync track from master").
If "sync track with master" enabled, and the host has changed and the track has not resync'ed in any way, a visual indication that track is not in sync would be groovy.

Right now, I hope / believe I have a workaround, and it's sensible. Whenever I touch the tempo or start/stop, do a global reset after not before (I think I had been doing a GR, then changing the tempo or start time, then attempting to loop).

Thanks again for a great program / plugin! The new "session" settings are FAR more discoverable!