Problem: Pickup Machines Individual Length?

Yep. With REC/FLEX, possible to overdub, to disable timestretch, add plocks, no tempo change…

As Pickups came after an update, they should be the hack, no ? :content:
OT coming from MD UW, I think Rec/Flex is the normal way. But yes it feels hacky compared to a regular looper.

Main problem with REC/FLEX : starting the loop just after the end of the recording if you want different lengths.
That needs a sort of midi hack.
Doable with a midi device sending 2 messages, or adding a midi processor. Doable with midi plays free tracks and midi loopback.

Every once in a while if I’m using multiple pickup machines, after I’ve recorded a loop in the master, the next PUM I record on will record backward. The audio won’t be backward (I guess technically maybe it is, I don’t know) but the step count on the min page will run backward and the one time I checked the REC1 page the record and play indicators were moving in opposite directions. Has happened 5 or 6 times and I’m still not sure what’s causing it (and no, it’s not the direction parameter or anything like that). It doesn’t actually cause any problems so I haven’t tried to figure it out, it’s just a weird thing I’ve noticed.

Not helpful, but there it is.

1 Like

Yes. I looked for the thread on that from before… I think I found a way of hitting buttons that it was practically immediate

Okay found it:

Midi-routed would still be the pro route for sure. Hacky is good :slight_smile:

1 Like

There is a way to make your first PU loop any length you can dial into the rlen, and have subsequent PU machines be of individual lengths, without changing the tempo or timestretching.

I will get back to you on this because I don’t remember the procedure exactly and can’t check it before some time tomorrow.

1 Like

Please! Curious about it.
I couldn’t find anything reliable with PU yet, if you’re out of power of 2 numbers (1,2,4,16,32,64…steps). Tempo change or wrong timestretch…

Sorry forgot about this for a bit. Here’s a video that shows how it can be done. The caveats iirc are you need to have the sequencer running and you must specify in advance how many steps each recording will be.

3 Likes

Ok thanks but it doesn’t proove it works musically, and I don’t think that anybody doing live looping would want to set their loop previously with RLEN. And they usually want to define tempo with the first loop (not my case, I prefer to keep an existing tempo reference).

Secondly, from what I tested yesterday, with those lengths, new loops are timestretched. Doesn’t work. I’ll probably edit my post to precise/confirm caveats.

FLEX.

If it works musically or not is up to the user. I’m just showing you what I promised. They are not timestretched.

Ah ok. But quantized to PLEN? So you can’t record when you want?
Or maybe with a 2 steps pattern length…

I think you can do it unquantized but this is the way I prefer because I can “arm” the recording with one press and know it will begin on a beat and record for however many steps I told it to.

Not everything might have to be exactly like in the example. I’m just saying it’s a way.

1 Like

A way, but not the way regular loopers work, for sure. :content:

Thanks again, I’ll make some tests, maybe tonight.

Personally, I may use a Pickup to record a loop with pattern length RLEN and QREC, for overdub.
Other loops with REC/FLEX. Sending 2 notes from a midi controller : C2-G2 note (Tracks 1-8) + C4 (Combo Rec) with ONE2 mode, you can record any length, when you want. I prefer to quantize to 1 or 2 steps.

@JSZ I made some tests, so yes it doesn’t change tempo or use timestretch if you define the loop length with RLEN, using ONE, even with QREC off.

Btw I’m surprised you chose HOLD, which seem to work with QREC on, but not off.

I also set OP to GAIN instead of DUB to avoid overdub, because of the ONE mode.

Well, interesting, still not sure it will change my preference for REC/FLEX.

The reason for this is that afaik the one press solution to start and stop the recording quantized only works with hold. It’s been a long time since I settled on this method and I don’t remember why exactly.

1 Like

except you can’t overdub on a Flex machine. It’s very irritating that the first pickup loop sets the length for all the others… this behavior makes no sense

2 Likes

Hi there, I came across you posts about the RC505 on soem other forums, do you still use yours? I’m contemplating getting one. If so, does it work well when sync’ed to midi clock? (Most important thing for me).

Thanks!

Slaved, it is ok if you don’t send midi notes nor too much CCs. Ideally only Clock / Transport. There can be a little modulation just after play. I’d say it’s acceptable, but it’s annoying by principle.

If you send too much midi data (especially notes), the tempo seems to vary more, with bad timestretch modulation. It’s possible to disable timestretch, but tracks can be stopped randomly, so it’s worse.

I wouldn’t expect an update to correct that.

No problem if master. I like to use it gigging with friends, works well with DT and DN.

I don’t want to use OT slaved, so I’d use RC505 slaved, with these potential variations.

That’s how I do it.

No choice with OT. Annoying when you’re used to have undefined loop lengths.

For what I’ve been doing, undefined loop lengths wouldn’t actually work