Date   

Re: FS. New in box fcb1010 #for_sale

Roger Colwell
 

Bearing in mind this group has an international membership, John, please tell us your location and whether you'd prefer to set any shipping limits for your FCB1010? From your email address, it seems you're most likely located in PA, USA?
--
Roger Colwell
FCB1010 Group Owner/Moderator


FS. New in box fcb1010 #for_sale

John L. Dunne
 

Cleaning out a my studio storage and find a as new sealed box unit / no damage no marks. Was a back up to a long ago project and forgotten . Pristine condition w original unit inside 

make offer 


Re: UnO2 Trigger CC with Up/Down Buttons // Relay

David Grosz
 

Alexis

Sorry I didn't understand your question and did not think it was possible to assign the updown switches as
11 and 12.  I have I believe chip #12 and my chip does not do this function but it does work if I paste your
setup into the online editor but it does not in mine.  I guess I am out of touch to the advancements and changes
of the current chip vs the one I have so this is good stuff and maybe I need an upgrade

Dave

On Sunday, April 2, 2023 at 04:09:08 AM PDT, alexis@... <alexis@...> wrote:


Hi everyone,

since there was no reply on my original post in the Ono2 Subgroup yet, I'd like to share my requirements and the script I worked on here in the main group in hope to get some feedback and improvement advices for the code. 

