Post
by mikemc » Fri Apr 09, 2010 3:26 am
fwiw, I just tried something prior to seeing zoe's screenshot and dennis' questions. (I'm on windows vista).
Here is what i did
1- Put a clip into session view sending midi note out thru a midi yoke (loopbe30) and set up midi map so this activates the global transport record button. Loopbe30 was set up in preferences as sending midi out thru track and back in as remote.
2- Global loop was active, but punch in/out were not active.
3- Armed the audio input track, and kept it armed.
4- I set the arrangement loop to start after 4 beats, and loop for another 4 beats.
The session "triggering" clip was 4 beats, with the triggering note on the first beat. So when I started the clip, this armed the global record, allowing recording audio, and then when it looped back around to "1" when the arrangment was coming into the global looped region (starting on beat 5) for the first time it disarmed the global record, and then re-armed it repeatedly every other time as the arrangement loop came back around.
Here is what I saw doing simply the above:
Triggering the scene started the transport, and the midi note armed the global record button. But this did not happen instantly, precisely on "1". Because the global transport is running, the triggering MIDI clip is recorded into the arrangement as well as the audio, and because recording did not happen precisely on "1", that arrangment- recorded triggering clip's start marker is behind the triggering note. So what actually happens when the loop in session comes back around, is a multiple triggering, one coming from the reflected clip in arrange, which results in a little tiny wee audio clip followed by the longer 'intended' clip.
(with punch in/out active, you can't see this happening as plainly, because the triggering clip is not reflected in arrangement.)
you might want to try this with punch in/out deactivated, to see if you see the same thing.
[edit] not sure how to work around this, if this is the same problem you are seeing. I'm thinking you'll need to mess with the track latency, but then it is hard to know when "1" is at the very get go.
UTENZIL a tool... of the muse.
) 1, 2 .... etc; etc;