Hi! I want to build multiple layers of a 2-bar loop first, and then extend that loop layer when I play the main melodic theme .
When using the Ditto+'s Extended Loop Mode, can I defer extending the loop later, after recording multiple layers? Or does the second layer always dictate the final fixed length of the loop?
If Ditto+ cannot handle what I need, is there a compact looper pedal that can?
As the title says, I’m looking for some good budget friendly (under 100$) IEMS for live looping.
I use multiple instruments and stack vocals with a Boss RC 505. MK2. I play different styles of music based on the events I’m attending.
I mostly play alone, occasionally with other musicians.
I’m looking for a place to start as I don’t have the budget to try multiple IEMs right now.
Preferably something that’s clear and well balanced.
Hi everyone, Raphaël here, the developer of Everyday Looper :) !
Some of you might remember the original from the early App Store days (2009!). Over the years I kept getting messages from singers, beatboxers, and loop artists in general who never let go of it, and that convinced me to get back to work. So I've rebuilt it from the ground up for today's iPhones and iPads, and the beta is now open :D !
What's in this version:
8 tracks you touch directly to mix, mute, merge, overdub, and more
Pretty decent echo cancellation, so you can actually loop through the speaker without headphones
Synced video capture of the take, straight from the app
Per track 10-level undo/redo, speed/reverse, and adaptive track lengths
The demo is by Ty Suite, a long-time Everyday Looper user. It was performed, recorded, and filmed entirely inside the beta on an iPhone, through the speaker, with no headphones.
I'd especially love feedback from people used to live looping: does the workflow feel immediate, what gets in the way, and what would you need before using something like this for a real performance?
Ciao colleghi musicisti di strada! Volevo solo condividere un piccolo estratto della mia recente esibizione dal vivo all'"ai300scalini" di Bologna. Sto suonando lo standard jazz di John Coltrane "My One and Only Love" contemporaneamente con una chitarra-pianoforte ibrida a 14 corde personalizzata e una batteria a pedale. Ci è voluto molto esercizio per coordinare il tutto, ma la risposta del pubblico a questo arrangiamento è stata incredibile. Mi piacerebbe sapere cosa ne pensate della configurazione o del mix! Un saluto dall'Italia 🇮🇹
Hi! I'd really appreciate your advice because I think I'm looking for a pretty unusual setup.
I'm a pianist/keyboard player, not a producer or a DJ. I own a Yamaha Reface CP, which I absolutely love, but I'd like to expand it with basses, drums, pads and a few other sounds.
My goal is to perform completely live as a one-man band. I want to play every part myself—drums, bass, chords, melodies and solos—and build songs layer by layer during the performance.
The important part is this: I'm not looking for a production workflow. I don't want to program patterns, edit MIDI, or build songs like in a DAW. If something is looping, it's because I just played it.
Ideally, I'd like to:
select a bass sound,
play the bass live,
capture that exact performance as a loop,
switch to another instrument,
play the next layer,
and continue building the song until I finish with a live solo.
In other words, I want to preserve my actual performance (timing, dynamics and feel), not just record MIDI notes that can later be edited or replayed differently.
I'd also like a compact, battery-powered device that:
works well with an external MIDI keyboard (my Reface CP),
provides a good selection of instruments (especially basses, drums, pads and synth leads),
lets me prepare projects for each song in advance,
allows me to switch quickly between those sounds during a performance,
is designed more for playing than for music production.
At first I thought I needed a sound module together with a Boss RC-505/RC-202. But now I'm wondering whether something like the Yamaha SEQTRAK, Novation Circuit Tracks, or the new Akai MPC Sample could replace both in a simpler, more portable setup.
If you were building this kind of live rig today, what would you recommend and why? Is there another device I should seriously consider?
I'd especially love to hear from someone who actually performs this way rather than produces music in the studio.
Title asks the question - if you're not using some kind of MIDI clock signal, how do you stay in time when playing with others, especially when the people you play with loop themselves or use drum machines/DAWs? I've never been able to get accurate enough that it isn't noticeably out of time after several repeats.
Image is semi-related. I play in a improv electronic group, I'm not sure we do enough looping to fit in this sub really but we do a bit. I use Ableton (looping, effects, MIDI instruments), other dude uses an old Roland sequencer (percussion mostly) but his laptop - which he used to loop his guitar - has recently died and we're trying to find a replacement that we can afford.
Finding a loop pedal that takes a MIDI clock signal is proving to be more challenging than we expected, so how do yous all do it?
I am a music producer who has been making beats, recording, producing for the more than 13 years and i have been working on making my own Looper centric DAW.
Through the years i have used many DAW including Fl Studio (3 years), Maschine (5 years), Reaper (4 years) and since have been using Cubase as my main DAW with that said i always feel something is missing in terms of looping. it never really friendly to loop on your computer while still having a sense of control and not needing to hit those mute, plugin bypass, or rec perfectly with your mouse at the right time while holding a guitar.
My goal was simply to build something that makes it easy to loop on your computer without needing to do complicated MIDI (Although midi mapping is available), i wanted this DAW to feel like a software version of the Boss rc-505 and i think i have made that.
The core idea here is that everything runs on a scene(s), think of a scene as 1 Boss rc-505 unit BUT you get to have an unlimited number of tracks including MIDI (VST3 Support), Audio, Midi CTRL, and a dedicated guitar track with a "Pedalboard" more on that later
Each track can have its own numbers of bars, maybe your guitar track is 4 bars, but your drum track is 8 bars, this means the guitar track will loop twice in a full scene cycle then the scene loops and the cycle repeats.
What is different here ?
Most settings can be synchronized to the tempo, muting/soling a track, activating a master FX, recording a loop, random mode quantize
1 Audio track can stack multiple take and play them together, you can choose per track if recording overwrites the original take or stack, and during performance even deleting a take can be synchronized on tempo
Guitar Track, this is simply an audio track that automatically monitors the track but also open an "instrument" plugin called Pedalboard, this is simply a container that can be run serial, split, parallel and allow you to put any VST3 plugins you would want in your guitar chain, i also have my own amp plugin and have a native NAM plugin to allow loading your own sounds (my amp support IR loading) plus a good amount already on guitar effect like in house plugins.
I don't know yet what i want to do with this, but i guess i am ready to finally start sharing i am missing a lot of features here is a rundown of where i am right now :
Looping & Transport
- Play / Pause / Stop — pause freezes in place and resumes from the same spot
- Tempo — set BPM; while playing, a change queues and lands on the next loop
- Tempo re-cut — clips re-fit the new grid (MIDI rescaled, audio re-cut, no time-stretch for now)
- Per-track loop engine — each track loops its active-scene clip to the scene length
Scenes
- Multiple scenes (song sections) — each a full set of per-track clips
- Quantized launch — engages on the next loop boundary (instant when stopped)
First of all, thank you for creating the RC-600. It has become the center of my live performance setup.
After spending a considerable amount of time experimenting with MIDI control, I found one limitation that could be solved very easily with a firmware update.
Currently, the RC-600 allows assigning Tap Tempo to external controllers. However, when the RC-600 is synchronized to an external MIDI Clock, Tap Tempo is no longer available, which is understandable.
A much simpler and more flexible solution would be to add two new Assign Targets:
Tempo Increase
Tempo Decrease
This would allow performers to adjust the tempo gradually during a performance using any external footswitch (such as the BOSS FS-1-WL or FS-7) without relying on Tap Tempo.
This feature would be extremely useful for live musicians who need subtle tempo adjustments while looping.
I believe this addition would greatly improve the RC-600 without changing its existing MIDI implementation.
Thank you for your consideration, and thank you for continuing to support the RC-600 through firmware updates.
Very easy, just mark a start and end and the app will loop it infinitely ♾️ as an accompaniment practice. It's free to download and get start with a loop, or a one time purchase if you need to make multiple saved loops.
Disclaimer: i'm the creator of the app, would love to hear your feedbacks. Unfortunately, I couldn't make the Spotify version because the sdk doesn't support such integration deeply.
We review the popular STRICH Stereo Looper with Built-in Drum Machine. This budget stereo looper pedal could be a great tool for musicians who require a creative practice tool.
For more than a year, I have been getting desperate trying to make my Roland/Boss RC-600 sync properly to my external MIDI clock. My master clock comes from a Launchpad Pro MK3, which feeds into a Miditech MIDI Thru 7 splitter to sync all of my gear. Every single synthesizer in my setup works flawlessly—except for the RC-600.
Recording Track 1 works fine with the external MIDI clock. But as soon as I record Track 2, the audio is plagued by artifacts, glitches, and stuttering. It is completely unusable. For over a year, Thomann and Boss/Roland support kept telling me the same thing: "Your external MIDI clock signal must be unstable."
So, I decided to end the guessing game. I connected my Rigol laboratory oscilloscope, logged the MIDI clock data, and used an AI-assisted Python script to analyze the exact timing of the incoming signal.
The Result: Out of over 280,000 recorded MIDI clock edges, the standard deviation (jitter) was an astonishing 0.0018 ms (1.8 microseconds)! Given that 1–2 ms of jitter is considered perfectly acceptable for MIDI, my external clock is literally running with reference-class precision.
But I didn't stop there. To put the final nail in the coffin, I eliminated the "MIDI scapegoat" entirely:
I completely disconnected the MIDI cable from the RC-600.
I factory-reset the device to ensure absolute stock behavior.
I recorded a clean loop on Track 1 at internal 120.0 BPM and saved it.
I changed the memory slot forward and back to reload the saved loop freshly.
I recorded onto Track 2—and the moment I pressed play, the internal BPM display suddenly jumped from 120.0 BPM down to 80.3 BPM!
I repeated the exact same test: This time, the internal clock randomly jumped from 120.0 BPM to 120.4 BPM.
This happens completely WITHOUT any external MIDI clock connected. The RC-600's internal buffer management and time-stretching algorithms are fundamentally broken on the secondary tracks.
I have fully documented this mess, uploaded the videos of the behavior, and even provided my raw CSV oscilloscope files from my Launchpad Pro MK3 midi-clock as it arrived on the RC-600 (which I was told it would have a bad quality - but every other device works properly).
Luckily, I officially reported this defect to my dealer (Thomann) before my warranty expired in late 2025. Now that the hardware and external clock are scientifically proven to be flawless, they either need to provide a working firmware or give me a full refund for one of the worst-coded devices I have ever wrestled with.
Nice hardare - but too many firmware issues.
Has anyone else noticed this exact internal BPM-drop behavior on Track 2?
Or audio-jitter, when using an external midi-clock?
Might my device be broken?