Dan - this is a problem that was flagged on this forum by you, not me.danatkorg wrote:Kevin,
The posts to this thread imply that this is not the expected behavior for the keyboard action, and as markuk notes, apparently can be easily addressed if it occurs. As always, if you have concerns or questions about Korg gear, especially related to service, you should contact the support department of your national Korg distributor (see the contact info in my signature). While various Korg employees participate in this forum from time to time, as their schedules permit, it is not an official path for product support.
- Dan
That aside, while I understand that the distributor network is how things are generally dealt with ( individual problems on an individual OASYS) - this scenario is different.
There is arguably sufficient evidence to indicate a systemic problem with O88 keyboards in general. Hence - irrespective of the proposed solution, or how it is ultimately implemented (or indeed where it was flagged) - I respectfully but strongly urge Korg to fully characterise the problem and identify a generic solution.
Furthermore, I feel that individuals having to deal with distributors and go though a potentially arduous process regarding whether they are eligible for a repair should be circumvented in this instance - if the problem is real and systemic – whereby, for example, Korg could offer a general decree that anyone needing this repair will get it.
Dan - I kid you not - you complete swept the rug from under my feet with your original post yesterday. I am now wondering if I have an instrument with a fundamentally flawed keyboard for the long run. You have completely unnerved me – hence theses responses. I thought it was an irrelevant issue, but now fear not. So I suggest, respectfully, that it is in Korg's best interest to at least characterise the problem and restore confidence.
Kevin.
