DataLooper has to independently calculate tempo during new session mode. In most circumstances, the calculation agrees with Abletons calculation, but every once in a while, seemingly at bpms below 80 or above 130, Ableton decides the tempo is double or half of DataLooper. When this occurs, the pitch will be off by an octave. If you see this occur again, can you note the tempo calculated on Live and the tempo noted in the Looper device? I will try to reproduce and see if I can further match Abletons algorithm.