Sorry to hear that, were you having issues while clicking the pop-up to update firmware via WiFi?
I had a couple of issues (but again, note that this was firmware 3.0.0, which came installed on the hardware):
I attempted to connect to an “xfinitywifi” network - I doubted this would work, as those networks require a web browser for authentication purposes and so many devices aren’t able to use that network. I then connected to my phone’s hotspot, which uses WPA2 authentication, and the WIFI manager seemed to crash (I got a message saying server not available, and I couldn’t enable WIFI on the device to get a list of hotspots). This happened twice; I was able to reboot the device, connect to my hotspot, and put in a WPA2 password. This could have been due to a number of network exceptions that weren’t handled correctly - no way to be sure.
After connecting, I downloaded the update once, and upon rebooting I got an error screen:
"Error code 0.
- Please insert a valid update file using the SD card
- Unplug the Aeros power supply
- Reconnect the Aeros power supply
Wasn’t sure if I’d bricked it, so rebooted it to verify. It booted the 3.0.0 firmware, and running the update again worked correctly. Not sure what happened there.
The Aeros currently only responds to whole number integers, we do not currently have a plan for introducing smaller values.
Thanks for your response. While I can understand why this is the case, I think that an integer tempo representation might cause MIDI sync issues with MIDI devices that have higher tempo precision (like the Line 6 Helix, unless its tempo is set to a whole number) or older devices that report a tempo as an integer but their MIDI clock tempo reported interval is slower or faster by a a fraction. (It seems that my Alesis Nitro falls into the latter category; when I do MIDI sync with the Alesis as the master, the Alesis and the Aeros are off by 1 bpm; the Alesis is 1bpm faster.) The Aeros seems to try to round to the nearest integer based on the average tempo for some set interval of MTC information.
With the Helix, I can work around this if I use an integer tempo. Unfortunately, with the Alesis, I don’t think there’s anything that I can do here to make them sync.
So just as a heads up, if anyone else runs into syncing issues, it may be an integer precision issue. Another device used as a MIDI master may have a non-integer tempo value (even if the device reports it as such) and the Aeros may not be able to sync perfectly with that external device’s timekeeping. I know you guys have a roadmap of features that users are clamoring for (loudly), but I’d like to humbly add this one to the list; I think that higher tempo precision might be a core concern that would allow for better MIDI syncing between the Aeros and other devices.
If there’s something that I’m missing, let me know. I’m happy to take any suggestions if I’m missing something; I’ve got a couple of MIDI cables and if necessary, I can log and analyze the MIDI messages coming from the Alesis to verify my hypothesis about the skewed tempo.
Hope this helps.