I need to move several freshly-recorded audio regions, one per track, 322 samples later to preserve accurate timing. This is all to do with source-monitored vs software-monitored recording, as discussed in my post about using external FX. I'll need to do this quite often. Pasting 322 samples of silence at the start of each audio region in the Sample Editor will be a tedious procedure, unless there's a way to do it quickly. Bussing the tracks to a sample delay is problematic because A) it's still inaccurate for editing purposes, and B) there might be stuff recorded elsewhere on those tracks that _doesn't_ need to be compensated by +322 samples (though I suppose I could avoid doing that). Any bright ideas? John Pitcairn ----------------------------------------------------------------- Got midi fader/knob hardware? Want to control/automate Logic? Fadermapper demo: http://www.revolver.co.nz/fadermapper/ -----------------------------------------------------------------

From: "John Pitcairn" <johnp@...> > I need to move several freshly-recorded audio regions, one per > track, 322 samples later to preserve accurate timing. This is all > to do with source-monitored vs software-monitored recording, as > discussed in my post about using external FX. I'll need to do this > quite often. > > Pasting 322 samples of silence at the start of each audio region > in the Sample Editor will be a tedious procedure, unless there's > a way to do it quickly. > > Bussing the tracks to a sample delay is problematic because A) > it's still inaccurate for editing purposes, and B) there might be > stuff recorded elsewhere on those tracks that _doesn't_ need to > be compensated by +322 samples (though I suppose I could > avoid doing that). > > Any bright ideas? John, do you wish the offset in the part info box would be editable in samples? I do. ;-) I guess for now the bussing/sample-delay plug-in is the way to go. :-/ Peter --- http://www.merlinsound.de

John Pitcairn wrote: > Any bright ideas? Maybe not bright but why not use the delay function in the parameters?

> Any bright ideas? Route them thru a bus and insert logics sample delay Muhammed

> John Pitcairn wrote: > > Any bright ideas? From: "homburg" <homburg@...> > Maybe not bright but why not use the delay function in the parameters? That´s not sample-accurate (AFAIR 1,5ms resolution). Peter --- http://www.merlinsound.de

--- In logic-users@y..., homburg <homburg@c...> wrote: > Maybe not bright but why not use the delay function in the > parameters? That's a delay in ticks, which is tempo-dependent. I don't want to have to calculate the amount of delay for each tempo I use, I just want to have a "standard" nudge or delay amount I can remember... John Pitcairn ----------------------------------------------------------------- Got midi fader/knob hardware? Want to control/automate Logic? Fadermapper demo: http://www.revolver.co.nz/fadermapper/ -----------------------------------------------------------------

--- In logic-users@y..., "Newtown Music" <muhammed@n...> wrote: > Route them thru a bus and insert logics sample delay 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. John Pitcairn ----------------------------------------------------------------- Got midi fader/knob hardware? Want to control/automate Logic? Fadermapper demo: http://www.revolver.co.nz/fadermapper/ -----------------------------------------------------------------

--- In logic-users@y..., "Peter Duemmler" <merlin@m...> wrote: > do you wish the offset in the part info box would be editable in > samples? That's a big fat yes...! Or a decent record delay setup (per input). Or a sample-accurate Arrange. Or plugins on inputs that can be recorded without being monitored. John Pitcairn ----------------------------------------------------------------- Got midi fader/knob hardware? Want to control/automate Logic? Fadermapper demo: http://www.revolver.co.nz/fadermapper/ -----------------------------------------------------------------

"John Pitcairn" <johnp@r...> wrote: > I need to move several freshly-recorded audio regions, one per > track, 322 samples later to preserve accurate timing. This is all > to do with source-monitored vs software-monitored recording, as > discussed in my post about using external FX. I'll need to do this > quite often. > > Pasting 322 samples of silence at the start of each audio region > in the Sample Editor will be a tedious procedure, unless there's > a way to do it quickly. > > Bussing the tracks to a sample delay is problematic because A) > it's still inaccurate for editing purposes, and B) there might be > stuff recorded elsewhere on those tracks that _doesn't_ need to > be compensated by +322 samples (though I suppose I could > avoid doing that). > > Any bright ideas? May I ask a (maybe) very stupid question: WHY the hell do you HAVE to move SOME regions by 322 samples? Not only because I'm interested in what other power users trick out of Logic but maybe there's an easier solution for your problem... Marc

