The benefits are easy overdubbing, super simple messages for windowing and rate.
Max buffers are arrays, yes.

Thanks, that's weird. I need to investigate.

I was wondering if there was someone interested in porting karma~for pd. It's an amazing object for recording/overdubbing/mangling loops.
https://github.com/rconstanzo/karma/tree/master/karma~1.5

Here's another attempt showing another approach. It works almost as expected except that it waits one whole loop to settle the inner loop. My understanding is that my routine to bang on loop bangs on the beginning instead of the ending of the loop ? I feel like it's close to be working but I can't wrap my head around it.
Mlr_work 2.zip

Thanks a lot for the answer,
I've been trying to avoid this type of solution, precisely because I felt that the timing won't be accurate. I'll be playing several loops on top of each other and I suspect that this will cause loop drifting. In your example, each loop will have an error of up to 10ms, right ?
I'd love to stay with signal only. But maybe I'm wrong ?

Hi there,

I'm having headaches trying to figure out a (stupid ?) problem in a patch I'm working on, and I thought maybe it would be obvious to someone here, who knows ?
Basically, I'm working on my own MLR-inspired patch for monome grid. It's a sample cutter that accesses 16 start points in a sample loop.
Where I'm struggling is at "inner loops". The idea is that when you hold a first button and press a second one, the file loops between these two points. If only one press happens, the whole file loops, starting from here. It works but the playhead "jumps" when the end point is pressed. This is what I want to avoid.
I guess something should be corrected in my [scale~] patcher, or something like that.
I also tried to hold the second press into an [f] and trigger at the end of the [phasor~] loop (using cyclone [edge~] and [onebang]) but no luck.

Here's a patch to illustrate the problem.
Any help would be awesome.

Cheers,

Louis

Mlr_work.zip

Yep, the 64-bit.
I managed to make the maths so it's not a big deal, but the actual object would be handy. Thanks !

Anyway, it should be replaceable with an expr~ , isn't it ? I'll look into it.

Thanks for the answer.
Downloaded the cyclone library from PD itself. I have the habit to copy any external to the current patch's folder.
So far, every object works except this one. Even when opening the help file from the library folder itself, it can't open the object.

Hi,

I'm on OSX, with PD 0.49, cyclone's [scale~] object won't load. Is it a known issue ? Any idea ?