Requirements:

  1. Only one bank
  2. An individual CC command per foot pedal every time one of the 12 (!) foot pedals is pressed.
  3. So: Up/down pedals same function as the other 1-10 `normal` pedals
  4. Exception: Pedal 4: When pressed, open relay 1 for a really short time (not toggle)
  5. General: Only Channel 16 used (CC01-CC14)
  6. Every Pedal in `trigger mode’ so that the lights only lighten up when pressing (not toggle).
  7. Express-Pedal: Channel 16 CC 13 resp. CC 14; 0-127 no matter what preset I’m in.  

Code:

// Defining the 12 triggers:

 

TRIGGERS =

{

1 _Git_1

2 _Git_2

3_Bass

4 _Trigger_CV

5_Play_all

6_Tas1

7_Tas2

8_Tas3

9_Rol_Midi

10_delete

11_up

12_down

}

 

// Up/down pedals same function as the other 1-10 `normal` pedals:

 

NO_UPDOWN_SWITCHES

 

// Defining the one and only bank „Looper“:

 

BANKS  = 

{
Looper : 1 _Git_1 | 2 _Git_2 | 3_Bass | 4 _Trigger_CV | 5_Play_all | 6_Tas1 | 7_Tas2 | 8_Tas3 | 9_Rol_Midi | 10_delete | 11_up | 12_down

}

CHANNEL Looper = 16

 

// Defining the Pedals (generic naming because of yada yada)

 

INIT_FCB = 
{

Pedal 1 = Pedal_1

Pedal 2 = Pedal_2

 

// Defining what the triggers do:

TRIGGER_CLICK  1_Git_1 = SendMidi Looper CtrlChange 1 127 

TRIGGER_CLICK  2 _Git_2 = SendMidi Looper CtrlChange 2 127 

TRIGGER_CLICK  3_Bass = SendMidi Looper CtrlChange 3 127 

TRIGGER_CLICK  4 _Trigger_CV = Open  Relay1

TRIGGER_CLICK  5_Play_all = SendMidi Looper CtrlChange 5 127 

TRIGGER_CLICK  6_Tas1 = SendMidi Looper CtrlChange 6 127 

TRIGGER_CLICK  7_Tas2 = SendMidi Looper CtrlChange 7 127 

TRIGGER_CLICK  8_Tas3 = SendMidi Looper CtrlChange 8 127 

TRIGGER_CLICK  9_Rol_Midi = SendMidi Looper CtrlChange 9 127 

TRIGGER_CLICK  10_delete = SendMidi Looper CtrlChange 10 127 

TRIGGER_CLICK  11_up = SendMidi Looper CtrlChange 11 127 

TRIGGER_CLICK  12_down = SendMidi Looper CtrlChange 12 127 

 

// Defining what the pedals do:

 

SWEEP Pedal_1 = SendMidi Looper CtrlChange 13 0-127

SWEEP Pedal_2 = SendMidi Looper CtrlChange 14 0-127

I would be very happy if someone could review and give some feedback for the code. 

Cheers
Alexis


Re: UnO2 Trigger CC with Up/Down Buttons // Relay

alexis@...
 

Hi Ossandust,

great, thanks for your reply! I was a little worried if I got everything figured out right, especially the syntax. 

Also thanks for the hint regarding the Relay. I will check that out. 

I couldn’t try it yet as the eeprom is only being shipped. I‘ll let you know my results as soon as I received it. 

cheers 


Re: UnO2 Trigger CC with Up/Down Buttons // Relay

ossandust
 

Hi Alexis,

your setup is as easy as it can get - 1 message per switch, it should work without problem, did you try it? 
"open relay 1 for a really short time (not toggle)" -> for that you would need to do something like 
Open Relay1
Wait 1
Close Relay1

(I would rather expect it to be the other way around, briefly closing the relay instead of opening it - but you'll probably need to test it out to know for sure)


Re: UnO2 Trigger CC with Up/Down Buttons // Relay

alexis@...
 

Hi Dave,

Thanks for your reply! I’m not quite sure if I get your point but to make things clear, I am planning to use the fcb for remote controlling a system for live looping in a DAW Software called Ableton Live. This is done by CC Messages. I just need 12 controls to tell the DAW what buttons to push (record/play for different Instruments, delete, go to next row, go to previous row). 

As I tried to point out in my requirements I don’t want to change to any other bank at all. There’s just the initial one I’m in. I only need the fcb to send CCs.

Cheers
Alexis

 


Re: UnO2 Trigger CC with Up/Down Buttons // Relay

David Grosz
 

Alexis

not quite sure why using the up down switches when you simply change to another bank but have you considered
using the toe and or heel virtual switches on each expression pedal to get your extra switches?

I use my FCB1010 UnO2 for controlling my Axe-Fx rack and it really works well with everything in groups of 10.  For me
I have 1 Bank that can send PC 001-768
2nd Bank controls the 8 Scenes and tuner and tap tempo on other 2 switches and the 3rd Bank I use for the Looper
control of the Axe-Fx.  Bank 4 can be set up for Stomp box mode of effects if needed.  I have also setup a Bank 5 which
I can assign the Expression pedals in pairs of because the Axe-Fx has 8 External Controller pedal slots,  So that means
I can use all eight of the available slots easily and once you assign a pedal it stays that way until you change it so that
rounds out how I use it

The biggest downfall I have had was the lack of knowing whats happening because of the lack of a display (wished I got the
TinyBos instead) but its easy to think of things in groups of 10's.  People have asked this question in the past and I do not
believe it can be done and not sure why you would want to because if you could then you have just limited yourself to only
having 12 switches because you could not change banks if you assigned them to something else but changing between banks
is easy and one extra button press.

The attached image is of one preset I have for using my big rack and UnO2 chipped FCB1010  does it with out issue cjanging multiple
midi effects on individual midi channels.  I know of no other pedal capable of doing this and the MFC-101 midi controller from Fractal
is said to be capable but I haven't been able to make it happen.

You can easily make the changes your looking to do if you set them up on 2 banks so its not that difficult you just think in groups of
ten and bank up to bank 2 then bank back down to 1

Good Luck
Dave

On Sunday, April 2, 2023 at 04:09:08 AM PDT, alexis@... <alexis@...> wrote:


Hi everyone,

since there was no reply on my original post in the Ono2 Subgroup yet, I'd like to share my requirements and the script I worked on here in the main group in hope to get some feedback and improvement advices for the code. 

Requirements:

  1. Only one bank
  2. An individual CC command per foot pedal every time one of the 12 (!) foot pedals is pressed.
  3. So: Up/down pedals same function as the other 1-10 `normal` pedals
  4. Exception: Pedal 4: When pressed, open relay 1 for a really short time (not toggle)
  5. General: Only Channel 16 used (CC01-CC14)
  6. Every Pedal in `trigger mode’ so that the lights only lighten up when pressing (not toggle).
  7. Express-Pedal: Channel 16 CC 13 resp. CC 14; 0-127 no matter what preset I’m in.  

