Here's what I did and why:

So pulling up a specific preset requires using a PC#?  I don't have my gear with me today as it's at the club we're playing tonight, so I'll mess with this next week.

A picture is worth a thousand words... thanks, you have made more clear something I wasn't sussing out -- namely how to us PC#s.  Based on the picture you sent I think I've deduced a few things, but I'm not sure:

   the FCB sends the HXS certain info via PC#s  in conjunction with CC#s, but not all require the PC#? 

 

   Some functions require only CC#s?  Is there an implied PC# if you don't explicitly state 

   one (most likely the current preset)?

   Once you've sent a PC#, you don't need to send it again to work on that preset?  

   

For instance, you send PC# 1 to call HXS preset 000/ss1 on fs-1, but you're not explicitly sending the PC# on any other FCB footswitches in that bank.  

   to call up preset 000 to work on?  Or to put it another way, if I hit fs-2 instead of fs-1 

I noticed on bank 1/fs-5 you call the tap temp with a note value of 127.  

   Is this a typo or is that how it works?  

The HXS manual says that tap tempo is called with CC#64, values 64-127.

Lastly, you set the tuner on/off by sending CC#68 val=0/alt=127 on CC1.  

   What is CC2 for?  

Oddly, on the Ed Dixon and the Mark van den Berg editors, it only shows one CC# value for CNT1, not two.  I think I guessed that the alt CC# value was supposed to be sent via CC2/CNT2.  That may be why the tuner isn't working for me???  Mark van den Berg calls it CNT, Ed Dixon CC... so I thought CNT1 was the same as CC1 abd CC2/CNT2 was how you sent the alt. value.

So I did download the Mark van den Berg editor, FCB manager, from mountain utilities as well as Ed Dixons editor.    I haven't used Mark's it yet, but it appears to have the copy/paste functionality you mention.

I will eventually buy the ControlCenter software since it is so highly rated, but I don't mind doing the programming for each bank setting by setting, if need be.

FYI, the modes work as I have that functioning correctly now.  They change the screen on the HXS and reconfigure how the FS work as long as they are set properly on the HXS.

Sorry for the long messages....

First, because the UNO chip remembers which CNT (CC) was sent last, I was having trouble testing the configuration.

Between jumping between ControlCenter and Ed Dixon, and trying to get my UNO chip to act like the stock chip, I managed to confuse myself big time!

Attached is the sysex as configured with the Ed Dixon editor. Disregard the old one!

Hopefully, it will work properly with your stock chip. Try it out and let me know.

I've also attached a new ControlCenter picture, which pretty much matches the Ed Dixon configuration. Just disregard the Alt Value column. 

When I imported the Ed Dixon sysex into ControlCenter and saved it as a ControlCenter formatted .lgp file, it works fine.

If I just load the Ed Dixon sysex version onto my UNO chip, it does not. Who knows.

As to your questions:

Don't confuse CNT1 and CC with actual MIDI CC#s!

Think of PC1-PC2-PC3-PC4-PC5-CNT1-CNT2-NOTE as "variable" names.

Like in math, X=1 means that the variable X=a value of 1.

FCB Preset 01.01 (Bank 01.Preset 01) variable PC1 = value 000 calls HXS Preset 000.

                                                               variable CNT1 = CC# 069 value 000 calls snapshot 1.

To confuse the issue a little more, the CC variables are called CNT1 and CNT2 by Behringer, but they're called CC1 and CC2 in ControlCenter. Below I'm going to refer to the variable names as CNT1 and CNT2 to differentiate from the actual CC#s.

When you press button 1 in bank 01 it sends PC#000, then CC#069 with a value of 000.

The Stock FCB allows two CNT variables, each with one value.

When configured on the same CC# and  MIDI Channel, the first time you hit the button it (supposedly, according to the clear as mud Behringer manual) sends CNT1 (CC1), the second time it sends CNT2 (CC2). This is how the stock chip does CC Toggling. Hopefully, this is how it will work for you.

