Disklavier

Is there an easy way to change the channel of the data in a midi file. For some reason many files don't play on my disklavier because the data seems to be on the incorrect channel... Many thanks!

Your Disklavier plays your piano keys on whatever is on Channels 1 and 2.  If you connect a speaker, and have a built in tone generator, you would probably hear other MIDI instruments as well.

There are 2 ways to check your files.  You may need to visit the www.midiplayertools.com website for details.

The first way is to look at your users manual to check the MIDI OUT settings and use something like L=1 and R=# or something like that.  Also, while the file in question is playing, you can simply push the right arrow key on the control box (->) and see if any data is blinking on other channels beside 1 and 2 (L and R)

The other way is to use 3rd party software to change the channel assignment.  Converting the file to MIDI 0 puts all the tracks on Chanel 1.
 Hope this helps.

Carol Beigel


Sent from my iPhone

> On Aug 3, 2019, at 9:33 AM, carlspost2@... [disklavier] <disklavier@yahoogroups.com> wrote:
> 
> Is there an easy way to change the channel of the data in a midi file. For some reason many files don't play on my disklavier because the data seems to be on the incorrect channel... Many thanks! 
> 
> ------------------------------------
> Posted by: carlspost2@yahoo.com.au
> ------------------------------------
> 
> 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://groups.yahoo.com/neo/groups/disklavier/info
> 
> 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@...
> ------------------------------------
> 
> Yahoo Groups Links
> 
> 
>

Thanks Ian,I wish it was this simple. I have tried various programs but without success. I usually use Vanbasco to play the midi files. 
It seems that only files using channel 1 work ... Any files with channel 0 does not work.. even if  I select the cable output to the piano. 
Cheers.    On Sunday, 4 August 2019, 06:48:37 pm AEST, Ian wam@... [disklavier] <disklavier@yahoogroups.com> wrote:  
 
 Carl,
Channel probably has little to do with it. Output setting is more likely the problem. Whatever player you are using to send the signal to the piano should have an 'Output' button selector, within which you can select to play either thru your cable to the piano or thru the synthesiser in your computer. Simply switch from one to the other, and then back. It resets and works for me every time.

Ian Williamson




On 04/08/2019, at 9:53 AM, carlspost2@... [disklavier] wrote:

   
Thanks you for your replies Mark and Carol. I am still a little stumped on this one.

Basically I am having trouble with files downloaded from the http://www.piano-e-competition.com/ website.It seems that there is a difference in the available files between certain years of the competition.For example all of the 2002 files work perfectly, however those from 2014 (and other years) do not. From what I can tell they  both use the same channel (but maybe I reading things incorrectly)
I have attached a sample of one from each year.  Could you possibly shed some light on what the difference between them is? It would be greatly appreciated.Carl
  <2014.MID><2002.mid>

Carl, it is that simple for me using Mac and MidiSwing. 
The 2014 file did not work for me, just as it did not work for you. I reset my Output and now it does work!
Look for the Output on Van Basco and try it. You mention trying various programs, but not that you tried resetting that Output button.
Don't confuse MidiType 1 with Channel 1, all files to be played on Yamaha need to be Type 0, NOT Type 1. Channel 1 is the channel within a Type 0 file which plays the Piano 'live'. Any other notes in other channels in the same file will play various synthesised instruments and drums thru the speakers to accompany the actual piano. Try the attached file and see what I'm talking about. It is set up for Disklavier.


Ian Williamson

On 04/08/2019, at 7:28 PM, 'carlspost2@...' carlspost2@... [disklavier] wrote:

> 
> Thanks Ian,
> I wish it was this simple. I have tried various programs but without success. I usually use Vanbasco to play the midi files. 
> 
> It seems that only files using channel 1 work ... Any files with channel 0 does not work.. even if  I select the cable output to the piano. 
> 
> Cheers.
> On Sunday, 4 August 2019, 06:48:37 pm AEST, Ian wam@....au [disklavier] <disklavier@yahoogroups.com> wrote:
> 
> 
> Carl,
> 
> Channel probably has little to do with it. Output setting is more likely the problem. Whatever player you are using to send the signal to the piano should have an 'Output' button selector, within which you can select to play either thru your cable to the piano or thru the synthesiser in your computer. Simply switch from one to the other, and then back. It resets and works for me every time.
> 
> 
> Ian Williamson
> 
> 
> 
> 
> 
> On 04/08/2019, at 9:53 AM, carlspost2@... [disklavier] wrote:
> 
>>  
>> Thanks you for your replies Mark and Carol. I am still a little stumped on this one.
>> 
>> 
>> Basically I am having trouble with files downloaded from the http://www.piano-e-competition.com/ website.
>> It seems that there is a difference in the available files between certain years of the competition.
>> For example all of the 2002 files work perfectly, however those from 2014 (and other years) do not. 
>> From what I can tell they  both use the same channel (but maybe I reading things incorrectly)
>> 
>> I have attached a sample of one from each year.  Could you possibly shed some light on what the difference between them is? It would be greatly appreciated.
>> Carl
>> 
>> <2014.MID><2002.mid>
> 
> 
> 
>

Good afternoon, everyone.

A clarification regarding Type 0 and Type 1 Standard MIDI Files (SMFs):

Pre-Mark IIXG Disklaviers require the recording to be in Type 0 format when played from media inserted into the piano. An updated Mark IIXG or later Disklavier can read both types of MIDI files.

