|
|
|
|
|
|
#292584 - 09/09/10 01:09 PM
Re: AUDYA ---> 2nd "bug"
|
Registered: 04/25/05
Posts: 14269
Loc: NW Florida
|
This issue has nothing to do with VELOCITY. It is you, playing hard, activating the aftertouch sensor. And aftertouch is a monophonic sensor. There is no such thing (AFAIK) as an arranger with a split aftertouch sensor. Polyphonic aftertouch kind of died out years ago (sadly, IMO). Aftertouch is generated by a sensor strip that lies underneath the keys, and it generates ONE value. In other words, if you press hard on the lower end of the keyboard (even inadvertently, by playing hard, any sound being played high up will get vibrato'd (if that is what it is programmed to do). Your G70 does this as well (as does ANY modern keyboard). The idea of a 'split' aftertouch sensor is kind of nice, until you start to think of the difficulties... If there are then TWO aftertouch sensors, where do you put the split...? After all, it is NOT a software function, it will have to be two physical sensor strips. So there will be no way to program where it splits. So you will STILL have the same problem, depending on where you split your LH/RH sounds. I would try messing around with the sensitivity of the aftertouch if I were you, if weight at the LH is triggering the aftertouch on high notes. Even better would be a curve selector, where you could choose whether the aftertouch response is linear or weighted towards heavier touch, so your LH doesn't activate it if played softer than your RH. I don't know if the Audya offers this, but it's worth looking in the manual. In the meantime, you are 0 for 2 in the 'bug' category, all you have so far described is behavior that even your G70 does. I would, in future, post something more along the lines of 'Is this normal behavior?' in your posts than screaming 'BUG!' at the top of your lungs. Or even checking whether your G70 does it as well before you even post! Once again (even after actually getting one!) you seem determined to find fault with the Audya, to the point of inventing problems that don't exist (or at least ALL keyboards suffer from)..! How about getting on with discovering what the Audya does WELL, rather than trying (WAY too hard, IMO!) to be the first to report a genuine 'bug'..? You might remember that I used to run the old G70 Users Club's Bug Forum... we had a system there where, BEFORE anything was allowed to be called a bug, we went through the process of, first of all, noting the EXACT set of steps needed to reproduce something weird. If you can't make it happen consistently, it's much more likely to be PEBCAK (problem exists BETWEEN chair and keyboard!) than a true bug. And then a discussion about whether this behavior is actually contrary to anything in the manual. Often, it was simply decided that a flaw in the system was simply bad design rather than a bug, because it did nothing that the manual said it shouldn't. To get prompt updates to fix bugs, it is important to not flood the company with mere moaning about 'this doesn't work the way I'd LIKE it to', and concentrate on 'this doesn't work the way you SAY it should'. A bug is NOT a design choice that is poorly made... or a technical limitation that all other keyboards suffer from.
_________________________
An arranger is just a tool. What matters is what you build with it..!
|
Top
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
#292586 - 09/09/10 01:16 PM
Re: AUDYA ---> 2nd "bug"
|
Senior Member
Registered: 06/24/08
Posts: 3131
|
Originally posted by Scott Langholff:
But then again, who on purpose would hit the left hand chord as hard as they can anyway? Scott, not sure if you own an AUDYA but on the AUDYA, when you hit the left hand HARD, it senses your playing, and automatically will randomize a fill, maybe a different bass line, or an accented drum groove, (different from the generic fills A,B,C this is why you would hit harder, on AUDYA at least....
|
Top
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
#292588 - 09/09/10 01:26 PM
Re: AUDYA ---> 2nd "bug"
|
Senior Member
Registered: 05/26/99
Posts: 9673
Loc: Levittown, Pa, USA
|
Originally posted by Diki: This issue has nothing to do with VELOCITY. It is you, playing hard, activating the aftertouch sensor. And aftertouch is a monophonic sensor. There is no such thing (AFAIK) as an arranger with a split aftertouch sensor. Polyphonic aftertouch kind of died out years ago (sadly, IMO).
Aftertouch is generated by a sensor strip that lies underneath the keys, and it generates ONE value. In other words, if you press hard on the lower end of the keyboard (even inadvertently, by playing hard, any sound being played high up will get vibrato'd (if that is what it is programmed to do). Your G70 does this as well (as does ANY modern keyboard).
The idea of a 'split' aftertouch sensor is kind of nice, until you start to think of the difficulties... If there are then TWO aftertouch sensors, where do you put the split...? After all, it is NOT a software function, it will have to be two physical sensor strips. So there will be no way to program where it splits. So you will STILL have the same problem, depending on where you split your LH/RH sounds.
I would try messing around with the sensitivity of the aftertouch if I were you, if weight at the LH is triggering the aftertouch on high notes. Even better would be a curve selector, where you could choose whether the aftertouch response is linear or weighted towards heavier touch, so your LH doesn't activate it if played softer than your RH. I don't know if the Audya offers this, but it's worth looking in the manual.
In the meantime, you are 0 for 2 in the 'bug' category, all you have so far described is behavior that even your G70 does. I would, in future, post something more along the lines of 'Is this normal behavior?' in your posts than screaming 'BUG!' at the top of your lungs. Or even checking whether your G70 does it as well before you even post!
Once again (even after actually getting one!) you seem determined to find fault with the Audya, to the point of inventing problems that don't exist (or at least ALL keyboards suffer from)..! How about getting on with discovering what the Audya does WELL, rather than trying (WAY too hard, IMO!) to be the first to report a genuine 'bug'..?
You might remember that I used to run the old G70 Users Club's Bug Forum... we had a system there where, BEFORE anything was allowed to be called a bug, we went through the process of, first of all, noting the EXACT set of steps needed to reproduce something weird. If you can't make it happen consistently, it's much more likely to be PEBCAK (problem exists BETWEEN chair and keyboard!) than a true bug. And then a discussion about whether this behavior is actually contrary to anything in the manual. Often, it was simply decided that a flaw in the system was simply bad design rather than a bug, because it did nothing that the manual said it shouldn't. To get prompt updates to fix bugs, it is important to not flood the company with mere moaning about 'this doesn't work the way I'd LIKE it to', and concentrate on 'this doesn't work the way you SAY it should'.
A bug is NOT a design choice that is poorly made... or a technical limitation that all other keyboards suffer from.But...aftertouch can be turned on or off for each part...so...that should not be a problem... [This message has been edited by Fran Carango (edited 09-09-2010).]
|
Top
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
#292589 - 09/09/10 01:29 PM
Re: AUDYA ---> 2nd "bug"
|
Senior Member
Registered: 12/08/02
Posts: 15576
Loc: Forest Hill, MD USA
|
With Yamaha keyboards, you have an option of turning on or off the left, right1 and right2 and on some models, touch sensitivity for the style. I cannot remember which ones had the style sensitivity setting, though.
I would think someone that is very knowledgeable with Ketron products would have this information at their fingertips.
Good Luck,
Gary
_________________________
PSR-S950, TC Helicon Harmony-M, Digitech VR, Samson Q7, Sennheiser E855, Custom Console, and lots of other silly stuff!
K+E=W (Knowledge Plus Experience = Wisdom.)
|
Top
|
|
|
|
|
|
|
|
|
|
|
|
|