The UNO Chip allows two CNT variables with TWO values each. The first time you hit the button it sends the first value of CNT1 then the first value of CNT2. The next time you hit the button it sends the second values.

   "the FCB sends the HXS certain info via PC#s  in conjunction with CC#s, but not all require the PC#? 

 

   Some functions require only CC#s?  Is there an implied PC# if you don't explicitly state 

   one (most likely the current preset)?

   Once you've sent a PC#, you don't need to send it again to work on that preset?

For instance, you send PC# 1 to call HXS preset 000/ss1 on fs-1, but you're not explicitly sending the PC# on any other FCB footswitches in that bank."

That is correct. I'm only sending the PC# on button 1 because, although sending it on 2 and 3 would allow you to select your choice of snapshots on preset load, when you then changed the snapshot it would reload the preset. Every time you reload a preset it (HXS) takes a moment to reload, which can cause a momentary audio dropout, which could cause a problem if you need the snapshot change to be seamless. If you need to return to snapshot one after changing to one of the others, you COULD experience this dropout. Sorry, just the way it is. If we had another button I could dedicate it to snapshot one, but we're out of buttons! Worry about it if it becomes a problem.

   "Does this mean that once bank 1 is selected, I must press FCB fs-1 next

   to call up preset 000 to work on?  Or to put it another way, if I hit fs-2 instead of fs-1 

   after calling the FCB bank, will it only work on the currently selected HXS preset or 

   will it switch to preset 000?"

Yes. Hitting button 1 loads the preset. Until you change banks AND hit button 1 again, the other button act on the currently loaded HXS preset.

"I noticed on bank 1/fs-5 you call the tap temp with a note value of 127.  

   Is this a typo or is that how it works?  

The HXS manual says that tap tempo is called with CC#64, values 64-127."

In order to accomplish Tap Tempo using CC values of 0-127, the FCB does some weird math stuff. It's all explained in the FCB manual, in the usual clear as mud Behringer fashion. That's why I said it was an adventure figuring it out.

"Lastly, you set the tuner on/off by sending CC#68 val=0/alt=127 on CC1. What is CC2 for?"

This could be confusion caused by the first picture I sent (give me a break, it was like 2AM!). The new picture should make more sense. Ignore the ALT column. 

I don't know the Mark van der berg thing. I've heard OF it, but never heard of anyone actually using it. I'm sure you've noticed that pretty much everyone here uses ControlCenter. There's a reason for that. It's the best. Get it, you'll thank me later. Import the sysex and save it using the regular SAVE method, which (non-destructively) converts it to ControlCenter format. THEN put ControlCenter into Stock FCB Mode (it should detect the stock chip automatically, click the FCB1010 logo to see the modes) and load it onto your FCB. That should do the job.

Hopefully this LONG post is not TOO confusing. Myself, I need a drink. 

DAMN! I don't drink......

  

If you ever need to set up Tap Tempo again, simple CC#064 value 127 does the trick. Don't read the Behringer manual, it'll just confuse you the way it did me!

Sorry about the confusion. Way I see it, I learned something new, so it was worth the time.

Rd2rk,

I just wanted to get back to you since you've helped me so much...

Just a reminder, I'm the guy with the new HX Stomp and new FCB1010 (Stock Firmware Version 2.5, BTW) who has never messed with Midi till now.

Whew, I spent a long day, yesterday, configuring both the HXS and the FCB.

I bought a copy of Control Center as you suggested.  I had a small issue getting my registration key, but that has been straightened out (they use your primary paypal email address to send you the key.  Mine was incorrect!).

I did not use the sysex file you sent me, but instead, I used it as a jumping off point to start from scratch.  I've included all the files I created yesterday, in case anyone else finds them useful or instructional.

 1) The tuner is working fine.  Not sure why I couldn't get it working before, but no issues now.

 2) The tap tempo config you sent me did not work (note=127).  But, CC#64, 64&127 works just fine!

 3) Bank 0 is my ground zero (pun intended).  I could use only that bank and still play gigs with it.

 4) Banks 1-9/FS1 call HXS preset 1-9, SnapShot1 respectively, like the file you sent me.

 5) Banks 1-9 have tap tempo setup on FS9 and HXS FS1-3 emulated on FS6-8.  

 6) All banks have FS4 & 5 emulating HXS FS4 & 5.  The HXS is programmed to scroll down/up one preset on those footswitches.

 7) All banks universally have FS10 call the tuner on/off.

 8) All banks universally have FS1-3 select SnapShots 1-3.

 9) Bank 0 has the HXS mode=up scrolling function on FS6, so HXS FS1-3 emulation is shifted to FS7-9, eliminating the tap tempo on that bank.

