Re: [sooperlooper-users] Strange behavior during overdub.

[Jesse C. <je...@es...>]

You need to remove the loop, then add a new one (or add custom) to get
a loop instance with more memory.  By just changing the default and
committing it only affects how loops are created in the future.

If you were wondering *why* you need to make a loop with more memory,
it's all related to the (admittedly unfortunate) implementation of
Undo.
At each "loop-changing" operation
(like rec,overdub,multiply,insert,etc) SL will move to a new area of
loop memory and continue the operation (replicating the original on
the fly and apllying whatever new operation you're in).  This lets
undo simply jump back to the previous area.  The loop memory area is
circular, so when you are about to do an operation that will impact
past history, that historical loop(s) will be reclaimed and life goes
on.  The downside is that if your current loop is > 1/2 the available
space (or maybe smaller) it won't let you do an operation that uses
the previous loop state (eg, you can only record).

This among other things is why I would like to totally reimplement
SL's innards using a more elegant design.  It will likely be based on
the backend of Ardour (an open source DAW I also contribute to).
When this happens, is of course totally up in the air.

jlc

On 8/14/07, mid...@co... <mid...@co...> wrote:
 When going straight into overdub from record, a weird thing happens.
All audio stops. It  says its overdubbing, but all activity has
stopped. I tried increasing memory (turning up  seconds of memory and
hitting committ changes), but it seems to make no difference. I
thought I might be out of memory (1gb ram, 1.5Ghz Powerbook), but even
if I turn down seconds of memory, to say 30 seconds, after I hit
commit changes, nothing happens. Available memory remains at 47.5. I
tried rebooting Live and SL but to no avail. Any ideas? This only
happens on passages longer then 20 seconds so it seems to be a
function of memory.