TweetFollow Us on Twitter

MIDI Music
Volume Number:10
Issue Number:10
Column Tag:New Apple Technology

Related Info: Sound Manager

Making MIDI Music

Using QuickTime 2.0 to make some music of your own

By Glenn Andreas, Fridley, MN

Note: Source code files accompanying article are located on MacTech CD-ROM or source code disks.

About The Author

Glenn Andreas - Glenn started Mac programming in the Fall of 84 when he conned his boss into buying him a Lisa and the original IM. Since then, he’s written the game Theldrow, worked for Palomar Software writing printer drivers, and done various freelance programming jobs, including a sped up version of the Stylewriter driver (which never shipped), and some work on the printing portions of Bedrock (which also never shipped). He’s currently working a “day job” which involves hacking the BSD kernel, while trying to finish his latest game Chimera (which will hopefully ship one day).

Editor’s Introduction

Glenn tried to use Apple docs to figure out how to generate MIDImusic with QuickTime 2.0. He ran into the common insufficient documentation (what’s that error number, again?) roadblock, and dove in to figure out how things really operate. In doing so, he ran some risk of learning how to do things the wrong way, so we gave some good folks at Apple a crack at his article. While calling the approach a bit “hackish” because he defines his own headers, they say he pretty much got it right. While there are easier ways to put MIDItunes into QuickTime movies and play them as background music, this article shows you how to drive from the APIlevel. It’s rather like using the Sound Manager with QuickTime.

Two caveats - the flags in TuneStop are not implemented (the article suggests they are) and TuneResume doesn’t.

Be sure to check out the real documentation when it comes available, and enjoy MusicTest in the meantime!

The Motivation

As I worked on my latest project, I wanted to have background music. I was originally planning on writing some sort of “auto mixing my own sound buffers from hell” sound manager hack, and while these are fun to write, it would take a great deal of resources to get it correct. Then I heard that QuickTime 2.0 would include the ability to play music, as music. “Sort of like MIDI” I heard. Call me a crazy, but I’d rather just make a few component manager calls rather than spend months writing my own music playing routines (besides having all my work done for me, QT 2.0 can play the music through an external MIDI device as well for even better quality with almost no system load). So, I got a beta of QT 2.0, and immediately dove into the “Macintosh Music Architecture” document. This was rather like diving in the shallow end of the pool. Given that the header code and the documentation didn’t synch all that well, and assuming that the underlying code followed yet another convention, I did what any resourceful programmer would do - I dropped into MacsBug.

Fortunately for me, MoviePlayer was able to correctly play some of the sample music movies included on the beta CD. And, also fortunately for me, the whole music architecture is build uses the component manager (which, by the way for those who have never really looked at it, is really cool). So I set a breakpoint at the beginning of the “Tune Player Component”, and watched every call made by QuickTime as it played music. And finally, after countless reboots, I was able to make my Mac play music from my own programs.

At this point, I saw this as an opportunity for a little fortune and glory. Given that the only existing document I had on how to play music was inaccurate, I figured that I would write this article explaining just what it will take for you to easily add background music to your current or future project. Note that this article is in no way official documentation, it is simply what I have discovered on how things works. I’ll only present a subset of the routines available (see the header files for QuickTime 2.0 which appear in the August Developer CD for more details), and all examples will be based on what I’ve found in snooping around (so if I say that this parameter is zero, that means that I’ve always seen this parameter as zero, not that it has to be - but unless you like rebooting, you might want to leave it as zero). Also, I will attempt to avoid as much “music theory” as possible, since not only are there good books on this already, my knowledge is weak in that area, and I wouldn’t want to provide misleading information. This will be in Pascal, and I’ll simplify the header file so we don’t have to include dozens of other files (because QuickTime wants Aliases which wants AppleTalk which wants, well, you get the idea). First, however, let’s look at a quick bit of pseudo-code and see what it is we are going to do.


In order to play music, we need two important pieces of information - what notes to play, and what instruments to play them on. This first part is the body of the tune, while the second is what is called the header of the tune. In QuickTime, the tune header, along with some additional information, is stored in the media handler information (in the resource fork), while the tune body is stored in the actual data (on the data fork). For this article, we will store both in a single resource, starting with what the media handler information would be (as defined in MusicDescription record), with the tune body appended onto the end.

Here, then, are the basic steps we will use to play music:

• Create a tune player component

• Feed the music header the header from our resource

• Tell it to start playing the body from our resource

• Wait until it finishes

• Make sure to tell it to stop playing

• Dispose and clean up.

But before we get to the code, let’s look how the music is stored (this is important, so don’t skip ahead).

