@C.B. said:

I have the same issue (annoying key noise on some release notes).The noise is more audible when playing softly (final chord of a soft piece, for example). It reminds me the noise of a silent piano.

The Steinway is beautiful but I agree that hammers are too hard (at least, compared to then my own 205 cm grand piano). It is not easy to produce a «muffled» sound with that software intrument.

Best,

C.

Here is my solution thus far that may be acceptable in crafting a better sound...

Turn up Dynamic to around 120 (maybe more?) and turn down MIDI Sensitivity to around -20.

Also, go to the edit page and take the upper half of the keyboard and put an EQ shelf below 200hz... (or get the bell curves so you can keep a little bit of the piano "body" below 70hz) that helps reduce all that noise, yet on the lower half of the keyboad you can preserve the low end.

Hi all,

Thanks for the replies.  In the past few days I did a direct comparison with the VSL Vinenna Imperial and it does not have the same problem.  The Imperial runs fine with a linear curve off the Kawai NV10, much like Garritan and my other VSTs.  There is something definitely different with the VSL Steinway D.

I do not beleive there is anything wrong with the sample set, the problem would be remedied by adding a 1-D velocity curve editor.  The only case in which a 1-D velocity curve editor could not address this is if there was (a) a sparse sample set and (b) strong non-linear characteristic to how the samples were originally captured.  For example if the sample set had 8 layers and most layers were recorded near ff-sfz..not much can be done there.

However with so many sample points on the velocity axis, just fixing the curve would fine even if the 'robot' velocity curve for layers was non-linear.

Someone commented on the VSL video and how the pianist did not notice this, this is a good observation. I would note that that this was a specific weighted MIDI controller which has some implemented velocity mapping curve.  It could be that the VST was designed to work very well with that in-house controller, but that doesn't mean it would work with others, which is why having a 1-D velocity curve editor is standard on all other VSTs.

I agree that if the velocty curve issue is fixed as far as I can tell this could be the definitive sampled Steinway D.  What great sound, and ambience, absolutely mesmerizing.

I can't help wondering what is done with all this perfection of velocity levels etc. by the people demanding it.  

There are lots of people on this Forum who write all this complicated stuff about how this or that parameter is just not right and not acceptable, etc. etc. - and yet what do they do with all this technique?  

Not trying to be obnoxious!  Maybe all the complaints are correct, sure.  I don't know.  But I wonder what is the actual musical use of all of this?  If the instrument is just perfect ----  do the people who are complaining then proceed to create masterpiece after masterpiece?    Somehow I never hear any music by them.

@William said:

Somehow I never hear any music by them.

Allow me to flex. 😛

If the suggestions in this were implemented, I would say they would have the following direct musical benefits:

• Better "out of the box" sound requiring less EQ to fix the noise.
• Better playability requiring fewer adjustments to the MIDI after a performance.
• For film scoring, piano parts tend to air on the soft side (the opposite of the current curve)... could be more inspirational for composers!

Granted, this is what *I* would do.  If none of these are implemented, then I certainly have workarounds and handy "save presets" options once I get it dialed in how I like it. 😃  I have a feeling though VSL will introduce a curve... they're really good about listening to their customers when they have reasonable requests.

@opus64 said:

Hi all,

Thanks for the replies.  In the past few days I did a direct comparison with the VSL Vinenna Imperial and it does not have the same problem.  The Imperial runs fine with a linear curve off the Kawai NV10, much like Garritan and my other VSTs.  There is something definitely different with the VSL Steinway D.

I do not beleive there is anything wrong with the sample set, the problem would be remedied by adding a 1-D velocity curve editor.  The only case in which a 1-D velocity curve editor could not address this is if there was (a) a sparse sample set and (b) strong non-linear characteristic to how the samples were originally captured.  For example if the sample set had 8 layers and most layers were recorded near ff-sfz..not much can be done there.

However with so many sample points on the velocity axis, just fixing the curve would fine even if the 'robot' velocity curve for layers was non-linear.

