Hi all,
this is my first post here. I am actually not an engineer of any kind, I joined this forum hoping to kindly ask for a professional's opinion over an issue that I am having with a musical instrument, that I am clueless about. I hope it is the right section of the forum and I hope it's OK for a total layman to post such requests in what seems to me like a highly specialised forum to start with. Further disclaimer: I'm not native in English, so please forgive possibly wrong sentences here and there.
The issue is the following: I have recently got a Hammond XK-5, a digital organ, and there something it sometime does, that I believe is a bug, that I am losing my mind trying to see a patter for. It's been totally unpredictable: it goes one month of heavy use without popping up, then it pops up 10 times in two hours, then gone again.
I imagine most people here aren't necessarily familiar with such an instrument, but my hope is that an "expert's eye" could perhaps have a much more informed guess, based on the symptoms shown, as to what could be possibly going on here.
The issue is simple to describe: a popup message that should only appear on the display when I turn a specific knob, appears sometimes on its own upon patch loading. (A "patch" in these kind of electronic keyboards refers to a preset of parameters that constitute a sound -- a saved profile pretty much).
That popup is usually but not always the "Overdrive level bar" that again "should" only appear if I tweak its associated knob. Attached pic 1 shows the main screen as when in normal operation mode, and pic 2 shows the popup as I tweak the knob. I haven't been able to film this bug in real time because it's so random, but luckily a guy on the Internet experiencing the same problem was able to:
<Mod: deleted link>
Now, not only does the popup appear, but it actually changes the Overdrive parameter associated with that patch. I have to recall the patch again to make the value back again as it is as stored in the patch.
As I said, the only "pattern" I could find for this is that it only happens as soon as a patch has been loaded (by whatever means it has been loaded by -- there are several). If it doesn't happen a second after this, then it doesn't happen.
The only few responses I was able to find online are from people who say "I am getting this bug too", but being this instrument an extremely niche (and extremely expensive!) one, there isn't a community of any kind around it that could provide insights.
Now what I am wondering is the following:
1) first of all, as a layman I'd strongly suspect it's not hardware related but a glitch in the firmware. Does it look the same way to you?
1a) Sure enough the knobs aren't faulty (any of them)
2) Could this possibly be caused by some "overbuffering", if this makes sense, of certain data that until the keyboard hasn't refreshed, makes the bug appear?
3) The firmware I am running (this is the link) is the latest one provided by the manufacturer: the idea of trying looking inside it and embark the enterprise of trying fixing it... is feasible or I should rather forget about it?
This was long to read and I thank very much all of you who took the time to read.
Any insight would be highly appreciated.
Steve
this is my first post here. I am actually not an engineer of any kind, I joined this forum hoping to kindly ask for a professional's opinion over an issue that I am having with a musical instrument, that I am clueless about. I hope it is the right section of the forum and I hope it's OK for a total layman to post such requests in what seems to me like a highly specialised forum to start with. Further disclaimer: I'm not native in English, so please forgive possibly wrong sentences here and there.
The issue is the following: I have recently got a Hammond XK-5, a digital organ, and there something it sometime does, that I believe is a bug, that I am losing my mind trying to see a patter for. It's been totally unpredictable: it goes one month of heavy use without popping up, then it pops up 10 times in two hours, then gone again.
I imagine most people here aren't necessarily familiar with such an instrument, but my hope is that an "expert's eye" could perhaps have a much more informed guess, based on the symptoms shown, as to what could be possibly going on here.
The issue is simple to describe: a popup message that should only appear on the display when I turn a specific knob, appears sometimes on its own upon patch loading. (A "patch" in these kind of electronic keyboards refers to a preset of parameters that constitute a sound -- a saved profile pretty much).
That popup is usually but not always the "Overdrive level bar" that again "should" only appear if I tweak its associated knob. Attached pic 1 shows the main screen as when in normal operation mode, and pic 2 shows the popup as I tweak the knob. I haven't been able to film this bug in real time because it's so random, but luckily a guy on the Internet experiencing the same problem was able to:
<Mod: deleted link>
Now, not only does the popup appear, but it actually changes the Overdrive parameter associated with that patch. I have to recall the patch again to make the value back again as it is as stored in the patch.
As I said, the only "pattern" I could find for this is that it only happens as soon as a patch has been loaded (by whatever means it has been loaded by -- there are several). If it doesn't happen a second after this, then it doesn't happen.
The only few responses I was able to find online are from people who say "I am getting this bug too", but being this instrument an extremely niche (and extremely expensive!) one, there isn't a community of any kind around it that could provide insights.
Now what I am wondering is the following:
1) first of all, as a layman I'd strongly suspect it's not hardware related but a glitch in the firmware. Does it look the same way to you?
1a) Sure enough the knobs aren't faulty (any of them)
2) Could this possibly be caused by some "overbuffering", if this makes sense, of certain data that until the keyboard hasn't refreshed, makes the bug appear?
3) The firmware I am running (this is the link) is the latest one provided by the manufacturer: the idea of trying looking inside it and embark the enterprise of trying fixing it... is feasible or I should rather forget about it?
This was long to read and I thank very much all of you who took the time to read.
Any insight would be highly appreciated.
Steve
Attachments
-
2.6 MB Views: 12
-
2.4 MB Views: 11
Last edited by a moderator: