trevorn1 Glad it's working for you. I'm concerned that you needed to set Leader Acceptance to Accept. That should have been the default so the upgrader may be broken.
I didn't explain this well in the release notes, but the two "Acceptance" parameters work like this...
There are two special states a track can be in: Leader and Master.
Leader is what pre-46 called the Track Sync Master. It is the track that you record with when using "track sync", making one track match the length of another track. It works the same as it did before, but I changed the parameter names so it wasn't obvious. The default leader has always been the first track that you record,
Master is what pre-46 called the Sync Master or Transport Master. This is the track that causes MIDI clocks to be sent out. It is equivalent to what the EDP calls Sync=Out.
The biggest change in b46 was around the selection of the master track. Before you asked for this by setting the Sync Source parameter to Master. I think Mobius 2 called this SyncSource=Out to match the EDP.
In an environment with multiple tracks, I felt this parameter was misleading. You could set SyncSource=Master in all tracks but only one of them could actually become the master. The first one recorded would get to be the master, and the rest would silently start syncing with the Transport. I didn't like this because it wasn't obvious this was happening. You asked for this track to be the master, but there was already a master so that couldn't happen, and now there is no way to say what this track should do instead, it always went to the Transport.
b46 splits the two concepts of "this is what I want to sync with" and "I would like this track to generate midi clocks".
If you want a track to become the master and generate clocks, you set the Master Acceptance parameter. It doesn't matter what the track syncs with, any track can become the master if it accepts it.
I wrestled with the names around this: master-select, master-request, master-promotion, auto-assignment, etc. I settled on the notion of an "election" which was perhaps too cute. But the concept is simple. There are 8 tracks and only one of them can have a special state (leader or master). Who wins? Each time a track is recorded, and each time a track is reset, we have to go through a selection process. If there was no master, and now there is a track that wants to be the master, select it. If a track was the master but it is now reset, we can pick a different track to be the master.
In b47 this all still exists, but I added a simpler way to ask for this that is closer to what it was in b45. Underneath where you set the sync source for a track is a checkbox labeled Master Request. This behaves the same as what b45 would do when setting Sync Source to Master. It's just an on/off decision and you don't have to ponder levels of acceptance and elections. Those will be moved to section containing advanced parameters for those that want them, and they won't clutter up the main sync parameters.
