Date   

Re: New to my FCB1010, could use programing help.

EJ SHELDON
 
Edited

"Why is there a 1-128 and a 0-127… that seems confusing.  Why didn’t the MIDI founders just make it one set? lol."

They did: 0-127. Somewhere along the line. device mfrs decided that displaying 1-128 was more "User Friendly". Right.

More Fun MIDI Factoids:
MIDI was originally designed to control HW Synths. As a standardization method, certain CC#s were "Reserved" for certain functions. Not all synths used all, or any, or the "Standards". Most likely, you can ignore these and use whatever CC#s you like for whatever. For our purposes, just make sure that if more than one device is "Daisy Chained", they're all listening on different Channels. Here's a list of "Reserved CCs", in case you're interested:

MIDI CC List (Quick Guide) - Professional Composers

"There are 10 presets on the FCB1010 and 2 expression pedals…
 
But there are only 10 presets in the FCB manager… where do I set the expression pedals?"

Here's where I'm going to recommend that you read the FCB1010 Manual. It's kind of a "rite of passage" to allow Behringer to confuse new users as much as possible.

The short story:

The FCB has two operating Modes Direct Select Activated and Deactivated. Forget Direct Select. Deactivate it (default).

There's 10 Presets in each of the FCB's 10 Banks. Each preset can send 5 Program Changes, 2 CCs (or 1 Toggling CC), 1 NOTE, and control 2 Exp Pedals (A & B), all on different MIDI Channels. Each Preset can also control 2 HW Switches - useful for Channel Changing/Reverb etc on amps that support it.

In the editor that you are using, the individual 10 Preset Banks are differentiated by Light or Dark Grey.

NOTE: Before the Expression pedals are activated, you have to select a Preset where the Exp Pedals are assigned. If they are NOT assigned in a given Preset, they won't work. The settings are NOT Global.

"Also if you’re not using the FCB manager… what are you using to program the board?"

I HIGHLY recommend that you spend $22 to get the UNO_ControlCenter Editor. The editor that you are using is not bad, but IIRC, is not actively supported, and the UNO_ControlCenter is just better. You do not need the UNO Chip, but when you upgrade to UNO, your current editor will no longer work.

FCB/UnO Control Center for the Behringer FCB1010

"Finally… I’m not sure what this means.
 
“ Note that, if you select a different Preset (press a different button), the status of the CNT sequence is NOT SAVED!"
 
So if I use preset 1 as an on/off toggle and hit the peddle… I’ve run the first part of the sequence… but if I then hit preset #2… the FCB will think that it hasn’t started the preset 1 initial sequence.  So if I hit preset #1 again… if will initiate, again, the fist part fo the sequence?
 
Does that make sense?"

Exactly!

If you upgrade to the UNO Chip, what you get is 19 Banks. In each Bank, either the top or bottom row of switches (your choice) acts as "Stomp" style buttons, sending up to two "Toggling" CCs, with the LEDs reflecting the status of the Stomp. The other row sends PCs (Presets). Each Stomp has it's own memory - within the selected preset, if you send ON with Stomp 1, then send OFF with Stomp 2, Stomp 1 remembers that when you press it again it needs to send OFF. Also, you can send all 5 Stomp Messages (with assigned Value1 or 2 - ON or OFF or NO CHANGE) on Preset Load. This means that, for instance, in an Amp Sim with 5 FX, you can turn ON/OFF whichever FX you need for that song or song part. The LEDs on the Stomps will reflect the status (can't be done at all with the stock chip) and if you need to change the configuration, the assigned Stomp is ready to go - if you sent ON at Preset Load, it'll send OFF.

IOW - whereas the FCB communicates in one direction only, this allows you to create faux two-way communication.

If you change presets, however, you're back to where you started.

UNO reduces the total number of presets available to 95 (19 * 5). The saved memory is used for the Stomp functions.





New to my FCB1010, could use programing help.

Drew Weininger
 


Thanks Ed!

This is  helping me clarify all of  this in my head.

I have a few questions for you if you get another cup of coffee in you and feel like answering! :)

PC and CC… got it and that makes sense thanks for the explanation...

Why is there a 1-128 and a 0-127… that seems confusing.  Why didn’t the MIDI founders just make it one set? lol.  

OK, it works!  I was able to program my board and get preset 1 to toggle my MainStage footswitch on and an off.   I set my CNT1 to 80 which is a general on/off toggle and the value to 0 and the CNT2 #80 and Value to 127.  Programed the board and it works with MainStage.  Very, very cool.