--- In logic-users@y..., "der_jazzman" <vibeklub@w...> wrote: > May I ask a (maybe) very stupid question: WHY the hell do you HAVE to move SOME regions by 322 > samples? Because with Logic's rather inadequate record delay compensation, you can attempt (note: attempt) to provide correct record-placement for source-monitored tracks, or software monitored tracks, but not both. The differing latencies involved mean different record-delay settings are required, depending on how you monitor. Logic provides a single fairly inaccurate record delay setting for ASIO drivers - if you use a combination of source- and software-monitoring, and you want what plays back to have exactly the same timing as what you monitored, _and_ be placed correctly for editing, then some post-record nudging is generally necessary for one or the other, if not both. A 322-sample record misplacement is definitely noticeable with fast percussive material ... I just moved a recorded bassline that was placed 322 samples early due to recording while software monitoring (with record delay set for source monitoring). John Pitcairn ----------------------------------------------------------------- Got a controller? Wish there was a midi learn function in Logic? Fadermapper demo: http://www.revolver.co.nz/fadermapper/ -----------------------------------------------------------------

Hi > Because with Logic's rather inadequate record delay > compensation, you can attempt (note: attempt) to provide correct > record-placement for source-monitored tracks, or software > monitored tracks, but not both. This has been on my mind for a little while now. It's strange how this little problem still exists considering the 'Pro' status Logic has?! Kim

> > I need to move several freshly-recorded audio regions, one per > > track, 322 samples later to preserve accurate timing. > > > > Any bright ideas? Maybe someone's already mentioned this, but wouldn't the simplest method be to 1. use VIEW: delay as ms. 2. Select all your tracks on the arrange page and delay them the appropriate number of milliseconds (you'd have to figure out what 322 samples amounts to), 3. Hit Shift-N to normalize the playback parameters and shift the audio for good. It may seem like a pain (which it is) but at least you can do it pretty quickly, and work on mulitiple tracks at once. Anyway, that's the way I usually do it. I really wish Logic had a way to link multiple audio tracks together so that if you dragged the anchor point of one in the editor it would affect all the others as well. It would make editing multi- track drum stuff much easier. cheers

--- In logic-users@y..., "timsonian" <timburns@p...> wrote: > Maybe someone's already mentioned this, but wouldn't the simplest > method > be to 1. use VIEW: delay as ms. 2. Select all your tracks > on the arrange page and delay them the appropriate number of > milliseconds (you'd have to figure out what 322 samples amounts to), > 3. Hit Shift-N to normalize the playback parameters and shift the > audio for good. Nope. View in milliseconds is just that - view-only. The actual delay is still in ticks, and still tempo-dependent. And when you normalize the parameters, the move is in ticks. We've been over this before, please review the whole thread. 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/ ------------------------------------------------------------------

From: "timsonian" <timburns@...> > Maybe someone's already mentioned this, but wouldn't the simplest method > be to 1. use VIEW: delay as ms. 2. Select all your tracks on the arrange page > and delay them the appropriate number of milliseconds (you'd have to figure > out what 322 samples amounts to), 3. Hit Shift-N to normalize the playback > parameters and shift the audio for good. > > It may seem like a pain (which it is) but at least you can do it pretty quickly, > and work on mulitiple tracks at once. You won´t get sample accurate that way. :-( > Anyway, that's the way I usually do it. I really wish Logic had a way to link > multiple audio tracks together so that if you dragged the anchor point of one in > the editor it would affect all the others as well. It would make editing multi- > track drum stuff much easier. Yes. An old wish. Peter --- http://www.merlinsound.de