jump to beginning show previous Showing Logic-users Thread 9723 of 105817 show next jump to end

Forum Index | Read LUG: Policy/Rules Messages Threads Digests | Post New Message | Search!

From: zerobeat@xxxxxxxxx.xxxxxxxxxxxxxxxxxx)
Date: Mon, 20 Dec 1999 at 11:20:06 AM
Subject: Re: EMAG: Hyperdraw latency bug?
Message #11767
mari-zu.okereke@... writes: > > >I'm using LAWP 4.1.1 and SBLive MME drivers which have a >latency of 297 ms. Logic accomodates this latency when >playing back audio so that it is in sync with the midi. The >problem is that Hyperdraw messages don't appear to get >sent 297 ms early to compensate. They appear to get sent >at the exact time as if there was no latency in the audio. >I attempted to alter the delay to -297 to compensate but this >brought the audio forward as well. > I think you mean to say that a negative delay of -297 brought the audio BACKWARD (ie... back in time, or earlier in time) as well. Workaround #1: Don't do your automation on top of the audio regions. Instead, do them in independent "MIDI-only" regions that will affect the audio (ie.... the A-Playback Track). Then negative delay these "MIDI" regions. Workaround #2: Don't set a global negative delay for this particular audio driver, but rather for each audio region. Then, the automation and the automation data will be put back in time (netagive delayed) by the same amount. There is another aspect of latency that you cannot compensate for: SLEW. This is where the automation data can't be read fast enough by the specific audio hardware. In other words, fast *changes* will smooth over and won't be recognized exactly. Not all hardware is created equal, so automation latency/slew are different always. f-erenc "Fix signs"
Viewed 279 times, 0 replies, 1 message in thread. Reply to this message.

Forum Index | Read LUG: Policy/Rules Messages Threads Digests | Post New Message | Search!

Forum Index | Read LUG: Policy/Rules Messages Threads Digests | Post New Message | Search!


© 1994-2008, All Rights Reserved.