Aeros 2.3.1 : Quantize to Measure Gone

My Aeros just updated to 2.3.1. When I create a New Song, “Quantize to Measure” is no longer an option. “Sync Tracks” is also missing. There is no “Backing Track” menu item either. I see only the following:
Song Name
Time Signature
Count In
Number of Tracks

How do I find the other items?

1 Like

I encountered the same issue in the update. I can’t quantize my loops with my Beatbuddy. Is this going to be fixed soon?

Quantize measure is on by default. We removed the feature to avoid confusion while we contiue working on freeform mode. Once that’s added you see these options reappear.

This shouldn’t impact quantization with BeatBuddy as it’ll play just like it used to.

Sync tracks feature isn’t available yet. This feature will force all tracks to be multiples of each other (so if you record the first track 3 measures long, second track needs to be 1, 3, 6, etc measures long) – without this feature, you everything will still stay synced if you just record the tracks to be multiples of each other

Backing track is also under development hence the removal of the menu option. We’re already testing 2.4.1 internally so stay tuned updates are coming soon!

Okay, well, let me explain what is happening since the update.

I am using 2x2 with a one bar count in.

When I record a loop of 4 bars, and press the BB to transition, everything is the same as before the update.

When I press to transition back is where I am seeing a difference. I am not being taken to the beginning of the first loop. If I guess, I would say I’m about 1 bar to 1 beat off (I’ll have to study it more to be sure), but, it is not lined up with BB anymore.

Then, if I stop the BB with a double press and then start it again, everything lines back up again.

I agree that it probably Quantized to the beat, but it seems to be missing a beat or two in the transitions.

It stood out pretty strongly to me because I was working on a song just before the update that, after the update, I can’t perform because the transitions are not “right”.

If you haven’t heard of this issue from anyone else, I’ll double check it tonight to make sure it isn’t something I’m doing wrong.

I was able to try it again and it worked perfectly. So, unless someone else has this issue, you can close this issue for me.

Hmmm, yeah we haven’t had any reported issues along these lines. If you catch something again, try to pull out the phone a get a quick video, that can help the devs big time in catching what’s going on. I’ll leave this for the devs to look at just incase it’s an intermittent issue that they can catch.