Faderfox UC4

Bitstream is a total pain to work with by most accounts.

Have you used one?

I wasn’t even aware of the Bitstream until now. It certainly looks like a good controller if you have a use for all the extra controls.
As for the UC4, it is completely solid and easy to program from the unit. The faders are small, but surprisingly usable.
I’ve got it set up with faders controlling track levels on my Digitakt through the MIDi port, the buttons and crossfader controlling a couple of loopers in Ableton and the encoders controlling a few plugins via the USB connection.
It’s always worked perfectly.


Mine arrives Monday!

No but researched it very heavily a few years ago as it seems a super powerful dream controller. The programming sounded like more work than I was prepared to take on.

I would be interested if any OS came out to improve this aspect.

Received mine for chrismas (self gift :grin:), and I’m a bit disappointed by the quality. It’s my first Faderfox controller, and for 275e at least I expect an english quick start guide and not a german-only sheet. The plastic feels cheap, and the feeling of encoders/faders does not feels great, so a bit bummed for the price.
Still, there’s not much choice for compact controllers with knobs and faders that can be programmed without a computer, so I’ll probably forget these flaws once I’ll start playing with it and my M8.


Something that really bothers me: is there a way to make the knob change the value faster, besides the acceleration curves? I would like the knobs to be more reactive, but acceleration is hit and miss and I lose all precision with it. I would like to keep the linear response, just a faster one.

Is that possible?

I don’t think so, I believe that there’s only acceleration or the standard “no acceleration” speed per encoder.

One thing is that you may set it to work on a much finer scale if using CCAh mode, but that’s the opposite of what you’re asking for. Are you sure you’re not accidentally using that? Most likely not. Here’s what the manual has to say about it. “CCAh: Two control change commands (MSB/LSB) in 14 bit highres mode (values 0 to 16383).” That is 16383 discrete values, as opposed to 128, so it takes a lot longer to “sweep” through.

Given that you are not using the encoder in CCAh mode and the acceleration is disabled; another way to proceed then would be to perhaps set a more narrow window/range for an encoder turn to address. It may feel more responsive in practice that way, but it requires a lot of fine tuning, potentially making it a somewhat finicky process. I believe you’d have to do that on the receiving devices and (set a min and max) to feel the difference.

Edit: Or do I have that backwards? Now I’m thinking that setting a smaller range would make it feel less fast (but more precise). I would just need to try it… I can’t wrap my head around it right now! :joy:

I’ve heard this elsewhere and, yeah, the encoders are a bit “sandy”. Once I got used to them I didn’t mind them at all, though. They are very consistent, and their acceleration is really handy for working with 14-bit values. As far as the “cheap” plastic, I just thought it was kind of ugly at first, but it’s pretty rugged for plastic. I expect it to age much better than, say, the Nanokontrol (which, to be fair, is at a much different price point).


I had my friend over for a jam and they picked up the UC4 and told me that they think it has the aesthetic and feeling of a 1980’s car stereo head unit with an 8 band equalizer. I kind of looked perplexed for a moment as I flashed back to the late 80’s and recalled an upgraded car audio system in my life which certainly did resemble the UC4. Black plastic with a similar finish, similar knob caps, a basic display, silkscreened text and some green accents.

Passionately loving this controller; I defended its build quality and honor! I agreed that it maybe has a simple kind of utilitarian look, but it works so nicely and is by no means flimsy at all.

My only issue with the UC4 would be that it serves as my only set of faders in the studio - and they’re really short ones. For most of my purposes; they’re not the best for controlling gain.

Otherwise I’m still super impressed by UC4 overall. I can’t deny that it feels extremely solid in practice. The form factor is a dream. The encoders break in and start to feel easier to turn after some time. I also found it forgiving to program, which happens to be pretty rare for MIDI devices in general.


I love mine for controlling Ableton. Its super easy to automap to parameters with it, which is awesome.

I need to try it for more stuff. Octatrack, bluebox…I have a bunch of things I could probably plug this thing into. Its such a cool little controller.

1 Like

Button to CC mapping is nice for the Octatrack for discrete parameter values, as in the Freeze Delay control mode. This is more useful than a continuous range of values for parameters based on rhythm or pitch. For example, you can set all 8 to control retrigger time, where button 1 is 8 steps, button 2 is 6 steps, button 3 is 4 steps, etc.


Hey, Im trying to send transport, clock and midi notes from logic > through my UC4 to my > octatrack, do you mind advising as to how to do this?

Thanks in advance.


1 Like

Liam Killen just made a video about the lack of easy documentation about controlling the Octatrack… Im curious what you come up with.

Le dot.

That should be easy enough to set up.
On the UC4, go to setup mode and select routing “ROU1” using encoder 2.
This will pass any midi received from the USB through to the MIDI DIN output merged with any MIDI from the UC4 faders, encoders etc.
It will save automatically when you exit setup mode.
I can’t help you with the specifics of Logic, but it should be set to send MIDI, clock etc through the faderfox usb interface.
The Octatrack should then be set to receive MIDI, clock, transport through it’s MIDI port.
Hope that helps.

1 Like

Thanks for getting back to me, I worked out the routing in the end, was easy enough once I find the routing set up in the manual.


1 Like