When playing back a MIDI file from an external source—such as a computer or mobile device, the MIDI file type is irrelevant. Playback of either type of MIDI file results in the same MIDI stream sent to the Disklavier.

Regards,
Pianobench

> On Aug 4, 2019, at 7:55 AM, Ian wam@... [disklavier] <disklavier@yahoogroups.com> wrote:
> 
> Carl, it is that simple for me using Mac and MidiSwing. 
> The 2014 file did not work for me, just as it did not work for you. I reset my Output and now it does work!
> Look for the Output on Van Basco and try it. You mention trying various programs, but not that you tried resetting that Output button.
> Don't confuse MidiType 1 with Channel 1, all files to be played on Yamaha need to be Type 0, NOT Type 1. Channel 1 is the channel within a Type 0 file which plays the Piano 'live'. Any other notes in other channels in the same file will play various synthesised instruments and drums thru the speakers to accompany the actual piano. Try the attached file and see what I'm talking about. It is set up for Disklavier.
> <PastedGraphic-8.pdf>
> 
> Ian Williamson
> 
> <O Come, O Come Emmanuel.mid>
> 
> 
> 
> On 04/08/2019, at 7:28 PM, 'carlspost2@yahoo.com.au <mailto:'carlspost2@...>' carlspost2@... <mailto:carlspost2@...> [disklavier] wrote:
> 
>> 
>> Thanks Ian,
>> I wish it was this simple. I have tried various programs but without success. I usually use Vanbasco to play the midi files. 
>> 
>> It seems that only files using channel 1 work ... Any files with channel 0 does not work.. even if  I select the cable output to the piano. 
>> 
>> Cheers.
>> On Sunday, 4 August 2019, 06:48:37 pm AEST, Ian wam@... <mailto:wam@...> [disklavier] <disklavier@yahoogroups.com <mailto:disklavier@yahoogroups.com>> wrote:
>> 
>> 
>> Carl,
>> 
>> Channel probably has little to do with it. Output setting is more likely the problem. Whatever player you are using to send the signal to the piano should have an 'Output' button selector, within which you can select to play either thru your cable to the piano or thru the synthesiser in your computer. Simply switch from one to the other, and then back. It resets and works for me every time.
>> 
>> 
>> Ian Williamson
>> 
>> 
>> 
>> 
>> 
>> On 04/08/2019, at 9:53 AM, carlspost2@...m.au <mailto:carlspost2@yahoo..com.au> [disklavier] wrote:
>> 
>>>  
>>> Thanks you for your replies Mark and Carol. I am still a little stumped on this one.
>>> 
>>> 
>>> Basically I am having trouble with files downloaded from the http://www.piano-e-competition.com/ <http://www.piano-e-competition.com/> website.
>>> It seems that there is a difference in the available files between certain years of the competition.
>>> For example all of the 2002 files work perfectly, however those from 2014 (and other years) do not. 
>>> From what I can tell they  both use the same channel (but maybe I reading things incorrectly)
>>> 
>>> I have attached a sample of one from each year.  Could you possibly shed some light on what the difference between them is? It would be greatly appreciated.
>>> Carl
>>> 
>>> <2014.MID><2002.mid>
>> 
>> 
>> 
>

Hi Carl, I examined the events in 2002.mid and 2014.mid.� Both are type 
0 MIDI files, and it looks like the actual piano performance data is 
arranged similarly; all piano events are on MIDI channel 0 and have 
incremental pedaling.� Both files also include polyphonic aftertouch 
data, part of Yamaha's XP extensions.� Both set the volume to 100 and 
specify piano for the channel used for the piano performance data.� 
Seems like the basics are satisfied.� But the files differ in that 
2014.mid includes some additional non-performance-related events at the 
start, such as some sequencer-specific events and additional/different 
SYSEX messages beyond what's in 2002.mid.� Maybe these extra events are 
tripping up your particular model of Disklavier or being misinterpreted 
by external playback software.� I would suggest using sequencing 
software to create a couple of different versions of 2014.mid in which 
you try removing some of these events.� If you do this methodically, you 
can determine which events are causing the problem.� (Another way to 
edit out these events would be to use one of those programs that 
converts a MIDI file to an editable text file, which you'd then edit and 
convert back to a MIDI file.� That approach would eliminate the 
possibility of sequencing software trying to be helpful and introducing 
new problems.)

In the case where 2014.mid fails to play, can you immediately play a 
file that works (like 2002.mid) afterwards without touching the 
Disklavier (no need to power cycle or otherwise reset it)?

Does 2014.mid work OK if you play it directly on the Disklavier (i.e. 
have the Disklavier itself interpret the file instead of using external 
software like VanBasco)?

Mark Fontana

On 8/3/19 6:53 PM, carlspost2@... [disklavier] wrote:
> Basically I am having trouble with files downloaded from the 
> http://www.piano-e-competition.com/�website.
> It seems that there is a difference in the available files between 
> certain years of the competition.
> For example all of the 2002 files work perfectly, however those from 
> 2014 (and other years) do not.� . . .
> I have attached a sample of one from each year. Could you possibly 
> shed some light on what the difference between them is? It would be 
> greatly appreciated.

Thank you for your explanation of how this software can work.  Except for changing a note‘s pitch and timing using Logic, I have never been anywhere near competent in using sequencing software.

What software do you use that you can see all those events in a MIDI file?

Can you recommend a software program that does that MIDI to text and back again function?

