BB2 - request option to choose "fill" behavior when no fill is present in a part

I have an issue with BB2 fw:1.0.1, where if the fill button is pressed during playback and there are no fills defined in that part (or even in the whole song), the BB2 will still restart at the beginning of the part.
The behavior of the BB1 fw:4.1.6 and BB2 fw:1.0.0 is that nothing happens and the song just continues on as if the button was never pressed. I was told that this behavior is by design. I still believe that this behavior is a bug introduced with fw:1.0.1 and not by design, and I don’t see any reason why in any song where this behavior would be desirable (when no fill is present).

However, if this truly is by design, I would like to request a feature to include an option so a user can choose which behavior they want:
A) restart at the measure even if no fill is present (behavior of BB2v1.0.1) or
B) ignore the button press when no fill is present (behavior of BB1 and BB2v1.0.0).
Obviously, if there is a fill present, it should play the fill and restart the part, that is the basic design.

The use case to support option “B” and why I think option “A” is actually a bug, occurs when any part is a more than just a single repeated measure, where an accidental press of the button will mess up the timing of the whole song and will quickly lead to a train wreck on stage. This will occur in any song, whether or not someone is using AutoPilot.

Unfortunately, I will again need to revert back to fw:1.0.0 and stay there until this new behavior is reverted/fixed or an option to choose the desired behavior is added. Thanks.

4 Likes

Thank you for posting your request! I’ve forwarded it to our development team for consideration.

1 Like

I see the following in the changelog for 1.0.1 release, which does indicate that this was an intended design change and not a newly introduced bug:

“Allowed extending song parts that don’t have any fills with a tap, triggering a fill in a part will now restart the part. The screen will say No Fill in this case.”

I have a couple of questions:
What is the specific use case to support making this change in behavior of the BB2?

Was this a user requested change request?

This is a significant change in behavior from both BB1 and the initial release of BB2, so there must have been a compelling reason to make and include that change request in the release.

Adding the option as I suggested would support both use cases.

The request has been sent to the team. As a workaround, you could add your one-press song onto the Outro section instead of part 1. Alternatively, you can add a fill to the song and adjust it so it only plays for one beat.