We are currently working on building the team to span across all of our products, so everything will be getting a little better quicker. The Lock Track function will not be in this next live release. The next two big updates will be MIDI implementation and then Lock Tracks.
As to the current beta, this one has some bugs we really want to kink out before we can release it. That being said, we are so damn close guys. We can taste it almost, the sweet taste of crossing this finish line. We get the antsiness, we’re antsy too. We’ve already cut off the food and water to the dev team and turned the heater on. The whips are delayed in Amazon as backorders, more info on that soon. We are doing everything in our power to test this firmware, improve it, and make sure it’s ready for you all and for every other user.
We will have just one last beta for you guys within a week, and as long as nothing serious happens to anyone while beta testing after 2 days, we will post live.
This auto-naming bug has been seen and will hopefully be fixed by the next beta posting within a week.
Following up from my previous comment about tracks being deleted/not saved properly in the Aeros, I have the most recent 2.17 firmware installed and I am still having issues with tracks/parts being deleted after saving them in the Aeros.
Really hoping this isn’t a malfunction specific to my unit, and that this could be solved in the next firmware update.
I understand Beat Buddy is the genesis of Aeros and most are happy with midi, set loop lengths, & quantizing, but some of us freeform players on the long looping journey saw the Aeros glowing on the mountain top as the hopeful culmination of our compositional and performance quest. The same action triggered in different ways in different modes has clouds obscuring the glow for some, especially as after a lifetime of tapping on the beat, successfully learning to transfer that to a split second before the beat just isn’t reliably realistic. Can’t imagine you haven’t considered this, but in 2x2 is it possible to program the Next Part button with a double tap command to open the mixer, thus freeing up a single tap to trigger changing song parts on press instead of release? Thanks for your consideration!
Since I bought it (last week) I think I played the game of suggesting new features etc, but I came back to reality.
Even the basic feature is malfunctioning. The crossfade feature does not work. I opened a bug describing it.
I just changed the firmware version in the original post from 2.17.1 to 2.17.5. We hope this is the final beta version – please test this and if there are no major issues we will publish it over wifi.
@LaurentB please post if you see the same problem with this firmware version. If anyone else can replicate this issue and let us know how you did it, that would be very helpful for us to figure out how to fix it.
Looks like the team has been busy. A lot of subtle issues looked to be cleaned up. I suspect this makes the looper more polished and intuitive.
As a very minor question, does the Aeros require that all the names are unique for all features to operate properly?
If so, then this would be incompatible with the SD card (and there’s no simple way to enforce this as the logic is inconsistent). On the other hand, if the unique name is just for the convenience of the user, it’s not a problem.
@DavidPackouz Update installed, but the changelog displayed on the device is not consistent with what you just posted. It says Version 2.17.3 not 5…
Here is the file hash:
@LaurentB my apologies, I should have noted this in the original post. We didn’t change the changelog for this version because we plan to clean that up for the wifi version.
If you look under the updates section you’ll see that the version number is 2.17.5
@Quad the name of the song needs to be unique. If you try to move a song from the internal memory to the SD card or vice versa and there is a song with an identical name, you will see a warning message saying that you need to change the name first.
@DavidPackouz If that’s the case, the uniqueness guarantee is flawed. Here’s a simple example of a sequence over time that breaks this:
Internal: CreateSong 1
SD card: Create Song 2
Eject SD card
Internal: Create Song 2 (or rename song 1)
Insert SD card: Boom
One workaround is to scan for this at any time an SD card is inserted and reject it … but you’d need a way to let the user fix this which leads to other issues.
You will be forever trying to fix the next issue that comes up. You simple fix has other issues and fixes to that have other issues.
A simple solution is to not use the song name as a unique ID. Instead create a large random number that is extremely unlikely to be a duplicate (UUID) and use that. If an SD card is inserted without uuid’s, you would simply generate them. Seems scary, but it’s pretty simple and a very common, reliable pattern.
@Quad you can have a song with the same name on the SD card and in the internal memory. It’s only an issue if you try to move the song over, then it will prompt you to change the name.
Are you on the version 2.17.6? Did you use an SD card when this happened? If so the Aeros will keep a crash log file, you can zip (compress) it and PM it to me
