Disklavier

You've done a service to those with an affection for more of those pesky jewel
cases.

As an alternative, some might wish to convert their PianoSoft material to MIDI
and put the files on a CD-ROM.  Let's say you devote 600 MB of a CD-ROM to
data.  That would allow you to store at least 800 each 720 KB albums on a single
CD.  Of course, you'd put the files in appropriately labeled folders and name
the files descriptively.  You'd devote a folder in the CD to playlists and use a
sequencer to play your DKV.  Rather than search and shuffle through jewel cases,
you use your Windows "Find" facility to locate files by composer, title, or
performer.  You don't have to bother about returning disks and cases to their
proper places. 

> jes wrote:
> 
> Floppy disk storage - organization
> 
> I found a company which sells the CD-type jewel
> cases with the floppy disk liner.  They also sell
> jewel cases the size of a floppy disk (like those
> used by QRS).  I've ordered and used some of each.
> They've really helped me organize/label/protect my
> collection of floppies.
> 
> http://www.westnc.com/floppy.html
> 
> Jewel cases with  3.5" floppy diskette tray
> are  63 cents each   #J35TR
> 
> Jewel cases for a single 3.5" floppy disk
> are  43 cents each    #J3501
> 
> from  Western Numerical Control
>          983 Golden Gate Terrace
>          Grass Valley, California (CA)   (USA)  95945-5938
>          (530) 477-7575 --- FAX (530) 477-1917
> Jim
> 
>                    Yahoo! Groups Sponsor
> [Check out great fares at Orbitz!]
> 
> 
> To Post a message to the group, send it to:   disklavier@...
> 
> To Post a private message to Todd Muncy, the group's founder and moderator,
> send it to:
> disklavier-owner@...
> 
> To reach our group's web site go to:
> http://Yahoogroups.com/group/disklavier
> 
> Todd's family web site was completely rewritten in June 2001 and contains some
> fun disklavier content and links to midi sites among other things, The url is:
> http://MuncyFamily.com
> 
> THINKING OF LEAVING THE GROUP?
> If you are thinking of unsubcribing because you are getting too much mail, go
> the the web site and change your email delivery option instead.  That will fix
> the problem, while maintaining your access to the group.  If you insist on
> leaving us completely send a blank email to:
> disklavier-unsubscribe@...
> 
> Know someone who wants to join?  Have them send a blank email to:
> disklavier-subscribe@... or give them this link:
> http://Yahoogroups.com/group/disklavier/join
> 
> Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.

-- 
Robert Welcyng
Anchorage, Alaska

I wonder if there might be a technical disadvantage to the approach of
driving the Disklavier via MIDI from a computer.  Namely:

Suppose a piece contains a chord of three notes struck simultaneously.  
This can be represented in ESEQ or MIDI format as three note-on events with
delta times of 0 between the second and third events.  The Disklavier's
embedded controller can process a string of events like this as quickly as
possible, ensuring all three notes strike at the same time (or as close to
it as possible).

Whereas if you send MIDI data into the Disklavier, there is no notion of
delta time; notes are played as they are received (actually 500 ms after
being received, so that the Disklavier can compensate for varying solenoid
strike times at different velocity levels).  As MIDI is a serial protocol
at 31250 bits/sec, 10 bits/byte (8 + start bit + stop bit), a certain
amount of time is required to transmit each byte.

With notes being played as they're received, it's impossible to specify
that multiple notes be struck simultaneously.  Using running status, a 
three-note chord would require a minimum of almost 19 ms to transmit via
MIDI, or about 28 ms without.  A larger chord with note-offs and pedal data
mixed in could slow things much more.

Has anyone been able to tell a difference between playing the same material 
using the console and from a computer?

On the other hand, it could be that the convenience of storing one's music
library on the computer outweighs any concerns about timing accuracy.

On Thu, 28 Jun 2001, Robert E. Welcyng wrote:

> You've done a service to those with an affection for more of those pesky jewel
> cases.
> 
> As an alternative, some might wish to convert their PianoSoft material to MIDI
> and put the files on a CD-ROM.  Let's say you devote 600 MB of a CD-ROM to
> data.  That would allow you to store at least 800 each 720 KB albums on a single
> CD.  Of course, you'd put the files in appropriately labeled folders and name
> the files descriptively.  You'd devote a folder in the CD to playlists and use a
> sequencer to play your DKV.  Rather than search and shuffle through jewel cases,
> you use your Windows "Find" facility to locate files by composer, title, or
> performer.  You don't have to bother about returning disks and cases to their
> proper places.