Someone commented on the VSL video and how the pianist did not notice this, this is a good observation. I would note that that this was a specific weighted MIDI controller which has some implemented velocity mapping curve.  It could be that the VST was designed to work very well with that in-house controller, but that doesn't mean it would work with others, which is why having a 1-D velocity curve editor is standard on all other VSTs.

I agree that if the velocty curve issue is fixed as far as I can tell this could be the definitive sampled Steinway D.  What great sound, and ambience, absolutely mesmerizing.

Unfortunately it's not as simple as that; if it were there would be no problem because there are countless free velocity curve editors already out there which can easily be used with Synchron Pianos already.

The problem is that the perceived loudness of the piano comes from two things: objective amplitude (sound pressure level) and timbre.  If I record a piano really loud, and then greatly reduce the volume on playback, it doesn't sound like a soft piano, it sounds like a loud piano being played back quietly.

A velocity curve editor enables the user to change the mapping between the input and the amplitude-timbre combination (because the two are fixed together in the sample).  However, if the amplitude-timbre mapping is wrong, which in this it clearly is, that cannot be fixed by changing the velocity curve.  I could, for example, edit my velocity curve to require me to play much harder in order to achieve higher velocity layers, which would help to fix the input-timbre mapping.  However, that would have the effect of making it much harder to achieve higher amplitudes, i.e. it would distort the input-velocity mapping.  Or instead, I could edit the velocity curve to ensure that the input-velocity mapping is okay (which it more or less already is in this case), but that would then create (or leave/not fix) the problem with the input-timbre mapping.

In other words, you cannot, by adjusting the mapping of the input to different samples, fix a problem which is caused by internal inconsistency in the samples in terms of the amplitude and the timbre.  The amplitude-timbre mapping of the samples needs to be adjusted and that can only be done by VSL.

Steven, yes actually I realized I had heard something of yours after writing that. Excellent work though I'm sure you don't care what I think.  

Opus64 thanks for that - very interesting and I'm certain the feedback is valuable to VSL.

Hi Karvala,

Interesting point, but i'm not sure I understand something if you don't mind clarifying:

My understanding of how the piano was sampled is that multiple mics are placed in the room with fixed settings(preamp gain, etc).

Considering only a single pedal/etc condition layer, the robot plays a key at multiple velocities and the microphones capture the resulting sound.

Unless VSL is changing the mic settings for velocity(perhaps to accomodate dynamic range?) or post-adjusting the amplitude of the samples during playback, it seems to me the amplitude and timbre are linked at the recording point and if the microphones are linear, should represent what the instrument sounds like.

If these two are truly linked at sampling time, then it seems the midi->velocity map should allow to adjust for the problem, which in my view is that for a relatively soft keypress velocity the resulting sound is more ff or even sfz.

I'm probably missing something....

Thanks. 

@William said:

Steven, yes actually I realized I had heard something of yours after writing that. Excellent work though I'm sure you don't care what I think.  

Just having a little fun, and never missing an opportunity for a little shameless self promotion 😉 But thank you very much! 😃

Eukalyptis wrote:

If the Steinway simply had the playability / velocity reaction of the Pianoteq 6 Steinway, in my opinion, the search for pianos would be over! Really hoping for a fix soon.

+1

Dear VSL team, please fix this.

@opus64 said:

Hi Karvala,

Interesting point, but i'm not sure I understand something if you don't mind clarifying:

My understanding of how the piano was sampled is that multiple mics are placed in the room with fixed settings(preamp gain, etc).

Considering only a single pedal/etc condition layer, the robot plays a key at multiple velocities and the microphones capture the resulting sound.

Unless VSL is changing the mic settings for velocity(perhaps to accomodate dynamic range?) or post-adjusting the amplitude of the samples during playback, it seems to me the amplitude and timbre are linked at the recording point and if the microphones are linear, should represent what the instrument sounds like.

If these two are truly linked at sampling time, then it seems the midi->velocity map should allow to adjust for the problem, which in my view is that for a relatively soft keypress velocity the resulting sound is more ff or even sfz.

I'm probably missing something....

Thanks. 

That's a fair question.  If there were no post-processing, you would be absolutely right, but in practice there is a *lot* of processing of the samples after recording, and amplitude adjustment is certainly one of them.

