Reported Bug in MusicSequence
Reported Bug in MusicSequence
- Subject: Reported Bug in MusicSequence
- From: William Stewart <email@hidden>
- Date: Tue, 14 Sep 2004 17:46:53 -0700
There was a bug reported some time ago about the MusicSequence generating
stuck notes when sending out a MIDI Endpoint but not when sending to the
software synth... (This was with MIDI files that have duplicate note
events).
The MusicSequence is correctly sending MIDI in both situations - in these
cases it sends out two note ons and two note offs, so we believe the bug is
in the external hardware as this is what we should do in these situations
(or if you don't want that affect, the MIDI files are bad)
* * Track 1 * *
SequenceTrack @502380
NumEvents:3
0.000: Prgm:Chan:0 125 0
3.523: Note:Ch:0 57 113 (0.896)
3.523: Note:Ch:0 57 113 (0.896)
Ready to play <0.000000 beats>:/Volumes/Luthien/bill/Desktop/single stuck
note
<Enter> to continue:
1 packets:
c0 7d
Started Playing:/Volumes/Luthien/bill/Desktop/single stuck note, 0.006596
beats
current time:2.107740 beats,
1 packets:
90 39 71
1 packets:
90 39 71
current time:4.110173 beats,
1 packets:
90 39 0
1 packets:
90 39 0
Bill
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden