Midi Tempo Bug??
Midi Tempo Bug??
- Subject: Midi Tempo Bug??
- From: Peter Zegelin <email@hidden>
- Date: Thu, 22 Apr 2004 16:23:59 +1000
Hi,
While developing my Midi app I've been creating some test files in
another application and noticed that they often caused my app to
crash. I assumed that there was a bug somewhere in my code as they play
fine in other CoreAudio Midi apps. However today I noticed that one
thing in common is that none of these files ( I've only checked 3) have
any Tempo events. As soon as I add a Tempo event to the beginning of
the file they suddenly play fine in my app!
That reminded me of a very recent question I asked here and although
the answer wasn't really to my question it does seem like this is
indeed the culprit:
Also is there any default maximum Tempo value? I'm generating a
fairly standard squiggly line type Tempo view and was wondering what
a reasonable maximum might be. At the moment I am actually
calculating the maximum tempo for the current file and using that,
but is there some sort of standard?
We actually have a bug with files that don't have a tempo event in
them... I'd generally consider these badly authored files, but it is
something we should have guarded against properly and didn't! The
default tempo that most people are using (including ourselves) is 120
bpm
So my questions are: This looks like its a known issue - is there a
suggested work around? I checked the archives and couldn't find any
mention of this bug. Yet the other apps I've looked at handle this fine.
If there is no suggested workaround, do I just check to see if there
are no Tempo events and add one? Or do I have to see if the first Tempo
event starts at > 0? Or do I just add a default (120) Tempo event to
the beginning of all files?
BTW I'm using OSX10.2.8
thanks!
Peter
_______________________________________________
coreaudio-api mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/coreaudio-api
Do not post admin requests to the list. They will be ignored.