Yahoo Groups archive

Disklavier

Index last updated: 2026-04-28 23:20 UTC

Message

Re: [disklavier] Re: 1986 Disklavier midi play back volumne

2011-03-09 by Mark Fontana

George, it still remains the case that the effective "typical" velocity 
range of a Disklavier (ALL past and current models) is compressed into 
the MIDI velocity range of approximately 30-95, correct?  Otherwise, 
Yamaha would need to release different versions of their music diskettes 
for different models.

The difference on newer models is that levels 95+ continue to get a 
little louder and levels below 30 continue to get a little softer (to 
some point), but the core range of 30-95 is intended to produce roughly 
the same dynamic range in decibels across instruments.  Right?

My understanding is that XP enhancement just adds more incremental steps 
along this existing curve.

It would be great if Yamaha could develop some guidelines for content 
creators (tips for ensuring consistent performance across Disklavier 
models, particularly regarding note velocities and pedaling).

I'm not aware of any such documentation.  It seems like Zenph, 
WebOnlyPiano and others are having to figure these things out for 
themselves.  Is there anything official?

Mark Fontana


On Wed, Mar 09, 2011 at 05:17:17PM -0500, George Frederick Litterst wrote:

> The early Disklaviers compressed the dynamic range on playback, 
> boosting the low MIDI velocities and capping the high MIDI velocities.
> 
> Starting with the Mark IIXG Pro, Yamaha achieved a full spectrum of 
> playback possibilities on the Disklavier. The original Pro and 
> subsequent Pro models have been unsurpassed in this regard and offer 
> more resolution in between the traditional 0-127 velocity 
> measurements. The Mark III, current E3, and Mark IVs non-Pros also 
> have a much wider dynamic range compared to the early model 
> instruments.
> 
> Regards,
> PianoBench

Attachments

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.