Voyager Aftertouch fix?

Tips and techniques for Minimoog Analog Synthesizers
Post Reply
Marzzz
Posts: 111
Joined: Sun Jul 20, 2003 12:41 am
Location: Phoenix, AZ

Voyager Aftertouch fix?

Post by Marzzz » Mon Jan 23, 2006 10:54 am

Has anyone heard anything official about a hardware modification to fix the aftertouch response (making it smoother, less on/off) of the Voyager keyboard?

User avatar
MC
Posts: 2925
Joined: Tue Aug 12, 2003 2:20 pm
Location: Secluded Tranquil Tropical Country

Post by MC » Mon Jan 23, 2006 3:25 pm

I would sooooo want the fix. I don't care for the discrete on/off action of aftertouch - continuous smooth action would be so much better.

User avatar
till
Posts: 1425
Joined: Tue Nov 22, 2005 6:17 pm
Location: south-west Germany
Contact:

Post by till » Tue Jan 24, 2006 6:12 pm

no fix is known to me. Either made by Moog Music or third party. And I guess all Moog certified technicians that got schematics have to sign a paper not to share it. I never ever saw a snippid of the Voyager schematics. And reverse engeniering this isn't that easy.
keep on turning these Moog knobs

Prodigy * minimoog '79 * Voyager * MF102 * MF103 * MF104z * MP201 * Taurus 3 * Minitaur * Sub Phatty * MF105 * Minimoog 2017+ MUSE * One 16 (sold)

theglyph
Posts: 471
Joined: Tue Aug 31, 2004 4:58 pm
Location: Jungle of patch cables

Post by theglyph » Tue Jan 24, 2006 7:21 pm

I mentioned this in another post but again, the new digital board is smaller than the original leaving extra space inside the Voyager. The new board required 4 screws instead of six leaving extra space between the board and the power supply.

I wonder if they will design new hardware to fill this space such as a fix for the aftertouch?

thebedroom
Posts: 83
Joined: Sun Nov 28, 2004 7:20 pm

Post by thebedroom » Wed Jan 25, 2006 10:28 am

When my board was in the moog shop for a version 3 upgrade and tune up, I spoke to amos about the aftertouch. He said it is a known issue and they are working on a hardware fix for it. He has no idea when this will happen, but it is good to know moog is aware of the issue and wants to fix it. I am sure it will cost money which will most definitely cause a flare of anger among many owners, but I will pay for this fix gladly. It is just so frustrating to play a keybed with great aftertouch, like my dave smith PEK, but then have such sub-par performance on my voyager. I have actually started using the PEK as a master controller on the voyager occassionally when I really want good aftertouch response. This sucks.

Hopefully we will see the fix at MESSE, when they announce the new stuff??who knows.

User avatar
MC
Posts: 2925
Joined: Tue Aug 12, 2003 2:20 pm
Location: Secluded Tranquil Tropical Country

Post by MC » Wed Jan 25, 2006 7:23 pm

You wanna hear something interesting?

We all know that the aftertouch is discrete.

But if you view the MIDI data coming out of the Voyager, the aftertouch is continuous - not discrete.

I don't see a hardware problem...

LWG
Posts: 282
Joined: Tue May 25, 2004 1:27 am
Location: New Jersey

Re: Post subject

Post by LWG » Wed Jan 25, 2006 9:20 pm

MC wrote:I don't see a hardware problem...

Hello,

I'm also inclined to think its not hardware. The PEK's pre-production keyboard supposedly had the same issue (its possibly the same manufacturer) and it was said to have been fixed by "massaging the data".


Regards,


LWG

OysterRock
Posts: 800
Joined: Thu May 26, 2005 8:52 pm
Location: Portland, OR
Contact:

Post by OysterRock » Wed Jan 25, 2006 10:29 pm

MC wrote: I don't see a hardware problem...
That's what I said on the Squarewave group a month or two ago!
But here it is, straight form Moog:


OysterRock:
"I don't think adjusting the response of the aftertouch would be a hardware
issue no more than adjusting the velocity curve is. Its the software that
tells the Voyager what to do with the aftertouch data, it just a matter of
writing the software so it reads the data differently."
punkdISCO:
Yeah, this is what commensense would have us beleive, however.. We are now
on o/s version 3.1 and this is the only really major issue with the Voyager.
If it was fixable, it would have been fixed in version 1.1. The fact that it
is still with us tells us something about the difficulty in fixing it..

Besides, Moog have said its hardware when I asked them the question (see
below).

Im kinda used to it now and find it querky-creative. Sure, given the
choice, I would want it fixed but there is too much that is right about the
Voyager for me to loose sleep on this one..

See you,

Paul
London
www.punkdisco.co.uk
Moog's email to punkdisco:
Hey Paul -

It's actually a hardware thing - If we come up with a fix for it we will let
our customers know.

Best Regards,

Steve Dunnington

Product Development Specialist
Moog Music Inc.
554 C Riverside Dr.
Asheville, NC 28801 USA
Ph:828-251-0090
www.moogmusic.com
Timeless Electronic Musical Instruments

....I'm confused...

punkdisco
Posts: 99
Joined: Mon May 23, 2005 4:44 am
Location: London
Contact:

Post by punkdisco » Fri Jan 27, 2006 12:43 pm

..as mentioned above, yeah Moog did confirm to me that it was hardware. But just to add to this: The biggest bit of evidence that we have relating to this being a hardware issue is the fact that it still exists! Moog are a very conscientious company and to them, reputation is everything. If this was a software issue it would have been fixed in version 1.1, more likely it would have been fixed during beta testing. Every Voyager review I have read comments negatively on the aftertouch - no company wants this sort of press, least of all Moog..

Maybe one day..
Paul
London
www.punkdisco.co.uk : Getting Married? Need a [url=http://www.punkdisco.co.uk/Weddings.htm]reception band[/url]? New [url=http://www.punkdisco.co.uk/Music/DVDA.mp3]DVDA Track[/url]

Marzzz
Posts: 111
Joined: Sun Jul 20, 2003 12:41 am
Location: Phoenix, AZ

Post by Marzzz » Sat Jan 28, 2006 2:49 am

Hence my original question. Not knowing anything about synth design or EE, I am pretty sure if it were a software issue it would have been fixed awhile ago. Since it "appears" to be a hardware issue (and a fairly egregious one at that) my guess is that Moog are working on it. I get by with using the slew limiter on the CP-251, but will gladly send it back to NC if they find a fix for it.....and they can update, calibrate, tune, etc. while they have it!

Post Reply