![]() A little reformatting is needed after these cues are recorded, but the motion can then be played back or further edited to scale the timing of the motions (make it faster of slower). Qlab then calculates the time elapsed between fade cues and writes the corresponding pre-wait and action time of the cue. The Group cues collapse nicely, hiding the workings from careless fingers: Here’s the script in the Script cue: tell application id '.3' to tell front workspace try set thefadetime to post wait of cue 'GO' as string set thecustommessage to '/panicInTime ' & thefadetime set the custom message of cue 'FADE' to thecustommessage. 5 seconds (limited by the compiling time of apple script) with the current XY values. ![]() I will go into more details below, but basically Qlab creates a fade cue about every. QLab creates a smooth fade between points, but you can make sharper changes by adding points close together. So a fade time of 0.5 sec would be 12 frames. We then setup in QLab a group for every action (DCA1 fade up, DCA1 fade down, etc) Each group then 1) disarms itself and 2) arms the inverse action This way we can repeat calls to a fade up / fade down command, but it only operates if it hasn't already been performed prior. This has to be done in a 24-frames-per-second manner. When you select TIMEDGO in Qlab you can enter the right fade-time in seconds / frames. A yellow line will appear along the top of the waveform view, and you can click and drag along the line to create fade points. I don't know why but the GMA seems to use some kind of standard fade time and does not take account of the fade-times that are programmed. The recording portion on the other hand takes a few more steps. To use the integrated fade envelope, check the box marked Use integrated fade to the right of the waveform view. The live playback portion simply takes the value for each speaker and writes it to the reference audio cue in real time. These values are then written to another set of memo cues that are referenced for the "live playback" portion and the "recording" portion. Qlab then calculates the level of the speakers using the sum or difference of the XY midi values put into a parabolic equation. Target your Fade Action to an Audio Cue that you want to Fade by:a)Naming Audio Cue specifically, and editing the Target on the Fade cue.b) Click and Drag the. These values are then referred to in the following step. When a Fade cue targets a Group cue, QLab attempts to apply the result of that fade to all the child cues within the Group. ![]() These then trigger a corresponding OSC cue that renames a memo cue (utilized as a global variable) with the raw midi value. The Ipad using "Touch OSC" sends two midi messages to Qlab for the X and Y values. In a nutshell, the program needs to take inputs from the XY pad on the ipad, calculate the relative level of the speakers, and record these movements to play back on command.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |