Some keys from my keyboard are NOT recognised ( strange one)

No doubt, but unlikely to be a bug — you’ve probably inadvertently mapped a note to one of your widgets, either directly or via rig manager.

As @pianopaul noted, check the MIDI Assignments

2 Likes

Is this issue only existent in Pianoteq or are other plugins also affected?
I remember that Pianoteq spares out several black keys when running in demo mode, so maybe it’s just some kind of “lost license”?

2 Likes

ahh, i stumbled over such posts.

Okeeey, i begin to see how to “debug” such a problem !
and begin to see whats wrong here.
Please see the 4th line, counting from below, plus the three lines above that.
Midi input: SL GRAND…thats wrong !

Thats the source of the problem then !!
i just checked this vs. two div Rackspaces.
One Rack has only one note failing, the other both of the two Notes.
The midi assignements vary exactly accordingly vs. the Note-failure Issue.
Thats it !

i´m unclear why my SL88 is here the midi input ? thats wrong !
Everything should be related to the Launch Controls.
not shure where its coming from, …and how to change this ?
and not shure, how to avoid that mistake ?

D0 is an unnamed widget…?
Thats the Note that does NOT play in any of my recently used Gigs, …a thing i deal with since several weeks. Well, i guess these few Gigs i´m using were all spring offs, one from the other.
…now that i think about it :wink:

Thanks ALOTS for reading thru this ! and helping !
awesomeness

( for now, i do not press the solved button allready)

That’s ok – I will!

you´ve been quite confident that i will make my way thru it :laughing:
Since we only found the Cause of my issue, yet the issue itself was not solved. :wink:
But it is now :wink:

Ok, that was really a wild one.
The unnamed widgets caused some head scratching. indeed.
I knew it has to be some widgets, so i started first to check ALL unmapped widgets.
no luck.
I then guessd the naming labels could be it.
While checking these, i accidentally clicked the Shape-backround thingy, and it emerged, ohh, …thats widgets too ! attention.
I mean, who has that backround frame thing in mind when thinking of widgets ?
but it was exactly that !!
so i went thru all rackspaces in this GIG. ALL keys are now playing !

problem solved !!
Thank you VERY Much everybody ! much appreciated !

i will add later here more information, from where its was coming from.
Its quite interesting. ( has to do with my specific setup)

Well, I wasn’t confident you would make your way thru it but I was confident that it wasn’t a Gig Performer problem :slight_smile:

There’s no magic here — notes (or anything else for that matter) don’t simply work and then suddenly don’t work unless something changed and assigning notes to widgets by mistake is usually the reason notes stop working.

For what it’s worth, the other main reasons notes stop working are

  1. as @pianopaul suggested, keys are disabled by a plugin for demo purposes
  2. Some keys are being used as keyswitches (e.g., bottom octave of many hammond plugins are used for changing presets), many Kontakt instruments also use some keys for control purposes
  3. Samples are missing

As soon as you mentioned widgets, we all guessed the most likely reason - it’s not the first time people have reported on these forums that notes stopped working - that’s why the very first thing everyone asked you to check was your MIDI assignments, a feature we added a long time ago specifically to help with situations like this.

Glad you figured it out.

Yes, you are right, I didn’t tought to those possible reasons when I anwsered “what else” as I thought that @pianopaul found the only possible reason to this issue. :+1:

Nor should you have — the process for figuring out these kinds of problems is pretty much the same as the medical concept of differential diagnosis, i.e, a problem for which there might be multiple reasons and you’re trying to find the right reason.

So whenever one hears (or doesn’t hear in this case :slight_smile: ) a problem with missing notes, the first thing to check is widget blocking as that’s the most likely cause. If there were no widgets involved, only then would we look at the other reasons.

2 Likes

glad you did !
another example vs. how outstanding GP is ! Chapaux

here is where my “problem” came from:
This mac qwrty + Trackpad placement plays a HUGE role for me,
vs that my whole computer “realtime-play” experience would feel way way better than any Hardware Synth/Workstation i ever had…or -imho- ever could be.

I can play the keyboard, and have my fingers at any time immediatedly on my Trackpad.
so, i permanently refine or reprogramm things in my patches…while playing.
The workflow is immensly fast ! i have to move my hands less than with any HW.

