V3.1.2 Issue, marking set for save when nothing changed

Support
1

Mac OS 26.5.2

Ableset 3.1.2

Ableton Live 12.4.3

Using Multi-file projects

This only started happening with 3.1.2

Every time I load a song (set) into Ableton, if Ablest is running, as soon as I load another song it does a save of the previous song, even if nothing has changed.,

Something in Ablest is marking the song as needing to be saved when in fact nothing has changed.

So just to be clear. If Ablest is running

  1. Load a song (either using a setlist in ablest or manually in Ableton
  2. Do nothing
  3. Load another song (either with Ablest or Ableton)
  4. Save box flashes up and previous song is automatically saved.

I do not want this to happen as it is updating song when it should not be doing (IE changes modified dated etc)

It didnt happen in previous version although I have reported it before a long time ago in a much earlier version and it was fixed but seems to have come back :frowning:

Pls can you take a look to stop this happening?

Thanks

Mark

2

Hey @GuitarMark,

This is likely the Save Changes Before Loading Project option in the Multi-File Project settings.

You can find it here: click the AbleSet icon in your menu bar/tray → gear icon → Multi-File Project → Save Changes Before Loading Project.

By default this is enabled, so whenever you jump to another song, AbleSet saves the currently open project file first (even if nothing was actually changed, Ableton can still flag the project as “dirty” internally). This is meant to prevent accidental data loss, but if you’re sure you don’t want files touched/modified on every jump, you can disable it here to speed up switching and stop the automatic saves.

It’s possible this setting existed in the version you were on before but you didn’t run into it (e.g. if you weren’t jumping between songs as often), rather than something that broke in 3.1.2 — but if you disable it and still see saves happening, let us know and we’ll dig further.