Re: Ending actions by Record in Mobius (Re: Following Acoustic Musicians with Looper)

[Per Boysen <perboysen@gmail.com>]

On 5 okt 2007, at 19.38, Jeff Larson wrote:

> So you're hearing an audio glitch in the Mobius loop when output
> sync is enabled and you do Multiply/Record and sometimes just
> a simple Overdub?  Thanks I can look into that.
>
> Glitches after Overdub are most often caused by a low
> setting for the global parameter "Drift Resync Frames".
> This defaults to 256 which is actually way too low, it
> should be around 4096.  When this is too low even the
> slightest amount of clock drift will cause Mobius to
> "skip" as it tries to match the clock.  There is always
> clock jitter but it tends to cancel itself over time.
> On one play of the loop you may be 300 frames ahead of
> the clock, then next you will be -180 frames behind,
> the next 295 ahead, etc.  If Drift Resync Frames
> is too low this jitter will cause Mobius to retrigger
> all the time when it should just be ignored.
>
> Multiply/Record is much more complicated because the
> tempo and a lot of other internal sync state changes.
> Glitches here are usually caused by bugs.

Mobius is working so damn well for me now, in the latest beta, so  
lately I haven't put a lot time into researching the above referred  
problems, since I have avoided the situations where they tend to  
appear. But now when you bring it up and give good advice on the  
"Drift Resync Frames" setting I would like to take a couple of hours  
to check it out fully. I'll send you a report tomorrow.

BTW, I don't have a problem with jitter in the sent out clock. If  
slaved plug-ins are slow to catch up a quick tempo change I might  
even think it sounds cool. But what may be really disturbing is when  
a loop skips over a fragment of its own timing, because then it goes  
off sync with your inner "human click-track" and that's just evil  
torture.

Greetings from Sweden

Per Boysen
(marking this thread with a huge flag)