The stumbling block: my right hand (on the TP) DOES lie on the keybed keys while operating the trackpad…thats the one drawback of that setup, it turns out.
its prone for failures while mapping widgets. …but usually, you´d quickly recognise it.
but not these “shape” widget thingys. Need to watch these too !

Glad you´re here to help, folks !

1 Like

Yeah, we can’t really guess at everybody’s individual workflow or how it might impact things.

I guess it’s just necessary for users to be aware of how some things function such as widgets blocking events by default.

1 Like

unfortunately, this problem is NOT solved !

something is wild:
i have again a key NOT working.
i checked the “midi assignement window”.
There is NO entry vs. my keyboard ( the SL88Grand) ( no midi omni was used)

Also: From all entries, where a note/button of one of the NovationLaunch Controls XL has been used, is none equivalent to that unworking key.

while on the other hand:
its again, one of the two same keys, that allways pop up as unworking.
means: its one of those two keys i press down the most - unwantedly- ,
while mapping things. (yes, this key works with Pianoteq in standalone / i checked)
so, its obvious, the fail must come from: "i have mapped a widget, AND pressed unwantedly a key down on my masterkeyboard.
But, i repeat: its not reflected in my “Midi assignement” window !
Can´t figure it out.

( i´m now on GP 4.5 something / latest)

Scripting, on note event ?

1 Like
  • Yes a On Note matching the missing note
  • two non overlapping splits (in GP or in the controller)
  • a dead note in the controller
  • a missing finger

or ?

  • a note assigned to a widget ! :wink:
    (which appears in the MIDI assignments list only for the rackspace where the assignment applies and it can also be displayed as a Rig Manager Alias, so check in Rig Manager if an alias lights up when the missing note is played)
1 Like

NO scripting in the whole Gig. exept tap tempo, which i just deleted.
to be sure.

i checked, but only vs. the active rackspace that has the problem.
Every other rackspace does not have that problem (that key not playing) !
i just checked

i had today several sessions, allways beeing within that particular rackspace,
and shuffled things around further. But: only there !
at the first sessions, the particular key was working !
I´ve not changed anywhere anything, other than within this rackspace.

but i can hunt for the fail everywhere else ofcourse.
this will take me some time.

Rig manager has nothing or very little mapped.
and if any, was it not changed the last 2-3 months.

i never make keyboard splits btw.
as sayed: only some widgets have been juggled around.

each rack is a derivate of a previous one.
ALL main settings, midi blocks etc. are same in each rack !

i´ll see, i go check more wide spread !..thanks so far !

Post a gig file with the problematic rackspace with the missing note.

1 Like

it must be this !
i found another Rack that has sayed ( allready known vs. me ) key mapped by fail.

as far i understood you, could the fail be related/coming from another rack, right ?
Can you confirm on this ? it is possible ?
well, it must be this.
But: this other rack, has the key in question playing. No fail…
it will a tough one to find the “unnamed widget”, but i´m on it…:wink:
i can say more when i found it. (could be any naming plate / checvked the “shape” widgets allready)

Bildschirmfoto 2022-07-10 um 00.49.46

the most upper entry. (edit: its from the next rackspace)

so far i´m under the opinion vs. waht i learnt from this thread:
if i run into this problem, a key on my masterkeyboard (SL Grand) not “playing”,
does it HAS to my “SL Grand” that is mentioned as the midi source in the “midi assignements” window, …i´m right on this, right ?

it can´t be any other from my undersdtanding. correct me anybody if wrong.

whats now new to me: that the source of mismapping a widget could also lie within another rackspace

ok, i found the “mismapped Note” vs my SL Grand in that other rack, and removed it.
this does NOT solve the problem in my problem rack.
But there is NO such note from my SL Grand mapped in that problem rack.
i have no entry in the midi assignements vs. my SL Grand vs. the failing Rack.

no such note mapped in global midi.
i understand this aspect, ie. global midi and waht i have set there

a restart of the computer has solved this issue now.

to notes:
i had deinstalled the PA GP, and installed the deskew GP this afternoon, and much likely have NOT powercycled the mac

edit:
from “midi assignement” window:
there is no possibility to delete a mapping, or even the whole widget, right ?
—> will turn into a feature request, in case i missed something

Yes, it just gives you an overview.
You cannot delete or map something inside that window.

1 Like