aftertouch being rather on/off style

[Qwave]

Hi,
I hadn't used the velocity and after touch that much yet. But I just did a patch to use these expressive controls to change the cutoff and resonance of a solo patch.
Well, the after touch right now in OS 2.3 is still kind of useless for real playing. Its more like an on/off switch. Try this: route the after touch to pitch and then increase the force to play after touch. You won't be able to get values other then close to zero and close to max. No values like 60 or 80. I used a MIDI Monitor and other keyboards to check this. Sending aftertouch data from a different keyboard (like the Waldorf Q that use the same keyboard action made by Fatar as the Voyager) will get the desired values easily. Therefor I think there is a scaling problem inside the Voyager's software.
The same is a bit also true for the velocity. But this might be more a problem of my playing skills.

I wish some after touch and velocity scaling options for the next software release to make full use of the hardware capabilities that are inside all Voyagers to make it more expressive in terms of classic (velocity) and typical synth expression.

[sir_dss]

Isn't this "aftertouch" problem an issue of hardware not software?

The actual keyboard not any OS-x.xx?

I think it's been brought up many times before.

I do hope it can be fixed with an OS update, but I guess I've learned to deal with it along with the filter glide issue.

The Voyager still rules in my book and when you start using some modular synths like Blacet and MOTM you can get very deep in synth.

[Qwave]

Isn't this "aftertouch" problem an issue of hardware not software?

You would be right in the world of pure analog synths. But the keyboard of the Voyager is not an analog one like the one used in a Minimoog. Its an Fatar keyboard action that is built into many of todays keyboards. For example in the non analog Waldorf Q. The keyboard is sending out some digital data that needs to be converted to play the synth and to send data from the MIDI Out port to other instruments or computers. The stage where the digital data is converted into the analog control voltages that control the analog sound generartion circuits is somewhere in the back of the Voyagers boards. Its not part of the keyboard.
The data generated by those keyboards is always the same on every keyboard action of the same model (but with different number of keys).
Other companies using the same model of keyboard action are able to send and to play all possible values in between the min and max range of the aftertouch. Try to route aftertouch to a parameter and listen for your self. Its more on/off like on the Voyager. And other companies did manage to make use of the full range with all expressive use in the whole range of aftertouch data going from 0 -127 on MIDI. The Voyager is behaving right when the aftertouch is send to it via MIDI. The problem is the converting of the keyboard data into values send into the analog stage and to the MIDI out port. And I hope this is software based. Or at least there is a way of scaling the data by means of software.
To me this sound much easier to solve then the filter not being able to track the glide. I think this was done in the pure analog. So solving this ould need soldering and therefor most users would have to send their unit to some technician. And this is really expensive. Doing the software to scale the aftertouch is a software job. Software isn't coded for free. But I think its way cheaper then soldering every unit.

[Cruel Hoax]

While the filter/glide problem plagues me, I can't say that I've been bothered by the aftertouch issue.

I use the after touch to add vibrato or "growl", and an on-one-note, off-the-next approach works very well for me, Bernie Worrel style.

I use the mod wheel for filter or weirdness, and so almost never have it as a vibrato controller, except with sensitive flutey sounds. Well, not as a LFO->pitch controller. That's never sounded good to me. I do use the mod wheel as a "finger vibrato" for a vocal patch I like. I route Osc 3 to Osc 3 via the wheel, turn on FM and sync, and listen only to osc 2. Very, very cool stuff here if you tune carefully!

-Hoax

[LWG]

Hello,

I have also noticed the degree to which the parameter value jumps too rapidly when the aftertouch and velocity is applied. Someone had raised this
point on another thread some time ago. It's present scaling makes it a bit awkward to use.
I chalked it up to whatever force sensor was being used in the keyboard assembly however, if this is the midi scaling and the aftertouch and velocity response can be made a little more wieldy with some software changes, that would be cool.

regards,


LWG

[s16016wb]

i wonder if this could be remedied with a cp251 and a 351:

aftertouch patched to the lag processer, fine-tuned with the cv mixer?

[mee3d]

Yes, it is possible to patch the pressure out of the 351 into the Lag on the 251 and then back into one of the mod busses or VCF on the Voyager. The results aren't quite how I would like them, being used to the soft Aftertouch on Vintage yamaha CS poly's as you still have to press quite hard to get the voyager to trigger the Aftertouch but it is better then the "Switch" of the Voyagers inbuilt keyboard aftertouch.

Does anyone know if Moog changed the keyboard hardware during production as my early Signature Edition has a much nicer keyboard action then both the Performer or AE?

Mal