You picked up on something… I thought MIDI was a two way signal… so I only had one cable running from my FCB1010 to my interface.  I hooked up a second cable going the opposite direction…. Don’t know what I didn’t think of that in the fist place.

Questions:

There are 10 presets on the FCB1010 and 2 expression pedals…

But there are only 10 presets in the FCB manager… where do I set the expression pedals?

Also if you’re not using the FCB manager… what are you using to program the board?

Finally… I’m not sure what this means.

“ Note that, if you select a different Preset (press a different button), the status of the CNT sequence is NOT SAVED!"

So if I use preset 1 as an on/off toggle and hit the peddle… I’ve run the first part of the sequence… but if I then hit preset #2… the FCB will think that it hasn’t started the preset 1 initial sequence.  So if I hit preset #1 again… if will initiate, again, the fist part fo the sequence?

Does that make sense?


Thanks again!



On Nov 30, 2021, at 10:32 AM, EJ SHELDON <bluesrock13@...> wrote:

[Edited Message Follows]

A VERY simplified explanation:

Think of a PC (Program/Preset Change) as a message that calls a saved collection of instructions.
They might configure a sound on a synthesizer or a scene in a light show.
Some programs/devices respond to 0-127, some use 1-128. Differences are usually resolved in code behind the scenes.

A CC (Control Change) is used to set a single parameter (or group of parameters) within a Preset. For example, Volume.
It might be a simple ON/OFF (CC# + VALUE = 0-63/64-127), or a specific "level" - CC# + VALUE 0=0db;127=100db.

By default, all of the buttons on the stock FCB send PC messages. If CNT values are set, it sends them sequentially - PC-CNT1-CNT2.
The Exp Pedals send CC# + a variable VALUE based on pedal position.

To create a "Toggling" CC, you disable the PC message (not required, see below), then set BOTH CNT1 and CNT2 to the SAME CC#.
You set the VALUE of CNT1 to either 0 or 64 (I always use 0/127), and set the VALUE of CNT2 to the opposite.
Some programs/devices simply use 0/1. RTM!

The first time you press the button it sends CNT1, then next press CNT2.
If you don't disable the PC message, the first press sends the PC followed by CNT1, the next press sends just CNT2.
Subsequent presses alternate the CNT messages.

Note that, if you select a different Preset (press a different button), the status of the CNT sequence is NOT SAVED!
This is one of the many differences between the stock FCB and the UNO chip.

I can't tell you specifics of how to apply this information to Mainstage, as I am a PC guy.
From what I've read about Mainstage, it uses an intervening "VIRTUAL Control Panel". You assign (or "Learn") a value to a virtual controller in the "Control Panel", then assign that controller to whatever you want to control within the program according to the program's requirements. I think you can also create multiple "Control Panels" for different purposes. RTM!

Hope this helps/makes sense!

EDIT: I've never used that editor beyond seeing what it was about but it LOOKS like you're doing it right. If the editor isn't sending the configuration to the FCB it COULD be because your MIDI interface won't send sysex messages. What MIDI Interface are you using? It could also be because the editor requires two cable (IN/OUT) connections, or that you haven't configured the I/O Ports correctly in the editor's SETTINGS/PREFERENCES dialog. Since I haven't had the stock chip in my FCB since two hours after I bought it, I can't really help beyond that.



Re: New to my FCB1010, could use programing help.

EJ SHELDON
 

Further thoughts:

It's always a good idea, when programming your FCB, to have two cables connected. This way, after you send the sysex to the FCB, you can verify the success of the operation using a MIDI Monitor. I don't know if that editor has a Monitor, but I'm pretty sure that Mainstage does, and there are standalone Monitors available online for MAC.

Another reason that a sysex send might fail is that sometimes the FCB's tiny little brain gets scrambled, and it starts to do strange things. When your FCB starts acting wonky for no apparent reason, perform a factory reset by booting while holding buttons 1 + 6.

Anytime you perform a factory reset, and before the first time you use an editor, you need to set the FCB to Receive Sysex.
You do this by booting while holding the DOWN button, hit the UP button twice, then hit button 7. The LED will light.
Then hold the DOWN button until the FCB starts it's reboot sequence.

I'm into my second cup of coffee, so I may think of something else. :-)


Re: New to my FCB1010, could use programing help.

EJ SHELDON
 
Edited

A VERY simplified explanation:

Think of a PC (Program/Preset Change) as a message that calls a saved collection of instructions.
They might configure a sound on a synthesizer or a scene in a light show.
Some programs/devices respond to 0-127, some use 1-128. Differences are usually resolved in code behind the scenes.

A CC (Control Change) is used to set a single parameter (or group of parameters) within a Preset. For example, Volume.
It might be a simple ON/OFF (CC# + VALUE = 0-63/64-127), or a specific "level" - CC# + VALUE 0=0db;127=100db.

By default, all of the buttons on the stock FCB send PC messages. If CNT values are set, it sends them sequentially - PC-CNT1-CNT2.
The Exp Pedals send CC# + a variable VALUE based on pedal position.

To create a "Toggling" CC, you disable the PC message (not required, see below), then set BOTH CNT1 and CNT2 to the SAME CC#.
You set the VALUE of CNT1 to either 0 or 64 (I always use 0/127), and set the VALUE of CNT2 to the opposite.
Some programs/devices simply use 0/1. RTM!

The first time you press the button it sends CNT1, then next press CNT2.
If you don't disable the PC message, the first press sends the PC followed by CNT1, the next press sends just CNT2.
Subsequent presses alternate the CNT messages.

Note that, if you select a different Preset (press a different button), the status of the CNT sequence is NOT SAVED!
This is one of the many differences between the stock FCB and the UNO chip.

I can't tell you specifics of how to apply this information to Mainstage, as I am a PC guy.
From what I've read about Mainstage, it uses an intervening "VIRTUAL Control Panel". You assign (or "Learn") a value to a virtual controller in the "Control Panel", then assign that controller to whatever you want to control within the program according to the program's requirements. I think you can also create multiple "Control Panels" for different purposes. RTM!

Hope this helps/makes sense!

EDIT: I've never used that editor beyond seeing what it was about but it LOOKS like you're doing it right. If the editor isn't sending the configuration to the FCB it COULD be because your MIDI interface won't send sysex messages. What MIDI Interface are you using? It could also be because the editor requires two cable (IN/OUT) connections, or that you haven't configured the I/O Ports correctly in the editor's SETTINGS/PREFERENCES dialog. Since I haven't had the stock chip in my FCB since two hours after I bought it, I can't really help beyond that.


New to my FCB1010, could use programing help.

Drew Weininger
 



Hello Everyone. 

Totally new to FCB1010 and this chat group.  I bought an FCB1010 on a whim and trying to set it up.  I’d love to understand better how to program it.

I want to use it to control MainStage

BigSur 11.4
MacBook Pro: Apple M1

I’ve installed FCB1010 Manager and watched a handful of tutorials and read through the manual.  I’m new to Midi… 

My understanding… 

I want my FCB1010 to simply toggle on/off a foot pedal in MainStage.  I can set up MainStage and my keyboard to do this but my FCB will not seem to do it.  My Bank 0; 1-10 switches seem to do nothing.  My expression pedals however… I can map that to my MainStage pedals.

All I want to do is set Bank 0; Switch 1 to my pedal in MainStage.

I think where I’m getting confused is I’m not certain what a CC is vs a PC vs a Note and which one I should use.  

MainStage uses 1-128 and so Does FCB…

But I don’t know where to plug in the numbers and which numbers to put in?  I would think I would set something like

Preset0:1 to Cnt 1 to 1 (= off). And Cont 2 to 64 (=on) and controlling the Value 80… which I think is an on/off CC…. ?  So if I tap it twice I would get those values sequentially?

As you can see I’m not doing this correctly- but I feel like I’m close!

I would map those values in FCB1010 Manager and then send them to my FCB1010  to program into the board.   Then switch the cable over to output and finish setting them up in MS.

Any help is appreciated! Would love to get this board working.

THanks!!!

-Drew




Re: FCB1010 first steps w/UnO chip and total desesperation

Antonio Díaz
 

It's just I found strange that after creating that new keyboard for S1 there is no need to indicate the different switches and pedals with any "Learn MIDI" instructions. It's not that I care: it works and it's all I wanted.
Again, thanks! This device is making me happy and I wouldn't have make it work without your invaluable help!


Re: FCB1010 first steps w/UnO chip and total desesperation

EJ SHELDON
 

On Sun, Nov 7, 2021 at 10:34 AM, Antonio Díaz wrote:
strangely you don't need to map that "new keyboard

Not sure what you mean by that. You have to CREATE the new Keyboard, but when you create the Instrument track and point it at Amplitube/CH1 it maps itself, since ( I guess) that's what's sending on CH1.

Anyhow, glad it's all working!


Re: FCB1010 first steps w/UnO chip and total desesperation

Antonio Díaz
 

Well, dude. I have tried with Reaper following the kind instrucions you provided me. Later I tried to use the FCB as the guy from S1 forums told you (strangely you don't need to map that "new keyboard"), and this is what I got: absolute bliss. 

There are no words to describe how I feel: I can use the FCB in both DAW's thanks to your help. I can use it even with Neural DSP just using the sysex you provided me for Amplitube 4. My God, I am sooooo happy I purchased this thing and met you.

THANKS!!!!!!!

De: main@fcb1010.groups.io <main@fcb1010.groups.io> en nombre de EJ SHELDON <bluesrock13@...>
Enviado: domingo, 7 de noviembre de 2021 1:48
Para: main@fcb1010.groups.io <main@fcb1010.groups.io>
Asunto: Re: [fcb1010] FCB1010 first steps w/UnO chip and total desesperation
 
Got a reply on the S1 Forum:

Hi there,
the FCB 1010 has to be integrated as an "New Keyboard"!
NOT as a "Surface" and NOT as a "New Instrument"!

FCB1010 + UnO2 rules! 

Regards,
Tino

-----------------------------------------

I deleted the device I was using and created a Keyboard device and IT WORKS!
The setup is just like any other DAW - separate track for MIDI, pointed at the VST.


Re: FCB1010 first steps w/UnO chip and total desesperation

EJ SHELDON
 

Got a reply on the S1 Forum:

Hi there,
the FCB 1010 has to be integrated as an "New Keyboard"!
NOT as a "Surface" and NOT as a "New Instrument"!

FCB1010 + UnO2 rules! 

Regards,
Tino

-----------------------------------------

I deleted the device I was using and created a Keyboard device and IT WORKS!
The setup is just like any other DAW - separate track for MIDI, pointed at the VST.


Re: FCB1010 first steps w/UnO chip and total desesperation

EJ SHELDON
 

Place the attached midimonitor.dll in your C:\Program Files\VstPlugins folder (it's 64bit).
Make sure that path is in the Reaper VST Scan settings (Preferences>Plug-ins>VST).
Make sure your MIDI Interface is enabled in Reaper Preferences>MIDI Devices.
Put Amplitube on your Audio Track - in Reaper the track type is defined by the Input - if it's an input from your Audio Interface it's an Audio Track. If it's an input from your MIDI Interface it's a MIDI Track.
Put the MIDI Monitor on the Audio Track. It's in the VSTi list.
Route your MIDI track to the Audio Track.

The attached screenshot should fill in all the blanks.
You'll know it's set up correctly when you see the FCB's output in the MIDI Monitor, which is on the Audio track with the AT4 VST.
MIDI in AT4 should now work just like in the Standalone.

Questions?


Re: FCB1010 first steps w/UnO chip and total desesperation

Antonio Díaz
 

Well, I have been trying Reaper this afternoon and I like it a lot! It's bare-bones look suits me. Amplitube sounds just ok, I can use my MIDI keyboard to play all my VST synths, but... I just can`t figure out how to use the FCB! I must be a lost cause. 

The device is recognized by Reaper, but I don't know what to do. Please, please, please: this will be the last time, I promise, but tell me what to do? The moment I can hear Amplitube and bypass effects in Reaper I will be the happiest guy in the world


Re: FCB1010 first steps w/UnO chip and total desesperation

EJ SHELDON
 
Edited

Unless there's something that you use in S1 that nobody else has, any of the three DAWs that I use - Reaper, LIVE! or even Cakewalk - can be used for FREE. 

Reaper is fully functional and apart from the nag screen on loading, is FREE until you feel like paying them the (very reasonable) $60 registration. It has HUNDREDS of excellent video tutorials, a large and helpful community and is regularly updated. The routing options are virtually limitless!
Apart from the Loop functions in LIVE! (see below), I've never found anything I couldn't do in Reaper, though TBH, my needs are pretty simple - play, record. 
If it has a weakness, it's that there's so much you can do, it can be overwhelming. For instance, Using a utility called ReaRoute, I can integrate LIVE! and the APCmini loop matrix controller for using the Loop matrix in LIVE!, and it feels like it's all one program with two distinct UIs. There's a way to integrate the very cheap Korg nanoKontrol2 (what I use) as a UI controller so that it feels like an actual recording console with physical knobs and sliders.
Have I mentioned that I LOVE Reaper?

LIVE! has a FREE version that's only limited in the number of tracks and sends. If you're into synths, loops or EDM LIVE! it's the live performance king. It also has great HW integration with reasonably priced controllers like AKAI APCmini (what I use). LIVE! also has a lot of tutorials and a large and helpful community. Their support is excellent. It can also utilize the Korg nanoKontrol2, which has a setting for use with LIVE!

Cakewalk is FREE and unlimited, but less straightforward to use. It was my first DAW, and I have an irrational nostalgic connection to it.
It's pretty.
I just installed the latest version, and it still has quirks and bugs that remind me why I prefer Reaper.
It took me a few minutes to remember the workarounds, but AT4 with MIDI works fine.
The Korg also works with Cakewalk.

Of course, there's a learning curve when you start with a new DAW, but while you watch the tutorials you can be playing your guitar with Amplitube and controlling it with your FCB.

Something worth considering.


Re: FCB1010 first steps w/UnO chip and total desesperation

Antonio Díaz
 

Oh man, I loved S1... until now. I think it's just a great DAW, but when it comes to FCB-MIDI, well, you know what it is.

I'm really sorry if I made you think everything was going fine in previous posts... My bad again. I miss so much my old 32-bit Nuendo: everything worked flawlessly. My greedy 64-bit attitude lead me here. I guess.

I hope that guy explains us what are we doing wrong. I just can't wait to play and forget this tech-ordeal!


Re: FCB1010 first steps w/UnO chip and total desesperation

EJ SHELDON
 

I had a really good day at work and I'm feeling flush, so I bought S1 Artist.
Now I see your problem.
I searched the S1 Forums and it seems most of the folks over there are KB players.
The few who've tried to use MIDI with Amplitube have mostly failed.
Except the one guy who said "It's really quite simple..."
He went on to explain pretty much what your screenshot showed.
It doesn't work.
I posted a request for help with a screenshot and quoted the guy's post.
We'll see if we get a solution.
Did I mention how much I hate S1?
Between you and me we've spent dozens (hundreds?) of hours trying to do what takes less than 2 minutes to set up in any other DAW.
AARGH!


Re: FCB1010 first steps w/UnO chip and total desesperation

EJ SHELDON
 

You've got me really confused. First you say it works, then it doesn't.
When you reply to what follows, just tell me exactly what is happening. Don't speculate, prognosticate or tell me what you want to do.
JUST the facts.

PART A
1) In U_CC, in the MIDI IN window, are the stomps sending CCs 111-115 and the other pedals sending PCs? In EVERY Bank EXCEPT 18, in which :
Pedal 6 = PC#90
Pedal 7 = PC#91
Pedal 8 = CC#110
Pedal 9 = CC#118
Pedal 10 = CC#119

If NO THEN you STILL don't have the sysex loaded. I'm pretty sure I asked this before, but what MIDI Controller (the thing between the FCB and the Computer) are you using? FULL DISCLOSURE PLEASE!

IF YES THEN

PART B
1) go back to Amplitube standalone. IIRC, you're on AT4? In MIDI>CONTROL CHANGE>GLOBAL you should be able to LEARN Stomp A Slot 1-5 BYPASS to CC#s 111-115 using the Lower Row Stomps. You've also stated that the Expression Pedals work, which means that AT is receiving MIDI, in which case, if you CAN"T LEARN the BYPASS settings, but the Expression pedals work, and you tested the Pedals in U_CC as described above, then space aliens are interfering with your life.

2) In U_CC, UPLOAD what's in the FCB to U_CC (the square with the UP ARROW), SAVE it with YOUR NAME and attach it to your reply so I can look at it.


Re: FCB1010 first steps w/UnO chip and total desesperation

Antonio Díaz
 

ossandust and EJ SHELDON, I really appreciate your help, but the FCB still does not work with Amplitube 5 via S1. I have tried creating a MIDI/instrument track, not using that track, etc. Nothing. 

Besides, when trying again to make S1 learn MIDI controls, nothing works with bank 18. It's not that a want to user tuner and those things (to be honest, I just would like to bypass pedals and use exp pedals). I'm just commenting it in case it could be related with this issue.

Sadly, this seems just impossible to make it work. I guess there must be something really simple that I'm missing out, but I just can't locate it.
Nov 


Re: FCB1010 first steps w/UnO chip and total desesperation

EJ SHELDON
 

I see that Ossandust explained the Bank thing.
So S1 works like all the other DAWs when using 3rd Party VSTs. Good to know.
Anyhow, glad it's finally working for you!

Thanks for the beer offer, but if you'd like to do something nice, make a donation to a Children's Hospital or something like that.
A better cause than free beer!

Rock On!


Re: FCB1010 first steps w/UnO chip and total desesperation

Antonio Díaz
 

I did not know anything about it! I will try. BTW, here goes the picture I mentioned but that I did not send.


Re: FCB1010 first steps w/UnO chip and total desesperation

ossandust
 

On Wed, Nov 3, 2021 at 06:42 PM, Antonio Díaz wrote:
just can't get the FCB to go to Bank 18 (just 00-09 and 01.-09., with a full stop symbol after the number)
That's just how the bank number was displayed in the old UnO v.1.0.2 firmware : 00-09 for the first 10 banks and 00.-08. for the next 9 banks. 
There used to be a transpose function in that firmware, which used the 2 left side digits of the display to show the current transpose setting (-12 -> +12). That's why the right side digit and dot were used to show the bank number. From v.1.0.3 on the transpose functionality was removed and all digits were used to show the bank number in a more regular way (00-18)  


Re: FCB1010 first steps w/UnO chip and total desesperation

Antonio Díaz
 

Hi again, dude:

It seems to me that there must be another initial issue, since, althought creating a blank device and using LEARN option has done the trick, I, as I told you earlier, just can't get the FCB to go to Bank 18 (just 00-09 and 01.-09., with a full stop symbol after the number). So I just can configure 1-5 buttons and both expression pedals.

Beside this strange issue, as I can see, native S1 plugins are the only one where you can see an option to point their different parameters to the MIDI device. You told me S1 demo does not allow third party plugins, so this info is, of course, not accesible to you. That said, you do have to create that instrument/MIDI track I mentioned to use MIDI devices with other plugins. It was something I have been doing with my MIDI keyboard for a long time with many VST effects.


So the current state of my ordeal is this: I suspect there ir some basic mistake on my side because there is no visible way to active Banks 11 and above and the FCB still does not work with Amplitube 5 via S1 despite the DAW recognizes the device and has learnt the stompbox buttons and the exp pedals. Moreover, when I load a Amplitube 5 preset previously edited in Standalone mode (a preset that works just great in Standalone mode), it seems that the info it contains is recognized in S1 (in the attached picture, you can see that if I try to use the Learn option, Amplitube just don't seem to need it, since it knows the CC it should work).


Man, I don't know if you are the creator of the chip or the EPROM, but I would really like to show you my sincere gratitude by buying you a couple of beers (PayPal maybe?). A huge thanks!!!!

De: main@fcb1010.groups.io <main@fcb1010.groups.io> en nombre de EJ SHELDON <bluesrock13@...>
Enviado: lunes, 1 de noviembre de 2021 20:29
Para: main@fcb1010.groups.io <main@fcb1010.groups.io>
Asunto: Re: [fcb1010] FCB1010 first steps w/UnO chip and total desesperation
 
Create your External Device as a Control Surface. That'll give you a blank device and a LEARN button.
Press each of the Stomp pedals consecutively, then operate each Exp Pedal, then go to Bank 18 and press pedals 8 (for the Tuner) 9 (Preset Prev) and 10 (Preset Next). This will add controllers to the Control Surface.

The reason there's no track for the FCB is because S1 uses a different method. Instead of using a MIDI track to receive the messages, then pointing the Output of that track at the VST on an Audio track (Cakewalk) or the track with whatever VST (Reaper, LIVE!), the Control Surface receives the MIDI messages. You then press/operate the FCB pedal which activates the related Control Surface knob/switch, and do whatever in the VST starts the assign process. With the native S1 plugins that means to right-click the plugin UI control you want to assign and select "Assign "X" (control name) to ControlY on FCB" (name you assigned to the Control Surface when you created it) as in my screenshot.

The question when doing this with Amplitube will be - do you operate the FCB pedal BEFORE you select the UI control (as with the S1 plugin) and LEARN or do you do the reverse as would be normal with any of the other DAWs?

You'll have to try both. Let me know what works. If I liked S1 at all, I'd buy it to try, but giving me a crippled "DEMO" was strike one.

41 - 60 of 29161