Estimated song lengths in AbleSet are suddenly all over the map. I can’t seem to figure out how it’s determining them, but they are definitely not correct. Unfortunately, I recently made two changes at the same time, so I’m trying to figure out which was the cause. One was updating to the 3.1.2 (and since then 3.1.3, which hasn’t resolved it). The other was changing the method by which I set the tempo for each song in my project.
I’ve always used Will Doggett’s (FS2S) method of creating individual songs with a tempo track and an empty audio clip with warp settings set to “Lead”. But that is limiting if I want to be able to change tempo on the fly. Additionally, as AbleSet has gotten better, over time I’ve begun to build our songs directly inside of our master file, and the tempo track has sort of lost its main purpose of being able to move songs from one project to another while retaining tempo settings.
All that being said, I decided to remove the tempo track and create a MIDI track with OSC clips at the start of each song. It’s easier and quicker to make changes by re-naming midi clips than by having to go into the clip settings, adjust the tempo, then toggle the warp lead on and off. Plus, it doesn’t lock me into a tempo, which means I can use a tap tempo button or type in a tempo on the Canvas if we want to make changes on the fly.
My guess would have been that it’s this change that is throwing off AbleSet’s song length times. But I tried muting the MIDI/OSC clips track, and re-adding the tempo track as I had it before, and that didn’t seem to resolve the issue…
Please fill out these values to make it easier to troubleshoot:
- OS and Version: MacOS Sequoia 15.6.1
- Version of AbleSet: 3.1.3
- Version of Ableton Live: 12.4.2
