Lines Matching full:clip
712 moment the game event occurs might result in a music clip starting in the
713 middle. Alternatively, a clip could be started from the beginning, but then it
718 <p class=MsoNormal>However, with the JET sync engine, a clip can be started at
721 w:st="on">MIDI</st1:place> event in the stream signifies the start of a clip
722 and a second event signifies the end of a clip. When the application calls the
723 JET clip function, the next clip in the track is allowed to play fully
838 103<span style='mso-tab-count:2'>?????????????????????? </span>JET clip marker</p>
909 <h4>Controller 103 ? JET Clip Marker</h4>
913 API call. The clip ID is encoded in the low 6 bits of the controller value. Bit
914 6 is set to one to indicate the start of a clip, and set to zero to indicate
915 the end of a clip.</p>
919 <p class=MsoNormal>For example, to identify a clip with a clip ID of 1, the
921 controller=103 and value=65 at the start of the clip and another event with controller=103
922 and value=1 at the end of the clip. When the JET_TriggerClip() function is
923 called with a clip ID of 1, the track will be un-muted when the controller
944 style='mso-element:field-end'></span><![endif]-->: Synchronized Clip</p>
950 first controller event occurs, the first clip will play, and the track will be
953 be un-muted when the third controller event occurs, the second clip will play,
959 the track containing the clip is muted by the application when the segment is
960 initially queued by the call to JET_QueueSegment(). If it is not muted, the clip
961 will always play until Jet_TriggerClip() has been called with the clip ID.</p>
1264 <p class=MsoNormal>Automatically updates mute flags in sync with the JET Clip