I put a little thought into this and I reorganized the presets on my HXS so that presets 1-7 are my most used presets.  Of course I set up the HXS so that their numbers match the banks that call them so I have a reference back to the HXS display that matches up, keeping in mind that I must press FS1 after selecting the bank to actually change the HXS preset.

I'm gigging this weekend, so I'll get a chance to try this out.  I'm looking forward to the improvements.

I am having trouble with downloading/uploading the sysex files... could be my USB/Midi interface is not compatible with Control Center.  I'm using a MIO.

When I put the FCB in config mode and press sysex receive (FS7) and then try to download to it from the PC, the midi icon grays-out and the cursor spins and the indicator on the bottom right of the screen all show they are busy, but it never finishes or gives an error.  I can let it go for an hour and it never gets out of that mode.  If I press the MIDI-connection icon on the upper left, it stops.  If I repeat the process at that point, it seems to work fine!  I save the config and everything is there!

I have a different issue when I try to upload from the FCB to the PC...  that process works, but the sysex presets are all out of order and it keeps changing from "regular" mode to "direct select" mode after each attempt.

I will send an email to the Control Center folks, but I fear it has something to do with the interface I'm using.

Again, I can't thank you enough for all your help.  I see that I'm not to only one you've been helping out, either.  I owe you, big time -- thanks for making this and the other groups you participate in so helpful.  I hope someday I can return the favor!

Ryan D.

I've got so many versions of that sysex floating around, I really need to sort them out! That Tap Tempo/NOTE configuration is leftover from my attempt to get Tap Tempo working the Behringer way. Epic fail! Kudos for working it out on your own!

The Upload /Download issues should be fixable. Start by doing a factory reset on the FCB (boot holding 1+6). When you boot again into Configuration mode, set sysex Receive, then hold down the DOWN pedal till the display returns to 00 That saves the new configuration, and you shouldn't have to reset sysex receive again unless you do another factory reset. That should fix the DL problem. If it still hangs, stop the process and test the physical FCB pedals in the MIDI IN Monitor window - click Global Configuration twice, depending where you're at. It's the panel on the lower right. Click the little connector icon so it turns red, Now it'll receive from the FCB. Click it again to clear it - it's a tiny panel and the data gets hard to read. I've found that usually, when the DL hangs, it's actually done, and the data is in the FCB. It's a problem that seems to have started with one of Microsoft's wonderful mandatory updates. AARGH!

Xavier, if you're reading this......

The Upload problem was probably cured by the Factory reset. Sometimes when you make a bunch of changes, the FCB gets corrupted. Anytime it starts acting weird out of the blue, that's probably what happened Do the reset, DL your sysex again, you should be good.

I just had a look at your screenshot. You really have done well learning ControlCenter!

I found a typo in the sysex I posted and I decided to make a tweak already.  The mode control on FS6/bank0 has the wrong CC1# and value, and it does not need a CC2# (which is what the CC1# should be).  I the moved that function to FS9, thereby giving me better consistency across all the banks.

I did a factory reset and I'm still getting the same behaviour.  I've determined that you are correct -- the sysex gets to the FCB, even though the process never completes.  I also see if I don't select FS7="sysex rcv" again, the process completes without reporting an error.  It's hard to know if it's actually working since the first/hung attempt actually did complete the transfer.

I wish I had another USB/midi interface that is known to work to try...

Thanks again.

Ryan D.

I'm told that it works, many here recommend it.

In my last reply I described saving the Global Configuration using the DOWN pedal after setting Sysex Receive. You shouldn't need to re-set it unless you've done a factory reset.

Anyway, glad you've got it working. Rock On!

Yup. That's my interface.  I didn't see it listed in the database, so I wasn't sure if it is compatible or not.