porco_rosso
vagfilm Hey vagfilm,
thank you for your very detailed response! 🙂
- Bottomline, the structure of the keyboard is still a Fatar action, and in Fatar actions many people complain exactly about its structure: non perfectly machined metal rods in which the keys pivot, keybed warping, etc...
- AFAIK, the keys are not made of wood, but covered on the sides with a thin wood veneer (like the high-end Roland actions). The key itself (and all the pivots) are made of plastic.
- Yes, I know, whereby I would expect (or hope) that these imperfections are corrected, but maybe they are not because they are integral the design of the Fatar action.
- That's right, but that's not a problem. IMO the whole "keystick is fully wooden" in digital pianos is also marketing bs. Rolands higher end actions work very well without fully wooden keys, making them significantly lighter than Kawais counterparts.
- MIDI resolution of 4096 steps. This a marketing mumbo-jumbo. All manufacturers at some point in their calculations end up with velocities with that kind of resolution (because the resolution comes primarily from the microcontroller timer, and not from the touch or optical sensor - velocity of the key is a difference between two sensor TIMES, not two sensor values). It would really difficult (and stupid) to downgrade the microcontroller to force him to calculate times with the 128 range of MIDI values... So, in all keyboards the timings have, at least, 4096 levels of resolution (I assume much more than that), that then are rouded to 128 MIDI steps. Lachnit rounds it first to 4096, and then to 128. Do you think this is relevant? I don't... The main problem with MIDI output is the way sequences of notes are grouped for transmission, because notes are not timestamped at the origin and are sent in sequence: two simultaneous notes on the keyboard (if that is possible...) are always transformed into 2 notes sent one after the other. In a perfect midi controller, those notes should me sent as fast as possible, with minimal gaps of fixed intervals. Many times, those gaps are unequal, and there is some jitter. This is much more relevant than the 4096 steps of resolution.
I agree fully with the second section. I had the feeling that the VPC1 had more of his "jitter" than my FP-30. The timing often just felt a little off.
Not sure about the first one. Now there are 128 steps for me in Pianoteq. If I play mf, I have, let's say, 10 velocitiy steps in that range I can use. Of course I can't exactly intentionally hit for example 80 a few times in a row. It's not about that. But it could happen that I hit a note twice with the same velocity and that would mean I hear twice the exact same sound. With more steps there is much, much more timbral variety (like in an acoustic piano, where it is more or less impossible that two notes sound the exactly same). I know that these differences would be very subtly at best or not even conscious. But it would be a step in the analog direction of an acoustic piano.
- MIDI range. Again, this is irrelevant and may even be bad engineering. If you force a system to always output in the 0-127 range, you are cutting any events that go below or above the set values. It makes much more sense, from an engineering point of view (and that should be the point of view of a controller), to translate velocity in a linear fashion rather than a realistic fashion. I mean, there is no reason why the controller should output ppp as 0-10, and pp as 11-20, and so forth. Zero velocity of the key is known, and maximum velocity of the key can also be measured (velocity will plateau at some point). That range should be split into 128 equal steps. Translating that into realistic velocities IS THE JOB OF THE VST (OR OF THE PIANO ENGINE), and it is called velocity mapping. Is this how it is done by manufacturers? I don't know for sure, but I assume IT IS NOT because otherwise people complain about supposedly missing MIDI ranges, and so they build a velocity curve right into the velocity calculator (like you are complaining of ppp being 30 in MP11SE; but consider that if you remove the fake let off, then ppp can become 20; and if the key gets a bit sluggish, ppp can become 10. If Kawai had set predefined value of ppp as 5 in a new keyboard, after removing the fake letoff the value would still be 5, and in a sluggish key it would continue to be 5, because it cannot go below that. Is this good universal enginneering? Again, I don't think it is...
I can follow you, but somehow that was not my experience with the MP11SE. Using Pianoteq and playing the ppp, pp or p the resulting midi velocity made more or less no difference - around 30. There was no good differentiation of my touch in the first place. So when I mapped it to the lower velocities to get a better pianissimo experience this low resolution of my touch was just relocated and spread, and I could get softer tones, but the MIDI response was still not as reliable in that range as with PHA-50 for example. I couldn't get it right… I am not able to explain it well. The Problem is not that the 30 - 110 range is to narrow per se. But that ppp, pp, p all output at around 30 from the Kawai. If it was like that 30 is ppp, 40 pp, 50 p, 60 mp, and so one it would have worked better. I don't know, maybe I just have to try it again with the MP11SE.