If you're an FCB1010 owner who hasn't invested in the alternate ROMs, you'll be wanting this.
PD-FCB1010_usage.mp4
FCB1010.pd

It's a patch that uses the Note feature to break out stomp and release on each pedal into two separate Bangs for each switch, and captures the exp datas. From there, you can do anything you like with the inputs.

Inspired by my disgust that they shipped this product with firmware that cannot act as a piano sustain pedal out of the box. I had no idea that such a monumentally absurd decision could be made, even by the likes of Behringer. Now it's fixed.

Everything is hardcoded, so unless you go in and change the patch yourself, you will need setup a complete bank of ten switches with exp pedals enabled on CC7 and CC27 and the Notes for switches 1-10 as 34,36,38,40,42,41,43,45,47,49, everything sending on Channel 16.

Since PureData can do everything the board can and so much more, that could be your very last riverdance.

Thank you for the reply! Yes, I was very very confused and I figured out that problem last night. It was Message boxes I needed, that was all. It boils down to this, which is going to become ten subpatches that select for different notes, which I have programmed into my FCB1010's footswitches. I am reeeeeeally loving PD now. I didn't understand the limitations of this controller when I bought it, and I have been resentful of it for the ensuing couple of years. I knew I could do it this way, but I was waiting until I could afford the UNO rom, but I mean, this is way cheaper, and I can integrate it into my Zynthian, which is with me always. :>

edit: you'll notice, I also figured out that I could put the channel right in the notein object, so that saved me a lot of extra spaghetti and reduced it to a two-body problem, as the physicists might say.

Fastest version: I have a bunch of bangs filtered out from a notein - it filters for channel and note, and has four bangs, three bang on Velocity 0 and a different three bang for Velocity 100, which is the only numbers it will ever get. I want to turn this into a little "black box" that outputs a bang for 100 and a bang for 0, only when the channel/note are correct.

I cannot seem to get the "spigot" objects to let the resultant bangs through, I was trying to stack two of them one test for channel and note and then they approve the passing through of the 0 and 100 values into the "out bangs" and it's because I am a rank newb at PureData, but I am determined to solve this problem with pd (I also know Python, and could also solve this with a Teensy I have at hand with traditional C++ code), because once I get through this early pain I will have a swiss army knife for further work in audio and midi specifically, and I have a lot of stuff I need to do just to handly my own personal needs. I play guitar, keys, other strings, and need to call up fairly complex sets of things for the work I need to do coming up.

What this is for: I have a Behringer FCB1010. Absolute tank of a midi control pedal. It has ten stomp switches and two exp pedals, and this is enough for all of my needs,
but the built-in functionality of this device is absolutely goofy, in that while you can send NoteOn and NoteOff of your choice with each of the ten pedals, what you cannot do, is send CCvalueX when you stomp, and CCvalueY when you release.

In other words, out of the box, this bank of midi pedals cannot act as your piano/keyboard sustain pedal. Supreme fail, on a certain level, but easily solved with pd, I think. The reason is that it was marketed to guitar players as a means of setting all their midi-controllable gear with a single stomp, so you can send up five different CCs when you stomp, but the only thing it sends to indicate you lifted your foot, is the noteOff.

There is an alternate ROM one can get, but it costs 70euro before shipping and we are not rich. I am certain that once I am clear on how to filter for "all three bangs are banging" I will be able to have PD send forward whatever I want, notes, chords (big plans here, as you might imagine), CC changes, for each of the ten pedals. I have beaten my head against this probably very simple problem for a while now, I started watching a PD course this morning on youtube and I believe he will get to the knowledge I need, but he's kinda roundabout and talking a lot about audio, which I have zero need for in this application, this is strictly to get the midi I need out of those built-like-a-tank pedals. Once I've got it sorted I will probably pack in a Raspberry Pi, but this laptop will probably always be with me too, the versatility is part of why I'm definitely using PD and not something else.

You automatically ask the AI when you google these days, of course, and I have ceased to resist reading it, but even the AI seems confused by my wording. I just need to build ten of these little "black boxes" that I can use to build and send what I really want. I have previously watched every one of Miller Puckette's original videos and I guess I should just go find those again... I hate starting out sometimes, I have trouble with patience. Especially when sooooo much of the training material out there is focused on wild-eyes synths and all that I'm just a guy playing a LOT of instruments in a band.

Thanks for reading, not a single word of this was AI generated.

Hey folks, new PD user. I have just set out to creating the filter described in the subject line, and I'm curious before I go too far whether this has already been created.

My use case is, I am a longtime guitar/vox who has more recently learned keys, and I would like to integrate my sustain pedal (CC64) into one of the switches on my FCB-1010 rather than have another device on the floor/dangling wire.

Long story short on the FCB-1010 is, the only option for Sustain Pedal type functionality, where it notifies the midi out that I have raised my foot, is by sending a NoteOn/NoteOff on a specific channel. It's actually an incredibly frustrating device and I plan to get the Uno upgrade put in as soon as I have spare cash, but in the meantime, this seems like a job for puredata. I own a Zynthian, which runs PureData and provides my Piano sounds, so in theory this would just monitor channel 16 for one specific note, and send out 127 or 0 to CC64 to its output (I believe that PD's output will be available on the chain I place it in, but I haven't sorted that out yet...) on that specific note only.

I'm wondering, this being such a simple filter, if maybe I shouldn't have a go at writing an LV2 filter instead, but in the meantime, has anyone already implemented this filter? Is there a Midi Filter Collection page somewhere round here that I could browse?

I feel a bit out of place when I look at many of the tutorials, cause while I am a gadgethead and I do appreciate synths, I don't tend to use any generative stuff like arpeggiators and whatnot, though I'm trying to wrap my head around the loopers and sequencers Zynthian implements, now that I'm invested in a platform. But I guess I'm not an "electronic" musician, is my point I guess. Using midi came hard and with a lot of pain. :>