I have used a DAT and Sound Forge to measure the timing accuracy of my Mark II. 
At note velocities over 40, the timing error 90% of the time is less than a
millisecond for single notes played in succession.  Statistically speaking, I
found no difference in timing accuracy between MIDI from a sequencer and E-SEQ
in the Mark II drive.  With older slower computers there can be noticeable
timing degradation of MIDI under Windows if you give Windows other jobs
concurrently.

Driving the DKV through the MIDI input does have another catch that is not a
problem with E-SEQ: You should take note of the pedaling.  If the MIDI file has
continuous pedaling directed to channel 3, you will want to set the DKV's MIDI
IN for "CH=HP" so that the DKV responds to the continuous pedal.  If only on/off
pedaling is present and directed to, say, channel 1, then you will want to set
the DKV for MIDI IN as "CH=01".  Of the PianoSoft disks published, some use one
scheme and some use the other.  (I've modified my files so that there is always
pedaling directed to channel 3.)

Putting all one's files on a CD is not going to be everyone's cup of tea.  It's
still a lot of work and the operation is not "iron ball" simple as with a
diskette.  Yet even operating with diskettes is not fool-proof--insert the
diskette upside down and, I understand, you will destroy the floppy drive.

"Mark A. Fontana" wrote:
> 
> I wonder if there might be a technical disadvantage to the approach of
> driving the Disklavier via MIDI from a computer.  Namely:
> 
> Suppose a piece contains a chord of three notes struck simultaneously.
> This can be represented in ESEQ or MIDI format as three note-on events with
> delta times of 0 between the second and third events.  The Disklavier's
> embedded controller can process a string of events like this as quickly as
> possible, ensuring all three notes strike at the same time (or as close to
> it as possible).
> 
> Whereas if you send MIDI data into the Disklavier, there is no notion of
> delta time; notes are played as they are received (actually 500 ms after
> being received, so that the Disklavier can compensate for varying solenoid
> strike times at different velocity levels).  As MIDI is a serial protocol
> at 31250 bits/sec, 10 bits/byte (8 + start bit + stop bit), a certain
> amount of time is required to transmit each byte.
> 
> With notes being played as they're received, it's impossible to specify
> that multiple notes be struck simultaneously.  Using running status, a
> three-note chord would require a minimum of almost 19 ms to transmit via
> MIDI, or about 28 ms without.  A larger chord with note-offs and pedal data
> mixed in could slow things much more.
> 
> Has anyone been able to tell a difference between playing the same material
> using the console and from a computer?
> 
> On the other hand, it could be that the convenience of storing one's music
> library on the computer outweighs any concerns about timing accuracy.
> 
> On Thu, 28 Jun 2001, Robert E. Welcyng wrote:
> 
> > You've done a service to those with an affection for more of those pesky jewel
> > cases.
> >
> > As an alternative, some might wish to convert their PianoSoft material to MIDI
> > and put the files on a CD-ROM.  Let's say you devote 600 MB of a CD-ROM to
> > data.  That would allow you to store at least 800 each 720 KB albums on a single
> > CD.  Of course, you'd put the files in appropriately labeled folders and name
> > the files descriptively.  You'd devote a folder in the CD to playlists and use a
> > sequencer to play your DKV.  Rather than search and shuffle through jewel cases,
> > you use your Windows "Find" facility to locate files by composer, title, or
> > performer.  You don't have to bother about returning disks and cases to their
> > proper places.
> 
> To Post a message to the group, send it to:   disklavier@...
> 
> To Post a private message to Todd Muncy, the group's founder and moderator, send it to:
> disklavier-owner@...
> 
> To reach our group's web site go to:
> http://Yahoogroups.com/group/disklavier
> 
> Todd's family web site was completely rewritten in June 2001 and contains some fun disklavier content and links to midi sites among other things, The url is:
> http://MuncyFamily.com
> 
> THINKING OF LEAVING THE GROUP?
> If you are thinking of unsubcribing because you are getting too much mail, go the the web site and change your email delivery option instead.  That will fix the problem, while maintaining your access to the group.  If you insist on leaving us completely send a blank email to:
> disklavier-unsubscribe@...
> 
> Know someone who wants to join?  Have them send a blank email to:
> disklavier-subscribe@... or give them this link:
> http://Yahoogroups.com/group/disklavier/join
> 
> 
> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/

