In my last few posts, I’ve been trying to deconstruct recording workflows (and doing so a bit too brashly), to ask an open question:

Can we improve the way recording works, for your average musician?

Let’s focus on recording at home for now, and acknowledge that professional studio recording and power users might have different requirements . Let’s also assume that I’m starting fresh on a new song.

The two scenarios we’ll consider are 1) that I’ve got an idea that I’d like to record, or that I’d like to play my instrument and see if I stumble on something that sounds nice while being recorded.

You can record an idea into a DAW or a wave editor, but before you move forward and use that recording to start a new song, you need to do some things like:

Chopping up the recording. Picking a tempo for the song that matches your recording, in case you didn’t already pick a tempo beforehand.

These might seem obvious and completely necessary. How could you use a recording in a song without manually trimming it? How could you use a recording without having picked a tempo?

But when you think of a catchy melody in your head, did you start by picking a numerical tempo in your mind? Or did you just think of the melody? Is there a way to communicate a catchy melody to the computer without explicitly expressing the tempo, yet still allowing you to build on it (in a quantized environment like a DAW)? [1]

Now, what if we re-imagine the role of the computer in this. Instead of thinking about the computer as a workstation, which we sit down and operate, let’s think of it as something more passive. Could we change this workflow so that the computer instead passively supports you when you want to record, and maybe even eliminates the chopping and tempo picking you need to do before turning your recording into a song?

Sounds like a interesting challenge to me. So here’s my attempt at changing this recording workflow to eliminate these steps, in order to help you go from having an idea in your head to building a song around it, faster. It’s by no means perfect, and is not necessarily better, but it’s different, and I hope that it’s a good starting point from which we can build on.

The Freestyle Recorder is a completely hands-off MIDI recorder. I started by removing the record button. There’s no stopping it, it’s always recording into a 3 minute long buffer. Next, it listens to what you play, and when it hears you stop playing, it automatically chops the thing you just played into a segment.

You can sit down and jam until you play something nice, and the Freestyle Recorder tries to cut up your takes automatically. You can just focus on playing.

Next, because the Freestyle Recorder is just listening for silence when it’s detecting takes, we need a way to tell it how to chop a recording more tightly. Remember, we want to avoid manual chopping. Next, let’s assume we want to produce a loop out of our recording.

But maybe we can kill two birds with one stone here. We still need to tell the computer some information about the tempo of our song, but BPM detection might not be accurate enough, and I didn’t play along with a metronome. I just played. How about if the recording were played back, and we just tapped along with it? This would tell us both the tempo of the recording, and give us a hint about how many beats were in the recording, so we can chop it tighter.

This is exactly what I programmed, and it works… OK. You need to play in 4/4 time, at a fairly constant tempo, and when you tap along with your recording, it has to be pretty tight. But if you get those things close enough, the Freestyle Recorder produces a seamless loop of your recording, without you ever having to hit record or entering a tempo. Above all, it’s different, and I hope this approach helps generate some new ideas to take it even further.

Did I mention that because it knows the loop length and tempo, the Freestyle Recorder can automatically snap a beat perfectly over your recording? When it works, it’s pure magic:

What’s your impression of the Freestyle Recorder? Leave a comment and let us know what you think!

[1] BPM detection is one way to have a computer extract this information. My experience has been that some algorithms struggle with very short pieces. The algorithm I tested really struggled with jingles that were just a few bars long and played naturally.