Concernd about upgrading 2.0 to 2.5...

Chest Rockwell · Post by **Chest Rockwell** » Tue Mar 22, 2005 2:42 pm

Lookey here y'all need some advice! I'm still running version 2.0 and want to upgrade to 2.5 but I've heard some bad things on this forum like patches not playing back, going out of tune and some guy who killed his Moog! Is upgrading risky or do you just need to know what you're doing?
One more thing regarding oscillator tuning, on my Voyager osc2 needs to be at -5 and osc3 at -3 to be in tune with osc1. Should they be set to 0 or is it because they're analog that they're slightly out? Thanks for any advice people...

MC · Post by MC » Tue Mar 22, 2005 3:17 pm

You need to "initialize" the patches in memory and make adjustments for tuning when you upgrade to v2.1 or higher. Most folks missed that when upgrading to v2.5. The details are in the pdf document for OS v2.1.

My Voyager VCOs are also slightly out - that's analog, that's normal.

ticker · Post by **ticker** » Tue Mar 22, 2005 5:42 pm

My AE had 2.1 on it when I got it. I went to 2.5 not long ago with no problems. My VCOs are also very slightly off.

suthnear · Post by **suthnear** » Wed Mar 23, 2005 4:36 am

No problems with going to 2.5 here either. And my oscs are also ever so slightly out of tune

Demokid · Post by **Demokid** » Wed Mar 23, 2005 5:17 am

I upgraded my AE from 2.3 to 2.5 and it worked like a charm. I don’t know if my VCO’s are slightly off… compared to my Model D they are not.

Qwave · Post by **Qwave** » Wed Mar 23, 2005 6:24 am

My ocillators are also a little detuned when set to zero detune. This is very normal.
But on my Minimoog I scalled the oscillators right to make then close to zero detune if the big detune knob is set to zero (as close as possible for a knob like this).
If we would get a tuning and trimming manaul, we (tech freaks) could make the zero detune value to be very close to zero detune. But I have no hope of seeing such a tuning and trimming manual that soon