Rbrt Contributions

[rbrt]

thanks a lot!

..I just uploaded some new looper-objects to the communitiy library,I'll document them later on.
I decided to focus on 'building blocks',rather than all-in-one-solutions for now..

here's a patch using the new objects:
looper_blocks_v1.axp (16.6 KB)
it's using the new objects for recording and syncing,the playback is done with factory objects.

to answer your question:yeah you can also pitch up,there's a comment 'modulate global tempo'
in the patch,at this position you can do pretty much anything with the tempo
(reverse doesn't work yet)

cheers,Robert

[stepan.dvoracek]

I downloaded the patch but I couldn´t find the custom objects on github. Also it looks like the tempo dial works the same way as in my_looper_SYNC_NEW_100.axp which means that if you start recording with the tempo dial at 32, the master loop is pitched and slowed down, but than all following dubs are in the recorded pitch. I´d like to be able to record a master loop and have the ability to pitch it up (just like on the EHX loopers). I´m guessing this is not possible so I´m thinking about tapping a tempo of a master loop which would play back a click sound than could be muted after the first recorded overdub. Also adding play/stop button would be a great feature.
Sorry for bothering you, but I am working on my busking patch and your work is very helpful to me.

Steve

[jaffasplaffa]

I decided to focus on 'building blocks',rather than all-in-one-solutions for now..

To me that is the best solution anyway. I prefer to patch everything from low level objects rather than custom specialized objects. custom objects are probably easier on the DSP, but from what I have learned now, I'd rather use low level objects and have more control over what happens. For example amounts, rations, etc. There are so many things that is overlooked in the custom objects, things that could be tweeked if they were just kept as building blocks.

I know, some things cannot be patched with factory object and for sure for these tasks custom objects are necessary. But in most cases I prefer to build the patches form building blocks, like you mention. ANd just throw it into a patcher and voila!

So keep the building block coming

[rbrt]

...to speed up the whole 'transport-system',instead of being able to just pitch down:

...the dial before the 'tablestore' is set to 32,the ctrl/i is set to 2..like this,you get 'original' speed...
now,if you set the dial to 64,you get double-speed.
if you want different speeds in your setup,just use several loop_drives and send them diffrent tempi..

[stepan.dvoracek]

Thank you, this looks great, can you upload the custom objects or am I missing something?

[thetechnobear]

@stepan.dvoracek Are you running 1.0.10? Have you done a 'sync libraries' ?

[KontinuumLab]

I get exactly the same thing - on 1.0.10, on Ubuntu 14.04.

I have synced libraries, as well as a tried a reset of libraries through the preferences menu. I think the problem is that the objects are missing from the contrib library.

@rbrt - is it possible that you erased the objects from your contrib folder? Maybe you intended to erase the "looper_blocks_v1" patch as well, since all this stuff is also absent from your object list here on the forum.
I don't see them on github either (here: https://github.com/axoloti/axoloti-contrib/tree/1.0.10/objects/rbrt). Seems to be missing the following files:
rbrt/looper/loop_master
rbrt/looper/loop_drive
rbrt/looper/loop_slave 1
rbrt/data/tablestore 4 (there is a "tablestore 8")
rbrt/lfo/square

Anyway, maybe it's just a "work in progress" situation. Your initial looper objects are already extremely useful to me, so do take your time Thanks for all the great work

[rbrt]

seems I can't sync anymore!

I'll try tomorrow,too tired now..

[rbrt]

Hi All,

should be working now!
I had some wrong settings for github...

[Blindsmyth]

Hi I tried it a little bit,
first of all thanks for your effort, I think this is an amazing step for building loopers in axoloti

However I have some things that I would do differently:
From working with Ableton's Looper and Loopy I have a particular workflow that I really like and that I'm missing with your patch:
First Loop sets tempo (just like in your patch) BUT it isn't neccessarily a one bar loop. Ableton recognizes with longer loops, that it is several bars. With loopy you have to tell the software what kind of bar/length you're entering.

Other loops are set according to a quantization value rather than a fixed length.
That way you could start the first loop with a short rhythmic pattern and then add a longer melodic pattern on top or vice versa, and you do so by just keeping the same work flow, of starting and stopping recording with one switch.

So this would be a lot more flexible.

Furthermore some midi/clock sync mechanism would be great to. Like if there is no clock make one according to the first loop, if there is a clock synchronize the loops.

But still really great work! I really appreciate the loops saving function, really great for creating a musical sketch book.
If you like shoot me a pm, we could work at this together, I have a nice garden for patching in our backyard

[Blindsmyth]

Hi little update here:

It seems as if I can do a lot of the things I want to do just with your blocks. Considering the sync/quantize things I think the way to go for me is use a master loop block for each loop.

I am also starting to build funky mlr style choping step sequencer patches wich is really great

The only feature I am missing now is Overdub Feedback. I tried using table/record with now succes.

a) it glitches b) it only overdubs one time when you press the overdub toggle.

