Hey People,

for my live setup - we are using a macbook anyway so its ok to have PD running - i am routing the Behringer FCB1010 Footpedal to various things. I was following the mailinglist on the FCP1010 for a while but these custom eproms people there are using still looked kind of unflexible to me - not to speak about the internal programming feature of the foot pedal, which is a (complicated) joke.

So i decided to make a PD patch which can route:

• Signals to multiple Midi-Outs
• Expression Pedals to any Parameter
• Use footswitches as either on-off toggles, one-shot trigger or patch changer

i left the FCB1010 in default programm, sending its output exclusively to PD, transforming the data to which i want to and then use internal Midi Routing via IAC (on the mac) to send it to software or routing it to other midi out, a Line6 Pocketpod in my case.

Its my first patch so it is kind of horrible probably (but working for my purpose), so i wanted to ask for suggestions what i could optimize.

maybe if some of you can spare a minute to check it out, that would be great.

btw. i receive midi with my M-audio FW410 from the FCB1010, sending it to Live internally and Line6 Pocketpod connected via USB.

ciao,
t

http://www.pdpatchrepo.info/hurleur/fcb1010_puredata.pd

i use the fcb1010 for my pd live stuff aswell and i totally love it. i've got the modded eprom version and for editing i use the java editor, which you can sure find somewhere on the web. it makes programming the pedal way easier and gives you a better idea of the capabilities of it. for uploading my settings i use sysex librarian.

your patch looks pretty simple and straight forward. not much to optimize there as far as i can tell.

Hi
I have a similar patch, but a bit bigger.
A quick cut&paste out a part where you can see the way I did things.

I dont have a fcb1010 or a Mac, so maybe you have tweek a bit.

Is that Behringer FCB1010 able to send Note on/off (with hacked EPROM) ?

http://www.pdpatchrepo.info/hurleur/floorboard.zip

thanks for sharing the idea with state saving.

I tried to get into that to make a more modular version of my FCB1010 Floorboard patch but i am kind of lost with the [param] external. I am not sure if it is a limitation of the external itself or if i am doing something wrong. i was thinking it might be a good idea to make abstractions for the devices i have, defining their "tweakable" parameters as [param] files and load them into my patch.

The problem is, [param] neither allows namespaces, nor subdirectories for storing the data... it saves the stuff in the same directory as the root patch, naming them after the root patch. which does not work for me. imagine you define 5 external midi devices with all the parameters, all the files all called the same etc.

so my question: are there other options for state saving / routing / restoring, which might be more suited to this specific task, which means, either subdirectories for parameter saving, or definable names for the saved states etc?

Here is an example of how i would define one of the tweakable parameters for the Line6 PocketPod, each one in one File, so this could be "pp_params_001.param"

/PocketPodParameters_Name symbol Tweak;
/PocketPodParameters_MidiCC float 1;
/PocketPodParameters_ParamLimitHi float 127;
/PocketPodParameters_ParamLimitLo float 0;
/PocketPodParameters_Notes symbol 0=Blend/Blend, 1=Split/ Blend, 2=Blend/Split, 3=Split/Split;

I think with the [save.me] abstraction this is not possible, haven't checked out SSSAD - or what else might be worth looking at for what i want to do?

cheers,
t.

Since I changed from [param] to [save.me.mmb] I had no more crashes with statesaveing stuff. I dont know if I used it the wrong way or if [param] had a bug.
And in your case I would say: [save.me.mmb] can do that.
I also gave SSAD a try, but I liked mmb stuff better.

and thats the way I use it

http://www.pdpatchrepo.info/hurleur/statesaving.zip

Excellent, thank you so much.

What i am imagining is a modular midi patching setup, where people can provide their own device abstractions and connect them with the input devices of their choice. Obviously this needs some transforming modules as well, i.e. CC routing from one midi channel to another, midi note conversion, macro player would be nice...

also if i look at my behringer fx2000 it seems kind of complicated to construct a gui, as sometimes CC values control a hz parameter (i.e. for auto panning) sometimes a ms value (reverb) sometimes ON/OFF Parameters etc.

might be a good learning project at least, even if it is only to find out that it is too complicated to achieve.