Loopy Pro: Create music, your way.
What is Loopy Pro? — Loopy Pro is a powerful, flexible, and intuitive live looper, sampler, clip launcher and DAW for iPhone and iPad. At its core, it allows you to record and layer sounds in real-time to create complex musical arrangements. But it doesn’t stop there—Loopy Pro offers advanced tools to customize your workflow, build dynamic performance setups, and create a seamless connection between instruments, effects, and external gear.
Use it for live looping, sequencing, arranging, mixing, and much more. Whether you're a live performer, a producer, or just experimenting with sound, Loopy Pro helps you take control of your creative process.
Download on the App StoreLoopy Pro is your all-in-one musical toolkit. Try it for free today.
Do I need "Fcbff" app and uno chip if I buy fcb1010 footpedal?
Quick question, I'm Thinking about buying the fcb1010 foot pedal to loop in loopy. Will I be fine with just the unit or do I have to buy any extra stuff? I'm using with the behringer istudio202 docking station.
Comments
The FCBFF app does NOt work with the UNO chip. But you don't need the UNO to use the FCB1010 with Loopy, etc. See for further info the description of the FCBFF app in the iTunes store.
Thank you for the response. So just to be clear... I'll be fine with the app and just the pedal? I'm purchasing it off of Amazon BEHRINGER FCB1010 https://www.amazon.com/dp/B000CZ0RK6/ref=cm_sw_r_cp_api_3G97xb6F7QTBN
Hi -- I'm the dev for FCBFF. It does not work with the Uno chip (@Harro is right). The app is designed for the stock FCB firmware, and just makes the programming of the FCB easier. The app also does a little bit of emulation, so you can develop and test out configurations, and it'll also store the configuration SYSEXes, so that you can move your setups around.
If you only want to control Loopy, you could just use MIDI-learn on that, along with the default FCB preset configuration. If you want to control more apps, and have a more complex set-up -- that's when being able to tweak the FCB comes in handy.
The FCB weighs a ton, is built like a tank, and is incredibly hard to program (which is why I wrote the app). If you're doing a lot of MIDI control of different things, it's worth the time and effort to get it going. If it's just simple on/off of one or two apps, there are probably easier ways to go.
I'd say the uno chip is non essential. Makes the pedal even harder to program stand alone. The best thing i found, it tightened up the cc pedals.
Hey, thanks for the explanation .. your guy's apps are incredible. I plan out starting out with a more simple approach but eventually plan on using the fcb1010 with other apps. I've just heard about how complicating it is getting started with the fcb, So yea, I'll definitely be purchasing the app. I'm just glad someone created it! Also glad I don't need the uno chip, thanks for clarifying that for me.
The FCBFF app is a gift to humanity. Not that I'm terribly good at it but I have been programming music machines basically since that was a thing and the FCB remains a mother.
Agreed.. I get the fcb1010 tomorrow in the mail. I'm gonna buy the FCBFF app after I'm done writing this post. Props to @SecretBaseDesign for this 1. Midimorphosis is next on my list.
Sorry to waste ur time. Hoping u can help me. So I got the fcb1010 and FCBFF. Now.. this is confusing and I only have so much time to figure this out. I'm sure your time is valuable also so I would completely understand if u can't help me.
So before I even use the pedal , am I supposed to upload the fcb1010 configuration to the app? Because I tried just hooking up the pedal to the istudio202 str8 out the box .. and it doesn't even show up in the " control inputs " section. The istudio does tho.
I know I set up the midi cable correctly. Maybe hook up another one from the "out" on istudio to the "in" on the fcb
Nope that did nothing. I just though that it would least register in the control input section in loopy out the box. Thanks for ur app .. lol it's definitely gonna come in handy with this beast!
Correction-- it did register. It was under "bseries app" my mistake
FCBFF is a god send![B) B)](https://forum.loopypro.com/resources/emoji/sunglasses.png)
Ok -- did you get it going? Let me know if you need some help!
Yes sir! Finished about 20 minutes ago. I ran into one issue (which was not on your end) I just had to calibrate the expression pedals using this link http://www.sweetwater.com/sweetcare/articles/the-expression-pedals-on-my-behringer-fcb1010-midi-foot-controller-dont-work-properly-in-programming-mode/ .Thanks again.. ur app made it EZ. I'm PSYCHED! Bout to jam!!
So I got 10 banks of presets/bindings that I can program on this bad boy!? Wha!? ...I can't WAIT for loopy 3.
Damn straight. Have fun with that new foot board.
Rock n roll!
Hi all. Sorry to dig up this old thread.
I bought a brand spanking new fsb for £30 today and as most if not all I'm stuck at the taming phase. I've tried video tuts on YouTube but I'm not getting anywhere. Anyone can point me to anyones they found useful?
I'm guessing part of the problem is that FCBs with different chips will respond differently. Mine is the stock one (i think).
Question to @SecretBaseDesign
Can your editor program all 1 to 10 buttons to send CC messages? Also does it work with all chips?
Thanks
Hi -- that's a good deal on the FCB!
My app will let you program all the buttons, on all the banks -- but it's designed for the stock FCB firmware. It does not support the UnO mods, or anything like that.
The FCB is a little weird (ok, a lot weird). Each pedal can send multiple MIDI messages on multiple channels, with some of them being note on/off, others being CC values, and so on. Powerful pedal, but not easy to get your head wrapped around.
There's a manual for the fcb1010-editor (for Windows and Mac) from the maker of the Uno-chip, that explains the functions and programming of the fcb1010 very well. You can find it here: http://www.fcb1010.uno/downloads/FCB_UnO_ControlCenter_manual.pdf
It helps you to understand this footpedal better. Also if you don't have the Uno-chip installed. His website is also a good startingpoint, with links to usergroups, etc.
Got it working for most part on the unit itself. I isn't such a big deal once you understand their logic (doh). I got all controls sending CCs between 22-33 including the expression pedals that needed to be calibrated before they'd send out anything.
The only thing is that I still can't get my head around the PC vs CC vs Note.
So I think I understand PC and Note
Note = on when pressed, off when released
PC = single message to change patch
However I'm still struggling with CCs momentary and toggle. So momentary just fires one message that triggers something and toggle works just like a light switch.
If that's the case, how does FCB differentiate between the two? Is this where other chips come in? @SecretBaseDesign @Harro
@supadom
momentary sends same CC value whenever pushed .
toggle requires 2 values ( usually 0 + 127 ) & switches to the other whenever pushed .
you might find helpful what I wrote on LoopyHd forum about FCB a few years ago now , collated
(re: standard chip )"The main thing to realise is that every 1-10 footswitch is a preset in itself, which includes the settings for the two expression pedals, so depending on how its programmed , pressing another footswitch can change the midi cc numbers of your pedals. You can use this to your advantage to control many different midi ccs with the pedals, but it can cause confusion until you realise whats happening.
The Uno firmware was originally to use the fcb more like a standard guitar pedal, so that the top row of switches turn on/off different fx within a multifx patch.
The Fcb can be programmed to behave like this with the standard firmware, treating a bank of ten presets as a single "board" , and using the toggle function of the switches , but without the red light indicating whether each switch is on or off that the Uno firmware adds.
(To explain how you manage to achieve the 'board' setup? ) :
It's a question of understanding the three levels of operation, as the board functions differently depending on what level you are in.
At the micro level (editing within a preset ) each switch becomes a programmable parameter .
In normal operating mode (up a level , zooming out so to speak) each switch is an individual preset , containing the ten parameters programmed across the board in edit mode).
There are ten presets per bank , but each one is independent.
Ok , so for guitar pedal mode ,we want to zoom up another level , and think of all ten presets within a bank as the ten switch layout of a pedal board. So the "board" is a construct of how the ten presets are programmed to behave together.
basically we program all ten presets the same, except for the specific parameter we want to change at a specific location on the board. so for each of the top row of switches to turn on/off
Distortion,chorus,delay,reverb,eq sections of a multifx unit , copy the same basic preset which assigns the footpedals to do whatever you want ( across the board) and whatever you want the botton row to do (program change up/down maybe?) (across the board ) , and then modify (into edit mode) each of the top switches so that it toggles on/off the multifx parameter you want on that switch .
Look into the manual for toggling. Each preset has two toggle switches (you only want to use one)
Where two values are toggled each time the preset is selected , so choose your cc parameter for e.g delay on/off then give hi/lo values of 127/0 .
Hope this explains.it's conceptual more than anything , you have to program each preset within the bank to only change the one parameter you want on each switch, whilst replicating the overall settings so hitting a different switch to turn one thing on/off doesnt change the other settings ."
Wow, cheers @Wally for such a quick and comprehensive answer. Of course, makes sense that toggle would work like that. And yes I did realise that expression pedals' lights change every time I press a different pedal.
I will take a look at that thread on loopy forum. Thanks again.
@supadom No worries .
The main point is that the FCB1010 is not a standard guitar pedal board , where each of the buttons & pedals make up a whole control patch . On the FCB , each preset button is an independent preset sending instant CC,PC & notes including the 2 pedals .
if you want the FCB board to behave like a guitar board , you have to program ALL the ten presets in 1 bank to work together in a higher level construct .... so all ten have the same main settings including the same expression pedal settings , then any button you want for a particular parameter e.g button 6 for distortion on/off has that parameter CC set to toggle.
hope that makes sense.
^^^
when you press each button , you are changing a preset , so all presets need to be the same to behave like a standard guitar footboard .
@Wally -- that was a great explanation!
Just found an FCB1010 for £45 in a 2nd hand music store.
Glad I got the app a while ago in preparation for this day.![:) :)](https://forum.loopypro.com/resources/emoji/smile.png)
Any recommendations on the usb to midi din cable required?
cheers
I remember an issue with stock firmware and non desired tap tempo midi send each press... it was solved sometime? Just curious at this moment I have a rc100 mk2 modded...
Any old cheapo USB->DIN cable on amazon, ebay etc will work fine. 5-10 bucks.
You could also point it to the DIN in on the X-station with a stock MIDI cable and then set the XS config to send "MIDI In" to USB out. Haven't actually tried this with the FCB+XS but should work fine.
Y'know I was thinking just this about 30 minutes ago.
Not tested yet though. Cheers Will.