"Edwards, Ed" wrote:
>
By this I don't mean the effective level of the
> parameter AT applies to a function -- everyone knows that you can adjust the
> amount in the matrix.
IMO, if 'everyone' knew that there would be no need for a mailing list :-)
What I'm talking about is that the pressure strip is
> too sensitive and sends aftertouch too easily with just a light touch.
Ah ha! Now I see what you are talking about. What I overlooked in
Todd's original post was the word 'controller'!
Has
> anyone ordered a service manual for the AN yet? If so, maybe we could look
> at the schematics and see what might be altered to adjust sensitivity.
I don't know if Yamaha would sell - or issue - a service manual to an
unregistered tech? Typically, Service Centers pay a fee for Service
Manuals. If they won't provide one then maybe someone on the list is on
friendly terms with a local tech who would 'loan' a service manual ;-)
Another possibility: many of the keyboard mechanisms used in popular
keyboards are manufactured by another company other than the 'brand'
name, i.e., Korg and Yamaha have been known to use Fatar mechanisms in
many popular synths over the years. I always enjoyed the keyboard's in
my old "Korg" gear particularly. If you can't find an AN1x Service
Manual then maybe we could identify the original manufacture of the
keyboard mechanism itself and try for that companies service manual.
The third alternate is to damn the torpedoes and wing it! ;-) I can
tell you with absolute certainty I'd botch the job big time - ha haha
LOL ;-)
There are other possibilities.
1) As Sebastian recommended, use the Record Filter on your software
Sequencer to remove the Aftertouch MIDI CC while recording. I wonder if
this option 'filters' the AT MIDI CC only while recording or does it
occur at the MIDI Thru simultaneously?
2) Use whatever graphical or logical editor is available in your
software sequencer to 'thin', or rather - reduce, the data after it has
been recorded.
3) Use a hardware data filter from the likes of Anatek (or whomever
manufactures them this month) between your AN1x and the destination kb/module.
4) Reduce the depth amount modulated by AT on the destination kb/module.
5) Use a MIDI Interface which allows for MIDI Processing. I use to own
an Opcode Studio 4 which I would run off my Mac using OMS. When OMS
would load the Studio 4 driver it would also enable an application named
Studio Patches Editor. This app permitted the user to create
∗incredible∗ MIDI routings/layers/zones/filtering which would function
in real time if so desired. Now, I'm not current on this level of
functionality with the Emagic MIDI Interface but I'm pretty certain some
of the mid-range and high end MOTU models offer similar features.
Many years ago there use to be a number of manufacturers who produced
dedicated MIDI Patchbays (not to be confused with a MIDI Interface) that
offered the same type of functions the Studio 4 does but, and it's an
important 'but', they let you store your setting in program memory on
the box itself! The Studio 4 had a very limited program memory and most
of the good stuff could only be accessed from the Mac :-/ cost cutting
measure and all that...
Maybe some of these ideas will serve as workaround.
> > tspeer wrote:
> > >
> > > From: tspeer <tspeer@...>
> > >
> > > I may be alone here- but I use my AN1-x as my main controller.
> > > -and I find its monophonic aftertouch ..a bit too easy to trigger.
BTW - has anyone experimented with the Kbd Vel settings under the
Utility/Setup menu to see if there's any difference in the MIDI Values
transmitted or is it simply an internal setting? I simply dialed in a
setting I was comfortable with.
Regards,
Jon
--
http://www.jdlx-musique.com/