Home | History | Annotate | Download | only in docs

Lines Matching full:midi

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
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
1640 name of the SONiVOX MIDI synthesizer engine.</span></p>
1652 the overall composition. In JET, a segment can be an entire MIDI file or a
1653 derived from a portion of a <st1:place w:st="on">MIDI</st1:place> file.</span></p>
1658 lang=EN-IE>: Standard MIDI File Type 0, a MIDI file that contains a single
1659 track, but may be made up of multiple channels of <st1:place w:st="on">MIDI</st1:place>
1665 lang=EN-IE>: Standard MIDI File Type 1, a MIDI file that contains a one more
1667 w:st="on">MIDI</st1:place> data. By convention, each channel is stored on a
1668 separate track in an SMF-1 file. However, it is possible to have multiple MIDI
1670 w:st="on">MIDI</st1:place> channel.</span></p>
1676 w:st="on">MIDI</st1:place> events. Be careful not to confuse Tracks with
1677 Channels. A MIDI file may contain many tracks with several tracks utilizing the
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
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
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>
2002 MIDI Synthesizer and DLS2 soundsets that will be utilized in the Android
2011 plugin uses the same SONiVOX EAS MIDI synthesizer engine and default General
2012 MIDI<span style='mso-spacerun:yes'>? </span>wavetable soundset inherent in
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>
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
2043 include mute and unmute settings of individual tracks in the MIDI file(s) as
2044 well as <st1:place w:st="on">MIDI</st1:place> controller numbers that serve as
2082 w:st="on">MIDI</st1:place> sequence. The EAS Synth plugin allows for the
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
2166 Drums. The reason for this is that MIDI controller messages, such as Volume
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 MIDI</st1: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
2203 <p class=MsoNormal><span lang=EN-IE>Select All and use the ?Insert MIDI &gt;
2204 Insert MIDI Settings as Events? command.</span></p>
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
2222 When saving, be sure to select MIDI Type 1.</span></p>
2246 simultaneous soundsets or wavetables. One is the internal General MIDI wavetable
2250 SONiVOX format. The DLS2 soundsets are an open format published by the MIDI
2279 your MIDI Program Changes set correctly. DLS2 instruments must be assigned to a
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>
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
2417 hallway with no fighting might play the same midi file but mute tracks 9-16.
2429 method the game is utilizing JET Application Events, MIDI controllers that are
2430 embedded in the <st1:place w:st="on">MIDI</st1:place> file and read by the game