Lines Matching full:controller
506 <p class=MsoNormal><i style='mso-bidi-font-style:normal'>Controller</i>: A <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
509 associates many controller numbers with specific functions, such as volume,
510 expression, sustain pedal, etc. JET also uses controller events as a means of
823 <p class=MsoNormal>JET uses <st1:place w:st="on">MIDI</st1:place> controller
826 specification. The specific controller definitions are as follows:</p>
834 <p class=MsoNormal><span style='mso-tab-count:1'>??????????? </span>Controller 102<span
837 <p class=MsoNormal><span style='mso-tab-count:1'>??????????? </span>Controller
849 own purposes. When a controller in this range is encountered, the event is
856 <h4>Controller 102 ? JET Event Marker</h4>
858 <p class=MsoNormal>Controller 102 is reserved for marking events in the <st1:place
874 end-of-segment marker (controller=102, value=0) at the point where the segment is
909 <h4>Controller 103 ? JET Clip Marker</h4>
911 <p class=MsoNormal>Controller 103 is reserved for marking clips in a <st1:place
913 API call. The clip ID is encoded in the low 6 bits of the controller value. Bit
920 author inserts a <st1:place w:st="on">MIDI</st1:place> controller event with
921 controller=103 and value=65 at the start of the clip and another event with controller=103
923 called with a clip ID of 1, the track will be un-muted when the controller
924 value 65 is encountered and muted again when the controller value 1 is
949 called prior to the first controller event, Track 3 will be un-muted when the
950 first controller event occurs, the first clip will play, and the track will be
951 muted when the second controller event occurs. If the JET_TriggerClip()
952 function is called after the first controller event has occurred, Track 3 will
953 be un-muted when the third controller event occurs, the second clip will play,
954 and the track will be muted again when the fourth controller event occurs.</p>
1003 initialized with the appropriate values with the low and high controller
1033 careful placement of application controller events near the end of a segment so
1069 means that only controller events in the application range (80-83) will end up
1071 S_JET_CONFIG data structure and set the controller range to a different range.
1239 or controller events will be processed during the next audio frame. If the <i
1252 notes or controller events will be processed during the next audio frame. If
1265 Marker (controller 103). The parameter <i style='mso-bidi-font-style:normal'>clipID</i>
1267 encounters a controller event 103 with bits 0-5 of the value equal to <i
1270 the controller event. When JET encounters the complementary controller event