Problem with key G3 on my SL88 Grand midi control keyboard

[Project10]

Hi

I don't know if this is a midi problem, hardware problem, or user issue

Recently key G3 on my SL88 has begun behaving weirdly. When connected to my DAW (Logic Pro X 11.2.2) the SL88 will sound every note except G3. But it is not a dead key.

For some background, the SL88 uses 4 'Zones' to transmit midi information and programme changes etc. All the keyboard keys should connect to Logic using Zone 1 set to midi channel 1 which It does , except for G3. In order To make G3 work, I have to configure Zone 2 to transmit key G3 and this key only, also via midi channel 1 and I have to set midi out in Logic to Channel 2.

So in short I have to use 2 Zones on the keyboard both using midi channel 1 to get the all the keys on my keyboard to work. Whilst this is a workaround, it causes other problems like double notes sometimes, volume spikes and limits what I can do on the keyboard for program changes etc.

I have tried to ascertain whether the problem is a hardware issue with the keyboard or an accidental midi misconfiguration ( I'm a midi newbie, so possible). I've checked key commands in Logic and G3 is not configured there and I've run a midi monitor which shows G3 only sending on/off and velocity commands.

Am I missing something here? If not, has anyone else had this problem or have a fix?

Many thanks

 

[happyrat1]

First step of troubleshooting. Backup your settings and do a factory reset to test for misconfigurations.

 

[Project10]

Thanks happyrat1

I've already tried a factory reset. No change unfortunately.

 

[happyrat1]

Check your documentation to see if the keyboard assigns a keymap on powerup and if there's a default secondary control zone that can be moved and/or saved. It may be defaulting to the standard split point and there should be a way to move that right or left.

 

[Project10]

Hi. Sorry for the delay in getting back.

I checked the shipped manual (which is limited) then online and found a more detailed version. As far as I can tell the keyboard doesn't assign a keymap on startup nor is there a secondary control zone. There is no standard split point; this is set using the Zones and these had no effect on G3.

I went back to the keyboard and did a little deductive work: I tried a separate power supply in case the USB cable was not up handling both to power and data and I tried a new USB cable. These changes had no effect..

Then, when trying an assortment of different Zone configurations I found I can use Zone 1 alone and all notes will play if it is set to midi channel 2. And I don't get the volume spikes. If I set it to channel 1 which is the class compliant default, G3 wont play. So I assume the problem appears to have something to do with midi channel 1.

 

[Pete The Greek]

I would recommend using one of the midi monitor apps (e.g. MidiView) to see whether the G3 key on the SL88 is transmitting note on/off on channel 1. If it is not, then the fault lies with the SL88 (possibly a firmware issue? just guessing).

 

[Project10]

Thanks for the suggestion Pete.

After rechecking it looks like the trouble boils down to a single issue. All notes transmit on channel 1 including G3 but it is silent. It does sound however when using channel 2. So as a workaround I have to set up everything to transmit on Channel 2. It doesn't solve the root problem so I'll speak with the shop where I bought it for their comment. I have a feeling it's a software glitch...if it's a hardware issue it's a real shame because it's a fabulous keybed.

Anyhow, I really appreciate the help so far. I'll update the post when I've spoken with the shop.

Thanks all

 

[Pete The Greek]

Also maybe check with Studiologic technical support. Gianni Guidici is typically very responsive. I found a weird zone related glitch with my Numa X Piano 73 which required them to do a new firmware version (which they did within a day as I recall).

 

[Project10]

Thanks, good to know. I'll give that a go.

 

[Project10]

I believe I have discovered the problem.

I re-checked my midi assignments in Logic Pro Key and Controller Commands and found conflicting assignments with (I assume) the keyboard and Logic. It was hard to tell as it was not clear from Logic's matrix however I reassigned the conflicting Logic commands to their default settings and this appears to have solved the problem. Presumably then, I must have either mis-assigned something in Logic to respond to the keyboard or it was a Logic glitch..as a bit of a Midiot I suspect it was the former! Hopefully all will be well now

Thanks to you both, Pete and Happy for taking the time to reply to my post - most appreciated.

 

[delaware dave]

PEBKAC