Yahoo Groups archive

Disklavier

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

Message

Re: Audio recording with key's noise

2006-05-14 by franpeyr

Hi everybody
and, again, thanks for help.

--- In disklavier@...m, "George F. Litterst" <PianoBench@...> wrote:

> If you record your piano playing on a DU1A, it should play back with  
> a high degree of accuracy from its floppy drive or from internal  
> memory.

That whas I hopped...

> If you play with very wide ranging dynamics, you may find  
> that the quietest notes play back a bit louder and that the loudest  
> notes play back a bit software.

Yes, I have noticed that. But the problem isn't here, in the way of the notes sound, but in 
the way of the notes *stop* to sound. The "off" of the notes.
 
> If you play the MIDI performance back from a computer, but sure that  
> the Disklavier's MIDI In setting is set to the 500 ms delay. [...]

It is set like this.

> Certain models of Disklavier record Key Aftertouch data. If the  
> Disklavier is not a Pro, that data is used to control the decay of  
> the digital piano sound in silent mode. It has no effect on normal  
> acoustic playback. On a Pro, Key Aftertouch messages are also used as  
> part of a sophisticated scheme for recording with a higher resolution  
> than normal MIDI data permits.

Here, we are not talking about *Aftertouch* Data (key pressure after the note is sounded)
but about *Velocity-Note-Off* Data (used to convey when a note on a musical keyboard is 
released).

And, BTW, I don't like this term, "pro". :°)
Because, in fact, I'm a pro who can't offer pros instruments... :°)))))) Especially DK ones...

> Many people edit MIDI data on a computer before playing it back on a  
> Disklavier in order to get the Disklavier to sound appropriate. If  
> the recording was made on a Disklavier, this sort of editing is not  
> necessary.

I was hopping that too...

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.