Yahoo Groups archive

Elektron Musical Instruments

Index last updated: 2026-04-28 23:22 UTC

Message

Re: [elektron] timing problems with MD, please help me!

2005-02-14 by Federico Ciapi

>>>  I need
>>> to use few milliseconds of delay to keep the MD in time with Logic.
>>> Otherwhise, setting machinedrum  as master and logic as slave, give
>>> me the same timing problem.
>>
>> Do you mean that the MD stays in time but it's early (or late) ?
>
> MD it's late of few milliseconds, usually I put  -8 milliseconds in 
> the delay panel.
>

That's common behaviour, don't worry about that; any other timing 
issues?

Here are some good tips about logic and audio/midi latencies, you may 
find them useful.
have a look at the record offset parameter in Logic.


>
> OK, for Logic:
>
>  Start by measuring your record offset and and setting the record 
> delay driver parameter for source-monitored material. Follow the 
> instructions at http://www.opuslocus.com/logic/latency.html
>
>  If you are software-monitoring through Logic (not via MOTU CueMix or 
> RME TotalMix or such), the record delay calculated as above will 
> likely result in recordings that playback too early relative to 
> prerecorded tracks. How early will vary, according to whether and how 
> well a real musician is compensating for the monitoring latency, or 
> whether it's just triggered midi module playback. On the whole, I 
> recommend you do NOT attempt to compensate for software-monitored 
> recordings using the record delay driver parameter. Leave it 
> calibrated for source-monitored recordings, and run your buffer sizes 
> as low as you can possibly go. Consider using source monitoring 
> whenever possible, or "zero-latency" hardware monitoring via TotalMix, 
> CueMix, etc.
>
>  Sequence a midi click with the notes exactly on bars/beats. Output 
> that to your midi gear (set to a percussive sound with sharp attack), 
> and record the result to an audio track. Open the recording in the 
> Sample Editor, set to view in milliseconds. Measure the distance from 
> the bar/beat marks to the recorded clicks. Due to midi jitter, this 
> will not be consistent. Measure 20-30 clicks and average the result.
>
>  Adjust the "All midi output: delay" setting in Preferences >> Midi >> 
> Sync (Logic 7) or the "delay all midi output" setting in Song Settings 
> >> Synchronization >> Midi (earlier versions) to compensate. Measure 
> and check again until it's recording more or less on the beat, on 
> average. This adjusts for source-monitored midi gear.
>
>  Note that different midi gear may exhibit wildly differing delays. 
> It's your choice whether you compensate for the fastest, the slowest, 
> or an average. There's only one global setting available. For Logic 6 
> and earlier, it's a song setting, so make sure you save it into your 
> autoload, and you'll need to make the setting individually for 
> existing songs. In Logic 7 it will affect all existing and new songs 
> automatically.
>
>  You can attempt to further fine-tune for different delays among 
> different midi modules by using the Environment instrument "delay" 
> parameter, but be warned these are set in ticks, and the delay will 
> therefore change with the song tempo. You can view the delay in ms, 
> but the actual setting is always in tempo-dependent ticks. Change the 
> tempo with the Arrange "view: delay in ms" and see.
>
>  Get this far, and see what you think of the result. Then, if you 
> really really want to attempt to compensate for software-monitored 
> recordings, post again. There are a number of ways to go about it, 
> none of which are ideal. I need to to think about it a bit more before 
> I write it up.
>
>  John Pitcairn
>
>

Attachments

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.