harlan

i want to make a loop machine for guitar performance. i understand the basic principles but im just not entirely sure how to program it so it can overdub a new layer on top of a previous one. it would also be nice to have a buffer with dynamic length so i could start recording, play then stop recording and have that be the loop length. any help is appreciated. thanks!

overdubbing-looper

Adding to a buffer is possible, but your more likely to want to 

bounce back and fourth between 2 buffers. This is digital, no 

As for buffer lengths, you must understand that a buffer is an 

looping is done by setting up two points to loop INSIDE that buffer.

Cycling's documentation is the best on the planet, its not like 

normal documentation where you don't bother reading it.

Adding to a buffer is possible, but your more likely to want to  
bounce back and fourth between 2 buffers.  This is digital, no  
generation loss ;-)

As for buffer lengths, you must understand that a buffer is an  
allotment of memory for your program.
looping is done by setting up two points to loop INSIDE that buffer.

Cycling's documentation is the best on the planet, its not like  
normal documentation where you don't bother reading it.

I banged my head against the buffer~/groove~ wall for ages before finally abandoning it. A more successful approach for me has been using tapin~/tapout~. I use two pairs so that you can 'undo' as a hardware looping pedal would.

The strategies for overdubbing loops which I have used in the past offer three distinct possibilities:

1. tapin-tapout: the simplest; if you route the outlet from tapout back into the inlet of tapin, you have a basic loop. By putting a volume fader between outlet and inlet, you can use it as a delay. The commands "clear" and "freeze", or the interruption of the feedback-loop into tapin are the three pertinent commands. Drawback: the loop is cumulative, meaning that you cannot separate the layers which you have added to the loop. By changing the tapout times, you can vary the length of the loop, also while it is looping, but this can lead to a (not at all unpleasant) stuttering effect.

2. multiple buffers: I could just as well say "multiple tapins" (a tapin is basically a memory buffer which continually rereads and rewrites itself). Buffers need more components in order to function, but can be used for pitchbending. Also, you can layer the loops, fading various layers in and out. For me, one of the advantages of using buffers for looping is that I can save the individual loops and/or layers as wave-files.

3. stutter: the stutter object can be used either alone or in a layered setup. It is organized as if it were a tapin-tapout object which sends its contents to a buffer on command, allowing pitchbending. A bit tricky at first, but worth the work to discover its possibilities.

1. tapin-tapout:  the simplest; if you route the outlet from tapout back into the inlet of tapin, you have a basic loop.  By putting a volume fader between outlet and inlet, you can use it as a delay.  The commands "clear" and "freeze", or the interruption of the feedback-loop into tapin are the three pertinent commands.  Drawback:  the loop is cumulative, meaning that you cannot separate the layers which you have added to the loop.  By changing the tapout times, you can vary the length of the loop, also while it is looping, but this can lead to a (not at all unpleasant) stuttering effect.

2. multiple buffers:  I could just as well say "multiple tapins" (a tapin is basically a memory buffer which continually rereads and rewrites itself).  Buffers need more components in order to function, but can be used for pitchbending.  Also, you can layer the loops, fading various layers in and out.  For me, one of the advantages of using buffers for looping is that I can save the individual loops and/or layers as wave-files.

3. stutter: the stutter object can be used either alone or in a layered setup.  It is organized as if it were a tapin-tapout object which sends its contents to a buffer on command, allowing pitchbending.  A bit tricky at first, but worth the work to discover its possibilities.

>The strategies for overdubbing loops which I have used in the past 

no-one ever talks about the fripp~ object - i belive it never was 

100% finished but what existed was already quite great!! and since 

the author was prowinding the C code (and telling he would happily 

let anyone work on it) that seems a great possibility - for those of 

>The strategies for overdubbing loops which I have used in the past 
>offer three distinct possibilities:
>

no-one ever talks about the fripp~ object - i belive it never was 
100% finished but what existed was already quite great!! and since 
the author was prowinding the C code (and telling he would happily 
let anyone work on it) that seems a great possibility - for those of 
you who know how to code, that is

On Oct 1, 2006, at 11:41 AM, Kasper T Toeplitz wrote:

>> The strategies for overdubbing loops which I have used in the past 

> no-one ever talks about the fripp~ object - i belive it never was 

> 100% finished but what existed was already quite great!! and since 

> the author was prowinding the C code (and telling he would happily 

> let anyone work on it) that seems a great possibility - for those 

where is this mysterious fripp~ object?
i can't find any mention of it anywhere.

