Moog Music Forum

Hi Everybody,

just recieved my Taurus 3 today, I just started playing, and noticed that one of the VCO's was wayyy off, (G is G, G# is G#, A is A, Bb is Bb, B is B, BUT: F is G, E is F#, D is E, C# is F, and the Lowest C is approx a D)

Uploaded the firmware v1.12,uploaded the Factory Presets, made the tuning, and the problem was solved! good...well....
I shut the Taurus off, turned it on, and there was the same problem, made the tuning again, problem solved, turned it off, again...the same problem.

I hope I dont have to tune this beast every time I turn it on!

here's the YOUTUBE Link, please take a look: http://www.youtube.com/watch?v=EWpQbr9Lve8

please, Amos, can you help me with this problem?

Did you let them warm up for half an hour or so before tuning?

yes, at least for 30 Minutes. about 50 to 60 mins.

MORE INSIGHT:

the problem is even badder than I thought, I dont have to turn off the Taurus to get out of tune , even if I change the Preset right after tuning (i.e. from A1 to A3), or use the Control Wheel right after tuning (i.e. Cutoff) the tuning is immediately off.

this occurs only on the Keys C to F# in the lower octave setting, and only on OSC A (MIX to 0). means: all the presets with 2 OSC get a harsh and unmusical dissonance on the Keys C to F#, above that range, everything works fine.

might it be a defective EEPROM, or sort of write protection?

this drives me crazy and makes my Taurus 3 at the moment completely unusable.

EDIT: some more informations:

I hooked the TAURUS on my Voyager via MIDI, still the same misstuning. But the interesting thing is, using the Pitchbender -2 semitones resulted in an unexpected behavior, it lowers the pitch, and then it returns on the wrong note: check this short clip: http://www.youtube.com/watch?v=j9OX-v7ImdM

Hello,

Very sorry for this bug! We discovered it on Friday and I fixed it on Monday. Very busy here this week, trying to meet some end-of-the month shipping goals (which we exceeded admirably, btw), so I had not had time to release an update yet.

Here you go, this should fix that annoying tuning bug. It was very simple, calibration data was being saved correctly but there was a small error on reading the calibration data back out of the EEPROM. Not a hardware problem at all, but one mistaken line of code. My apologies. Here is version 1.13. This version will appear on our main website shortly.

Taurus 3 v1.13 files for Macintosh
Taurus 3 v1.13 files for Windows

Kind regards,

Amos

Hi Amos!

the Link doesn't work, but anyway, I've got the Firmware by my local dealer, and it works!!! YES!

thanks a lot, you guys rule!

aarghhh...

I think I'm going crazy...

turned the Taurus on this morning, and STILL the same annoying Problem, even the Calibration Procedure did not cure the tuning problem.
yesterday it worked flawlessly.... I have allready updated to V1.13, but that wasn't the cure.

yay,

got my EEPROM replaced today, now it works!!!! hooray!!!