Code:

// Defining the 12 triggers:

 

TRIGGERS =

{

1 _Git_1

2 _Git_2

3_Bass

4 _Trigger_CV

5_Play_all

6_Tas1

7_Tas2

8_Tas3

9_Rol_Midi

10_delete

11_up

12_down

}

 

// Up/down pedals same function as the other 1-10 `normal` pedals:

 

NO_UPDOWN_SWITCHES

 

// Defining the one and only bank „Looper“:

 

BANKS  = 

{
Looper : 1 _Git_1 | 2 _Git_2 | 3_Bass | 4 _Trigger_CV | 5_Play_all | 6_Tas1 | 7_Tas2 | 8_Tas3 | 9_Rol_Midi | 10_delete | 11_up | 12_down

}

CHANNEL Looper = 16

 

// Defining the Pedals (generic naming because of yada yada)

 

INIT_FCB = 
{

Pedal 1 = Pedal_1

Pedal 2 = Pedal_2

 

// Defining what the triggers do:

TRIGGER_CLICK  1_Git_1 = SendMidi Looper CtrlChange 1 127 

TRIGGER_CLICK  2 _Git_2 = SendMidi Looper CtrlChange 2 127 

TRIGGER_CLICK  3_Bass = SendMidi Looper CtrlChange 3 127 

TRIGGER_CLICK  4 _Trigger_CV = Open  Relay1

TRIGGER_CLICK  5_Play_all = SendMidi Looper CtrlChange 5 127 

TRIGGER_CLICK  6_Tas1 = SendMidi Looper CtrlChange 6 127 

TRIGGER_CLICK  7_Tas2 = SendMidi Looper CtrlChange 7 127 

TRIGGER_CLICK  8_Tas3 = SendMidi Looper CtrlChange 8 127 

TRIGGER_CLICK  9_Rol_Midi = SendMidi Looper CtrlChange 9 127 

TRIGGER_CLICK  10_delete = SendMidi Looper CtrlChange 10 127 

TRIGGER_CLICK  11_up = SendMidi Looper CtrlChange 11 127 

TRIGGER_CLICK  12_down = SendMidi Looper CtrlChange 12 127 

 

// Defining what the pedals do:

 

SWEEP Pedal_1 = SendMidi Looper CtrlChange 13 0-127

SWEEP Pedal_2 = SendMidi Looper CtrlChange 14 0-127

I would be very happy if someone could review and give some feedback for the code. 

Cheers
Alexis


UnO2 Trigger CC with Up/Down Buttons // Relay

alexis@...
 

Hi everyone,

since there was no reply on my original post in the Ono2 Subgroup yet, I'd like to share my requirements and the script I worked on here in the main group in hope to get some feedback and improvement advices for the code. 

Requirements:

  1. Only one bank
  2. An individual CC command per foot pedal every time one of the 12 (!) foot pedals is pressed.
  3. So: Up/down pedals same function as the other 1-10 `normal` pedals
  4. Exception: Pedal 4: When pressed, open relay 1 for a really short time (not toggle)
  5. General: Only Channel 16 used (CC01-CC14)
  6. Every Pedal in `trigger mode’ so that the lights only lighten up when pressing (not toggle).
  7. Express-Pedal: Channel 16 CC 13 resp. CC 14; 0-127 no matter what preset I’m in.  

Code:

// Defining the 12 triggers:

 

TRIGGERS =

{

1 _Git_1

2 _Git_2

3_Bass

4 _Trigger_CV

5_Play_all

6_Tas1

7_Tas2

8_Tas3

9_Rol_Midi

10_delete

11_up

12_down

}

 

// Up/down pedals same function as the other 1-10 `normal` pedals:

 

NO_UPDOWN_SWITCHES

 

// Defining the one and only bank „Looper“:

 

BANKS  = 

{
Looper : 1 _Git_1 | 2 _Git_2 | 3_Bass | 4 _Trigger_CV | 5_Play_all | 6_Tas1 | 7_Tas2 | 8_Tas3 | 9_Rol_Midi | 10_delete | 11_up | 12_down

}

CHANNEL Looper = 16

 

// Defining the Pedals (generic naming because of yada yada)

 

INIT_FCB = 
{

Pedal 1 = Pedal_1

Pedal 2 = Pedal_2

 

// Defining what the triggers do:

TRIGGER_CLICK  1_Git_1 = SendMidi Looper CtrlChange 1 127 

TRIGGER_CLICK  2 _Git_2 = SendMidi Looper CtrlChange 2 127 

TRIGGER_CLICK  3_Bass = SendMidi Looper CtrlChange 3 127 

TRIGGER_CLICK  4 _Trigger_CV = Open  Relay1

TRIGGER_CLICK  5_Play_all = SendMidi Looper CtrlChange 5 127 

TRIGGER_CLICK  6_Tas1 = SendMidi Looper CtrlChange 6 127 

TRIGGER_CLICK  7_Tas2 = SendMidi Looper CtrlChange 7 127 

TRIGGER_CLICK  8_Tas3 = SendMidi Looper CtrlChange 8 127 

TRIGGER_CLICK  9_Rol_Midi = SendMidi Looper CtrlChange 9 127 

TRIGGER_CLICK  10_delete = SendMidi Looper CtrlChange 10 127 

TRIGGER_CLICK  11_up = SendMidi Looper CtrlChange 11 127 

TRIGGER_CLICK  12_down = SendMidi Looper CtrlChange 12 127 

 

// Defining what the pedals do:

 

SWEEP Pedal_1 = SendMidi Looper CtrlChange 13 0-127

SWEEP Pedal_2 = SendMidi Looper CtrlChange 14 0-127

I would be very happy if someone could review and give some feedback for the code. 

Cheers
Alexis


Re: New to the FCB1010

Jack Fenton
 

Yes, I think the TinyBox might be good.  For me, for anything that UNO2 cannot handle I use a BomeBox.


Re: New to the FCB1010

Tim Lang
 

Thanks for the info. I did open it up and have the 2.4.1b firmware chip. I ordered the latest Uno chip (1.0.4). I'm waiting to get hold of the iConnectivity mioXM Midi/USB host box that lets you interconnect MIDI DIN and MIDI USB devices and customize the routing. I want to be able to use the FCB1010 without a DAW, or at most with Ableton Live for live performance. I want to be able to trigger/start/stop multiple things per switch. I may need to upgrade to the Uno2 in order to send multiple MIDI commands per switch, but I'll start out with the Uno and see what that can do first. I'm also interested in the TinyBox, but their web store is having technical problems and won't let me order anything.

I hadn't seen anything about the Mountain Utilities software until your mention. I'll give it a try. Once I get the Uno chip, I will probably try out the FCB Uno Editor, too.

I have a Tascam US20x20 interface for my DAW and recording setup. It has MINI DIN in and out. I doubt I will be using the FCB1010 with that setup, just for live performance.

Thanks,

Tim


Re: New to the FCB1010

Pmiller057
 

Hi

With the stock FCB1010 firmware, the simplest way to set up and program the controller is to use the Mountain Utilities software. There may be a link to or a copy in the files section of this forum, otherwise your favourite search engine should find it. Note - to use this or any other setup software you will also need a USB/MIDI interface that correctly handles multi-byte Sysex messages. The really cheap USB/MIDI interfaces available online generally won't work for this - I've used a Roland UM-ONE interface successfully. The Mountain Utilities website has some notes and ideas on how to use the FCB1010 with stock firmware with an RC-600.

To change the firmware in the FCB1010, you will need to unscrew the cover and change an IC (it is in a socket) on the main PCB inside.

Peter


New to the FCB1010

Tim Lang
 

Hello,

I just acquired an FCB1010 with a stock chip v2.4.1b (July 2003) installed.

I've read a bit about the UNO and UNO2 chips and the expanded capabilities possible there.

It sounds like any firmware update means replacing one chip with another (ie. no flashing the existing chip with new firmware). 

My first question is:

What can I do with the 2.4.1b firmware chip? How extensively can the programming be customized? What are its limitations?

I will not be controlling an amp. I do want to be able to use it live to start/stop/select patterns or songs on a drum machine (haven't settled on one yet), trigger synth parts,  possibly midi-controllable effects or at least a midi-enabled loop selector on a guitar pedalboard, and integrate with a looper like the Boss RC-600. It would be great to have the ability to change settings on multiple devices to make a solo set more hands-free.

Second question:

Which firmware/chip would offer more flexible/capable programming to get closer to accomplishing my objectives?

Thanks,

Tim Lang


Re: FCB1010n not receiving syx messages

EJ SHELDON
 

???

Need more info. Specifics, please.
It's been a long time since I had the stock chip in my FCB, but it sounds like you're doing a Factory Reset, not a sysex transfer.
What chip version? What editor? What interface? What steps?


FCB1010n not receiving syx messages

Augie
 

I have done all the necessary steps, but at the end of the process, instead of counting down as it is supposed to do, it just goes to the 00 and the syx was not transmitted.


Re: Best chip for FCB1010 for controlling Mobius

harmonicabr
 

UnO v.1.0.4

PURCHASE NOW
26 €

UnO2 v.1.4

PURCHASE NOW
50 €, incl. editor

UnO4Kemper v.1.4

PURCHASE NOW
26 €

FCB-505 v.1.0

PURCHASE NOW
26 €
So, as I did read on this thread, I can use several chip options to control the rc600 with the fcb1010: 505 chip, uno02, etc. Right?

Can someone please explain me what will be the best option and why?


Re: Best chip for FCB1010 for controlling Mobius

ossandust
 

On Sun, Feb 19, 2023 at 10:59 PM, harmonicabr wrote:
what makes the uno2 so expensive?
UnO firmware + FCB/UnO ControlCenter = 50€ + 12€ shipping
UnO2 firmware + UnO2 ControlCenter = 50€ + 12€ shipping

UnOFCB/UNO CONTROL CENTER


Re: Best chip for FCB1010 for controlling Mobius

harmonicabr
 

Hi, guys. 
 
I got a fcb1010 and a rc600. Completely new to the midi controllers world, doing some research and asking for some help here. 
 
I'd like to have more assignments, using the non clickable buttons and the expression pedals from the fcb1010 to control the rc600 (even it been meant for foot control already) 
 
So, as I did read on this thread, I can use several chip options to control the rc600 with the fcb1010: 505 chip, uno02, etc. Right? 
 
Can someone please explain me what will be the best option and why?
 
And what makes the uno2 so expensive? I don't understand yet its power.
 
Thanks in advance and regards from Brazil!
 
:) 


2.99-7

TEMAIVIF
 

Hi Guys, it seems that the link to donwload Ed Dixon latest version 2.99-7 is no more reacheable.
Is there one of you gys that can send me this version?

At teh monent I'm using version 2.99-2 but has soem limitations and i would like to test version 2.999-7.

Thnaks a lot in advance.

Go


Re: Update chip from a v1.1

circlepete
 

Hi Timothy, 

If you have a stock chip (maybe v2.5?) that you don't use, I'll be happy to test it with my FCB1010. Let me know how we can organize that. 

So more updates here when I could test my device with another chip.


Re: Update chip from a v1.1

Timothy Payne
 

I have a pretty new stock v2.5 chip you can have. I bought the FCB1010 from Amazon, open box, with the stock chip and I have upgraded to the Uno 1.4 and then to the Tinybox (Love the Tinybox). I don't need the chip. The stock chip worked fine.


On Thu, Jan 19, 2023 at 11:48 AM circlepete <alexandre.stehlin@...> wrote:
Great update, thanks! I'm happy to read that, even tho it doesn't work how I hoped it would, it doesn't have any hardware issue. 

When I talked about saving, I was talking about the FCB1010 itself, not the software. Also, when I reset the device from scratch (hold toggles 1 and 6 and turn it on), it takes some much time compared to what I saw in YouTube tutorials.