Lines Matching full:st1
5 xmlns:st1="urn:schemas-microsoft-com:office:smarttags"
83 st1\:*{behavior:url(#ieooui) }
1570 platform. It allows applications to include interactive music soundtracks, in <st1:place
1571 w:st="on">MIDI</st1:place> format, that respond in real-time to game play
1577 Embedded Audio Synthesizer (EAS) which is the <st1:place w:st="on">MIDI</st1:place>
1587 different applications to create JET content; a standard <st1:place w:st="on">MIDI</st1:place>
1607 terms to minimize confusion. Since JET uses <st1:place w:st="on">MIDI</st1:place>
1615 lang=EN-IE>: MIDI data associated with a specific <st1:place w:st="on">MIDI</st1:place>
1616 channel. Standard MIDI allows for 16 channels of <st1:place w:st="on">MIDI</st1:place>
1622 lang=EN-IE>: A <st1:place w:st="on">MIDI</st1:place> event consisting of a
1623 channel number, controller number, and a controller value. The <st1:place
1624 w:st="on">MIDI</st1:place> spec associates many controller numbers with
1627 <st1:place w:st="on">MIDI</st1:place> sequence to provide for audio
1633 lang=EN-IE>: Digital Audio Workstation. A common term for <st1:place w:st="on">MIDI</st1:place>
1639 lang=EN-IE> Embedded <st1:place w:st="on">MIDI</st1:place> Synthesizer. The
1653 derived from a portion of a <st1:place w:st="on">MIDI</st1:place> file.</span></p>
1659 track, but may be made up of multiple channels of <st1:place w:st="on">MIDI</st1:place>
1666 tracks, and each track may in turn be made up of one or more channels of <st1:place
1667 w:st="on">MIDI</st1:place> data. By convention, each channel is stored on a
1669 channels on a single track, or multiple tracks that contain data for the same <st1:place
1670 w:st="on">MIDI</st1:place> channel.</span></p>
1675 lang=EN-IE>: A single track in a DAW containing a timed sequence of <st1:place
1676 w:st="on">MIDI</st1:place> events. Be careful not to confuse Tracks with
1678 same <st1:place w:st="on">MIDI</st1:place> channel. </span></p>
1775 stored. Each segment is authored as a separate <st1:place w:st="on">MIDI</st1:place>
1855 track. A <st1:place w:st="on">MIDI</st1:place> event in the stream signifies
1859 automatically muted by a second <st1:place w:st="on">MIDI</st1:place> event.</span></p>
1883 relies on data embedded in the <st1:place w:st="on">MIDI</st1:place> file at
1942 work together smoothly. The first is application is any off-the-shelf <st1:place
1943 w:st="on">MIDI</st1:place> sequencing application or Digital Audio Workstation
1945 Here the author will compose their <st1:place w:st="on">MIDI</st1:place> music
1950 <p class=MsoNormal><span lang=EN-IE>Once the composer has completed their <st1:place
1951 w:st="on">MIDI</st1:place> file(s), they import them into the JET Creator application.
1960 the <st1:place w:st="on">MIDI</st1:place> files.</span></p>
1979 lang=EN-IE>Compose and save <st1:place w:st="on">MIDI</st1:place> file(s)</span></li>
1985 lang=EN-IE>Create segments using the <st1:place w:st="on">MIDI</st1:place>
1999 use a third party MIDI authoring application to compose their <st1:place w:st="on">MIDI</st1:place>
2014 rendering of the instruments and <st1:place w:st="on">MIDI</st1:place> file
2028 <p class=MsoNormal><span lang=EN-IE>Compose MIDI File ? Compose <st1:place
2029 w:st="on">MIDI</st1:place> soundtracks for the Android application.</span></p>
2033 <p class=MsoNormal><span lang=EN-IE>Launch JET Creator ? Once all DLS2 and <st1:place
2034 w:st="on">MIDI</st1:place> source files have been authored, the content author
2036 will reference the <st1:place w:st="on">MIDI</st1:place> files and any custom
2044 well as <st1:place w:st="on">MIDI</st1:place> controller numbers that serve as
2081 composer to hear the instruments used in Android as they are composing their <st1:place
2082 w:st="on">MIDI</st1:place> sequence. The EAS Synth plugin allows for the
2132 <p class=MsoNormal><span lang=EN-IE>Windows 2000 or <st1:place w:st="on">Vista</st1:place>
2147 </span></span></span><![endif]><span lang=EN-IE>Assigning <st1:place w:st="on">MIDI</st1:place>
2151 assigning <st1:place w:st="on">MIDI</st1:place> tracks to virtual instrument
2162 <st1:place w:st="on">MIDI</st1:place> channels in a single instance) In Logic
2165 its own <st1:place w:st="on">MIDI</st1:place> channel. Use Channel 10 for
2168 a single Instrument and all <st1:place w:st="on">MIDI</st1:place> tracks are
2169 set to playback on that Instrument. In order for each <st1:place w:st="on">MIDI</st1:place>
2186 <p class=MsoNormal><span lang=EN-IE>To write out a standard <st1st1:place>
2190 such non-destructive edit. Therefore when you export a <st1:place w:st="on">MIDI</st1:place>
2197 write out with the <st1:place w:st="on">MIDI</st1:place> file. Before exporting
2198 a <st1:place w:st="on">MIDI</st1:place> file in Logic it is recommended you do
2218 save than Logic 8. Simply open or start a new <st1:place w:st="on">MIDI</st1:place>
2220 Synth. Then assign each <st1:place w:st="on">MIDI</st1:place> track?s output to
2287 General MIDI Level 1 specification. Note: Most <st1:place w:st="on">MIDI</st1:place>
2299 number is in your <st1:place w:st="on">MIDI</st1:place> sequence. </span></p>
2303 <p class=MsoNormal><span lang=EN-IE>In your <st1:place w:st="on">MIDI</st1:place>
2353 final <st1:place w:st="on">MIDI</st1:place> file as needed for the application.
2359 be changes to the <st1:place w:st="on">MIDI</st1:place> file(s) and JET Creator
2369 compose as few MIDI files as possible, and create several segments from that <st1:place
2370 w:st="on">MIDI</st1:place> file. For example a 12 bar <st1:place w:st="on">MIDI</st1:place>
2372 Simply create multiple segments that reference the one <st1:place w:st="on">MIDI</st1:place>
2414 triggering mute and unmute events to specific tracks in a single <st1:place
2415 w:st="on">MIDI</st1:place> sequence. For example a hallway with lots of
2416 fighting might play <st1:place w:st="on">MIDI</st1:place> tracks 1-16 and a
2430 embedded in the <st1:place w:st="on">MIDI</st1:place> file and read by the game
