Transport "Bars per Loop" is ignored and reset to 1 on Master track record

shushz

Hello.

Observed in build 41, though I'm pretty sure this is not a new problem, which could be an indicator of my doing something wrong.

I'm trying to have my drum pedal sync tempo with a first recorded loop. The first track has its "Sync Source" set to master. In Globals -> Sync -> Transport both "beats per bar" and "bars per loop" are set to 4.
After a global reset Transport main element in the UI correctly shows both bars per loop and beats per bar as 4.

After the first track is recorded, the bars per loop suddenly jumps to 1. The tempo is then calculated as being 4 times slower. If instead of having both parameters set to 4 I only set the beats per bar to 16 (or, well, any other multiple of the parameters I intended) the tempo is calculated correctly.

A caveat - if the resulting tempo falls outside of the Min-Max range, usually too low, - the tempo is doubled and so is the number of bars in the "Transport" display element.

Just in case, here's a trace log of recording the first loop:
101 -3: Function Record down
101 -3: EventManager: Add event Record(Record) 0
101 -3: Loop: Set mode play
101 -3: E: Record(Record) 0
101 0: Loop: Set mode record
101 0: Layer: Starting record fade in
101 322173: Function Record down
ERROR: 101 322173: Sync: Scheduling RecordStop with number of frames
101 322173: Loop: prepareLoop: loop frames 322176 remaining 3
101 322173: Layer: pending frames 3
101 322173: Sync: Scheduled RecordStop at 322176
101 322173: EventManager: Add event RecordStop(Record) 322176
101 322173: E: RecordStop(Record) 322176
101 322176: Layer: Starting play fade in at 3
MidiRealizer: tempo 3575 msecsPerPulse 6991
Transport: Master track connected, sending start
Transport: Should be checking ManualStart
Transport: Starting unitPlayHead 0 unitLength 80544
MidiRealizer: tempo 3575 msecsPerPulse 6991
101 322176: Loop: shift: playing 0, new record layer 1
101 0: Loop: Set mode play
101 0: Layer: Applying fade out before frame 322176
MidiQueue internal: Start
Transport: Initial MIDI clock lag 128

Please let me know if I can provide any additional info.

jeff

Thanks for the report. It's possible that Bars Per Loop is influencing this, or being ignored. I normally have BPL at 1 and record relatively short master loops. If your first loop is long, say 4 bars of 120, it may be trying to fit that into one bar and wrapping it for the min/max tempo.