>> Route them thru a bus and insert logics sample delay John Pitcairn wrotes > Yeah, looks like that's what I'll have to do, but it means the > regions' _positions_ will still be inaccurate for editing purposes. > And any sends from those tracks won't have the correct delay > applied, so maybe I'll have to whack a sample delay onto every > software-monitored recorded track. Bummer. But if you're really fussy, you could then bounce them back. As for the track parameter delay. If you have it set in ms. It is independent of the tempo, though not accurate enough, 1.5ms. =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Matt McKenzie-Smith PO Box 10395 Adelaide BC 5000 South Australia +618(0)82938282 +61(0)416 197 883 mattrixx@...

--- In logic-users@y..., Matt McKenzie-Smith <mattrixx@o...> wrote: > But if you're really fussy, you could then bounce them back. True. Or if there are a shitload of i/o to spare, it's possible to do a little bit of loopback and record the _monitored_ signal, not the initial input signal. The goal being what-you-heard-is-what-you-get with no thinking required. Unfortunately I don't have the luxury of enough spare inputs... > As for the track parameter delay. If you have it set in ms. It is > independent of the tempo, though not accurate enough, 1.5ms. Unfortunately it just _displays_ the delay in ms, so it's still tempo dependent - set a delay in ms and change the tempo ... you had me excited there, oh well... John Pitcairn ------------------------------------------------------------------ Midi controller learn in Logic. Soft takeover. Lots of memories. Tracks remember control assignments. Write track automation. Fadermapper demo: http://www.revolver.co.nz/fadermapper/ ------------------------------------------------------------------

> Unfortunately it just _displays_ the delay in ms, so it's still tempo > dependent - set a delay in ms and change the tempo ... you had > me excited there, oh well... I don't have your original post - am I correct in thinking it was a shift of 322 samples? well - at 44.1 that would be a shift of 7.3 ms at 25 fps a smpte bit is 0.5 ms so you want to shift 15 bits enable smpte w bits view in arrange level event list - highlight the objects you want and scroll 15 bits this should do what you want it is not sample accurate (maybe by a dozen samples) but well beneath perception it is not tempo dependent - at least in terms of the amount of shift - and should you want to keep them from moving against external video you can always lock position best I can think of