ok
Paolo Piattica
You also don’t have to reverse the CC values on the sliders to use as SetBfree drawbars. Just set the CC 70-78 on the controller, and it works. No reversing, no midi learning, no workaround, no witchcraft.
This is true if your MIDI controller faders send value 0 when pulled closest to you and 127 when pushed corners away from you. If your faders are reversed, like @piattica’s hardware drawbars, then we need to reverse the behaviour. This can be done in zynthian now, or the hardware controller may have a configuration like @Baggypants said, or you can physically turn the controls around!!! 
2 Likes
That also solves a subject in another topic about lefthanded keyboards.
3 Likes
Good idea but now first drawbar acts as 1", second as 1 1/3", etc…
it is a mess 
Just turn your head upside down - sorted!
1 Like
OK, so as of version 2502, do the setBfree drawbars work in reverse? Up to now it has been straightforward to operate and use, no setup required. Someone didn’t understand this, so it had to be messed up? Should everyone else adapt, get used to it, or try to reverse their controller?
They work as they ever worked. But now you can reverse your controllers from the controller menú.
Regards
1 Like
I downloaded the latest stable image and created a new memory card. The SetBfree drawbars work in reverse by default, with the faders set to 0 at the bottom and 8 at the top, with the default MIDI CC values of 0 and 127. If I select Absolute Reverse and then Absolute Mode in the Control Options menu, this setting is only valid until the next reboot, despite the snapshot save.
They always have worked like that. We will fix the save snapshot to restore the configuration.
2 Likes
I mean, now they work the other way round compared to the way they have always worked. They used to work like organ drawbars, now they work by default like normal faders, i.e. the other way round compared to a drawbar.
I’m not aware of this change in behaviour. I will check in a few days, when i’m back to Zynthian labs.
Regards
1 Like
This is how absolute reverse mode works now. Regardless of the fader direction setting on the controller, the drawbars are unusable. F.U.B.A.R.
Could you show the clean output from your MIDI controller?
Thanks
1 Like
I just tested with latest Vangelis (testing) and Oram (staging) and i can’t see any problem. It works like a charm in my side. What software version are you using?
Anyway, the MIDI-CC learning is not processed in the ZynMidiRouter, but later, so what you are viewing in the MIDI log can’t be affected by the selection of absolute reverse, relative, etc. Indeed, you shouldn’t see CC going out the zynmidirouter the CC number is checked. By default only pedals are.
Regards,
1 Like
For years, I used SetBFree on Zynthian the way it was originally designed. The drawbar parameters worked as follows: CC value 0 → drawbar value 8, i.e., maximum volume, CC value 127 → drawbar value 0, i.e., zero volume. Fader pulled down → drawbar pulled out, fader pushed up → drawbar pushed in, as it should be. I set the MIDI CC number (70-78) for the faders on the controller, and I didn’t have to set anything else, no MIDI learning, no fader reverse, it worked like a charm. I was happy.
When this thread started, everything went wrong. This is a typical case of do not fix what isn’t broken. It was a mistake to touch it. Absolute reverse and the rest were created, and this completely confused the operation.
Now it looks like the controller input signal is fine, but the Control Feedback signal appears on MIDI channel 1, which, whatever it is, is the exact opposite of the controller input values. So after every 127 there is a 0, after 126 there is a 1, and so on, as shown in the picture. This is the case even when the fader is set as usual, and even when I reverse its operation. The effect is predictable: crackling, chaos.
When I set the same fader to a normal parameter, there is no problem with it, only with the SetBFree drawbar parameters.
Zynthian and SetBFree are set as they are after a fresh installation, so the problem is not with my device, but with the factory settings.
Hi @gilrain !
We don’t make changes without a reason. Zynthian include a lot of engines and setBfree, although a beloved one, it’s one of many that share a common infrastructure. And you can trust me when i say i really love setBfree:
Perhaps if you explain in detail your setup and use-case, we could find a solution. Just complaining is not a productive approach.
You could start by sending what i’ve requested:
If i asked for this, is for a good reason. Trust me.
And please, don’t forget to explain in detail your setup and workflow.
Thanks!
1 Like
Are you “hacking” the control feedback from setBfree? How? Why? We need the details to help you.
Thanks!
1 Like