Man… how excited I was when I saw a new firmware update 1-2 weeks ago! But alas, none of the above problems have been fixed.
The “Save On Astrolab” function is much appreciated!
The firmware update process itself was a nightmare… The firmware update crashed during the transfer. It took me 2 days to have the update work. Why? I have no idea!
I have 3 computers at my reach (luckily for me!)
- M1 Macbook Air
- i7 iMac
- M2 Mac Studio
The firmware update never worked on my M1 Macbook air, so I figured I’d try my intel Mac. Both computers couldn’t get the update going. I tried to revert to the previous firmware with no luck (the Astrolab was stuck in safe mode and was unusable). After a day of trying on both computers, with different USB C cables, I gave up and was ready to count the synth as “dead”… for real. On the second day, I figured I’d roll the dices and try my M2 Mac Studio. I grabbed the synth from my garage (where I jam) and went upstairs home to my mixing room. It worked flawlessly as soon as I connected it! Why? I have no clue! All my Arturia software were all the same and up to date on all computers, and I used a cable that didn’t previously work on my other two computers…
So I figure: it seems that my M2 Mac Studio is reliable to work with my Astrolab from now on? FALSE!
On my M2 Mac Studio I can edit sounds on Analog Lab with the synth connected, but I’m not able to drag my presets onto my Astrolab Setlists. The USB connects with the keyboard telling me that it’s connected, and I can see my Astrolab Patches, but I can’t ad any new patches onto it.
My workaround is super sketchy. I use Dropbox to EXPORT my M2 Mac Studio sounds to a shared folder. I then boot up my M1 Macbook air, import the presets from my dropbox and transfer the patches to my Astrolab. It’s super sketchy, because I have a computer with an audio interface to monitor my sounds, and another computer with no audio interface just to be able to save the sounds on the Astrolab.
Long story short, the M1 Macbook air couldn’t firmware update the Astrolab, but it’s now my only computer that can send patches to it? My M2 Mac Studio was my only computer that could firmware update the synth, but it can’t send any new patches to the Astrolab.
Find the logic?
At this point, I will finish the year with the Astrolab, as I have a sunken cost fallacy going on with it. I have put too much work on my live set, and I have too few time before my next live gigs to work a new setlist on a new keyboard. Next year, I will be changing my synth, because it is too unreliable. I will go back to a proper work station.
Also, did I mention that I had patches not load twice on me during two different festival gigs? Why? Because I need to wait sometimes as much as 3 seconds for a patch to load before playing it. Otherwise, it will either audibly glitch HARD or not load at all! 3 seconds can be an eternity! Like 2 measures of music depending on the tempo. It’s a ton of empty gaps, especially when you want to transition from a previous section to a new one with a punch!
I love the Arturia sounds, and while I’m at it, it’s a shame that the V3 sounds can’t be preserved onto the newer synths. I’ve lost so many lovely sounds that I never quite re-created as well on the newer versions. That being said, the software has a long history of crashing on me since 2014, when I’ve bought my first V Collection. It crashed often in my Ableton Sections, and now the glitches are plaguing my Astrolab. I should have been more cautious with the Astrolab Purchase, but the Arturia sound quality was too important to me to not take a chance on it.