Just one last note that I realised hasn't been stated yet in thread:
the most important factor in avoiding "bad sync between loops" is to
use as few loops as possible. The timing-wise rock solid approach is
to only create one loop and layer all musical parts into this loop.
That way no part can drift against any other part. The more musical
parts you distribute over multiple parallel loops the more sync and
timing issues you will get. No software or hardware can fix that,
sooner or later two - or more - loops will drift apart, this is just
the nature of the universe.
I'm not posting about what OS to run in a laptop because I have used
both Windows and Mac OS without finding any better than the other. I
do lack experience with Linux, so I can't tell about that.
Greetings from Sweden
On Fri, Dec 4, 2015 at 1:10 PM, andy butler <firstname.lastname@example.org> wrote:
> On 03/12/2015 23:00, Josh Elliott wrote:
> and this is a big deal in my case since my live guitar loops must sync with
> Ableton audio and midi clips.
> So this begs the question...
> Laptop specs. What should they be.? And Windows or MacBook? Does it matter?
> bit of a minefield.
> It's *possible* for the audio to still sync, Mobius & Echoloop have the
> It's just you'd miss a bit of audio from the beginning of a retriggered
> loop, unless
> that re-trigger was cued beforehand.
> Don't know how well Ableton copes, I did an analysis of the timing of one of
> Imogen Heap's
> performances and had to conclude that Ableton's timing wasn't great, but
> then that's
> micro-analysing in a DAW rather than just listening.
> If you want to use pre-recorded elements, ( and have the opportunity to fake
> for that mainstream live TV appearance, prob. not such a bad idea ;-) then
> Ableton's the way to go.
> If your latency IN/OUT is low enough, then it's an option to switch off the
> latency compensation
> in the looper. If you're monitoring the signal with latency for your live
> playing then your brain
> will do the compensation.
> (that actual latency on conscious awareness is something like 500mS, so an
> extra 50mS ain't too hard)
> Be aware that people will quote much lower latency figures than you'll ever
> get from actual measurements.
> :-) and be aware Per likes the "off" timings, incorporating them rather than
> avoiding them....and has made some fantastic music on the way
> On Dec 3, 2015 4:47 PM, "andy butler" <email@example.com> wrote:
>> On 03/12/2015 15:24, Per Boysen wrote:
>>> With looping you should never have any latency
>>> because when audio gets recorded into a loop the software has plenty
>>> of time to compensate for latency until it is time to play back that
>>> audio (on next loop return).
>> but let's not forget that's only aligning the playback.
>> Anything like triggering loops, or changing speed still suffers the