Storage of Musical Notes

Music is stored as a series of commands. Each command usually takes one longint, but can take two or more. Examples of these commands are to play a given note on a given instrument at a given pitch and given volume for a given duration, or to have a given instrument wait a given duration. And thanks to the “Time” part of QuickTime, multiple instruments can all be synched together, or their tempo can just as easily be changed (but for you QuickTime junkies, I will not be getting into time bases).

These commands are similar to MIDI commands, if you are familiar with them. If you aren’t, by the end of this section you’ll know that MIDI commands are similar to QuickTime music commands. These commands are tagged with what the command is in the high three or four bits, with the remaining bits (or following long word or words) providing the parameters. Note that all commands are multiples of four bytes long, so you can easily scan them as an array of LongInts.

Before we get to the commands themselves, we need to look at some of the parameters first. Almost all commands require a integer parameter to specify which instrument the command affects. An instrument is just that - a single instrument. QuickTime provides 30 some odd instruments to choose from. You can have more than one instrument playing in a given song (so you can have “Dueling -insert your favorite instrument here-”). Also, a single instrument can play more than one note at a time (being able to play a chord). Before playing the song, you tell the tune player component how many instruments there are and what they are, but we’ll get into this later.

Other parameters are fairly self explanatory.

Volume (also called velocity, because it refers to how hard you strike the key on a keyboard), ranges from 0 (silent) to 63.

Duration is specified in units that are specific to the tune component (in our examples we use 1/600ths of a second). Warning, some music theory follows: Based on the default time units, and assuming 4/4 time (which means that a quarter note is 1/2 second long), below is a quick table of duration values and the length of notes they produce:

Units at 600/second Note produced

75 sixteenth note

150 eight note

300 quarter note

600 half note

1200 whole note

Pitch, which ranges from 0 to 127, corresponds to the same values MIDI uses. Pitch ranges from C five octaves below middle C (0) to G five octaves above middle C (127). Middle C has the value of 60. A complete table of these values can be found on page 2-43 of the recently published IM:Sound. While it is possible to play what is called “microtonal values”, which can be just about any pitch (they are represented with fixed point numbers), this is done via a different, much less convenient, interface.

One other thing to be aware of is that most commands have an “extended” form that usually takes two long words instead of one. This allows more bits for each parameter, but in all my “snooping” I’ve yet to come across anything that uses them. For the sake of simplicity, I’ll also restrict myself to just the commands that are commonly used. In the commands below, I’ll show all thirty two bits, with the most significant bit on the left, with a space between each four bits for easier reading.

Our first command is the “rest” command:

 000- ---- dddd dddd dddd dddd dddd dddd

The 000 is the rest command. The next five bits would normally be for the instrument, but for the rest command are unused (and should be set to zero). Those are followed by twenty-four bits of duration d. This just instructs the instrument not to start any more commands until that time has passed.

The next command is the “note” command:

 001i iiii pppp ppvv vvvv vddd dddd dddd

The 001 is the note command, the i’s are five bits representing what instrument (0-31), and the d’s are again duration (though for this command there are only 11 bits, so the value ranges from 0 to 2047, or in our examples, over 3 seconds). The six bits of p’s are our pitch, again as a MIDI note value, and the seven bits of v’s are the volume.

These two commands are enough to start playing music. However, if you wanted to play a scale, and you just issued eight note commands with increasing pitches, you would get one short polyphonic cacophony - all the notes would play at the same time, as a chord, rather than as eight sequential notes. To achieve the desired effect (each note in sequence), you need to issue eight note-rest command pairs, to allow time for one note to play before starting the next.

One final command in this example is needed - a command to have it stop. Without it, it will start playing whatever’s in memory, and soon you’ll be rebooting. The command to stop playing is the “marker” command:

 011- ---- ssss ssss xxxx xxxx xxxx xxxx

The 011 is the marker command, the ‘-’s are unused (and should be set to zero). The eight bits of s are the marker event subtype, and the x’s are the marker event value. The only values I’ve seen are zero for both, which is used to mark the end of the playing - all music command lists end with the value $60000000.

For the sake of completeness, here are the rest of the commands (though we will only be using one of them):

 010i iiii cccc cccc xxxx xxxx xxxx xxxx

Control: i is instrument, c is controller, x is the value to set that controller to.

 1011 iiii iiii iiii hhhh hhhh hhhh hhhh
 10kk kkkk kkkk kkkk llll llll llll llll

Knob: i is instrument, k is what knob, h is the high word and l is the low word of what value to set that knob to.

 1001 iiii iiii iiii pppp pppp pppp pppp
 10-- ---- --vv vvvv vvvv vvvv vvvv vvvv

