MIDI import bug?

[Larry Troxler]

On Tue, 2 Sep 1997, Tobias Kunze wrote:

> 
> i see.  Your problem seems to be that the tempo/timing
> information is in track 0 (a "conductor" track?  I don't have my 
> documentation at hand) whereas your data is stored in track 1.  
> 
Yes, it seems to be a convention that the first track is used as a
conductor track. I remember having a discussion a while back as to whether
this was some kind of official standard, but I don't remember what the
verdict was.

But I think that if by timing, you mean ticks-per-second, I had thought
that this was in the file header, and not in each track. Even
"midifile-print" thinks this way, as it prints out the timebase before the
individual track data.


 > Now, when you instruct cm to "import foo.midi track 1", it is 
> obviously not going to parse the time track and thus resetting
> divisions, tempo, etc. to default values. 

Yes, after I sent you the file, I realized that the tempo event would not
have been seen. However, see my above comments about the timebase.

As to how the math works out for this
particular case, I'm too
lazy to figure it out.  I'll assume that my problem is that the import
command looks for a MIDI file tempo event, and if it doesn't see it,
defaults the tempo to some really slow value.


--  Larry Troxler  --  lt@westnet.com  --  Patterson, NY USA  --