Re: looping with albeton live

[Raul Bonell <raul.bonell@gmail.com>]

oh well, longer. i want to mean the app will have to be processing both patches during those 60 sec. and retaining enough ram for the two. tricky in a live situation. specially our poor macbooks, which need lots of ram for graphics. i commented since sjaak was advising how to save computational resources. i'm about to see the macbook fly when using mainstage, you can stop that fun fan! ...

2009/11/12 Per Boysen <perboysen@gmail.com>

60 seconds does not tax the CPU more than 5 seconds (my setting). Not
more, but longer ;-)  I do not like the way Apple has implemented this
in Mainstage. IMHO they should have done it the way you can do it if
using Bidule as the host: the software "listens" to the old patch and
mutes it when it goes silent.

I like very much to jump around between patches and play only one or
two notes with each patch sound. This works very well in Bidule
because on the shorter tail patches the old patch gets muted almost
the moment I go for a new sound - while in Mainstage every damn patch
stays open for 5 seconds even if it doesn't have a long tail. Because
of this I can't use that technique so much wiht Mainstage. Different
host applications for looping is just like having many guitars; each
one does something particularly well but no one is ultimately
universal.

Greetings from Sweden

Per Boysen
www.boysen.se
www.perboysen.com

On Thu, Nov 12, 2009 at 12:33 AM, Raul Bonell <raul.bonell@gmail.com> wrote:
> ... a 60 seconds tail to change patches will not tax cpu heavily, sjaak?

-- 
Raul Bonell at Blogger: http://raulbonell.blogspot.com
Chain Tape Collective: http://www.ct-collective.com