Visual Metronome issue

Support
1

Dear Ableset team,

I just came across an issue regarding the visual metronome - it does not seem to pick up time signature changes in the middle of the song correctly. Example: song starts in 4/4, then there is just one bar of 2/4 right in the middle, then back to 4/4. Ableton Session has the time signature change correctly in the timeline, but the visual metronome just counts 4/4 through, so it is shifted by 2/4 after the one bar of 2/4.

Hope you get what I mean ;-).

Anybody else experienced this? Tipps how to solve this?

Best,

Sebastian

2

Hey @Sebastian,

From what you describe, my hunch is that since beta 22, the visual metronome no longer relies exclusively on the AbleSet Controller M4L device or a Measures track. Instead, it can also parse bar / time-signature information directly from the Ableton Live project file.

Because of that, there’s one important caveat to check first:

Are you making that 2/4 bar change “on the fly”?
If the time-signature change is added or edited while the set is already open/running, AbleSet may not reflect it until the Live session is saved. In those cases, the visual metronome can keep counting in 4/4 and end up shifted exactly like you’re describing.

Make sure the time-signature change is in place on the Ableton timeline, and then save the Live set.

If after that you still see the issue, please send us a Log Package so we can inspect it properly:

  • AbleSet tray icon → gear icon → Create Log Package

  • Please include the project files (just the .als file(s), no audio needed)

I‘m looking forward to your reply!

1 Like
3

Indeed, you were right - I made the time signature change just yesterday, and it just did not translate to Ableton before closing and reopening the session again. Works perfectly now! :-).

Maybe a “good to know” addition to the description of the feature in the Docs section of the homepage, as it is not self-explanatory….

Thanks a lot!

3 Likes
4

Hey @Sebastian,

Glad to hear that solved it! :raising_hands:

While it’s not documented yet in the main docs (since AbleSet 3 hasn’t officially been released), @leolabs did mention this behavior here when beta 22 was released.

Upon official release, this will of course be properly documented in the docs section.

Thanks you for taking the time to report back!

1 Like