-- 
Robert Welcyng
Anchorage, Alaska

Hello Everyone,

Regarding playback of MIDI files from the computer:

In a message dated 6/29/01 6:20:47 AM, mfontana@... writes:

<< With notes being played as they're received, it's impossible to specify
that multiple notes be struck simultaneously.  Using running status, a 
three-note chord would require a minimum of almost 19 ms to transmit via
MIDI, or about 28 ms without.  A larger chord with note-offs and pedal data
mixed in could slow things much more. >>

This is an interesting issue. Most MIDI devices--which receive and react in 
real-time--would have to play those 3 note-on messages one at a time. 
Although I don't know how the Disklavier handles this issue, I think that it 
should be able to use the 500 ms delay to its advantage.

In theory, if running status is used, the 500 ms delay should enable the 
Disklavier to understand that the hammers of the 3-note chord are intended to 
strike together. In other words, the structure of the running status message 
contains enough information to tell the Disklavier that the 2nd and 3rd notes 
should be played at the same time as the first note.

Regards,
PianoBench

On Fri, 29 Jun 2001 PianoBench@... wrote:

> Regarding playback of MIDI files from the computer:
> 
> In a message dated 6/29/01 6:20:47 AM, mfontana@... writes:
> 
> << With notes being played as they're received, it's impossible to specify
> that multiple notes be struck simultaneously.  Using running status, a 
> three-note chord would require a minimum of almost 19 ms to transmit via
> MIDI, or about 28 ms without.  A larger chord with note-offs and pedal data
> mixed in could slow things much more. >>
> 
> This is an interesting issue. Most MIDI devices--which receive and react in 
> real-time--would have to play those 3 note-on messages one at a time. 
> Although I don't know how the Disklavier handles this issue, I think that it 
> should be able to use the 500 ms delay to its advantage.
> 
> In theory, if running status is used, the 500 ms delay should enable the 
> Disklavier to understand that the hammers of the 3-note chord are intended to 
> strike together. In other words, the structure of the running status message 
> contains enough information to tell the Disklavier that the 2nd and 3rd notes 
> should be played at the same time as the first note.


I'm pretty certain that running status can't solve this problem.  Running
status only serves as a means of reducing MIDI bandwidth, basically
permitting subsequent events of the same MIDI command to be sent without
the command byte.  It doesn't imply anything about the timing of the
events.

As an example, three note-ons:

90 60 7F
90 61 7F
90 62 7F

could be sent with running status as:

90 60 7F
61 7F
62 7F

In both cases, the three notes will inevitably be struck one at a time as
the messages are received, even though we intended them to be struck
simultaneously.

There's nothing to prevent you from inserting a delay between events:

90 60 7F
(wait 300 ms)
90 61 7F
(wait 1500 ms)
90 62 7F

You still have to insert the proper amount of delay when sending this with
running status employed:

90 60 7F
(wait 300 ms)
61 7F
(wait 1500 ms)
62 7F


The Disklavier can't use its 500 ms processing delay to figure out when
notes were intended to be struck at the same time.  It just receives a
stream of bytes with no timing information beyond noting the time each byte
was received.  With the events arriving serially, it can't differentiate
between the case when the events were intended to occur simultaneously and
the case when they were truly intended to occur in sequence.  It could try 
and make a best guess, but it would sometimes be wrong...

One way to reduce the amount of error would be to increase the transmission 
rate; instead of using MIDI, use the TO HOST connector at the fastest speed
it will support.  What's the highest speed the Disklavier controller will
support?


--
Mark A. Fontana
Minneapolis, MN

Mark, you might wish to recheck your calculations.  As you say,

> MIDI is a serial protocol
> at 31250 bits/sec, 10 bits/byte (8 + start bit + stop bit), a certain
> amount of time is required to transmit each byte.

A three byte Note On message would contain 3*10 = 30 bits.  At 31,250 bits/sec,
that's only 960 microseconds (0.96 milliseconds) duration.  To put it in
perspective, in 960 micoseconds, sound in air travels only about a foot.  A
chord arpeggiated with successive notes separated by a millisecond will surely
be perceived as a single event.

