Loopers

Sync wise, Roland/BOSS loopers are typically better behaved when they’re used as the master clock. Slave sync has always been a challenge for them.

That said, I’ve not used one in a good long while now because of that; so, perhaps that has been improved.

To that end, if it’s really down to only those two loopers for you, then I’d go with the RC-202.

Cheers!

3 Likes

Slaved, they can have slight timestretch fluctuation. (I tested RC50, RC300, RC 505, RC 202, RC500). It is worse if you send too much midi data like notes or CCs.

You can disable timestretch, but in this case it randomly stops some tracks, so it is worse.

No problem if master.

KP3 recording time is short.

3 Likes

Thanks for the insight, I don’t mind setting the 202 as the master so I’m leaning towards that.

New Aeros Firmware

2 Likes

Do you have such a device? How is the workflow with it, do you use the 6x6 mode?

No. But they still update it after a few years, wasn’t finished at release. Seems more and more interesting…

With quantised loops, sounds pretty fun, the question is how the synchronization of start /stop works, if a midi start stop, would trigger record the selected track, or if that could be remapped, if the AR could send a midi note for recording, and it stops after a set limit, that would be a intresting combo to explore, maybe even only as a loop recorder to arrange later on.

Could you rephrase the question ? I can ask in a french forum…or maybe you can ask in Aeros forum…

If you could set a part to record 8 bars, and start the recording with a specific midi event, like a note or CC value. Note A2 starta channel 1 record, note A3 starts track 2 record, etc.

Seems like the Aeros can’t be controlled with notes but CC, PC, transport.

I just got the rc202 and it works beautifully with my Syntakt, instant mangling and transition goodness. However, I’m not sure how to keep my midi controller in my setup. The rc202 and Faderfox don’t have midi thru so I tried to use a midi splitter cable, but that causes random stopping and starting behaviour. Anybody have a solution for this?

https://midisolutions.com/products.htm

2 Likes

:point_up:

I got the thru box for a rc202/digitakt/microfreak setup. Suddenly it all went swimmingly. The money was worth me not scratching my eyes out.

2 Likes

Thank you, I’m not sure if I should get a thru box or a merger. Because in my case I’m having two devices (rc202 faderfox) going into the Digitakt’s midi input.

Merger might be the thing then :blush: Remember to rtfm so you don’t get burned.

What controller are you using?

I use a Keystep 37 with my digitakt and digitone and AH2 - I have it in between the two Digis, clock sync only drifts by about .1 - .2 bpm between all three Elektron devices. So set up as follows - Digitakt Midi OUT > Keystep Midi IN > Keystep Midi OUT > Digitone Midi IN, and Digitone Midi THRU > AH2 Midi IN. In the Keystep software manager the OUT is set to THRU which merges the original midi from Digitakt with the midi data from Keystep. It works great, no issues at all except for the inevitable audio and power cable mess haha

I’ve tried a similar set up in the past successfully. However, the rc202 looper and the faderfox midi controller need to be at the beginning of the chain, but both devices don’t have midi thru.

A Midihub can solve so many issues like these.

3 Likes

Ahhhh I see what you’re doing there. It hurts my soul when there is no THRU port on a device, disgusting really.

Yeah midihub seems like the ticket and will allow for even more

2 Likes

Hi all, just to update you just in case anybody else has similar ideas. I took the plunge and went for a midi solutions merge and now everything is synced up nicely. Note;- the Faderfox couldn’t power the midi merge box but the RC-202 can.
Thanks for your help guys, this combo is ridiculous fun.

4 Likes