Hi all,
Most folks who have tried the new v2.0 firmware update for Taurus III are now enjoying the new features.
A small number of customers (four, so far) were unable to complete the update successfully.
In order to avoid any further inconvenience for our customers, Moog Music is temporarily removing the v2.0 firmware download from our website while we determine what went wrong for these users.
I anticipate this update will be available for download again next week or so.
Thanks,
Amos Gaynes
Moog Music Inc.
Taurus III firmware v2.0 temporarily unavailable
Re: Taurus III firmware v2.0 temporarily unavailable
This is great news, Amos! Thanks for all your hard work!
Minitaur, CP-251, EHX #1 Echo, EHX Space Drums/Crash Pads, QSC GX-3, Pyramid stereo power amp, Miracle Pianos, Walking Stick ribbon controller, Synthutron.com, 1983 Hammond organ, dot com modular.
Re: Taurus III firmware v2.0 temporarily unavailable
fixed! update soon. Thanks for your patience, all.
Re: Taurus III firmware v2.0 temporarily unavailable
Any additional changes... Will those that successfully updated to v2.0 need to load this latest FW update?
Thanks Amos
Thanks Amos
Rickenbacker 60's & early 70's 4001 basses ♦ Fender Pre-CBS J & P Basses ♦ Zon Sonus 8-string Bass ♦ Moog Taurus III Bass Pedals ♦ Hiwatt (Hylight) & Reeves Amplification
Re: Taurus III firmware v2.0 temporarily unavailable
I'd recommend it. The fix is pretty low-level, in that it initializes some stuff on start-up that was left uninitialized in the previous firmware.
Without going into eye-watering detail about it, I personally feel better about the new version and it's what I'd use.
The only new features are safety features, which make it easier to do a firmware update while a unit is in the locked-up state experienced by the four users who reported trouble with v2.0.
Without going into eye-watering detail about it, I personally feel better about the new version and it's what I'd use.
The only new features are safety features, which make it easier to do a firmware update while a unit is in the locked-up state experienced by the four users who reported trouble with v2.0.
-
- Posts: 600
- Joined: Fri Jun 06, 2008 8:43 am
Re: Taurus III firmware v2.0 temporarily unavailable
Is this update the one currently on the downloads page or do we need to wait?
http://soundcloud.com/luke-antony
Re: Taurus III firmware v2.0 temporarily unavailable
It's the one that's currently up. Version number is 2.0.2.Mr Arkadin wrote:Is this update the one currently on the downloads page or do we need to wait?
Cheers,
Amos
Last edited by Amos on Sat Jul 07, 2012 12:12 pm, edited 1 time in total.
Re: Taurus III firmware v2.0 temporarily unavailable
Has the firmware upgrade problem been rectified yet?
-
- Posts: 600
- Joined: Fri Jun 06, 2008 8:43 am
Re: Taurus III firmware v2.0 temporarily unavailable
All is now fixed, make sure you have 2.0.2 and you're fine.
http://soundcloud.com/luke-antony
Re: Taurus III firmware v2.0 temporarily unavailable
Cheers mate, will give it a try shortly.
Will I lose my saved settings/presets?
Will I lose my saved settings/presets?
-
- Posts: 600
- Joined: Fri Jun 06, 2008 8:43 am
Re: Taurus III firmware v2.0 temporarily unavailable
At the moment I have no custom patches, but in the past they were fine unless you loaded the 1.13 patches file. I imagine this is the same. Doesn't hurt to do a back-up though in any case before you flash.
http://soundcloud.com/luke-antony
Re: Taurus III firmware v2.0 temporarily unavailable
i definitely recommend a backup first. on general principle and because I can't recall at the moment whether it does an automatic reset or not.
There are a number of new global parameters, so if anything doesn't seem quite right on first boot to the new OS I'd definitely suggest a factory restore at that point, to make sure everything is initialized correctly. at that point you'd need to restore your own presets from a previously-saved sysex file.
There are a number of new global parameters, so if anything doesn't seem quite right on first boot to the new OS I'd definitely suggest a factory restore at that point, to make sure everything is initialized correctly. at that point you'd need to restore your own presets from a previously-saved sysex file.