-- 
Robert Welcyng
Anchorage, Alaska

How do you go about changing midi files to direct pedaling to channel 
3 (for continuous pedaling)?  I assume you use Cakewalk to do this.

Thanks.

--- In disklavier@y..., "Robert E. Welcyng" <rwelcyng@a...> wrote:
> I have used a DAT and Sound Forge to measure the timing accuracy of 
my Mark II. 
> At note velocities over 40, the timing error 90% of the time is 
less than a
> millisecond for single notes played in succession.  Statistically 
speaking, I
> found no difference in timing accuracy between MIDI from a 
sequencer and E-SEQ
> in the Mark II drive.  With older slower computers there can be 
noticeable
> timing degradation of MIDI under Windows if you give Windows other 
jobs
> concurrently.
> 
> Driving the DKV through the MIDI input does have another catch that 
is not a
> problem with E-SEQ: You should take note of the pedaling.  If the 
MIDI file has
> continuous pedaling directed to channel 3, you will want to set the 
DKV's MIDI
> IN for "CH=HP" so that the DKV responds to the continuous pedal.  
If only on/off
> pedaling is present and directed to, say, channel 1, then you will 
want to set
> the DKV for MIDI IN as "CH=01".  Of the PianoSoft disks published, 
some use one
> scheme and some use the other.  (I've modified my files so that 
there is always
> pedaling directed to channel 3.)
> 
> Putting all one's files on a CD is not going to be everyone's cup 
of tea.  It's
> still a lot of work and the operation is not "iron ball" simple as 
with a
> diskette.  Yet even operating with diskettes is not fool-proof--
insert the
> diskette upside down and, I understand, you will destroy the floppy 
drive.
> 
> "Mark A. Fontana" wrote:
> > 
> > I wonder if there might be a technical disadvantage to the 
approach of
> > driving the Disklavier via MIDI from a computer.  Namely:
> > 
> > Suppose a piece contains a chord of three notes struck 
simultaneously.
> > This can be represented in ESEQ or MIDI format as three note-on 
events with
> > delta times of 0 between the second and third events.  The 
Disklavier's
> > embedded controller can process a string of events like this as 
quickly as
> > possible, ensuring all three notes strike at the same time (or as 
close to
> > it as possible).
> > 
> > Whereas if you send MIDI data into the Disklavier, there is no 
notion of
> > delta time; notes are played as they are received (actually 500 
ms after
> > being received, so that the Disklavier can compensate for varying 
solenoid
> > strike times at different velocity levels).  As MIDI is a serial 
protocol
> > at 31250 bits/sec, 10 bits/byte (8 + start bit + stop bit), a 
certain
> > amount of time is required to transmit each byte.
> > 
> > With notes being played as they're received, it's impossible to 
specify
> > that multiple notes be struck simultaneously.  Using running 
status, a
> > three-note chord would require a minimum of almost 19 ms to 
transmit via
> > MIDI, or about 28 ms without.  A larger chord with note-offs and 
pedal data
> > mixed in could slow things much more.
> > 
> > Has anyone been able to tell a difference between playing the 
same material
> > using the console and from a computer?
> > 
> > On the other hand, it could be that the convenience of storing 
one's music
> > library on the computer outweighs any concerns about timing 
accuracy.
> > 
> > On Thu, 28 Jun 2001, Robert E. Welcyng wrote:
> > 
> > > You've done a service to those with an affection for more of 
those pesky jewel
> > > cases.
> > >
> > > As an alternative, some might wish to convert their PianoSoft 
material to MIDI
> > > and put the files on a CD-ROM.  Let's say you devote 600 MB of 
a CD-ROM to
> > > data.  That would allow you to store at least 800 each 720 KB 
albums on a single
> > > CD.  Of course, you'd put the files in appropriately labeled 
folders and name
> > > the files descriptively.  You'd devote a folder in the CD to 
playlists and use a
> > > sequencer to play your DKV.  Rather than search and shuffle 
through jewel cases,
> > > you use your Windows "Find" facility to locate files by 
composer, title, or
> > > performer.  You don't have to bother about returning disks and 
cases to their
> > > proper places.

