I had to power the device down and up again 6 times, with Nexus running on my computer, before the firmware update worked. The first 5 times, the update started, took a few shaky steps into the RP’s flash memory, then shut down. The sixth time, it went all the way. And to my great relief, the backup I’d saved of the 50 presets in my Huntersounds v17 patch set loaded on the first try.
So I’m up and running again with the RP360XP, ready to test the patch set in the audible world. I still don’t know if the problems I’ve seen with the stability of patches in the RP360’s memory have been solved by the latest firmware update, but I’ll know soon. Stay tuned.
And Digitech, if you’re reading this, would you please fix this s—? I own one of almost every RP you ever made, starting with the RP200. I’ve been programming the RPs for 10 years. And if I didn’t have that history, I would have thrown this thing into the trash on Day One, because so far it’s the buggiest piece of gear I’ve ever bought from anyone. And you must know it, because it’s pretty amazing to see the first firmware rev less than two weeks after a device becomes available for sale. It makes me wonder whether that rev was underway even before the device went public, i.e. whether you knew the thing had some serious issues when it was released. Did you?