As always, I am so grateful you wrote the utility for converting the ESEQ to MIDI files on the floppy disks people purchased for their Disklavier so they can continue to enjoy their music on today‘s formats.

Carol Beigel


Sent from my iPhone

> On Aug 6, 2019, at 3:43 AM, Mark Fontana mark@kinura.net [disklavier] <disklavier@yahoogroups.com> wrote:
> 
> 
> 
> 
> Hi Carl, I examined the events in 2002.mid and 2014.mid.  Both are type 0 MIDI files, and it looks like the actual piano performance data is arranged similarly; all piano events are on MIDI channel 0 and have incremental pedaling.  Both files also include polyphonic aftertouch data, part of Yamaha's XP extensions.  Both set the volume to 100 and specify piano for the channel used for the piano performance data.  Seems like the basics are satisfied.  But the files differ in that 2014.mid includes some additional non-performance-related events at the start, such as some sequencer-specific events and additional/different SYSEX messages beyond what's in 2002.mid.  Maybe these extra events are tripping up your particular model of Disklavier or being misinterpreted by external playback software.  I would suggest using sequencing software to create a couple of different versions of 2014.mid in which you try removing some of these events.  If you do this methodically, you can determine which events are causing the problem.  (Another way to edit out these events would be to use one of those programs that converts a MIDI file to an editable text file, which you'd then edit and convert back to a MIDI file.  That approach would eliminate the possibility of sequencing software trying to be helpful and introducing new problems.)
> 
> In the case where 2014.mid fails to play, can you immediately play a file that works (like 2002.mid) afterwards without touching the Disklavier (no need to power cycle or otherwise reset it)?
> 
> Does 2014.mid work OK if you play it directly on the Disklavier (i.e. have the Disklavier itself interpret the file instead of using external software like VanBasco)?
> 
> Mark Fontana
> 
> 
>> On 8/3/19 6:53 PM, carlspost2@... [disklavier] wrote:
>> Basically I am having trouble with files downloaded from the http://www.piano-e-competition.com/ website.
>> It seems that there is a difference in the available files between certain years of the competition.
>> For example all of the 2002 files work perfectly, however those from 2014 (and other years) do not.  . . .
>> I have attached a sample of one from each year.  Could you possibly shed some light on what the difference between them is? It would be greatly appreciated.
> 
> 
> 
>

Hi Mark

What program do you use to view the SYSEX messages?  I can’t seem to find them using Cakewalk Pro Audio 9.

 

Kind regards

 

Geoff Ward

From: disklavier@yahoogroups.com [mailto:disklavier@yahoogroups.com] 
Sent: Tuesday, 6 August 2019 5:44 PM
To: disklavier@yahoogroups.com
Subject: Re: [disklavier] Re: Midi File Channel

 

  


Hi Carl, I examined the events in 2002.mid and 2014.mid.  Both are type 0 MIDI files, and it looks like the actual piano performance data is arranged similarly; all piano events are on MIDI channel 0 and have incremental pedaling.  Both files also include polyphonic aftertouch data, part of Yamaha's XP extensions.  Both set the volume to 100 and specify piano for the channel used for the piano performance data.  Seems like the basics are satisfied.  But the files differ in that 2014.mid includes some additional non-performance-related events at the start, such as some sequencer-specific events and additional/different SYSEX messages beyond what's in 2002.mid.  Maybe these extra events are tripping up your particular model of Disklavier or being misinterpreted by external playback software.  I would suggest using sequencing software to create a couple of different versions of 2014.mid in which you try removing some of these events.  If you do this methodically, you can determine which events are causing the problem.  (Another way to edit out these events would be to use one of those programs that converts a MIDI file to an editable text file, which you'd then edit and convert back to a MIDI file.  That approach would eliminate the possibility of sequencing software trying to be helpful and introducing new problems.)

In the case where 2014.mid fails to play, can you immediately play a file that works (like 2002.mid) afterwards without touching the Disklavier (no need to power cycle or otherwise reset it)?

Does 2014.mid work OK if you play it directly on the Disklavier (i.e. have the Disklavier itself interpret the file instead of using external software like VanBasco)?

Mark Fontana



On 8/3/19 6:53 PM, carlspost2@... <mailto:carlspost2@...>  [disklavier] wrote:

  Basically I am having trouble with files downloaded from the http://www.piano-e-competition.com/ website. 

It seems that there is a difference in the available files between certain years of the competition.

For example all of the 2002 files work perfectly, however those from 2014 (and other years) do not.  . . .

I have attached a sample of one from each year.  Could you possibly shed some light on what the difference between them is? It would be greatly appreciated.

To inspect the events in MIDI files, I tend to use an ancient MusicQuest 
command line program from the early 1990s, strictly out of habit, but a 
quick and easy way would be to use this web-based tool:

http://valentin.dasdeck.com/midi/mid2txt.php 
<http://valentin.dasdeck.com/midi/mid2txt.php>

Some of its event names diverge from more accepted MIDI terminology 
("Par" = Control Change, 0xBn),� ("PoPr" = Aftertouch (Polyphonic 
Pressure), 0xAn) but this still looks reasonably useful for a quick 
inspection.

Some programs for converting back and forth between MIDI files and 
text-based formats are:

https://sourceforge.net/projects/mf2t/
https://www.fourmilab.ch/webtools/midicsv/
http://www.archduke.org/midi/
https://github.com/mtolly/midiscript

I haven't used any of them personally, but they all look to require some 
degree of comfort using command-line tools.
I tend to write little C or Perl programs to manipulate MIDI files when 
the need arises.

Mark Fontana

On 8/6/19 6:39 AM, Carol Beigel carol@... [disklavier] wrote:
>
> Thank you for your explanation of how this software can work. �Except 
> for changing a note\u2018s pitch and timing using Logic, I have never been 
> anywhere near competent in using sequencing software.
>
>
> What software do you use that you can see all those events in a MIDI file?
>
> Can you recommend a software program that does that MIDI to text and 
> back again function?
>
> As always, I am so grateful you wrote the utility for converting the 
> ESEQ to MIDI files on the floppy disks people purchased for their 
> Disklavier so they can continue to enjoy their music on today\u2018s formats.
>
> Carol Beigel
> Web Bug from 
> http://geo.yahoo.com/serv?s=97359714/grpId=1453643/grpspId=1705032012/msgId=13582/stime=1565095637 
>
> Web Bug from 
> http://y.analytics.yahoo.com/fpc.pl?ywarid=515FB27823A7407E&a=10001310322279&js=no&resp=img 
>
>

I also write little perl programs to do this stuff. My list midi events program lists sysex messages as well as most others

On August 6, 2019 3:50:26 PM MST, "Mark Fontana mark@... [disklavier]" <disklavier@yahoogroups.com> wrote:
>
>To inspect the events in MIDI files, I tend to use an ancient
>MusicQuest 
>command line program from the early 1990s, strictly out of habit, but a
>
>quick and easy way would be to use this web-based tool:
>
>http://valentin.dasdeck.com/midi/mid2txt.php 
><http://valentin.dasdeck.com/midi/mid2txt.php>
>
>Some of its event names diverge from more accepted MIDI terminology 
>("Par" = Control Change, 0xBn),  ("PoPr" = Aftertouch (Polyphonic 
>Pressure), 0xAn) but this still looks reasonably useful for a quick 
>inspection.
>
>Some programs for converting back and forth between MIDI files and 
>text-based formats are:
>
>https://sourceforge.net/projects/mf2t/
>https://www.fourmilab.ch/webtools/midicsv/
>http://www.archduke.org/midi/
>https://github.com/mtolly/midiscript
>
>I haven't used any of them personally, but they all look to require
>some 
>degree of comfort using command-line tools.
>I tend to write little C or Perl programs to manipulate MIDI files when
>
>the need arises.
>
>Mark Fontana
>
>
>On 8/6/19 6:39 AM, Carol Beigel carol@... [disklavier] wrote:
>>
>> Thank you for your explanation of how this software can work.  Except
>
>> for changing a note‘s pitch and timing using Logic, I have never been
>
>> anywhere near competent in using sequencing software.
>>
>>
>> What software do you use that you can see all those events in a MIDI
>file?
>>
>> Can you recommend a software program that does that MIDI to text and 
>> back again function?
>>
>> As always, I am so grateful you wrote the utility for converting the 
>> ESEQ to MIDI files on the floppy disks people purchased for their 
>> Disklavier so they can continue to enjoy their music on today‘s
>formats.
>>
>> Carol Beigel
>> Web Bug from 
>>
>http://geo.yahoo.com/serv?s=97359714/grpId=1453643/grpspId=1705032012/msgId=13582/stime=1565095637
>
>>
>> Web Bug from 
>>
>http://y.analytics.yahoo.com/fpc.pl?ywarid=515FB27823A7407E&a=10001310322279&js=no&resp=img
>
>>
>> 

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

Thank you again for all of your suggestions. I have looked at your various programs and have been helped a great deal. 
From what I have been able to deduce, it seems that the program I use to play the files (namely vanBasco) is the problem.
If I open the files in other programs (such as KaraFunPlayer 2)  and select the midi out cable to my disklavier , the files seem to play just fine.
So I am at a bit of a loss as to what was the problem in the first place!
I really appreciate your help in offering suggestions. 
Cheers!Carl


    On Wednesday, 7 August 2019, 08:27:08 pm AEST, Spencer Chase lists@... [disklavier] <disklavier@yahoogroups.com> wrote:  
 
     
 I also write little perl programs to do this stuff. My list midi events program lists sysex messages as well as most others


On August 6, 2019 3:50:26 PM MST, "Mark Fontana mark@... [disklavier]" <disklavier@yahoogroups.com> wrote:
   
 
 To inspect the events in MIDI files, I tend to use an ancient MusicQuest command line program from the early 1990s, strictly out of habit, but a quick and easy way would be to use this web-based tool:
 
 http://valentin.dasdeck.com/midi/mid2txt.php
 
 Some of its event names diverge from more accepted MIDI terminology ("Par" = Control Change, 0xBn),  ("PoPr" = Aftertouch (Polyphonic Pressure), 0xAn) but this still looks reasonably useful for a quick inspection.
 
 Some programs for converting back and forth between MIDI files and text-based formats are:
 
 https://sourceforge.net/projects/mf2t/
 https://www.fourmilab.ch/webtools/midicsv/
 http://www.archduke.org/midi/
 https://github.com/mtolly/midiscript
 
 I haven't used any of them personally, but they all look to require some degree of comfort using command-line tools.
 I tend to write little C or Perl programs to manipulate MIDI files when the need arises.
 
 Mark Fontana
 
 
 
On 8/6/19 6:39 AM, Carol Beigel carol@... [disklavier] wrote:
  
    
Thank you for your explanation of how this software can work.  Except for changing a note‘s pitch and timing using Logic, I have never been anywhere near competent in using sequencing software.
 
  What software do you use that you can see all those events in a MIDI file? 
  Can you recommend a software program that does that MIDI to text and back again function? 
  As always, I am so grateful you wrote the utility for converting the ESEQ to MIDI files on the floppy disks people purchased for their Disklavier so they can continue to enjoy their music on today‘s formats. 
  Carol Beigel      
 
    
   
 
 

  

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.  #yiv0299203585 #yiv0299203585 -- #yiv0299203585ygrp-mkp {border:1px solid #d8d8d8;font-family:Arial;margin:10px 0;padding:0 10px;}#yiv0299203585 #yiv0299203585ygrp-mkp hr {border:1px solid #d8d8d8;}#yiv0299203585 #yiv0299203585ygrp-mkp #yiv0299203585hd {color:#628c2a;font-size:85%;font-weight:700;line-height:122%;margin:10px 0;}#yiv0299203585 #yiv0299203585ygrp-mkp #yiv0299203585ads {margin-bottom:10px;}#yiv0299203585 #yiv0299203585ygrp-mkp .yiv0299203585ad {padding:0 0;}#yiv0299203585 #yiv0299203585ygrp-mkp .yiv0299203585ad p {margin:0;}#yiv0299203585 #yiv0299203585ygrp-mkp .yiv0299203585ad a {color:#0000ff;text-decoration:none;}#yiv0299203585 #yiv0299203585ygrp-sponsor #yiv0299203585ygrp-lc {font-family:Arial;}#yiv0299203585 #yiv0299203585ygrp-sponsor #yiv0299203585ygrp-lc #yiv0299203585hd {margin:10px 0px;font-weight:700;font-size:78%;line-height:122%;}#yiv0299203585 #yiv0299203585ygrp-sponsor #yiv0299203585ygrp-lc .yiv0299203585ad {margin-bottom:10px;padding:0 0;}#yiv0299203585 #yiv0299203585actions {font-family:Verdana;font-size:11px;padding:10px 0;}#yiv0299203585 #yiv0299203585activity {background-color:#e0ecee;float:left;font-family:Verdana;font-size:10px;padding:10px;}#yiv0299203585 #yiv0299203585activity span {font-weight:700;}#yiv0299203585 #yiv0299203585activity span:first-child {text-transform:uppercase;}#yiv0299203585 #yiv0299203585activity span a {color:#5085b6;text-decoration:none;}#yiv0299203585 #yiv0299203585activity span span {color:#ff7900;}#yiv0299203585 #yiv0299203585activity span .yiv0299203585underline {text-decoration:underline;}#yiv0299203585 .yiv0299203585attach {clear:both;display:table;font-family:Arial;font-size:12px;padding:10px 0;width:400px;}#yiv0299203585 .yiv0299203585attach div a {text-decoration:none;}#yiv0299203585 .yiv0299203585attach img {border:none;padding-right:5px;}#yiv0299203585 .yiv0299203585attach label {display:block;margin-bottom:5px;}#yiv0299203585 .yiv0299203585attach label a {text-decoration:none;}#yiv0299203585 blockquote {margin:0 0 0 4px;}#yiv0299203585 .yiv0299203585bold {font-family:Arial;font-size:13px;font-weight:700;}#yiv0299203585 .yiv0299203585bold a {text-decoration:none;}#yiv0299203585 dd.yiv0299203585last p a {font-family:Verdana;font-weight:700;}#yiv0299203585 dd.yiv0299203585last p span {margin-right:10px;font-family:Verdana;font-weight:700;}#yiv0299203585 dd.yiv0299203585last p span.yiv0299203585yshortcuts {margin-right:0;}#yiv0299203585 div.yiv0299203585attach-table div div a {text-decoration:none;}#yiv0299203585 div.yiv0299203585attach-table {width:400px;}#yiv0299203585 div.yiv0299203585file-title a, #yiv0299203585 div.yiv0299203585file-title a:active, #yiv0299203585 div.yiv0299203585file-title a:hover, #yiv0299203585 div.yiv0299203585file-title a:visited {text-decoration:none;}#yiv0299203585 div.yiv0299203585photo-title a, #yiv0299203585 div.yiv0299203585photo-title a:active, #yiv0299203585 div.yiv0299203585photo-title a:hover, #yiv0299203585 div.yiv0299203585photo-title a:visited {text-decoration:none;}#yiv0299203585 div#yiv0299203585ygrp-mlmsg #yiv0299203585ygrp-msg p a span.yiv0299203585yshortcuts {font-family:Verdana;font-size:10px;font-weight:normal;}#yiv0299203585 .yiv0299203585green {color:#628c2a;}#yiv0299203585 .yiv0299203585MsoNormal {margin:0 0 0 0;}#yiv0299203585 o {font-size:0;}#yiv0299203585 #yiv0299203585photos div {float:left;width:72px;}#yiv0299203585 #yiv0299203585photos div div {border:1px solid #666666;min-height:62px;overflow:hidden;width:62px;}#yiv0299203585 #yiv0299203585photos div label {color:#666666;font-size:10px;overflow:hidden;text-align:center;white-space:nowrap;width:64px;}#yiv0299203585 #yiv0299203585reco-category {font-size:77%;}#yiv0299203585 #yiv0299203585reco-desc {font-size:77%;}#yiv0299203585 .yiv0299203585replbq {margin:4px;}#yiv0299203585 #yiv0299203585ygrp-actbar div a:first-child {margin-right:2px;padding-right:5px;}#yiv0299203585 #yiv0299203585ygrp-mlmsg {font-size:13px;font-family:Arial, helvetica, clean, sans-serif;}#yiv0299203585 #yiv0299203585ygrp-mlmsg table {font-size:inherit;font:100%;}#yiv0299203585 #yiv0299203585ygrp-mlmsg select, #yiv0299203585 input, #yiv0299203585 textarea {font:99% Arial, Helvetica, clean, sans-serif;}#yiv0299203585 #yiv0299203585ygrp-mlmsg pre, #yiv0299203585 code {font:115% monospace;}#yiv0299203585 #yiv0299203585ygrp-mlmsg * {line-height:1.22em;}#yiv0299203585 #yiv0299203585ygrp-mlmsg #yiv0299203585logo {padding-bottom:10px;}#yiv0299203585 #yiv0299203585ygrp-msg p a {font-family:Verdana;}#yiv0299203585 #yiv0299203585ygrp-msg p#yiv0299203585attach-count span {color:#1E66AE;font-weight:700;}#yiv0299203585 #yiv0299203585ygrp-reco #yiv0299203585reco-head {color:#ff7900;font-weight:700;}#yiv0299203585 #yiv0299203585ygrp-reco {margin-bottom:20px;padding:0px;}#yiv0299203585 #yiv0299203585ygrp-sponsor #yiv0299203585ov li a {font-size:130%;text-decoration:none;}#yiv0299203585 #yiv0299203585ygrp-sponsor #yiv0299203585ov li {font-size:77%;list-style-type:square;padding:6px 0;}#yiv0299203585 #yiv0299203585ygrp-sponsor #yiv0299203585ov ul {margin:0;padding:0 0 0 8px;}#yiv0299203585 #yiv0299203585ygrp-text {font-family:Georgia;}#yiv0299203585 #yiv0299203585ygrp-text p {margin:0 0 1em 0;}#yiv0299203585 #yiv0299203585ygrp-text tt {font-size:120%;}#yiv0299203585 #yiv0299203585ygrp-vital ul li:last-child {border-right:none !important;}#yiv0299203585

Good morning, everyone.

A couple of points regarding System Exclusive (SysEx) MIDI messages and Sequencer-Specific Meta Events.

SysEx messages are always sent from the sequencer to the MIDI output device. They are not assigned to any particular channel in the MIDI file.

Each SysEx message includes a registered, manufacturer-specific ID. The idea behind these messages is that a manufacturer can create unique MIDI events that trigger features that are specific to their own instruments. Sometimes the nature of these messages are publicly disclosed or uncovered and other manufactures may choose to respond to them if they wish. 

If a MIDI output device does not understand a particular SysEx message, it is supposed to ignore it. 

There are a few universal SysEx messages that are not manufacturer-specific. For example, the General MIDI (GM) reset message that tells the MIDI output device to reset itself to neutral General MIDI settings. If the output device does not support the GM sound set, it should ignore the message.

Many keyboards insert SysEx messages at the beginning of every recording that you make. The Disklavier does this, for example. Over the years with changes to Disklavier models, there have been some changes to the recorded SysEx messages as well.

Unless a mistake has been made in the rendering of the Piano-e-Competition files, the embedded SysEx messages should be left in place and should not cause any problems with any particular model.

Different sequencers will display or not display these messages in various ways. I use Digital Performer on the Mac. DP always shows SysEx messages in a track that is assigned to MIDI channel 1. This display is technically incorrect since those messages do not actually have a channel assignment. However, that is where DP shows them.

Sequencer-specific meta events are messages that pass information on to the playback device when the file is opened. These messages are not sent to the output device during playback. Like SysEx messages, these messages begin with a registered manufacturer ID.

An example of such a message is this one (shown in hexadecimal):

FF 7F 05 43 7B 0C 02 01

“43” is Yamaha’s manufacturer ID. “02” tells the Yamaha keyboard that the notes on channel 2 should be interpreted as the right hand track. “01” tells the Yamaha keyboard that the notes on channel 1 should be interpreted as the left hand track.

In my experience, the overwhelming majority of sequencers blow away these sequencer-specific meta events if the sequencer, itself, does not understand the message. Thus, if you open a file with one of these messages in a sequencer such as DP and then export a new MIDI file, the sequencer-specific meta event will be lost.

MidiKit on the Mac is an event-list type editor that shows SysEx and sequencer-specific meta events. Spencer Chase has quite a number of Windows-based utilities. I am sure that some of them show and enable editing of these events.

Regards,
PianoBench

I am not sure these comments will be useful to you, but ...

The Mark II , by itself with no upgrades, only played ESEQ files from floppy disks and MIDI 0 Files thru the MIdi ports on the control box.  You need to have a working floppy disk in the floppy drive , turned on, to even access the midi ports.

Try disconnecting the DKC850, use the original controller and try your MIDI files from your laptop.

Try MIDI 0 format if MIDI 1 does not work.  Make sure the directory or folder or floppy disk only contains one single format of files - either 0 or 1.

I think the wireless Bluetooth BT01 interface would work fine with the original control box on your Disklavier.  It would cost you about $75 to buy the interface and Sweet MIDI Player from the App Store.  It only works with Apple devices.  You would put your ecomp files into Sweet MIDI PLAYER on your iPhone, etc. and hit Play.  The instructions are located at: 
www.midiplayertools.com/Connecting.htm

I have used this system successfully on Disklaviers, PianoDisc and QRS Pianomation.

Carol Beigel


Sent from my iPhone

> On Aug 10, 2019, at 7:46 AM, carlspost2@... [disklavier] <disklavier@yahoogroups.com> wrote:
> 
> 
> 
> HI Spencer,
> 
> Thank you again for all your help with our questions. We are lucky to have someone with such vast knowledge.
> 
> I have been pulling my hair put trying to sort out the trouble with my midi files from the e-piano competition.
> Despite using the programs you suggested to look at the files info , I have still had no luck getting anything from the 2011 competition and after to play on my Disklavier- despite trying various programs.
> 
> I have emailed the people at the competition website to see if they have any ideas...
> 
> My particular Disklavier model is a 1997 C7 Mark II DKC100R (With DSR1 Upgraded controller). 
> 
> I play the files from my laptop using Windows 10.
> 
> Im not sure if that makes a difference. 
> 
> There must be something I am not seeing when comparing the files. Maybe you can see something obvious.
> I have attached two for you to compare.. (keep in mind I am in no way knowledgeable about the technicalities of  midi as format so apologies if the solution turns out to be  a simple one :)
> 
> Regards,
> Carl
> 
> 
> 
> 
> 
> 
> 
> <NOT WORKING Sonata in B-flat Major D960 Schubert .MID>
> <WORKS Paganini-Liszt - La Campanella (kolessova).mid>

Good afternoon, everyone.

Carol, I believe that some or all pre-Mark II Disklaviers need a working floppy drive with a disk inserted in order to receive MIDI data using the MIDI In port. However, I do not believe that this is necessary with the Mark II.

When sending MIDI data from an external source to a Mark II, it is important to pay attention to matching the Disklavier’s MIDI In setting with the MIDI data itself. 

The Mark II can be set to receive MIDI data on any particular MIDI channel or it can be set to HP. If the Disklavier’s MIDI In channel is set to HP, the Disklavier expects notes and on/off pedals on channel 1 and incremental pedals on channel 3. I frankly don’t recall whether the Mark II responds to incremental pedal data if the MIDI In channel is set to one channel, such as channel 1.

Regards,
PianoBench

> On Aug 10, 2019, at 3:02 PM, Carol Beigel carol@... [disklavier] <disklavier@yahoogroups.com> wrote:
> 
> I am not sure these comments will be useful to you, but ...
> 
> 
> The Mark II , by itself with no upgrades, only played ESEQ files from floppy disks and MIDI 0 Files thru the MIdi ports on the control box.  You need to have a working floppy disk in the floppy drive , turned on, to even access the midi ports.
> 
> Try disconnecting the DKC850, use the original controller and try your MIDI files from your laptop.
> 
> Try MIDI 0 format if MIDI 1 does not work.  Make sure the directory or folder or floppy disk only contains one single format of files - either 0 or 1.
> 
> I think the wireless Bluetooth BT01 interface would work fine with the original control box on your Disklavier.  It would cost you about $75 to buy the interface and Sweet MIDI Player from the App Store.  It only works with Apple devices.  You would put your ecomp files into Sweet MIDI PLAYER on your iPhone, etc. and hit Play.  The instructions are located at: 
> www.midiplayertools.com/Connecting.htm <http://www.midiplayertools.com/Connecting.htm>
> 
> I have used this system successfully on Disklaviers, PianoDisc and QRS Pianomation.
> 
> Carol Beigel
> 
> 
> Sent from my iPhone
> 
> On Aug 10, 2019, at 7:46 AM, carlspost2@... <mailto:carlspost2@...> [disklavier] <disklavier@yahoogroups.com <mailto:disklavier@yahoogroups.com>> wrote:
> 
>> HI Spencer,
>> 
>> Thank you again for all your help with our questions. We are lucky to have someone with such vast knowledge.
>> 
>> I have been pulling my hair put trying to sort out the trouble with my midi files from the e-piano competition.
>> Despite using the programs you suggested to look at the files info , I have still had no luck getting anything from the 2011 competition and after to play on my Disklavier- despite trying various programs.
>> 
>> I have emailed the people at the competition website to see if they have any ideas...
>> 
>> My particular Disklavier model is a 1997 C7 Mark II DKC100R (With DSR1 Upgraded controller). 
>> 
>> I play the files from my laptop using Windows 10.
>> 
>> Im not sure if that makes a difference. 
>> 
>> There must be something I am not seeing when comparing the files. Maybe you can see something obvious.
>> I have attached two for you to compare.. (keep in mind I am in no way knowledgeable about the technicalities of  midi as format so apologies if the solution turns out to be  a simple one :)
>> 
>> Regards,
>> Carl
>> 
>> 
>> 
>> 
>> <NOT WORKING Sonata in B-flat Major D960 Schubert .MID>
>> <WORKS Paganini-Liszt - La Campanella (kolessova).mid>
> 
> 
>

Thank you for sending that test file Spencer,
I have now discovered something quite strange. The file did in fact work the first time I played it.
However, I noticed that if I attempt to play another file from the batch that doesn't work it seems to trigger a problem which means the test file you sent doesn't work again.
In order for me to get it playing I have to switch my Disklavier off and then on again to 'reset it'.
Im not sure if that narrows down the problem or make it more complicated??
Carl
    On Sunday, 11 August 2019, 01:22:42 am AEST, 'Spencer Chase' lists@... [disklavier] <disklavier@yahoogroups.com> wrote:  
 
     
 
does the attached file work? it has sysex and sequencer specific stuff removed.
  Best regards, Spencer Chase
67550 Bell Springs Rd.
Garberville, CA 95542 Postal service only..
Laytonville, CA 95454 UPS only.
Spencer@spencerserolls.com
Spencer@...
Spencer@...
http://www.spencerserolls.com
http://www.poodlex.com
(425) 791-0309
(707) 223-8212
------ Original Message ------From: "carlspost2@... [disklavier]" <disklavier@yahoogroups.com>To: disklavier@yahoogroups.comSent: 8/10/2019 4:46:36 AMSubject: [disklavier] Re: Midi File Channel

   
HI Spencer,

Thank you again for all your help with our questions. We are lucky to have someone with such vast knowledge.
I have been pulling my hair put trying to sort out the trouble with my midi files from the e-piano competition.Despite using the programs you suggested to look at the files info , I have still had no luck getting anything from the 2011 competition and after to play on my Disklavier- despite trying various programs.
I have emailed the people at the competition website to see if they have any ideas...
My particular Disklavier model is a 1997 C7 Mark II DKC100R (With DSR1 Upgraded controller). 

I play the files from my laptop using Windows 10.
Im not sure if that makes a difference. 
There must be something I am not seeing when comparing the files. Maybe you can see something obvious.I have attached two for you to compare.. (keep in mind I am in no way knowledgeable about the technicalities of  midi as format so apologies if the solution turns out to be  a simple one :)
Regards,Carl

Thanks Spencer,
I will give the cleaner program another go.  At least I can get them to play now - even if it means turning the DKV off and on again.
Cheers,Carl


    On Sunday, 11 August 2019, 02:11:00 pm AEST, 'Spencer Chase' lists@... [disklavier] <disklavier@yahoogroups.com> wrote:  
 
     
 
it must be that some sysex or sequencer specific events are being remembered by the DKV so playing any file with these events will prevent playing of other files until it is powered off or the events are canceled.
the best solution as far as i can tell would be to run the midi cleaner program on all files from the later set of files that cause problems. the cleaner program on my download page leaves in most important events and just removes rarely used stuff so it should not be a problem to process all the files. if you do have a problem i can modify the cleaner program to leave more stuff but just remove sysex andseq spec events.
another possibility is to use a little desktop program that i wrote that sends a general reset to a chosen midi device but you would need to do this every time you play a file and probably after it starts. much easier to process all the files with the cleaner.
  Best regards, Spencer Chase
67550 Bell Springs Rd.
Garberville, CA 95542 Postal service only..
Laytonville, CA 95454 UPS only.
Spencer@...
Spencer@...
Spencer@mcn.org
http://www.spencerserolls.com
http://www.poodlex.com
(425) 791-0309
(707) 223-8212
------ Original Message ------From: "'carlspost2@...' carlspost2@... [disklavier]" <disklavier@yahoogroups.com>To: "'Spencer Chase' lists@... [disklavier]" <disklavier@yahoogroups.com>Sent: 8/10/2019 4:41:53 PMSubject: Re: [disklavier] Re: Midi File Channel

   

 Thank you for sending that test file Spencer,
I have now discovered something quite strange. The file did in fact work the first time I played it.
However, I noticed that if I attempt to play another file from the batch that doesn't work it seems to trigger a problem which means the test file you sent doesn't work again.
In order for me to get it playing I have to switch my Disklavier off and then on again to 'reset it'.
Im not sure if that narrows down the problem or make it more complicated??
Carl
    On Sunday, 11 August 2019, 01:22:42 am AEST, 'Spencer Chase' lists@spencerserolls.com [disklavier] <disklavier@yahoogroups.com> wrote:  
 
     
 
does the attached file work? it has sysex and sequencer specific stuff removed.
  Best regards, Spencer Chase
67550 Bell Springs Rd.
Garberville, CA 95542 Postal service only..
Laytonville, CA 95454 UPS only.
Spencer@...
Spencer@...
Spencer@...
http://www.spencerserolls.com
http://www.poodlex.com
(425) 791-0309
(707) 223-8212
------ Original Message ------From: "carlspost2@.....au [disklavier]" <disklavier@yahoogroups.com>To: disklavier@yahoogroups.comSent: 8/10/2019 4:46:36 AMSubject: [disklavier] Re: Midi File Channel

   
HI Spencer,

Thank you again for all your help with our questions. We are lucky to have someone with such vast knowledge.
I have been pulling my hair put trying to sort out the trouble with my midi files from the e-piano competition.Despite using the programs you suggested to look at the files info , I have still had no luck getting anything from the 2011 competition and after to play on my Disklavier- despite trying various programs.
I have emailed the people at the competition website to see if they have any ideas...
My particular Disklavier model is a 1997 C7 Mark II DKC100R (With DSR1 Upgraded controller). 

I play the files from my laptop using Windows 10.
Im not sure if that makes a difference. 
There must be something I am not seeing when comparing the files. Maybe you can see something obvious..I have attached two for you to compare.. (keep in mind I am in no way knowledgeable about the technicalities of  midi as format so apologies if the solution turns out to be  a simple one :)
Regards,Carl