Extended note, with the same parameters as note.

 1010 iiii iiii iiii cccc cccc cccc cccc
 10-- ---- ---- ---- xxxx xxxx xxxx xxxx

Extended control, with the same parameters as control.

 1111 iiii iiii iiii llll llll llll llll
 10tt tttt tttt tttt llll llll llll llll

This is the general command, which isn’t used in playing the music, but rather is used when you set up the tune player component. It is this command that is used to tell the player what instruments are what. The i’s, of course, are the instrument, the t’s represent one of the following:

1 Note request

2 Instrument

3 Flat Instrument

4 Part Name

5 Part Key

I’ve only seen “Note Request”, so that is all that I will talk about. The l’s represent the length of the entire command, including any general data. This value is in long words, and includes both long words of the command. Finally, between the two commands is some amount of additional data. Here’s an example to help explain this - this is the command from the header portion of some music, and it instructs the tune player that instrument zero is a normal piano:

F0000017 00000001 00010000 00000000 0F416E79 2053796E 74686573 697A6572 
AAE20000 000000AC AAE60000 00130018 0B486172 70736963 686F7264 69616E6F 
5069616E 6F000000 00000000 00000000 00000007 00000007 C0010017

The $F0000017 says that this is a general event for instrument zero, and the whole thing is $17 (23) long words long. Following that is $15 long words, which actually are a data structure known as a NoteRequest. The last long word $C0010017 says that it is, surprisingly enough, a “note request”, and the whole thing was $17 long words long. Why this value is repeated in both places I’m not sure - perhaps there is some sort of integrity check.

Before we get to the code, let’s make some Rez definitions so we can create our music - I am currently working on a music editor that will produce these music resources, but I can hardly include the source for that as well in this article (especially since it isn’t done yet). It should be done and available in a variety of online places by the time you read this. [Check out our online places. See p.2 for details - Ed stb]

‘Musi’ Resources

I made a simple “Music.r” file (see listing 1) which will allow us to use Rez to create and edit music. Here is our sample input:

