Post
by salatspinatra » Tue Aug 30, 2011 9:13 pm
I see. So if you had a clip of any arbitrary length and you renamed it
[nextScene] (lseq) DUMMY; n/ scene >
Where n is the track name or number where the clip resides, assuming you have the xclip loop button engaged (which in this case will not actually loop the clip) the clip will play in full and then launch the next clip when it's complete, correct?
or better yet:
[nextClip] (lseq) DUMMY; PLAY >
Might be nice to figure out a way to self reference a clip, say using a command like THIS
That way, the 2nd time around on the examples above, you could also send the command CLIP LOOP OFF.
what other applications would you use relative scene/clip launching for?
I'm a dj first, and aside from playing other instruments, I'm everything else: producer, editor, etc a distant second. What other implications does relative scene triggering have to my performing? Currently, I don't use "select next (master) scene on launch", and sometimes I like to move the main bpm along with the clip seq tempo. I use a button to select a track in clip view which helps with my cueing, but unfortunately I can't maintain the focus on the last clip while firing the next: the next clip will always be viewable when I select it for firing (naturally) which makes keeping an eye on drop outs and the ending of the last clip just a little less precise. Would relative firing help with this? How could I use SHOWCLIP to keep the last track in view while keeping the next one selected and ready to fire?
With my djing in mind, are there any other clyphx gems that you imagine I may have overlooked? I know its a vague question! Currently, I'm underutilizing Macrobat, and I just migrated all my routine AU plugins to their vst equivalent.
I know that tempo automation is tough on playback, but what I'm really hoping to set up is a workaround for the fact that session view clips don't have a master/slave toggle upon the main tempo. Why? Just because I'm trying to warp a tune to beatmatch or to include sequencing and midi doesn't mean I always want to loose all the nuance of tempo fluctuations. I'm aiming to set up a clip that:
1) Fires an arrangement locator where I've converted the tempo changes in a master clip to the main tempo automation lane. The clip itself in arrangement would already be deleted.
2) simultaneously fires the equivalent clip in session view
Specifications are such that it does not trigger back to arrangement, or at least offers a work around to record arrangement even if the tempo automation is already in place while I'm still playing in session. I'd want to be able to use many separate session clips to perform this trick such that depending on what scene I put them on I'd know that the right locator in arrangement was starting up the correct tempo map.
I can see SCENE RND being very useful in sound installations, breakbeats, and live remixes if you set up your tunes the way Tom Cosm recommends.