If you were to add a replace mode to your overdub object I could patch the feedback path myself, wich would be really great

[mtyas]

Just wanted to say a big THANK YOU for your modules. I can't think of many of my patches without at least one module by you.
I'm quite amazed by the looping capacities offered by Axoloti, and with the synchronisation aspect it's even more capable.
But I have to agree with @Blindsmyth about the glitchiness. (I don't have any overdub problems). I often get clicks recorded during the loop point : would there be a way to minimise them ? I'm using 4 different loops in sync and the clicks can easily get in the way. I tried putting fast enveloppes here and there, but nothing worked out

Thanks for everything, I'm sure your modules are getting a lot of usage in the community, and the only thing I can give back is a warm thank you.

[rbrt]

hey! thank you for liking what I try to do not really knowing what I do

the clicks at loop-point are a problem that's inherit in programming loopers,
because when you start/stop recording a loop,the amplitude of the incoming signal
is NEVER at zero,but somewhere between -1. and 1.
the clicks are the result of the difference in amplitude between the loop's start and end...

the best way to get rid of the clicks would be::
when you start the recording,there's a small fade-in envelope,
when you stop,recording would continue for 100 msec or so with a fade-out envelope
applied to the input signal.of course,while the loop is already playing back
(that's the hard part of it)
I've done these things already using MAX/MSP, I'll give it a try with axoloti..

[logsol]

Hey @rbrt ,

I have a question regarding the loop_master object and its hz output. I connected a volca that is set to 120bpm using its sync output. With a timer, that outputs 0.33ms ticks I get exactly 6000 per bar as expected. When I use the same bar timing to record into the table using the loop_master object I always get something like 1.37 at the hz output. Could you please explain why that is? At 120bpm it should be 2 seconds per bar meaning 0.5 hz, no?

Thanks in advance!

[rbrt]

hi @logsol ,
ouch! you got me...I've noticed this too some time ago,
actually,hz is not the correct description...it should really be freq or something like that..
but what? is it?
I guess it's related to the 48 khz sampling rate axo is using...

[rbrt]

here is LOOPER BLOCKS!

...a bunch of objects for constructing looper-devices and whatever else....
here's an example-patch for a 4-slot-loopstation
4 slot loopstation.axp (58.2 KB)
I'll post some more,simpler patches soon (hopefully explaining the concepts behind)
there might be some bugs,as well.

...requires 1.0.11

[Djeremaille]

Hello!

I tried your example patch but there is missing objects. I'm on 1.011.

[rbrt]

...I just double-checked, all objects are on github...
have you synced libraries?

[Sputnki]

It's possible that you used object from your local library to make the help file, just replace those objects with the community library one. (the same thing happened to me)

[Blindsmyth]

for me the demo patch worked.

Did the new loop drive object replace the old? I seem to have problems using my older looper patch with it.

For the rest it looks like a really cool thing!