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.
Hey there, yes we are working diligently to make sure saving is 100% functional, the R&D team are aware of the issues and are focused on solving them.
Thanks for update, glad to hear itâs on the docket. I know you guys are working hard on these changes
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!
You forgot the leg irons! All the devs should be leg ironed to their chairs, with only a bottle of gatorade, some chips, and a bedpan!
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 feel pretty sad??? 
Hi Everybody,
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.
@DavidPackouz Downloading and installing. Wonât be able to perform tests before tomorrow morning (CET).
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:
$ sha512sum aeros-2.17.5.bin
a15a9c61c0addd29d43e4f6195279d19435cd8aa0e7d019e316af94b5006ebf7353b11d4613aae654b60361851b475299981dd8d71b1d7fa91d236fdeeb6b6d8 aeros-2.17.5.bin
Yet, the OS version reported in the Updates menu says aeros-2.17.5.
@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.
Cool. If uniqueness is only needed per âfile systemâ, we are good!
I replaced the 2.17.5 file in the original post with version 2.17.6 which @LaurentB has confirmed solved the audio pop issue in freeform.
If no other serious issues are discovered, we expect to have a version for wifi release by tomorrow.
Today my looper crashed. There was a sharp noise continuously. I turned it off, restarted. It works but it does not reassure me too much. 
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
Hello @Thovy64,
I think we are all interested in knowing which firmware version you use.
@BrennanSingularSound Are there different hardware versions of the Aeros ? If I understood well @Thovy64, he has been one of the early adopters and owns his device for almost one year whereas I just it got it 10 days agoâŚ
