Looper's Delight Archive Top (Search)
Date Index
Thread Index
Author Index
Looper's Delight Home
Mailing List Info

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Date Index][Thread Index][Author Index]

Re: Looper crossfade advice



Ahh!!  That's it - thanks so much, Jeff.  You're right - with some loops, it's better to have an isolated recording than a smooth crossfade, with others, a crossfade is a must.  It'll have to be adjustable!

Loopy does do seamless record-to-overdub transitioning already (and I have the depleted brain-power to prove it), but I have the feeling that more might be needed for a proper, smooth crossfade, than just a tail.

If I do only a microfade at the beginning of the recording (instead of crossfading over extra audio recorded before and after, and then overlapped), then regardless of the length of the tail on the overdub, it'll still have a hard beginning.

If I microfade over a longer time, from the beginning of the loop, then there'll be a hole...

So, the only alternative I can think of is to do what I'm doing currently - keeping an extra chunk of audio in the buffer at all times, so that when recording starts, that preceding audio can be popped into the start of the recording, overlapped with the end, and crossfaded.  That way, beat 1 is present and unmolested, but smooth.  Is that moderately sensible?

Anyway, that's totally the solution though - I'll add a slider so that users can adjust the crossfade duration, which will cause (duration ÷ 2) seconds to be prepended to the recording, and (duration ÷ 2) seconds extra recording at the end, and overlap this & fade.

Cheers =)
Michael


I think the most common approach to this in current loopers is to give
the performer an option to transition seamlessly from Record mode to
Overdub mode when the recording ends.  There is then no fade-to-zero at
the end of the loop, the current sound carries over seamlessly to the
start of the loop.  The performer then has control over when they
stop the overdub.
 
This does require an extra user action to end the overdub.  But it
gives them control over how long the recording "tail" is.  For
example a very short tail may be all you need to avoid a fade bump in
a drone or pad sound, but if you had a cymbal crash toward the end of
the loop you would want that to fully decay so the tail must be longer.
 
Automating the end of the overdub would be cool, but I'd recommend
having a parameter that the user can set to control the tail length so they
can adjust it depending on what they're playing.
 
> but a user was commenting that he can clearly hear the
> following downbeat after the recording of a loop
 
I'm not sure what you mean here, but if the performer is playing
something percussive and the end of the loop is followed immediately
by a sound with a sharp attack that you don't want to include in the
recorded loop...yes, that's the tradeoff of seamless overdub.  In
these cases though, the fade-to-zero is often less noticeable because
the sharp downbeat takes the listener's attention away from the fade.
This is why it is best if the record tail is user controllable,
sometimes you want it and sometimes you don't
 
Jeff