@robert - I don’t know if you are still looking for an answer to your question from March 2024, or if it has already been answered above, perhaps by @jtode , anyway, here’s a link-pointer that may help:
The FCB1010 user manual in English:
on page 7 you’ll find 2.3 Quick start guide for PRESET programming which includes:
For each of the 100 PRESETS you can determine which MIDI functions shall be transmitted as soon as you select the respective PRESET. For instance, you can send five different program change commands, two controller commands, two different controller values (using the expression pedals) and a Note On command to the connected equipment at the same time (menu structure as in fig. 2.4). It is up to you to determine, which commands are stored in a Preset. Do as follows to program the functions to be sent with each PRESET:
I made some improvements to single pedal mode in testing (vangelis).
Debounce to handle noisy pedals. (Mine is terribly bouncy!)
Fixed some erratic behaviour.
Press once and hold for longer than 1.5s will record or overdub until the pedal is released.
I am suprised someone hasn’t reported the poor behaviour of single pedal mode before. It was quite unusable when I tried it this morning. Hopefully I have tamed it now.
@riban has this been pushed to vangelis? I didn’t get an update…
Single pedal works fine for me, but I did find today it only works for the first two tracks.
If I add tracks 3 or 4 the pedal will only work for 1 and 2. The soft buttons work for all tracks, so to record beyond track 2 I need to use the soft button.
I have added a controller to the “Global levels” page that will load a wav file into loop 1. This is really handy if you have some prerecorded rhythm tracks that you want to play along with.
Right. That must be because of the incomplete implementation of whether or not to follow selected loop in midi binding.
Probably what happened is you bound your pedal when follow mode was off, thereby explicitly binding to loop 1 and 2. Loop 1 could also have been bound as such with the mode on.
@riban probably already had a binding of a bare single_pedal symbol from before, which ought to keep following the selected loop.
My PR hould be receiving some love this afternoon, but I already saw there is also probably a flaw in single_pedal mode when the same CC is bound to mutliple different loops at the same time, causing one loop to receive ‘single’ and the second one ‘double’.
I haven’t yet investigated whether this can be easily fixed (would be cool if it worked - adding support for grouping loops effectively).
If not, you may have to unlearn all loops with the setting OFF and then relearn once with the setting ON. Or use designated pedals for each loop.
As @niels pointed out, there is a controller on the last page called, “MIDI CC to selected loop” but this does not work for single pedal mode and he is working on a solution.
I just noticed that there is a flaw in the single pedal mode. When in paused mode, a tap should start playback but it is currently starting record. I will take a look…
This looks like the issue that @niels has identified. I may not have much time to look at this today so we may benefit from the PR…
[Edit] I found the time! (Well, something else probably sufferred…) The issue with single pedal on multiple loops should now be resolved. We still have the awkwardness that, to use the same pedal for each loop, you have to learn each loop (I thought I had solved that… but apparently not!) but it does now work as designed… I think/hope.
I’m now in the process of learning the Nektar Pacer possibilities, and i think i would get some very easy to setup and operating functionality if the prev/next button was restored. Can we have both?
I have a setup now that kinda works for shifting up and down through the loops, but i think sending ccxx 0 on one pedal and ccxx 127 on another would be the way to go with a multi pedal board?
And it would look like this:
which looks quite understanable + i mean you would not forget which pedal to push…
I can confirm that it does work as designed now - I thought it was a little weird before, but I quickly got used to it. This is better though.
I’m on to trying to master the different syncing options, they are not what I’m used to so far (I have a boss rc 500), but they do have some interesting possibilities.
I want to avoid adding more controls if we can avoid it.
Yes! If you can send CC value 0 from one switch without sending any other value, and CC value 127 from another switch without sending any other value, and can send the same CC on both pedals, then you should be able to bind them to the loop selection control in relative mode 4. One switch will nudge it down whilst the other switch will nudge it up. It is (pretty much) the same behaviour that we had on the prev/next controller.
We await your wise words in the form of some kind of tutorial on this… . The sync modes are flexible and powerful. There are two default presets, one syncs to loop 1 which is what most users will want and the other syncs to zynseq (well, effectively - it syncs to jack transport) which is handy for audio looping to a sequence. You may find that some functionality is still wanting… there is always the feature request system.
If you bold press a controller in the controlview you see the Control Options menu which allows you to change the mode of (non-toggle) MIDI bindings. “Relative Mode 4” will nudge up when a CC value > 63 is recieved and nudge down when a CC value < 64 is received.
Sounds like something odd has happened. I will have a look when I am next in the lab.
I do not get that here. If i bold press recording i get the momentary<->latch option, because i guess that would be a “toggle” midi binding. If i boldpress things like “selected loop” or “quantize” i do not get the momentary<->latch option, but i do not get to set any mode?. These would be “non toggle” midi bindings i guess?
The options i get is:
X Y touchpad:
X axis
Y axis
Midi Learn:
Chain learn…
Global learn…
Unlearn
Thanks for remembering my post. To be honest. I programmed the FCB1010 with UNO2 and wrote a program for 5 tracks.
Something like:
Button 1:
first press
select track, record,
second press: select track, overdub
third press: select track, play
And do that for all individual buttons . It worked oke, but after a Zynthian update the track selection process didn’t work as before and I decided to stop the whole project.
. The sync modes are flexible and powerful. There are two default presets, one syncs to loop 1 which is what most users will want and the other syncs to zynseq (well, effectively - it syncs to jack transport) which is handy for audio looping to a sequence. You may find that some functionality is still wanting… there is always the