Hi, I received a new Astrolab and via Analog Pro I updated the Firmware as it came with an old version. During part 12/25 it repeatedly looped download/install until it came up with an error about a network problem so try again later. I didn’t see a way to restart it, so I chose the update from file option after downloading the file. This now progressed but had 30 parts, and it finished successfully to V1.4.4. BUT, now all the MiniFreak V presets have no sound when played on Astrolab, but using keyboard on Analog Lab, the Macbook plays the sound. I don’t know if it’s a normal problem or whether I should try re-loading the firmware? It seemed odd that the online update seemed to have 25 parts, but the file had 30 parts.
Hi @PalmChange. Welcome to the community.
Which version is your Analog Lab? Be sure it’s the latest. Version 5.11.1.6049.
Also please note this info from the release notes for Analog Lab Pro and Astro lab:
Important:
- Please ensure to first update Analog Lab to version 5.11.1.6049 before upgrading your AstroLab
Yes, it is the latest version, according to the Arturia Software Centre, as everything was installed fresh yesterday. 5.11.1.6049 is showing as the version installed. Also, I took advantage of the upgrade discount and installed the Collection V.
In that case i suggest you contact Arturia support through your account.
I don’t have Astrolab.
For your information: Support concluded that the firmware was corrupted internally. Re-loading 1.4.4 did not fix it. Had to revert to previous Analog Lab and load firmware 1.3.5. It was now OK. Updated Analog Lab to latest version and then firmware 1.4.4 was now OK. All firmware done via Update from File.
Glad it’s solved.
Thanks for letting us know.
After updating your Astrolab to v1.4.4 using the file method, the MiniFreak V presets may be silent due to a corrupted install or preset mapping issue from the failed online update; try doing a factory reset on the Astrolab, then reinstall the firmware from file, and re-sync your presets via Analog Lab—if that doesn’t fix it, contact Arturia support as it may be a known firmware glitch.
Already fixed. See my earlier post from yesterday.