Lines Matching full:midi
460 to include interactive music soundtracks, in <st1:place w:st="on">MIDI</st1:place>
466 Synthesizer (EAS) which is the <st1:place w:st="on">MIDI</st1:place> playback
493 Since JET uses <st1:place w:st="on">MIDI</st1:place> in a unique way, normal
499 <p class=MsoNormal><i style='mso-bidi-font-style:normal'>Channel</i>: MIDI data
500 associated with a specific <st1:place w:st="on">MIDI</st1:place> channel.
501 Standard MIDI allows for 16 channels of <st1:place w:st="on">MIDI</st1:place>
507 w:st="on">MIDI</st1:place> event consisting of a channel number, controller
508 number, and a controller value. The <st1:place w:st="on">MIDI</st1:place> spec
511 embedding special control information in a <st1:place w:st="on">MIDI</st1:place>
517 Workstation. A common term for <st1:place w:st="on">MIDI</st1:place> and audio
523 w:st="on">MIDI</st1:place> Synthesizer. The name of the SONiVOX MIDI
535 composition. In JET, a segment can be an entire MIDI file or a derived from a
536 portion of a <st1:place w:st="on">MIDI</st1:place> file.</p>
541 MIDI File Type 0, a MIDI file that contains a single track, but may be made up
542 of multiple channels of <st1:place w:st="on">MIDI</st1:place> data.</p>
547 MIDI File Type 1, a MIDI file that contains a one more tracks, and each track
548 may in turn be made up of one or more channels of <st1:place w:st="on">MIDI</st1:place>
550 file. However, it is possible to have multiple MIDI channels on a single track,
551 or multiple tracks that contain data for the same <st1:place w:st="on">MIDI</st1:place>
557 track in a DAW containing a timed sequence of <st1:place w:st="on">MIDI</st1:place>
558 events. Be careful not to confuse Tracks with Channels. A MIDI file may contain
559 many tracks with several tracks utilizing the same <st1:place w:st="on">MIDI</st1:place>
644 segment is authored as a separate <st1:place w:st="on">MIDI</st1:place> file. A
721 w:st="on">MIDI</st1:place> event in the stream signifies the start of a clip
725 a second <st1:place w:st="on">MIDI</st1:place> event.</p>
749 embedded in the <st1:place w:st="on">MIDI</st1:place> file at the time the
807 w:st="on">MIDI</st1:place> streams that are synchronized to sound like a
815 <p class=MsoNormal>JET uses standard <st1:place w:st="on">MIDI</st1:place>
823 <p class=MsoNormal>JET uses <st1:place w:st="on">MIDI</st1:place> controller
825 defined for specific use by the <st1:place w:st="on">MIDI</st1:place>
852 in a <st1:place w:st="on">MIDI</st1:place> segment to queue up the next
859 w:st="on">MIDI</st1:place> streams that are specific to JET functionality.
866 repeats the current segment) when the <st1:place w:st="on">MIDI</st1:place>
867 end-of-track meta-event is encountered. Some <st1:place w:st="on">MIDI</st1:place>
912 w:st="on">MIDI</st1:place> track that can be triggered by the JET_TriggerClip
920 author inserts a <st1:place w:st="on">MIDI</st1:place> controller event with
1000 allow the application to monitor <st1:place w:st="on">MIDI</st1:place> events
1094 can be opened at a time. However, since JET can contain many <st1:place w:st="on">MIDI</st1:place>
1164 <p class=MsoNormal>Queues up a JET MIDI segment for playback. The parameters
1176 standard General MIDI library.</p>
1194 Specific which MIDI tracks (not <st1:place w:st="on">MIDI</st1:place> channels)
1316 <p class=MsoNormal>JET uses standard MIDI files and DLS files that can be
1318 Digital Performer, or SONAR for <st1:place w:st="on">MIDI</st1:place> files and