I use three different CAL routines with Cakewalk.  The first routine copies from
track 1 to track 2 the on/off pedaling directed to channel 1 .  The second
routine converts the pedaling in the selected track (say, track 2) from channel
1 to channel 3.  The third routine affects the selected track (again, say, track
2) and limits the sustain pedal to no less than 24 and no greater than 80 (and
leaves all values between 24 and 80 intact).

The three routines could have been combined into a single one, but there are
times when you may wish to apply one separately or modify one such as when track
2 is already occupied with note events.  

The third routine addresses the annoyance of on/off pedal thumping.  To use it
successfully, your pedal must be in adjustment such that you get full damping at
a value of 24 and completely undamped ringing at 80.  Once the first sustain
pedal event is encountered, the pedal will modulate between 24 and 80 rather
than drop with a crash from 127 to 0.  This routine can be applied singly to
quiet a piece that already has continuous pedaling but is banging back and forth
between extremes.

Here are the CAL scripts:

-------------------------------------------

; CopyControllersToTrack2.CAL 


(do
	
	(TrackSelect 1 0)
	(ResetFilter 0 1)
	(SetFilterKind 0 NOTE 0)
	(SetFilterKind 0 KEYAFT 0)
	(SetFilterKind 0 PATCH 0)
	(SetFilterKind 0 CHANAFT 0)
	(SetFilterKind 0 WHEEL 0)
	(SetFilterKind 0 RPN 0)
	(SetFilterKind 0 NRPN 0)
	(SetFilterKind 0 SYSX 0)
	(SetFilterKind 0 SYSXDATA 0)
	(SetFilterKind 0 TEXT 0)
	(SetFilterKind 0 LYRIC 0)
	(SetFilterKind 0 WAVE 0)
	(SetFilterKind 0 MCI 0)
	(SetFilterKind 0 EXPRESSION 0)
	(SetFilterKind 0 CHORD 0)
	(SetFilterKind 0 HAIRPIN 0)
	(EditCopy40 1 1 1 0 0 0 )
	(EditPaste40 0 1 1 1 215106 0 1 1 1 0 0 0 0 0 )
	(ResetFilter 0 1)
	(SetFilterRange 0 13 1 0 16384)
	(TrackSelect 1 1)
	(TrackSelect 0 1)
		
)

-------------------------------------------
; SetChannel to 3.cal

(do
	(TrackChannel 2 1)
	(forEachEvent
		(= Event.Chan 2)
	)
)

-------------------------------------------
;24-80.cal
;Limits sustain pedal to no less than 24
;and no greater than 80

(do
	(forEachEvent
		(if (== Control.Num 64)
			(do
				(if (> Control.Val 80)
					(= Control.Val 80))
				(if (< Control.Val 24)
					(= Control.Val 24))
			)
		)
	)
)

