There is a bug that repeat the same bar from a part of song several times, even existing more bars on this song. When bug it, i can’t to fill this part and i need advance to next part to fix this bug. In my last gig, occured it twice.
Hey there, please write to email@example.com at your earliest convenience showing them what you mean and any relevant files
Thanks for reporting!
New BeatBuddy firmware 4.1.6 and Changelog has been posted in the original post
Dear David, why not put the link in this announcement, so we don’t have to search, just a thought
Good idea edited!
If you’re using an iPhone, you can click on the title of this thread and it will take you to the top of this topic. It may work on computer browsers, tablets and Android phones as well.
just tested an it works on the computer thanks
A post was split to a new topic: What’s available in 4.1.6?
That should be the case for every new feature which modifies the existing behavior of the device.
I believe I found either a bug or what I consider to be a “feature” that was removed. Example: In version 4.1.3, if Aeros (master) has 3 song parts and the Beatbuddy (slave) song selection only has 2 parts, the Beatbuddy will always transition back to part 1 when I moved to part 3 on the Aeros. With this version (4.1.6) and the previous version (4.1.4), this does not occur. With these versions, when Aeros transitions from part 2 to part 3, the Beatbuddy remains in part 2 instead of resorting back to part 1.
Is the above-described change intentional or a bug? If it is intentional, this does not work for me, as I have many arrangements that depend of this to work as it does in 4.1.3. In a future firmware release, please provide a means to enable the behavior has it is in 4.1.3. If this is bug, great! I look forward to it being addressed soon! FYI…I will not be able to move beyond 4.1.3 if this is not fixed.
All of the other aspects of 4.1.6 appear to be working great for me so far.
Best Beat Buddy update ever (so far)!.. I really like the new abilities I have from my older firmware.
BTW, Which ones you found more useful?
Better configurations of the external foot switch probably summarizes it.
I personally LOVE the ability to cycle through “Parts” using the external foot switch while playing, and the ability to cycle through songs when stopped (also using the external foot switch)…
I feel in previous versions I was limited in how I could really USE the external foot switch, cause I really don’t like to rely on double-taps or triple-taps, or holds and releases… I personally prefer simple functionality for any “button”; so being able to configure my setup for 1 press only (3 buttons - 1 press each while live) fits much more into how I operate; simpler is better.
2 posts were split to a new topic: BeatBuddy 188.8.131.52 firmware update did not work
We understand this is problematic for you but the logic seems smoother for a specific Aeros part to open a specific BeatBuddy part, you can easily remedy this by making enough parts in your BB song to match the amount of parts in your Aeros song.
Otherwise, the behavior is not always doing what the user may expect, let me know below!
Are there a substantial amount of users that need the BB to work the other way?
- BeatBuddy should always transition to the next part no matter which CC:113 value 1-6 command it receives
- BeatBuddy should only transition to a part if it exists and the CC:113 value matches the part value, eg CC:113 value 1 always goes to part 1, CC:113 value 2 always goes to part 2, etc
Thanks for the feedback!
Yes I agree, there should be a 1 to 1 correspond between the Aeros parts and Beat Buddy parts.
Since the behavior changed after version 4.1.3 and this new behavior did not appear to be described anywhere. I thought it may have been unintended.
I will need to make changes to some of my Beatbuddy song parts to accommodate this, but the change makes sense going forward.
Thank you for the follow-up and explanation.
This happened to us as well: We didn’t do anything to fix it but noticed we had left that tab open and clicked it again in the forlorn hope that it would work, and it did! Took a few minutes to respond. BTW, this issue also occured trying to download the firmware originally, but again when we went back after a couple of minutes it downloaded without a problem. Our guess is that this is OneDrive issue and not a Singular Sound issue. ROKKON \m/