I have been making loops using Ableton live to use for a solo guitar set. After an initially great start just using the looper to make loops, I have decided to go down the computer audio recording route to make the loops, so I can scrutinise takes, add EQ, add compression and also get the timing perfect.

1. I initialise a loop folder by recording 8 bars with the tempo set at 127bpm (for instance) – this makes a LOOP01 folder with TRACK.WAV files all the same length (rather than doing this on the computer its far easier)

2. Then, I leave the 95000, I record my guitar loops into Ableton Live, add compression / effects / normalise etc.

3. Then I export them as mono WAV files at 127bpm, rename them TRACK1.WAV, TRACK2.WAV, connect USB and overwrite the identically named tracks in the LOOP01 folder. (again, for example as this is all hypothetical)

You would expect everything to loop perfectly…. 127bpm folder with 127bpm length samples.

OK – when I examine the LOOP01 folder .TXT file on my Macbook, it says LOOP01 project tempo is set to 126.0069 BPM. This value was created by the 95000 and all the WAVs are set to that length.

I nervously replace the WAV’s in the project with my new ones and rather weirdly, everything works perfectly. The timing is exactly 127bpm, yet the text file is numerically out.

So is this a bug? Is the Tempo of the LOOP folder (that the 95000 generated) recording a value error in the text file?

If I had corrected the TXT error would that create a timing error?

Thanks in advance