Re: Where did my event, part I
Re: Where did my event, part I
- Subject: Re: Where did my event, part I
- From: Craig Hopson <email@hidden>
- Date: Mon, 12 Sep 2005 15:55:25 -0600
Doug,
Thanks, I'll switch my code to use Sequencer-specific events (we are
already using the Track name, FF 03, event). However, originally we
had decided not to use Sequencer-specific events since we do not wish
to publish how other sequencers can use the data. We had assumed
that was the reason for the existence of the UserEvents. I agree
that MusicPlayer or MusicSequenceSaveSMFData, etc., should seamlessly
save & restore user events, however that is accomplished. I'll enter
a Radar report to that effect.
-Craig
On Sep 12, 2005, at 3:28 PM, Doug Wyatt wrote:
[resending, this hasn't shown up on the list as of 2 hours after I
sent it...]
On Sep 12, 2005, at 9:04, Craig Hopson wrote:
In our Cocoa app we create custom tracks in a music sequence and
populate them with our own events. At runtime this works quite
well. However, now I'm trying to implement Save/Open. As you can
see from the log output below, the basic track information
persists (MIDI track name event) but the custom UserEvents do
not. Is this a bug or am I missing something in my code?
MusicPlayer's user events don't get written or read from MIDI Files.
You can however use a sequencer-specific meta event:
FF 7F <var-len> <data>
By convention the first four bytes of the event's data should be a
"unique" identifier for your app.
(Arguably it would be natural for MusicPlayer to simply transform
user events into sequencer-specific meta events when saving and
restore them when opening -- you can write a Radar if you agree.)
Doug
--
Doug Wyatt
Core Audio, Apple
_______________________________________________
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