- one track of 6 bars
- one track of 2 bars
- set sync length active.
- record track 1, say 6 bars
- record track 2. Aeros will force length to be 6 or 12 or 18 bars etc. Two bar track impossible.
- set sync length active
- record track 1, say 2 bars
- record track 2, six bars.
- success. One 6 bar track. One 2 bar track.
The order that tracks are recorded in shouldn’t determine whether it’s an allowed situation.
The underlying problem is that given a track of M bars, aeros only allows integer multiples of the length of that bar. But integer fractions of that are just as valid (assuming they equal a whole number of bars).
So a 6 bar initial track should allow track 2 to be of length 1, 2, 3, 6, 12, 18, etc. I.e. M/6, M/3, M/2, M, 2M, 3M, etc.
It’s not a difficult mathematical test so CPU power shouldn’t be an issue to run the test from multiplies of 1/16 to 16 and see if they fit. (If you really want speed it’s only a matter of keeping a table of prime factors for the first 20 or so integers)