Welcome to the Piano World Piano Forums Over 3 million posts about pianos, digital pianos, and all types of keyboard instruments. Over 100,000 members from around the world.
Join the World's Largest Community of Piano Lovers
(it's free)
It's Fun to Play the Piano ... Please Pass It On!
I still don't understand why the "approved" touch curve should be in controller and not in the software. It doesn't make any difference.
Exactly, it doesn't make any difference. So, if you can do it on either side, what would be easier for the consumer who buys a VPC? If it's in the controller, the instructions are, basically, "hit a button." If it's in the software, you have to explain to the user how to load a new velocity curve into Ivory or whatever (and probably provide a data file either on CD ROM or have people download it). And if a user decides to buy a second or third software piano, they have to learn a different procedure for how to load a velocity curve into each of the programs. Since as you say it makes no difference, and they want to make the experience as plug-and-play as possible, it does seem sensible for Kawai to put the curve data in the device itself.
I still don't understand why the "approved" touch curve should be in controller and not in the software.
The difference is in velocity resolution post curving. If you pass 128 values (0-127) through a non trivial function and want 128 out, some values will be missing and/or some will be duplicated - so you need more values going in than coming out. Most keyboard encoders have excess internal resolution to cope with this.
If the controller kicks out high-res MIDI (2^14 values) this is pretty much moot and you can do the curve anywhere you want with impunity. Though the curve is traditionally in the controller (for the reason above) so there may be limited to no curve control in stand-alone sound modules.
OK, however if there are new software pianos in the future, it will get even harder for users to upload new curves to the VPC, especially on Mac. And there are only 5 slots for touch curves.
Dewster, you're right, the dynamic steps get less than 128 on the output if we remap values in software. So, it actually makes sense to use custom curves on the controller side. I am wondering if this will make any real difference and if it is perceptible though.
I still don't understand why the "approved" touch curve should be in controller and not in the software. It doesn't make any difference.
Dewster added a good point.. it can indeed make a difference. With a fixed number of velocity points, any "increased resolution" in one area of the dynamic range is offset by "decreased resolution" in another. On the software side, assuming you're using the typical controller that sends out 0 to 127, the software only has 128 possible values to work with. On the controller side, they may be able to do something better by manipulating the curve before it is "reduced" to 128 values to begin with.
The 'GF' has a longer key stick and pivot length, that's true. But 'RM3 Grand II' is still a superb action to play, and surely the most realistic in a controller board. May I ask if you or your piano-teaching wife have ever tried a wooden-key Kawai action, by the way?
Originally Posted by dewster
...in a case that is NOT the most ergonomic for PC use
I assume you are referring to the slight curvature of the top surface? As others who have seen the board have noted, it's really nothing to worry about.
Originally Posted by dewster
...with a UI that is NOT the most intuitive (use of the power switch & keys to select curves, no feedback whatsoever that I can see
The selected memory is indicated by the colour+state of the power button. If you can think of a better method to select/indicate the setting memory 'headless', I'd like to hear it. As explained in the owner's manual:
As noted above, these preset touch curves can be replaced/adjusted by the player using the VPC Editor software, if desired.
James, I don't want to be nitpicker and I am saying it mostly for the fun side of it, but I am color blind and I hate it when things rely on color codes, etc
We are musicians for Pete's sake, why not just generating different musical MIDI patterns when you change curves, say "God save the Queen" for normal, "Star spangled banner" for Ivory, etc Just kidding - I don't want to be banned again and I apologize to anyone affected in advance!
James, I don't want to be nitpicker and I am saying it mostly for the fun side of it, but I am color blind and I hate it when things rely on color codes, etc
Don't worry, I'm partially colour-blind too, but even I can spot the difference.
I'd like to congrat James for his patience and self control given some criticisms that, in my opinion, aren't called for regarding this product. It's a piano controller, with an (apparently) better action than most controllers on the market. It does exactly what it's meant for : control a piano sound, merging the best of both physical and software worlds. Those who wanted a semi-weighted keyboard to control their sounds already had plenty of models to choose from, but piano aficionados looking for a simple fully weighted action keyboard didn't. Now it's different.
I have two questions : - how would you compare the RM3II action with the one found on the ES7 ? - when is it available in Europe ?
The selected memory is indicated by the colour+state of the power button. If you can think of a better method to select/indicate the setting memory 'headless', I'd like to hear it. As explained in the owner's manual:
As noted above, these preset touch curves can be replaced/adjusted by the player using the VPC Editor software, if desired.
Cheers, James x
James:
Just wondering if you have a handle on the need for Kawai equipping the VPC controller with a place for velocity curves to match specific software products.
It would seem to me that every software package would simple assume the instrument sends the standard 0-127 velocity codes and the hardware companies (Kawai, Roland, etc ...) just do that.
Don
Kawai MP7SE, On Stage KS7350 keyboard stand, KRK Classic 5 powered monitors, SennHeiser HD 559 Headphones
Just wondering if you have a handle on the need for Kawai equipping the VPC controller with a place for velocity curves to match specific software products.
The touch curve is arguably the last piece of the jigsaw between a 'pretty good' playing experience and an 'absolutely fantastic' playing experience.
Originally Posted by dmd
It would seem to me that every software package would simple assume the instrument sends the standard 0-127 velocity codes and the hardware companies (Kawai, Roland, etc ...) just do that.
True, most keyboards/DPs send velocity values from 0-127 (although some do not...), however different keyboard actions require different amounts of force to produce the same MIDI value - hence the need for touch curves.
Thank you, James for posting this video of Jordan Rudess playing the VPC1. For me at least, being able to hear it, and see it in action is wonderful. To my knowledge (please tell me if there are others), this is the one and only post of the VPC in which somone actually plays it! Not only does it look good, it sounds wonderful! I too, would like to commend you and thank you for your patience over the last several days in answering graciously a thousand and one questions. You sir, are a gentleman and a scholar! Regards, H.K.
Keyboards are the best therapy I know of... ______________________________________________ Kawai MP6 stage piano; Kawai ES8; Kawai G20 Grand DCM CX-17 Monitors Sennheiser HD 205, DJ series, headset
True, most keyboards/DPs send velocity values from 0-127 (although some do not...), however different keyboard actions require different amounts of force to produce the same MIDI value - hence the need for touch curves.
Kind regards, James x
I do not mean to belabor this point but I really would like to understand this point. I have been delving into this topic for a while now and have not been completely satisfied as to the need.
What it appears that you are saying is that the the piano company may have manufactured a digital piano which sends codes midi codes 0 - 127 but in order to reach the upper range it must have to almost "pound" on the keys to get there. If so, I would say ... Why would they do that ?
You would think they also are aware that their users would wish to reach the entire range 0-127 with a normal effort. And, apparently it is not difficult to do since all that is needed now to correct the problem is to insert a velocity curve and ... viola ... done.
Don
Kawai MP7SE, On Stage KS7350 keyboard stand, KRK Classic 5 powered monitors, SennHeiser HD 559 Headphones
Just curious because nothing good ever comes here in AUS. I think I have bought most of my stuff from either the UK or the US because we have such limited amounts of gear here. The only really annoying thing is the import fees that I have to pay for.