tutorial: live looping with ableton live and boss fc-50

Since I realize there’s a bunch of not-german-speaking people out there willing to learn something about using the Boss FC-50 with Ableton Live as a loop station, I decided to translate my ariticle into awful english. tomauger.com already did half of the work – thanks for this! But still there is a little difference in how we wanted things to work.

My aim was to use only one single footswitch for one single loop-track.

Most approaches (also tomauger’s) required to use at least two footswitches for one track: The first for recording, the second for playing back the loop. Maybe also a third one to delete the scene. (If you want to loop a midi track you have to use even a fourth one in order to aim the track for playing). One could also try to use two other footswitches in order to select next/last scene/track. But all that means:  You have to use a lot of footswitches everytime you want to loop a single track.  It gets complicated, and thats not only uncomfortable but also dangerous in a live situation!

With the 6 pedals of my Boss I’m now able to control 10 (!) tracks.

It will work this way:

  • Footswitch 1 (FS 1/6) first hit: Start recording Track 1
  • (FS 1/6) second hit: Stop recording on Track 1 and play recorded sound in loop
  • (FS 1/6) third hit: Delete the loop and start recording Track 1 again
  • (FS 1/6) fourth hit: Stop recording, play loop…
  • and so on…

Remember: Switch 6 on the FC-50 is not working as a real trigger but kind of as an CAPS-Lock – but only kind of. Tomager wrote about that:

The one stupid thing that it does though (for my purposes) is that this 6th switch will send whatever PC Message would be triggered by whichever of the 1-5 (or 6-10) switch was last pressed. Let me state this more clearly using an example:

  • If you press Footswitch 1 (FS 1/6) by default the FC-50 sends PC #1
  • If you then press FS 2/7 by default it sends PC #2. So far so good.
  • If you then press the Bank Switcher (A/B) to switch to the higher bank (6-10), it will send PC #7, because FS 2/7 was last pressed and now that we’re in Bank B, FS2/7 sends PC #7.
  • If you then press FS 1/6, it sends PC #6, as one would expect.

This is a pain in the arse.

Yes, it definitely is. But with my approach this doesn’t lead to show-stop because using the Bank Switcher will cause nothing more than aiming a specific track in Ableton: For example, if you press FS1/6, Track 1 will be aimed. If you then press the Bank Switcher, Track 6 will be aimed. And so on.

Here’s a little tutorial how to use my script:


  1. A Boss FC-50 (of course, this will also work with other pedals sending progam-change commands)
  2. Download Bome’s Midi Translator (the free „classic“ version works fine enough)
  3. Ableton Live (It works with all versions)

How to do it

Download my srcipt and open it in Bome’s Midi-Translator. Then map the keyboard commands in Ableton as follows:

Important: Use capital letters! You can also use my Ableton file.

You don’t have to make more midi configuration in Ableton, but in Bome’s Midi Translator (if you didn’t do that before). In the menu, select the midi-in you hooked up your FC-50. Midi-Out is of none importance since we want to send keyboard commands to ableton.

Now things should work:  Switch to Ableton and trigger footswitch 1. Track 1 will be aimed for recording. If you trigger the same Footswitch again, it will start recording on track 1. Trigger one more time and recording will stop and play the recorded sound in loop.

In case it doesn’t work, try out this:

  • Your Boss might be connected badly. In Bome’s Midi-Translator a light is blinking down to the left if the program is recieving Midi data.
  • You pedal doesn’t support program-change commands or it’s sending other ones than the fc-50 does. Then you have to start editing my Midi-Translator script.
  • You didn’t use CAPITAL LETTERS in Ableton.
  • …or caps is activated on your keyboard.

So what’s the big deal about this script? How does it work?

The problem with Bome’s Midi-Translator is, that only one specific keyboard action (or string) can be assigned to one specific midi signal. The program doesn’t understand that a footswitch was already triggered before (e.g. for aiming a track) and that we now want him to execute another command if the switch will be triggered again (e.g. for recording the loop).

The solution can be found in Midi-Translator itself. With the software you’re not only able to execute keyboard commands, but also preset changes.

With this feature it is possible to assign to a footswitch BOTH a keyboard-command AND a Bome’s-internal preset switch (or change) . In this now activated preset, the footswitch is assigned to other commands than in the preset which was active before. The commands of the other footswitches will remain the same in this preset.  This you have to do for ALL the footswitches on EVERY step (aim, rec, play, del).