resource 'Musi' (128) {
 { /* array header: 1 elements */
 /* [1] */
 "Any Synthesizer",
 "Acoustic Grand Piano",
 { /* array: 10 elements */
 noteCommand { 0, 37, 64, 1800 },
 restCommand { 1800 },
 noteCommand { 0, 11, 64, 900 },
 restCommand { 900 },
 noteCommand { 0, 28, 64, 1800 },
 noteCommand { 0, 31, 64, 1800 },
 noteCommand { 0, 35, 64, 1800 },
 noteCommand { 0, 4, 64, 1800 },
 restCommand { 3300 },
 markerCommand { 0, 0 }

This says that we have one instrument, the grand piano, to be played on any synthesizer. If you want to just play around, you can change the last two ‘1’s to other values to play other instruments without having to change the name. I’d advise leaving the polyphony ‘1’ and ‘0x10000’ as is, as well as the synthesizer type and name.

After the header we play a C# in octave 3 (37) at average volume (64) for 3 seconds (1800, since our time scale will have 600 units per second). We rest for those three seconds to let the note play. We then play a B in octave 2 (11) for 1 1/2 second, and also rest to let the note play. We next play a chord of four notes for 3 seconds: E in octave 3 (28), G in octave 3 (31), B in octave 4 (35), and E in octave 1 (4). We let that play and rest for an additional 2 1/2 seconds. We end the thing with our marker command (we could have made that last command part of the rez template like we did for the header, but we might as well mark the end explicitly).

Here’s the hex dump of that resource, formatted to show what is going on a little better:

00000074offset to body
000000000000000100000000  flags, etc...
F0000017instrument 1
 00000001 00010000 Polyphony, etc...
 00000000 Any component
 “Any Synthesizer”
 “Acoustic Grand Piano”
 00000001 00000001 
60000000End of Commands

Body starts
20960708Play C# in octave 3
202E0384Play B in octave 2
20720708 207E0708 208E0708 20120708Play Chord
60000000End of Commands

The Interface

There are many more calls in “QuickTimeComponents.h” than I’ll document here, since the focus is to show what it takes to play music in the background of your application. Instead we will just look at the major routines for the tune player component, and ignore both the note allocator and low level music component. This is all from listing 2, my Music.p interface file derived from QuickTimeComponents.h. I’m also going to assume that you’ve got access to header files and documentation for the Component Manager (found in IM:More Macintosh Toolbox).

FUNCTION TuneSetHeader( tp: TunePlayer; 
 header: Ptr): ComponentResult;

This tells the newly created tune player what instruments will be used. We will pass in the header data from our resource.

FUNCTION TuneSetTimeScale(tp: TunePlayer;
 scale: LongInt): ComponentResult;

This specifies how many units per second the duration parameter in the music commands stand for. QuickTime uses 600, we use 600. The parameter is actually a TimeScale, but we don’t want to have to include all of the QuickTime interface files to find out that it is a longint.

FUNCTION TuneGetTimeScale(tp: TunePlayer;
 VAR scale: LongInt): ComponentResult;

This call will return what the current time scale is for the tune player.

 FUNCTION TuneQueue( tp: TunePlayer;
 tune: MusicOpWordPtr;
 tuneRate: Fixed;
 tuneStartPosition: LongInt;
 tuneStopPosition: LongInt;
 queueFlags: LongInt;
 callBackProc: ProcPtr;
 refCon: LongInt): ComponentResult;

This is the magic call to actually start playing. You pass in the tune player in tp, and a pointer to the start of the music opwords (make sure that everything is locked down) in tune. TuneRate contains a fixed value which lets you adjust how fast or slow the resulting tune is played. TuneStartPosition and TuneStopPosition specify, in time units, what section of the music to play. The music starts at zero, so to play everything, we pass in 0 and $7FFFFFFF. QueueFlags have the following values:

  kTuneStartNow = 1;
  kTuneDontClipNotes = 2;
  kTuneExcludeEdgeNotes = 4;
  kTuneStartNewMaster = 16384;

If no flags are specified, the tune starts playing as soon as any currently playing tune stops (or immediately if no music is currently being played). Up to eight tunes can be queued up at a time.

CallBackProc and refCon are used to help you queue up the next sequence chunk. It would be declared as:

PROCEDURE MyTuneCallBackProc(status:TuneStatus; refCon:LongInt);

where status is the same as is used in TuneGetStatus, and refCon is whatever you pass into the call of TuneQueue.

 TuneStatus = RECORD
 tune, tunePtr: ^LongInt;
 time: longint;
 queueCount, queueSpots: Integer;
 queueTime: LongInt;
 reserved: ARRAY[1..3] OF LongInt;
 FUNCTION TuneGetStatus (tp: TunePlayer;
 VAR status: TuneStatus): ComponentResult;

This routine will give you the status of the currently playing tune. Tune is the current tune, while TunePtr points to where in that tune we currently are. Time is how many time units have passed. QueueCount is how many tunes, including this one are currently queued up. QueueTime is how many time units worth of tunes are queued up waiting to be played.

FUNCTION TuneStop( tp: TunePlayer; 
 stopFlags: LongInt): ComponentResult;

This routine is used to stop the specified tune. StopFlags can be one of the following:

 kStopSustain = 1;
 kStopFadeout = 2;

This allows you to either let the currently playing note keep playing (which can be annoying), or to let it fade out in a nice manner. If you specify 0, then the music stops abruptly.

 FUNCTION TuneResume (tp: TunePlayer): ComponentResult;

After you have stopped a tune, this call will let you resume it.

 FUNCTION TuneFlush (tp: TunePlayer): ComponentResult;

If you decide to not resume a tune, you can call this routine and the next tune queued up should start.

 FUNCTION TuneSetVolume (tp: TunePlayer; volume: Fixed): ComponentResult;
 FUNCTION TuneGetVolume (tp: TunePlayer): ComponentResult;

This pair of routines allows you to change the volume of the playing tune. Don’t ask me how the volume is returned in TuneGetVolume, since there is no fixed value returned and no fixed var parameter, but that is what the call is.

 FUNCTION TunePreroll (tp: TunePlayer): ComponentResult;

This call is important, because it will reserve all the note channels for the instruments, load everything it can into memory, and do any other possible preparation for playing the given music.

 FUNCTION TuneUnroll (tp: TunePlayer): ComponentResult;

This is the opposite of TunePreroll in that it unreserves all the note channels that have been locked down. This call is typically called before suspending your application (after stopping the current music), so other applications can play their music.

Putting It All Together

Now that we’ve got the basic calls, and a simple little bit of music to play, let’s look at what calls need to made and in what order. This is the code from a simple application that just gets the music resource and plays it, busy waiting while playing, and quitting when done. We will just comment on the basic calls - to see all the details (where we actually check errors), see listing 3, MusicTest.p.

The first thing to do is to load in the resource we are playing and lock it down:

 h := MusicDescriptionHandle(GetResource('Musi', 128));

We then call the component manager to have it make a default tune player:

 tp := OpenDefaultComponent(kTunePlayerType,

The next step is to tell it the time units. We use the value 600 since that is what QuickTime movies normally use.

 result := TuneSetTimeScale(tp, 600);

We then need to tell the tune component what instruments are used. We get this data from our resource.

 result := TuneSetHeader(tp, @h^^.headerData);

Now that we’ve told it what instruments to use, we want to reserve those instruments and do any other sort of pre-play allocation we can.

 result := TunePreRoll(tp);

We can now say how loud we want to play it. We will use normal volume, which is a fixed point one.

 result := TuneSetVolume(tp, $10000);

Now we make the magic call to actually start the music playing. It will automatically play in the background, there is no extra stuff needed to do (unlike the sound manager). We pass in the start of the body of music, as based on our resource, tell it to play at normal tempo, play everything, start playing now, and we don’t have any callbacks.

 result := TuneQueue(tp, Pointer(ORD4(h^) + h^^.size),
 $10000, 0, $7FFFFFFF, kTuneStartNow, NIL, 0);

We can then wait and check to see how we doing. When the music stops, the queueCount field of the TuneStatus record will drop from 1 to 0. There are other ways to determine if we are done, but we won’t get into them, since the queueCount field is simple enough.

 result := TuneGetStatus(tp, theTuneStatus);
 UNTIL Button | (theTuneStatus.queueCount = 0);

That’s all there is to playing. When we are done, (or in our example, when the user clicks the button), we need to free up everything we allocate.

 result := TuneStop(tp, kStopFadeout);
 err := CloseComponent(tp);

That’s all there is to playing music. There are many more calls, include ones to present a dialog to the user to allow them to select an instrument, but we don’t have space to get into those here. The calls are all found in the QuickTime 2.0 interface files, while the documentation should be in a tech note or future article.

Listing 1 - Music.r

This is our combined header/body resource for playing music with QuickTime 
2.0's tune player component.

/* 1 */
type 'Musi' {
/* First the length of the header & MusicDescription record.  The MusicDescription 
/* record isn't actually used by us or passed as a parameter, but I kept 
this info */
/* just so it would be easy to convert QuickTime music tracks to 'Musi' 
resources. */
start:  longint = $$CountOf(header) * $17 * 4 + 20 + 4;
 /* next, the media handler type used by QuickTime */
 longint = 'musi';
 longint = 0; /* Reserved 1 */
 integer = 0; /* Reserved 2 */
 integer = 1; /* dataRefIndex */
 longint = 0; /* music flags */
/* and here is the actual start of the music header */
/* we just currently define NoteRequest general events */
 array header {
 bitstring[4] = $F;  /* general event */
 bitstring[12];  /* What instrument */
 bitstring[16] = $0017;   /* length of note request general event */
 /* here is the noteRequest record */
 longint; /* Polyphony, usually 1 */
 hex longint;    /* TypicalPolyphony, fixed, usually $10000 */
 longint kAnyComponentType = 0; /* OSType of synth component */
 pstring[31];    /* Synthesizer name such as "Any Synthesizer" */
 pstring[31];    /* Preferred Instrument name for human use*/
 longint; /* instrument number if synth-type matches */
 longint; /* gm number - best matching general MIDI number */
 longint = $C0010017;     /* this was a note request */
 longint = $60000000;     /* The marker at the end of the header */
/* Here is the body of the music */
 array {
 switch {
 case restCommand:
 key bitstring[3] = $0;
 bitstring[5] = 0; /* unused */
 bitstring[24];  /* duration */
 case noteCommand:
 key bitstring[3] = $1;
 unsigned bitstring[5];   /* instrument */
 unsigned bitstring[6];   /* pitch */
 unsigned bitstring[7];   /* volume */
 unsigned bitstring[11];  /* duration */
 case markerCommand:
 key bitstring[3] = $3;
 bitstring[5] = 0; /* unused */
 unsigned bitstring[8];   /* subtype */
 bitstring[16];  /* value */
 case controlCommand:
 key bitstring[3] = $2;
 unsigned bitstring[5];   /* instrument */
 unsigned bitstring[8];   /* control number */
 bitstring[16];  /* value */

Listing 2 - Music.p

/* 2 */
UNIT Music;
 kMusicComponentType = 'musi';
 MusicDescription = RECORD
 size: LongInt; { including header }
 musicType: LongInt; { 'musi' }
 resvd1: LongInt; { 0 }
 resvd2: Integer;{ 0 }
 dataRefIndex: Integer; { 1 }
 musicFlags: LongInt; { 0 }
 headerData: ARRAY[1..1] OF LongInt; 
 { actually, some sort of tone descriptions }
 MusicDescriptionPtr = ^MusicDescription;
 MusicDescriptionHandle = ^MusicDescriptionPtr;

 TunePlayer = ComponentInstance;
 kTuneQueueDepth = 8;
 TuneStatus = RECORD
 tune, tunePtr: ^LongInt;
 time: longint;
 queueCount, queueSpots: Integer;
 queueTime: LongInt;
 reserved: ARRAY[1..3] OF LongInt;
 kStopTuneFade = 1;
 kStopTuneSustain = 2;
 kStopTuneInstant = 4;
 kStopTuneReleaseChannels = 8;
 MusicOpWord = LongInt;
 MusicOpWordPtr = ^MusicOpWord;
 kMaxTunePlayerParts = 32;
 tunePlayerRunning = -2100;
 kTunePlayerType = 'tune';

 FUNCTION TuneSetHeader (tp: TunePlayer;
 header: Ptr): ComponentResult;
 INLINE $2F3C, $4, 4, $7000, $A82A;

 FUNCTION TuneSetTimeScale (tp: TunePlayer;
 scale: LongInt): ComponentResult;
 INLINE $2F3C, $4, 6, $7000, $A82A;

 FUNCTION TuneGetTimeScale (tp: TunePlayer;
 VAR scale: LongInt): ComponentResult;
 INLINE $2F3C, $4, 7, $7000, $A82A;

 kTuneStartNow = 1;
 kTuneDontClipNotes = 2;
 kTuneExcludeEdgeNotes = 4;
 kTuneStartNewMaster = 16384;

 FUNCTION TuneQueue (tp: TunePlayer;
 tune: MusicOpWordPtr;
 tuneRate: Fixed;
 tuneStartPosition: LongInt;
 tuneStopPosition: LongInt;
 queueFlags: LongInt;
 callBackProc: ProcPtr;
 refCon: LongInt): ComponentResult;
 INLINE $2F3C, $1C, 10, $7000, $A82A;

 FUNCTION TuneGetStatus (tp: TunePlayer;
 VAR status: TuneStatus): ComponentResult;
 INLINE $2F3C, $4, 12, $7000, $A82A;

 kStopSustain = 1;
 kStopFadeout = 2;

 FUNCTION TuneStop (tp: TunePlayer;
 stopFlags: LongInt): ComponentResult;
 INLINE $2F3C, $4, 13, $7000, $A82A;

 FUNCTION TuneResume (tp: TunePlayer): ComponentResult;
 INLINE $2F3C, 0, 14, $7000, $A82A;

 FUNCTION TuneFlush (tp: TunePlayer): ComponentResult;
 INLINE $2F3C, 0, 15, $7000, $A82A;

 FUNCTION TuneSetVolume (tp: TunePlayer;
 volume: Fixed): ComponentResult;
 INLINE $2F3C, $4, 16, $7000, $A82A;

 FUNCTION TuneGetVolume (tp: TunePlayer): ComponentResult;
 INLINE $2F3C, 0, 17, $7000, $A82A;

 FUNCTION TunePreroll (tp: TunePlayer): ComponentResult;
 INLINE $2F3C, 0, 18, $7000, $A82A;

 FUNCTION TuneUnroll (tp: TunePlayer): ComponentResult;
 INLINE $2F3C, 0, 19, $7000, $A82A;


Listing 3 - MusicTest.p

/* 3 */
PROGRAM MusicTest;
 Components, Music;

 h: MusicDescriptionHandle;
 tp: TunePlayer;
 result: ComponentResult;
 theTuneStatus: TuneStatus;
 err: OSErr;

 10; { used for error cleanup }
 { Get the music resource and lock it down }
 h := MusicDescriptionHandle(GetResource('Musi', 128));

 { open the default tune player }
 tp := OpenDefaultComponent(kTunePlayerType,

 { tell that we have 600 units per second }
 result := TuneSetTimeScale(tp, 600);
 IF result  noErr THEN
 GOTO 10;

 { Set the header, to tell what instruments are used }
 result := TuneSetHeader(tp, @h^^.headerData);
 IF result  noErr THEN
 GOTO 10;

 { Have it allocate whatever resources are needed }
 result := TunePreRoll(tp);
 IF result  noErr THEN
 GOTO 10;

 { We want to play at normal volume }
 result := TuneSetVolume(tp, $10000);
 IF result  noErr THEN
 GOTO 10;

 { Queue up the music, normal tempo, play everything now }
 result := TuneQueue(tp, Pointer(ORD4(h^) + h^^.size),
 $10000, 0, $7FFFFFFF, kTuneStartNow, NIL, 0);
 IF result  noErr THEN
 GOTO 10;

 result := TuneGetStatus(tp, theTuneStatus);
 IF result  noErr THEN
 GOTO 10;
 { spin until we click the button or no music left queued up }
 UNTIL Button | (theTuneStatus.queueCount = 0);

 { We get here either by getting an error or having everything finish 
 { Regardless, we need to stop and clean up everything }
 IF result  noErr THEN
 DebugStr('Music result');
 result := TuneStop(tp, kStopFadeout);
 err := CloseComponent(tp);

 { And we are done }

Apple Inc.
Microsoft Corpora
Google Inc.

MacTech Search:
Community Search:

Software Updates via MacUpdate

Audio Hijack Pro 2.11.0 - Record and enh...
Audio Hijack Pro drastically changes the way you use audio on your computer, giving you the freedom to listen to audio when you want and how you want. Record and enhance any audio with Audio Hijack... Read more
Intermission 1.1.1 - Pause and rewind li...
Intermission allows you to pause and rewind live audio from any application on your Mac. Intermission will buffer up to 3 hours of audio, allowing users to skip through any assortment of audio... Read more
Airfoil 4.8.7 - Send audio from any app...
Airfoil allows you to send any audio to AirPort Express units, Apple TVs, and even other Macs and PCs, all in sync! It's your audio - everywhere. With Airfoil you can take audio from any... Read more
Microsoft Remote Desktop 8.0.8 - Connect...
With Microsoft Remote Desktop, you can connect to a remote PC and your work resources from almost anywhere. Experience the power of Windows with RemoteFX in a Remote Desktop client designed to help... Read more
xACT 2.30 - Audio compression toolkit. (...
xACT stands for X Aaudio Compression Toolkit, an application that encodes and decodes FLAC, SHN, Monkey’s Audio, TTA, Wavpack, and Apple Lossless files. It also can encode these formats to MP3, AAC... Read more
Firefox 31.0 - Fast, safe Web browser. (...
Firefox for Mac offers a fast, safe Web browsing experience. Browse quickly, securely, and effortlessly. With its industry-leading features, Firefox is the choice of Web development professionals... Read more
Little Snitch 3.3.3 - Alerts you to outg...
Little Snitch gives you control over your private outgoing data. Track background activityAs soon as your computer connects to the Internet, applications often have permission to send any... Read more
Thunderbird 31.0 - Email client from Moz...
As of July 2012, Thunderbird has transitioned to a new governance model, with new features being developed by the broader free software and open source community, and security fixes and improvements... Read more
Together 3.2 - Store and organize all of...
Together helps you organize your Mac, giving you the ability to store, edit and preview your files in a single clean, uncluttered interface. Smart storage. With simple drag-and-drop functionality,... Read more
Cyberduck 4.5 - FTP and SFTP browser. (F...
Cyberduck is a robust FTP/FTP-TLS/SFTP browser for the Mac whose lack of visual clutter and cleverly intuitive features make it easy to use. Support for external editors and system technologies such... Read more

Latest Forum Discussions

See All

Thomas Was Alone Goes Universal, Slashes...
Thomas Was Alone Goes Universal, Slashes Price to $3.99 Posted by Ellis Spice on July 24th, 2014 [ permalink ] Universal App - Designed for iPhone and iPad | Read more »
Book Your Appointment with F.E.A.R. this...
Book Your Appointment with F.E.A.R. | Read more »
It Came From Canada: Epic Skater
For all the hate that it gets for being a pastime for slackers, skateboarding really does require a lot of skill. All those flips and spins take real athleticism, and there’s all the jargon to memorize. Fortunately for us less extreme individuals,... | Read more »
Cultures Review
Cultures Review By Jennifer Allen on July 24th, 2014 Our Rating: :: SLOW-PACED EMPIRE BUILDINGiPad Only App - Designed for the iPad Cute it might seem, but Cultures is a bit too slow paced when it comes to those pesky timers to... | Read more »
More Paintings Have Been Added to Paint...
More Paintings Have Been Added to Paint it Back! Posted by Jessica Fisher on July 24th, 2014 [ permalink ] Universal App - Designed for iPhone and iPad | Read more »
The Order of Souls Review
The Order of Souls Review By Campbell Bird on July 24th, 2014 Our Rating: :: STORY GRINDUniversal App - Designed for iPhone and iPad The Order of Souls is a free-to-play, turn-based RPG with a genre-mixing art style, interesting... | Read more »
Revolution 60 Review
Revolution 60 Review By Jordan Minor on July 24th, 2014 Our Rating: :: LASS EFFECTUniversal App - Designed for iPhone and iPad Revolution 60 is a bold, cinematic action game with ambition to spare.   | Read more »
Matter (Photography)
Matter 1.0.1 Device: iOS Universal Category: Photography Price: $1.99, Version: 1.0.1 (iTunes) Description: Add stunning 3D effects to your photos with real-time shadows and reflections. Export your creations as photos or video loops... | Read more »
Fanatic Earth Review
Fanatic Earth Review By Brittany Vincent on July 24th, 2014 Our Rating: :: BY-THE-NUMBERSUniversal App - Designed for iPhone and iPad Kemco’s stable of mobile RPGs grows, but in Fanatic Earth’s situation it’s a case of quantity... | Read more »
Together for iOS (Productivity)
Together for iOS 1.0 Device: iOS Universal Category: Productivity Price: $9.99, Version: 1.0 (iTunes) Description: Together is an app for keeping things in one place. Notes, documents, images, movies, sounds, web pages and bookmarks... | Read more »

Price Scanner via

What Should Apple’s Next MacBook Priority Be;...
Stabley Times’ Phil Moore says that after expanding its iMac lineup with a new low end model, Apple’s next Mac hardware decision will be how it wants to approach expanding its MacBook lineup as well... Read more
ArtRage For iPhone Painting App Free During C...
ArtRage for iPhone is currently being offered for free (regularly $1.99) during Comic-Con San Diego #SDCC, July 24-27, in celebration of the upcoming ArtRage 4.5 and other 64-bit versions of the... Read more
With The Apple/IBM Alliance, Is The iPad Now...
Almost since the iPad was rolled out in 2010, and especially after Apple made a 128 GB storage configuration available in 2012, there’s been debate over whether the iPad is a serious tool for... Read more
MacBook Airs on sale starting at $799, free s...
B&H Photo has the new 2014 MacBook Airs on sale for up to $100 off MSRP for a limited time. Shipping is free, and B&H charges NY sales tax only. They also include free copies of Parallels... Read more
Apple 27″ Thunderbolt Display (refurbished) a...
The Apple Store has Apple Certified Refurbished 27″ Thunderbolt Displays available for $799 including free shipping. That’s $200 off the cost of new models. Read more
WaterField Designs Unveils Cycling Ride Pouch...
High end computer case and bag maker WaterField Designs of San Francisco now enters the cycling market with the introduction of the Cycling Ride Pouch – an upscale toolkit with a scratch-free iPhone... Read more
Kingston Digital Ships Large Capacity Near 1T...
Kingston Digital, Inc., the Flash memory affiliate of Kingston Technology Company, Inc.,has announced its latest addition to the SSDNow V300 series, the V310. The Kingston SSDNow V310 solid-state... Read more
Apple’s Fiscal Third Quarter Results; Record...
Apple has announced financial results for its fiscal 2014 third quarter ended June 28, 2014, racking up quarterly revenue of $37.4 billion and quarterly net profit of $7.7 billion, or $1.28 per... Read more
15-inch 2.0GHz MacBook Pro Retina on sale for...
B&H Photo has the 15″ 2.0GHz Retina MacBook Pro on sale for $1829 including free shipping plus NY sales tax only. Their price is $170 off MSRP. B&H will also include free copies of Parallels... Read more
Apple restocks refurbished Mac minis for up t...
The Apple Store has restocked Apple Certified Refurbished Mac minis for up to $150 off the cost of new models. Apple’s one-year warranty is included with each mini, and shipping is free: - 2.5GHz Mac... Read more

Jobs Board

Sr Software Lead Engineer, *Apple* Online S...
Sr Software Lead Engineer, Apple Online Store Publishing Systems Keywords: Company: Apple Job Code: E3PCAK8MgYYkw Location (City or ZIP): Santa Clara Status: Full Read more
Senior Interaction Designer, *Apple* Online...
**Job Summary** Apple is looking for a hands on Senior…will be a key player in designing for the Apple Online Store. The ideal designer will have a Read more
*Apple* Sales Chat Rep - Apple (United State...
…is looking for motivated, outgoing, and tech savvy individuals who want to offer Apple Customers an unparalleled customer experience over chat. At Apple , we believe Read more
Mac Expert - *Apple* Online Store Mexico -...
…MUST be fluent in English and Spanish to be considered for this position At Apple , we believe that hard work, a fun environment, creativity and innovation fuel the Read more
*Apple* Industrial Design CAD Sculptor - App...
**Job Summary** The Apple Industrial Design team is looking for a CAD sculptor/Digital 3D modeler to create high quality CAD models used in the industrial design process Read more
All contents are Copyright 1984-2011 by Xplain Corporation. All rights reserved. Theme designed by Icreon.