Re: *.mid vs *.midi

[Bertalan Fodor (LilyPondTool)]

Why always speaking about broken OS-es and softwares? We want to make LilyPond better, don't we?
LilyPond generates .midi files, which are not usable for many applications. If LilyPond generated .mid files, it would work on every application (except LilyPondTool :-), which I think unfortunately depends on .midi).

So I'm sure this is a bug, so it should be fixed.

Bert

Graham Percival wrote:

On Thu, 15 May 2008 22:55:50 -0700
Michael David Crawford <address@hidden> wrote:

  

But when Apple bought NeXT from Steve Jobs, the Cocoa framework that 
became Mac OS X knew nothing of types and creator codes.  Now the Mac
is borked in the same way windows is.
    

Yes and no.  The underlying OS still knows what the files are:

tsubasa:~/tmp gperciva$ ls foo.mi*
foo.mid         foo.midi
tsubasa:~/tmp gperciva$ file foo.mi*
foo.mid:  Standard MIDI data (format 1) using 3 tracks at 1/384
foo.midi: Standard MIDI data (format 1) using 3 tracks at 1/384
tsubasa:~/tmp gperciva$ mv foo.mid foo.txt
tsubasa:~/tmp gperciva$ file foo.txt 
foo.txt: Standard MIDI data (format 1) using 3 tracks at 1/384
tsubasa:~/tmp gperciva$ 


I can double-click on both foo.mi* files and have Quicktime open
up and play the files.  However, trying to open foo.txt results in
TextEdit popping up.


I actualy consider this *more* broken than Windows.  I mean,
Windows is just stupid.  OSX *isn't* stupid, but it pretends to
be.  I have no clue what the Aqua people were up to.  :(

Cheers,
- Graham



_______________________________________________
lilypond-user mailing list
address@hidden
http://lists.gnu.org/mailman/listinfo/lilypond-user

  

-- 
LilyPondTool is the editor for LilyPond files.
See http://lilypondtool.organum.hu