-------------------------------------------
joannagalt@... wrote:
> 
> How do you go about changing midi files to direct pedaling to channel
> 3 (for continuous pedaling)?  I assume you use Cakewalk to do this.
> 
> Thanks.
> 
> --- In disklavier@y..., "Robert E. Welcyng" <rwelcyng@a...> wrote:
> > I have used a DAT and Sound Forge to measure the timing accuracy of
> my Mark II.
> > At note velocities over 40, the timing error 90% of the time is
> less than a
> > millisecond for single notes played in succession.  Statistically
> speaking, I
> > found no difference in timing accuracy between MIDI from a
> sequencer and E-SEQ
> > in the Mark II drive.  With older slower computers there can be
> noticeable
> > timing degradation of MIDI under Windows if you give Windows other
> jobs
> > concurrently.
> >
> > Driving the DKV through the MIDI input does have another catch that
> is not a
> > problem with E-SEQ: You should take note of the pedaling.  If the
> MIDI file has
> > continuous pedaling directed to channel 3, you will want to set the
> DKV's MIDI
> > IN for "CH=HP" so that the DKV responds to the continuous pedal.
> If only on/off
> > pedaling is present and directed to, say, channel 1, then you will
> want to set
> > the DKV for MIDI IN as "CH=01".  Of the PianoSoft disks published,
> some use one
> > scheme and some use the other.  (I've modified my files so that
> there is always
> > pedaling directed to channel 3.)
> >
> > Putting all one's files on a CD is not going to be everyone's cup
> of tea.  It's
> > still a lot of work and the operation is not "iron ball" simple as
> with a
> > diskette.  Yet even operating with diskettes is not fool-proof--
> insert the
> > diskette upside down and, I understand, you will destroy the floppy
> drive.
> >
> > "Mark A. Fontana" wrote:
> > >
> > > I wonder if there might be a technical disadvantage to the
> approach of
> > > driving the Disklavier via MIDI from a computer.  Namely:
> > >
> > > Suppose a piece contains a chord of three notes struck
> simultaneously.
> > > This can be represented in ESEQ or MIDI format as three note-on
> events with
> > > delta times of 0 between the second and third events.  The
> Disklavier's
> > > embedded controller can process a string of events like this as
> quickly as
> > > possible, ensuring all three notes strike at the same time (or as
> close to
> > > it as possible).
> > >
> > > Whereas if you send MIDI data into the Disklavier, there is no
> notion of
> > > delta time; notes are played as they are received (actually 500
> ms after
> > > being received, so that the Disklavier can compensate for varying
> solenoid
> > > strike times at different velocity levels).  As MIDI is a serial
> protocol
> > > at 31250 bits/sec, 10 bits/byte (8 + start bit + stop bit), a
> certain
> > > amount of time is required to transmit each byte.
> > >
> > > With notes being played as they're received, it's impossible to
> specify
> > > that multiple notes be struck simultaneously.  Using running
> status, a
> > > three-note chord would require a minimum of almost 19 ms to
> transmit via
> > > MIDI, or about 28 ms without.  A larger chord with note-offs and
> pedal data
> > > mixed in could slow things much more.
> > >
> > > Has anyone been able to tell a difference between playing the
> same material
> > > using the console and from a computer?
> > >
> > > On the other hand, it could be that the convenience of storing
> one's music
> > > library on the computer outweighs any concerns about timing
> accuracy.
> > >
> > > On Thu, 28 Jun 2001, Robert E. Welcyng wrote:
> > >
> > > > You've done a service to those with an affection for more of
> those pesky jewel
> > > > cases.
> > > >
> > > > As an alternative, some might wish to convert their PianoSoft
> material to MIDI
> > > > and put the files on a CD-ROM.  Let's say you devote 600 MB of
> a CD-ROM to
> > > > data.  That would allow you to store at least 800 each 720 KB
> albums on a single
> > > > CD.  Of course, you'd put the files in appropriately labeled
> folders and name
> > > > the files descriptively.  You'd devote a folder in the CD to
> playlists and use a
> > > > sequencer to play your DKV.  Rather than search and shuffle
> through jewel cases,
> > > > you use your Windows "Find" facility to locate files by
> composer, title, or
> > > > performer.  You don't have to bother about returning disks and
> cases to their
> > > > proper places.
> 
> To Post a message to the group, send it to:   disklavier@...
> 
> To Post a private message to Todd Muncy, the group's founder and moderator, send it to:
> disklavier-owner@...
> 
> To reach our group's web site go to:
> http://Yahoogroups.com/group/disklavier
> 
> Todd's family web site was completely rewritten in June 2001 and contains some fun disklavier content and links to midi sites among other things, The url is:
> http://MuncyFamily.com
> 
> THINKING OF LEAVING THE GROUP?
> If you are thinking of unsubcribing because you are getting too much mail, go the the web site and change your email delivery option instead.  That will fix the problem, while maintaining your access to the group.  If you insist on leaving us completely send a blank email to:
> disklavier-unsubscribe@...
> 
> Know someone who wants to join?  Have them send a blank email to:
> disklavier-subscribe@... or give them this link:
> http://Yahoogroups.com/group/disklavier/join
> 
> 
> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/

-- 
Robert Welcyng
Anchorage, Alaska

Robert, thanks for the CALs. I tried all 3 separately and I got them 
to direct the pedal to channel 3. I'll discuss your suggested pedal 
settings with my RPT.

Regards. 

