Post by mindlessinertia on Jun 12, 2019 22:57:18 GMT -5
i'm encountering an issue with the PLAY action: given a somewhat high number of longer audio clips in a scene, and with Quantization set to something other than None, PLAY applied to a range of tracks will often fail to launch all the clips in the Scene. the clips that don't launch fire at the next quantization point.
the behavior is inconsistent from launch to launch: the number of clips that don't fire right away ranges seemingly randomly from 0 to all, and anything in between. i've seen this with as few as 8 or 9 clips, though it's more apparent with a larger range. i haven't been able to reproduce it with very short clips, or with MIDI clips of any length, but it happens within a few tries with audio clips from a couple of seconds to a few minutes long, and even if all the clips are the same.
my x-control is as follows:
test = note, 1, 0, 0, 0, 1-20/play
in the debug log attached below, with 10 launch attempts, the number of clips that launched immediately out of expected 20 was as follows:
The PLAY action simply tells Live to launch clip slots. It has no control over when they actually launch. Live dictates that based on the quantization settings you're using. It sounds like you're saying this doesn't occur when using quantization of None. If that's the case, then the PLAY action is doing precisely what it should be doing and there is some other factor you need to look at.
On a related note, you mention that 'PLAY applied to a range of tracks will often fail to launch all the clips in the Scene'. That isn't how the naked PLAY action necessarily works. As mentioned in the manual:
When triggered via an X-Clip, Launch the Clip Slot on the same Scene as the X-Clip. Otherwise, re-Launch the playing Clip Slot or Launch the Clip Slot at the selected Scene.
If you're trying to launch clips on a particular scene from an X-Control, you should specify the scene. For example, PLAY SEL will launch the clips on the selected scene.
Post by mindlessinertia on Jun 13, 2019 12:00:59 GMT -5
i neglected to mention a couple of things that may be relevant: before triggering the X-Control, transport is stopped, and no clips are playing. also, the problem always occurs from left to right: a number of clips in tracks from 1 through x fire right away, and the rest of the clips to the right wait until the next quantization point. it may be that this is a timing issue: because the clips are fired sequentially from left to right (almost instantaneously, but not quite), for a number of them on the right it looks like transport is already past the 1st quantization point, and they have to wait for the next one.
incidentally, i was wrong about very short audio clips and MIDI clips – they do exhibit the same behavior, though with MIDI clips it happens much more rarely, and further to the right.
what i'm trying to achieve is an ability to fire a number of quantized clips in a scene from a stopped transport with either of two controllers, which operate on different MIDI channels. one of the controllers is using Live's Track Launch function, and it was my expectation that the PLAY action on an X-Control would act in the same way for the 2nd controller (i did in fact have PLAY SEL in my set, but in this situation PLAY does the same thing). however, it sometimes misses some of the right-most clips, where Track Launch never does.
is there something i can do differently to get the desired result? thanks, Stray d
Interesting. Yes, the fact that transport is stopped is definitely relevant. Live is having to do quite a bit in that case and so it has to prioritize. While it's typically not noticeable, scripts are low priority. Further, ClyphX Pro is dynamic in that it figures out what it needs to do when it's asked to do it. So, it's quite different from static MIDI mapping, which also has a higher priority.
In terms of what you can do, if you'll only be triggering the action in question when transport is stopped, try using PLAYQ NONE instead of PLAY. Or reorganize the set so you can either launch a whole scene or group the tracks so that you can launch the group. It could also be possible to use a user action to remove some of the dynamism. For example, you could explicitly launch tracks without ClyphX Pro having to dynamically locate them first.