Yahoo Groups archive

Disklavier

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

Message

RE: "Extraneous" MIDI files on USB stick - Newbie question

2013-09-02 by <mqphan@...>

Thank you so much everyone for the help. Per your advice I used a PC to download the files and saw that you were all correct! Thanks again everyone for answering my inquiry so quickly!


Minh



--- In disklavier@yahoogroups.com, <billbrando@...> wrote:

It's a MAC issue. Files are created on the MAC that are invisible when using the MAC. When a folder is copied from the MAC and viewed in a PC environment, these files become visable.

Bill

Sent from my iPhone.

On Sep 2, 2013, at 11:40 AM, <mqphan@...> wrote:

I am new and I hope that somebody can help me answer this question. I couldn't find anyone who asked this same question on the forum. Mine is a brand new DGB1KE3.


I purchased a downloadable Chopin Recital album from Yamaha Music that came in the form of a folder containing 12 MIDI files. I copied this folder onto a blank USB stick (via a MacBook Pro) and inserted the USB stick into the front panel USB port. This album would show up as Album No. 2 on the control unit display panel. Album 1 is empty and could not be deleted when I used the DELETE function. Furthermore, in Album 2 that contains the music files, I noticed that the first 12 "files" or "songs" don't contain any music, just the titles. Nothing would play when I tried to play them. The real music starts from Song 13 to 24 with the same titles repeated. In other words, to play Song 1 on the Disklavier, I have to use the directional control pad to go all the way to file 13. If I look into the content of the USB stick from my MacBook pro I only see one folder with 12 MIDI files. This same problem also happens to any other MIDI files from another source such as disklavierworld.

I just wonder if anyone has this same issue. Thank you in advance for your help.

Minh

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.