>> The strategies for overdubbing loops which I have used in the past  
>> offer three distinct possibilities:
>>
>
>
> no-one ever talks about the fripp~ object - i belive it never was  
> 100% finished but what existed was already quite great!! and since  
> the author was prowinding the C code (and telling he would happily  
> let anyone work on it) that seems a great possibility - for those  
> of you who know how to code, that is
>
>
> best
>
> kasper


for those looking for fripp~ it seems to be here:

http://www.angelfire.com/dc/swirlee/loop.html

On 9/29/06, Pierre Alexandre Tremblay wrote:

> You should have also a look on my ipoke~ object, to be able to

> emulate Boss DD-3. Soon to be available as UB.

for those looking for fripp~ it seems to be here:
http://www.angelfire.com/dc/swirlee/loop.html

On 9/29/06, Pierre Alexandre Tremblay  wrote:
> You should have also a look on my ipoke~ object, to be able to
> emulate Boss DD-3.  Soon to be available as UB.
>
> www.no-tv.org/MaxMSP/
>
> pa

-- 
www.hecanjog.com / www.cedarav.com
www.luvsound.org / www.lovelymedia.org


I made fripp~ available for win, if someone look for.

> for those looking for fripp~ it seems to be here:

> On 9/29/06, Pierre Alexandre Tremblay wrote:

>> You should have also a look on my ipoke~ object, to be able to

>> emulate Boss DD-3. Soon to be available as UB.

erik schoster wrote:
> ipoke~ is wonderful, thank you!
>
> for those looking for fripp~ it seems to be here:
> http://www.angelfire.com/dc/swirlee/loop.html
>
> best,
> erik
>
> On 9/29/06, Pierre Alexandre Tremblay  wrote:
>> You should have also a look on my ipoke~ object, to be able to
>> emulate Boss DD-3.  Soon to be available as UB.
>>
>> www.no-tv.org/MaxMSP/
>>
>> pa
>


hey I am a noob, I know, i just got max a couple days ago, but how does one get fripp~ to work. I have frippmc.help open but all I can do is get the adc~ to turn on. Do I need to put the fripp~ object in a certain folder that max will look in? I should probably spend more time fiddling before going on this forum, but i just thought i'd ask.

> I should probably spend more time fiddling before going on this

yup, and its much easier to start first with the original distribution, 

especially the tutorials and examples, before you dive into 3rd party 

externals. They can have their own problems...

Nicholas Esterer schrieb:
> I should probably spend more time fiddling before going on this
> forum, but i just thought i'd ask.

yup, and its much easier to start first with the original distribution, 
especially the tutorials and examples, before you dive into 3rd party 
externals. They can have their own problems...

-- 
Stefan Tiedje------------x-------
--_____-----------|--------------
--(_|_ ----|-----|-----()-------
-- _|_)----|-----()--------------
----------()--------www.ccmix.com


there was a good patch that shows the basics of what you want posted a few days ago:

does somebody can email me the ipoke external UB version?

Hello,
does somebody can email me the ipoke external UB version?
the original website is off...

Hnady little patch there leafcutter John thank you. Its saves me a some trouble thank you.

Could somebody please explain why i can't fill the buffer~ though? It allows me about 1000ms of record then loops over that section of the buffer~ again. I have modified the patch but it happens with the example above too.

Since I was the one who originally wrote that patch, I'll try to explain a little. The *~ object in this patch is configured in such a way that it plays through and records 88,200 samples, which is 2 seconds at 44.1khz sampling rate. If you are using a different sampling rate, you'll need to alter this patch to make it function properly. If you want to use a different length for the looping buffer, you'll have to calculate the settings for the phasor~ and multipliers.

Hello, 
Since I was the one who originally wrote that patch, I'll try to explain a little.  The *~ object in this patch is configured in such a way that it plays through and records 88,200 samples, which is 2 seconds at 44.1khz sampling rate.  If you are using a different sampling rate, you'll need to alter this patch to make it function properly.  If you want to use a different length for the looping buffer, you'll have to calculate the settings for the phasor~ and multipliers.

Hi, Thanks Andrew for the reply and the cool patch.

I'm trying to work this out but how do I work out work it out so that I can record, as you have defined with space bar, and overdub at 44.1 khz? I understand I need a sampling rate twice the frequency of my sound source but I'm stumped with the other signal boxes. Is there a tutorial you could recommend re-reading?

Hi, Thanks Andrew for the reply and the cool patch. 

I'm trying to work this out but how do I work out work it out so that I can record, as you have defined with space bar, and overdub at 44.1 khz?  I understand I need a sampling rate twice the frequency of my sound source but I'm stumped with the other signal boxes. Is there a tutorial you could recommend re-reading? 

overdubbing looper