Have you ever heard the Salamander piano - a Yamaha C5 VST?  It was essentially a fun project that someone did on their own, and it's probably the closest you'll come to a piano VST which has simply been sampled and  assembled with minimal post-processing (but even in that, they did some).  It's worth having a listen if you haven't , and you'll see just how raw and 'recorded' the sound is, and it will give you some idea of the amount of work which is needed after recording to turn it into a usable VST rather than a series of triggered individual piano recordings.  Indeed, one might even say that the quality of the post-processing is as important as the recording setup in determining the final quality of the VST.

Stephen, you should always be shameless in self-promotion - a musician has to be.  Also you're playing in real-time - fantastic. 

@William said:

Somehow I never hear any music by them.

Allow me to flex. 😛

If the suggestions in this were implemented, I would say they would have the following direct musical benefits:

• Better "out of the box" sound requiring less EQ to fix the noise.
• Better playability requiring fewer adjustments to the MIDI after a performance.
• For film scoring, piano parts tend to air on the soft side (the opposite of the current curve)... could be more inspirational for composers!

Granted, this is what *I* would do.  If none of these are implemented, then I certainly have workarounds and handy "save presets" options once I get it dialed in how I like it. 😃  I have a feeling though VSL will introduce a curve... they're really good about listening to their customers when they have reasonable requests.

Fantastic stuff, Stephen!!  Dazzling performance of the Rachmaninoff, and your Millennial Suite is superb and with such passionate performance.  Deeply impressive.

@karvala said:

... Indeed, one might even say that the quality of the post-processing is as important as the recording setup in determining the final quality of the VST.

I learn somthing almost every time you post. Thank you for your contribution. 

God Bless,

David

Thanks Karvala, this is a very interesting discussion.

I understand there is normally a lot of processing involved with most sampled pianos which have relatively few actual samples.  For example, the on-board Kawai NV10 engine I bet has a lot of processing going on to make use of the relatively few layers(mixing, splicing, looping, etc) and even with all the trickery one can clearly hear the limited velocity expression when playing it.  (Not to knock this piano, it's not bad compared to the competition)

However, with such a thoroughly sampled piano as the VSL Steinway D(I believe they quote 4000 samples per key!), my expectation is that if I select a single mic perspective and happen to exactly request an isolated key in a velocity/configuration that was sampled then pretty much the original sample would be played.  I'm not sure why it would need to be dramatically altered if I happen to ask for a sound that was sampled exactly.

I can undersand some EQ'ing to compensate for the microphone response, and layering of release samples and of resonance modelling/pedal noise but otherwise I would hope that what I hear is almost exactly what the selected microphone heard in the room...

Anyway this is sort of educated specilation.  I don't really know how VSL does it so interesting discussion!

And another datapoint, I just tested the VSL CFX for the first time, also does not suffer from the problem.  Definitely specific to the VSL Steinway D.

Hello everybody!

We have just released a Library Update for the Steinway D, with improved velocity mapping. 

So far, we have received great feedback from our testers, so this one should be quite a big step into the right direction 😊

Thanks for your input, everbody!!

Best, 
Paul

Apologies for the late reply.  I find this update does dramatically improve the playability at least on my Kawai NV10 in the 'Normal' response mode, while still mantianing some 'lightness' compared to the CFX and Bosendorfer libraries.

It really speaks volumes that you responded so quickly to provide an update, thank you very much.  A lot of companies could learn from this.

I recommend adding a velocity curve editor to these products sometime in the future.  It is physically impossible to have a single parameter account for the wild-west of MIDI controllers out there, all with different mechanical actions. These are simply the best sampled pianos ever, and having the flexibility to tune the velocity curve to the specific action of the controller will let us get the most out of them.

Thanks again.

Since this thread might be read by people waiting for the issues discussed here to be resolved, I just want to add my endorsement of the new update. No need to wait any longer! The VSL Steinway is the best virtual piano I have found. I am impressed that VSL responded so quickly and so thoroughly. Thanks, Paul!

The new update is great. I do agree though, a velocity curve editor would be the best addition to Synchron Pianos, & Vienna Imperial Player, that I can currently think of.