The script will get really confusing with increasing tracknumber, number of switches and numner of steps. So everyone who wants to f*** up his brain, feel free to take a look into the script and edit it ad libitum!

I look forward to see something of your approaches!

Getaggt mit , , , , , , ,

8 Gedanken zu „tutorial: live looping with ableton live and boss fc-50

  1. […] Anleitung: Live-Looping mit Ableton Live und Boss FC-50 Von alexispryds 6 Kommentare Kategorien: Equipment und Studio, Live Music und Software Tags: ableton, bome's midi-translator, boss fc-50, live, looping, pedal, tutorial Update: Click here for english verion of this article! […]

  2. matias sagt:

    thanks for the tutorial

    the files are no longer available from those links. any other source to download them from ?

  3. matias sagt:

    hey! it was really easy to make it work following your tutorial. thank you Alex.

  4. Thanks for your tutorial. I just purchased a Roland GFC-50 not knowing the difference between a program controller and a command controller. I really like the size of the GFC-50 and really want to make this work.

    I haven’t tried your tutorial yet but am really glad I have this to work with since there seems to be nothing else out on the net.

    Do you think your script would work with a Mac friendly looper like Mobius?

  5. Hallo, mal wieder Alexis. Ich versuche, die Verwendung von Google übersetzen diese in Deutsch zu schreiben. Ich hoffe, das funktioniert. 🙂

    Ich habe versucht, das skript herunterladen, aber es sagt, es ist ein problem. Ich denke, die zeit auf dem File-Sharing-Server erlaubt abgelaufen ist.

    Könnten Sie bitte laden und aktualisieren Sie Ihren Link bitte?
    Nochmals vielen Dank.

  6. Matthew sagt:

    Hi Alex,

    I am getting the following issue with programming my pedal:-

    Here’s my data capture:-
    Pedal 1 – C0 00 (this is consistent)
    Pedal 2 – C0 00 or C0 01 it randomly varies between the two data strings as I press the pedal numerous times
    Pedal 3 – C0 00 or C0 02 etc
    Pedal 4 – C0 02 or C0 03 etc
    Pedal 5 – C0 00 or C0 04 etc

    As you can see apart from Pedal 1 all the other pedals procuce two different values and they are random which order they apprear in, so clearly impossible to program.

    The pedal is fine as I have tested this on my PC’s MIDI card, so it would appear to be just my MIDI/USB interface to the laptop.

    It’s one of those cheap ones

    However it works fine for my MIDI keyboard but is clearly struggling with the Program Change data, I suspect the drivers are at fault.

    I am happy to buy a better MIDI/USB interface however my concern is I can’t be sure if this one will have the same issue too, perhaps someone can recommend one?

    Many thanks


    • alexispryds sagt:

      hi matt,

      this really sounds like a frustrating fault. anyway, it’s hard for me to believe that your problem origins from buggy transmissions of data information by your midi/usb interface. but since you already checked your pedal on your pc’s midi input and your midi keyboard also struggles with pc data when using it with your interface to the laptop, it seems almost obvious that it has to something to do with your adapter cable.

      nevertheless please check the following things (if you didn’t already):

      – what midi device/port is selected in bmt? is there any other device/port installed by the drivers of your interface? how do they behave?

      – is your midi interface plugged to another device or are there any other midi devices hooked up to your system? is there a possibility of midi feedback?

      – what happens if you change to another bank on the fc-50? how does the ‚randomness‘ behave?

      – does your midi-keaybord have a midi input? if yes, try to send your pedal through the keyboard and see if the same ‚randomness‘ appears.

      well, if nothing works and it comes to a new interface, i would not recommend to buy an adapter cable. have you considered to change to a combined usb (or firewire) audio/midi interface? usually the software is programmed way better and the ‚real‘ asio driver, as a side effect, will also lead to lower latency. not to speak of the audio quality. i can recommend everything from edirol/cakewalk, m-audio and in some cases behringer. it just depends on your needs. if you need some advice, just ask.

Kommentar verfassen

Trage deine Daten unten ein oder klicke ein Icon um dich einzuloggen:


Du kommentierst mit deinem WordPress.com-Konto. Abmelden /  Ändern )


Du kommentierst mit deinem Facebook-Konto. Abmelden /  Ändern )

Verbinde mit %s

%d Bloggern gefällt das: