For the OT the Amp volume. I use the Oktakontrol for the OT and have not used the Faderfox for the OT. For the synths I control CC07. Unfortunately, you cannot map whatever you like. Not everything is mappable via MIDI. I don’t think that the MIDI controller makes a difference there.
OT track level = cc 07
OT amp vol = cc 25
If you have a mappable midi controller you can make it do either…
2 Likes
Hi @faderfox, hi guys,
I think @Olaf_Wolkenhauer already give the answer but my midi known is not good and i has to be sure,
I have some question before buying the Faderfox MX12, i have Analog rytm, Analog four, DSI Tetra.
I juste need 4 faders for the rytm so,
Is it possible to map 4 faders for each 3 devices midi out ( like volume for A4 *4 , AR * 4, TETR4 * 4) and assign the top row of encoder for each device too without any conflict?
If yes, imagine all my volume faders on the MX12 are at 100 and my current project ‘‘in the boxes’’ volume are at 100 too;
if i change project and the volume ‘‘in the boxes’’ of the new project are set to 75;
Does the volume jump to the new parameter when project change, or does the fader jump when i move it?
so if i fade the fader down from 100 to 99, the volume in the box jump directly from 75 to 99?
Thanks you guys !
Thats what happens to me with OT using the Oktakontrol… Im trying to find a work around but cant find it in the manual.
On the access virus there are a few modes for knob behaviour and one of them allows you to turn the knob and nothing happens until you reach the current set value.
So in your example nothing would happen to volume until you came down from 100 to 75 then it would affect the volume.
Why encoders are so good.
Be interesting to see if faderfox worked differently.
Ok so for my elektron machines it will jump directly from 75 (in the box) to 99 if my fader was at 100 and i down it a little. It’s not an issue because when i change project on elektron boxes, i have just to reset all fader to 0 before launching clips or before a live set prapare every volume etc.
With oktacontrol your volume jump directly or you have to move the fader ?
My tetr4 as the jump / change after reach beahviour so im glad to know it will work on the MX12 faders !
And could i map 3 different machine on the device , no limitation i will be able too pass midi info trough the THRU and without conflict ? because of the 2 midi outs vs 3 machines ?
you can control 3 devices with MX12 but note to have different midi channels for each device to avoid any conflicts.
the problem with value jumps can be solved when the devices send feedback data by changing projects.
for ELEKTRONs this works afaik only with OT. not sure how the tetra works.
so you would have these jumps after changing projects on A4 and RYTM.
a little help is to use the fader mute function on MX12 to move the faders near to the new value (holding shift and move fader).
I hope the ELEKTRON guys will implement this feature (feedback data by project change) in the A4 and RYTM too like on the OT. then you can use the snap function on MX12.
or something like the snap/relative function on ACCESS VIRUS would be a good solution too.
with motorfaders and encoders you would have the same problem because they also need feedback data and encoder relative mode isn’t supported by the ELEKTRONs 
so the main issue is on device side and not on controller side
3 Likes
Ok thank you for the answer!
I really like the simple style of your products, simple and straight to the point. Full support
Thanks
1 Like
I have to move the fader. Then it jumps to value of controller position.
My work around is to save my parts with all the volumes down. Then when I change kits/patterns I have all the faders down (end of previous kit jam).
A quick reload part on OT and Im ready to jam the next pattern. On Rytm (and pehaps A4) there is an option to reload kit upon change or something like that that would make this workaround work well for you with faderfox I recon.
Just save kit with all volumes at zero, end your previous jam with faders all down, switch kit, then fade up as you wish 
2 Likes
Yes this would rock if elektron could implement it. Id love the elektrons to ignore cc value until it hit the current position to avoid these jumps.
Your “fader mute” function is nice 
Please explain this feature.
interestingly the Nord Lead 4 has no “Knob Value Pickup” function, although the Nord Lead 2 very surely offered this valuable midi option. Quite a simple yet vital option imho.
snap function on MX12 and PC12 works like you would expect:
you must catch the current value by moving the pot before the pot sends data out again.
2 Likes
this makes sense after changing setups on the device or you get feedback data from the external machines by moving the knobs there
1 Like
Will “snap function” or “know value pickup” work with Waldorf pulse 2? The manual (page 41 and 42) claims that CC and Sysex are sent. https://waldorfmusic.com/downloads/pulse2_downloads/pulse2_manual.pdf
Or will there be jumps?
not sure if the waldorf pulse 2 send out all parameters by CCs after changing presets.
that would be necessary to avoid value jumps.
I recommend to check it out with a midi monitor.
pay attention that MX12 & PC12 works NOT with sysex parameter dumps
So does OT do this as default but not the other Elektrons (AR, A4)?
Must be a lot of data getting sent at once when you change part(im assuming part).
1 Like
on OT you can request a CC dump by a special CC command.
I haven’t checked but I can read it in the manual.
maybe other users have any experiences on this.
3 Likes
Nice one…Hopefully other elektrons follow suit. Im quite interested in faderfox down the line for AR once I’ve got few other boxes first…Defo looks the best controller for AR.
Happy with the oktakontrol for OT now that I’ve modded it to work with Track levels and not Amp level but fader fox on AR would be a good friend.
Hi,
I can confirm that neither Waldorf Pulse 2, nor DSI Evolver desktop, send a complete CC dumb when presets are changed. Hence, the only way forward would be if sysex was implemented.
How probable is it that you implement Sysex? Your controller would be the ultimate complement of the desktop synths I believe. I would then create “synth label papers” to put over the nobs . 
I think about sysex but currently I haven’t the time to implement it…hope to get it next year…