--- In disklavier@y..., "Robert E. Welcyng" <rwelcyng@a...> wrote:
> I use three different CAL routines with Cakewalk.  The first 
routine copies from
> track 1 to track 2 the on/off pedaling directed to channel 1 .  The 
second
> routine converts the pedaling in the selected track (say, track 2) 
from channel
> 1 to channel 3.  The third routine affects the selected track 
(again, say, track
> 2) and limits the sustain pedal to no less than 24 and no greater 
than 80 (and
> leaves all values between 24 and 80 intact).
> 
> The three routines could have been combined into a single one, but 
there are
> times when you may wish to apply one separately or modify one such 
as when track
> 2 is already occupied with note events.  
> 
> The third routine addresses the annoyance of on/off pedal 
thumping.  To use it
> successfully, your pedal must be in adjustment such that you get 
full damping at
> a value of 24 and completely undamped ringing at 80.  Once the 
first sustain
> pedal event is encountered, the pedal will modulate between 24 and 
80 rather
> than drop with a crash from 127 to 0.  This routine can be applied 
singly to
> quiet a piece that already has continuous pedaling but is banging 
back and forth
> between extremes.
> 
> Here are the CAL scripts:
> 
> -------------------------------------------
> 
> ; CopyControllersToTrack2.CAL 
> 
> 
> (do
> 	
> 	(TrackSelect 1 0)
> 	(ResetFilter 0 1)
> 	(SetFilterKind 0 NOTE 0)
> 	(SetFilterKind 0 KEYAFT 0)
> 	(SetFilterKind 0 PATCH 0)
> 	(SetFilterKind 0 CHANAFT 0)
> 	(SetFilterKind 0 WHEEL 0)
> 	(SetFilterKind 0 RPN 0)
> 	(SetFilterKind 0 NRPN 0)
> 	(SetFilterKind 0 SYSX 0)
> 	(SetFilterKind 0 SYSXDATA 0)
> 	(SetFilterKind 0 TEXT 0)
> 	(SetFilterKind 0 LYRIC 0)
> 	(SetFilterKind 0 WAVE 0)
> 	(SetFilterKind 0 MCI 0)
> 	(SetFilterKind 0 EXPRESSION 0)
> 	(SetFilterKind 0 CHORD 0)
> 	(SetFilterKind 0 HAIRPIN 0)
> 	(EditCopy40 1 1 1 0 0 0 )
> 	(EditPaste40 0 1 1 1 215106 0 1 1 1 0 0 0 0 0 )
> 	(ResetFilter 0 1)
> 	(SetFilterRange 0 13 1 0 16384)
> 	(TrackSelect 1 1)
> 	(TrackSelect 0 1)
> 		
> )
> 
> -------------------------------------------
> ; SetChannel to 3.cal
> 
> (do
> 	(TrackChannel 2 1)
> 	(forEachEvent
> 		(= Event.Chan 2)
> 	)
> )
> 
> -------------------------------------------
> ;24-80.cal
> ;Limits sustain pedal to no less than 24
> ;and no greater than 80
> 
> (do
> 	(forEachEvent
> 		(if (== Control.Num 64)
> 			(do
> 				(if (> Control.Val 80)
> 					(= Control.Val 80))
> 				(if (< Control.Val 24)
> 					(= Control.Val 24))
> 			)
> 		)
> 	)
> )
> 
> -------------------------------------------
> joannagalt@y... wrote:
> > 
> > How do you go about changing midi files to direct pedaling to 
channel
> > 3 (for continuous pedaling)?  I assume you use Cakewalk to do 
this.
> > 
> > Thanks.
> > 
> > --- In disklavier@y..., "Robert E. Welcyng" <rwelcyng@a...> wrote:
> > > I have used a DAT and Sound Forge to measure the timing 
accuracy of
> > my Mark II.
> > > At note velocities over 40, the timing error 90% of the time is
> > less than a
> > > millisecond for single notes played in succession.  
Statistically
> > speaking, I
> > > found no difference in timing accuracy between MIDI from a
> > sequencer and E-SEQ
> > > in the Mark II drive.  With older slower computers there can be
> > noticeable
> > > timing degradation of MIDI under Windows if you give Windows 
other
> > jobs
> > > concurrently.
> > >
> > > Driving the DKV through the MIDI input does have another catch 
that
> > is not a
> > > problem with E-SEQ: You should take note of the pedaling.  If 
the
> > MIDI file has
> > > continuous pedaling directed to channel 3, you will want to set 
the
> > DKV's MIDI
> > > IN for "CH=HP" so that the DKV responds to the continuous pedal.
> > If only on/off
> > > pedaling is present and directed to, say, channel 1, then you 
will
> > want to set
> > > the DKV for MIDI IN as "CH=01".  Of the PianoSoft disks 
published,
> > some use one
> > > scheme and some use the other.  (I've modified my files so that
> > there is always
> > > pedaling directed to channel 3.)
> > >
> > > Putting all one's files on a CD is not going to be everyone's 
cup
> > of tea.  It's
> > > still a lot of work and the operation is not "iron ball" simple 
as
> > with a
> > > diskette.  Yet even operating with diskettes is not fool-proof--
> > insert the
> > > diskette upside down and, I understand, you will destroy the 
floppy
> > drive.
> > >
> > > "Mark A. Fontana" wrote:
> > > >
> > > > I wonder if there might be a technical disadvantage to the
> > approach of
> > > > driving the Disklavier via MIDI from a computer.  Namely:
> > > >
> > > > Suppose a piece contains a chord of three notes struck
> > simultaneously.
> > > > This can be represented in ESEQ or MIDI format as three note-
on
> > events with
> > > > delta times of 0 between the second and third events.  The
> > Disklavier's
> > > > embedded controller can process a string of events like this 
as
> > quickly as
> > > > possible, ensuring all three notes strike at the same time 
(or as
> > close to
> > > > it as possible).
> > > >
> > > > Whereas if you send MIDI data into the Disklavier, there is no
> > notion of
> > > > delta time; notes are played as they are received (actually 
500
> > ms after
> > > > being received, so that the Disklavier can compensate for 
varying
> > solenoid
> > > > strike times at different velocity levels).  As MIDI is a 
serial
> > protocol
> > > > at 31250 bits/sec, 10 bits/byte (8 + start bit + stop bit), a
> > certain
> > > > amount of time is required to transmit each byte.
> > > >
> > > > With notes being played as they're received, it's impossible 
to
> > specify
> > > > that multiple notes be struck simultaneously.  Using running
> > status, a
> > > > three-note chord would require a minimum of almost 19 ms to
> > transmit via
> > > > MIDI, or about 28 ms without.  A larger chord with note-offs 
and
> > pedal data
> > > > mixed in could slow things much more.
> > > >
> > > > Has anyone been able to tell a difference between playing the
> > same material
> > > > using the console and from a computer?
> > > >
> > > > On the other hand, it could be that the convenience of storing
> > one's music
> > > > library on the computer outweighs any concerns about timing
> > accuracy.
> > > >
> > > > On Thu, 28 Jun 2001, Robert E. Welcyng wrote:
> > > >
> > > > > You've done a service to those with an affection for more of
> > those pesky jewel
> > > > > cases.
> > > > >
> > > > > As an alternative, some might wish to convert their 
PianoSoft
> > material to MIDI
> > > > > and put the files on a CD-ROM.  Let's say you devote 600 MB 
of
> > a CD-ROM to
> > > > > data.  That would allow you to store at least 800 each 720 
KB
> > albums on a single
> > > > > CD.  Of course, you'd put the files in appropriately labeled
> > folders and name
> > > > > the files descriptively.  You'd devote a folder in the CD to
> > playlists and use a
> > > > > sequencer to play your DKV.  Rather than search and shuffle
> > through jewel cases,
> > > > > you use your Windows "Find" facility to locate files by
> > composer, title, or
> > > > > performer.  You don't have to bother about returning disks 
and
> > cases to their
> > > > > proper places.
> > 
> > To Post a message to the group, send it to:   disklavier@Y...
> > 
> > To Post a private message to Todd Muncy, the group's founder and 
moderator, send it to:
> > disklavier-owner@Y...
> > 
> > To reach our group's web site go to:
> > http://Yahoogroups.com/group/disklavier
> > 
> > Todd's family web site was completely rewritten in June 2001 and 
contains some fun disklavier content and links to midi sites among 
other things, The url is:
> > http://MuncyFamily.com
> > 
> > THINKING OF LEAVING THE GROUP?
> > If you are thinking of unsubcribing because you are getting too 
much mail, go the the web site and change your email delivery option 
instead.  That will fix the problem, while maintaining your access to 
the group.  If you insist on leaving us completely send a blank email 
to:
> > disklavier-unsubscribe@y...
> > 
> > Know someone who wants to join?  Have them send a blank email to:
> > disklavier-subscribe@e... or give them this link:
> > http://Yahoogroups.com/group/disklavier/join
> > 
> > 
> > Your use of Yahoo! Groups is subject to 
http://docs.yahoo.com/info/terms/

> 
> -- 
> Robert Welcyng
> Anchorage, Alaska