Faderfox UC4

[BR393]

Anyone using one of these (http://www.faderfox.de/uc4.html) in 14-bit mode with U-He synths? If so, how's it working out?

[Howard]

Me too. Anybody?

[bhinton]

I just got one. Will report back as soon as I have time to work with it.

Note that the faders, as with the UC3, can be set to output 14-bit messages but the resolution is 7. Encoders, though, can be either. (I've been searching for a reasonable box with 14-bit faders - real OSC - and internal soft takeover forever. )

[BR393]

I just got one. Will report back as soon as I have time to work with it.

Note that the faders, as with the UC3, can be set to output 14-bit messages but the resolution is 7. Encoders, though, can be either. (I've been searching for a reasonable box with 14-bit faders - real OSC - and internal soft takeover forever. )

Great! Would love to hear you experience. Been on the fence about getting one of these for a while.

14-bit faders would be great, but I'm guessing probably not that useful on the UC4 given that they're pretty short.

[Howard]

...the faders ... can be set to output 14-bit messages but the resolution is 7.

I didn't understand that. If the resolutions is 7, that would mean they can't be set to output 14-bit.

[pdxindy]

...the faders ... can be set to output 14-bit messages but the resolution is 7.

I didn't understand that. If the resolutions is 7, that would mean they can't be set to output 14-bit.

128 discrete steps in 14 bit format is how I read that...

[BR393]

...the faders ... can be set to output 14-bit messages but the resolution is 7.

I didn't understand that. If the resolutions is 7, that would mean they can't be set to output 14-bit.

128 discrete steps in 14 bit format is how I read that...

The manual states the faders can be set to send CC, pitch bend, program change, or aftertouch messages. I guess the faders must only have 7-bit resolution even when set to pitch bend. I know I've read elsewhere that only the encoders on the UC4 have a 14-bit resolution mode. The encoders have two selectable 14-bit modes, either pitch bend or MSB/LSB using two CCs.

[2020]

...the faders ... can be set to output 14-bit messages but the resolution is 7.

I didn't understand that. If the resolutions is 7, that would mean they can't be set to output 14-bit.

What pdxindy said. If the 7 bit value is used as the MSB value padded with a LSB value of zero, you get the whole 14-bit range but divided in 128 steps.

It's a wierd thing to do though, but maybe it was done for gear compatibility reasons.

[BR393]

Went ahead and ordered a UC4, and just got it in today. I've been testing things out and unfortunately it doesn't seem that DIVA or Bazille work with the UC4 in 14-bit mode when they're set to receive a "Continuous14bit" control. The assigned control will only respond to one of the CCs being sent by the controller.

As a workaround I also tried using two individual 7-bit CC assignments with one CC set to "normal" and the other CC set to "fine". This somewhat works, but isn't a great solution because the "fine" setting doesn't move a parameter the full range left between the "normal" values.

Ableton Live does however recognize the UC4's 14-bit mode. So, it's possible to get full 14-bit control by exposing a parameter to automation, and then making the midi assignment within Live.

[hyperscientist]

I've been testing things out and unfortunately it doesn't seem that DIVA or Bazille work with the UC4 in 14-bit mode when they're set to receive a "Continuous14bit" control.

That sounds like a bug! @Urs, could you chime in?

[tasmaniandevil]

There is a way to make this work.
14bit controllers need two controller numbers to work, one for the MSB and one for the LSB. The controller number for the LSB needs to be the number of the MSB +32. You will of course physically move only one controller, the MSB. When you turn this CC, it will send its data on both CCs simultaneously to achieve the 14 bit resolution.
And if I remember it correctly, only the first 64 CCs can currently be used as 14bit controllers (32 for the MSB and 32 for the LSB).
When you assign a 14bit controller via the integrated MIDI learn feature of e.g. Diva or Bazille, it will currently only recognize the first controller. You will have to add the second controller manually in the MIDI table page of the plugin preferences (which you can reach by clicking the cogwheel, usually at the right side of the plugin).
For example, if you are assigning CC 21 as 14bit controller, go to the MIDI table page and add another controller to the same parameter, using the same channel, but with CC number 53 (21+32). The settings for mode would usually be 'normal' for both CCs, and they both have to be set to 'continuous 14bit' type.
Then it should work. I don't have a Faderfox, but that is the way you can get it to work with other 14 bit controllers.

u-he_14bitCC.png

[uselessmind]

There is a way to make this work.
14bit controllers need two controller numbers to work, one for the MSB and one for the LSB. The controller number for the LSB needs to be the number of the MSB +32. You will of course physically move only one controller, the MSB. When you turn this CC, it will send its data on both CCs simultaneously to achieve the 14 bit resolution.
And if I remember it correctly, only the first 64 CCs can currently be used as 14bit controllers (32 for the MSB and 32 for the LSB).
When you assign a 14bit controller via the integrated MIDI learn feature of e.g. Diva or Bazille, it will currently only recognize the first controller. You will have to add the second controller manually in the MIDI table page of the plugin preferences (which you can reach by clicking the cogwheel, usually at the right side of the plugin).
For example, if you are assigning CC 21 as 14bit controller, go to the MIDI table page and add another controller to the same parameter, using the same channel, but with CC number 53 (21+32). The settings for mode would usually be 'normal' for both CCs, and they both have to be set to 'continuous 14bit' type.
Then it should work. I don't have a Faderfox, but that is the way you can get it to work with other 14 bit controllers.

u-he_14bitCC.png

Since now midi learn seems to recognize the 14bit Combos, how does this currently work with regards to Modulation sources like Modwheel or Breath as there is no option to tell the plugin to use MSB + LSB ?
Is there a good way to test if Modwheel is indeed recognized as 14 Bit by the plugin?

[tasmaniandevil]

Since now midi learn seems to recognize the 14bit Combos, how does this currently work with regards to Modulation sources like Modwheel or Breath as there is no option to tell the plugin to use MSB + LSB ?
Is there a good way to test if Modwheel is indeed recognized as 14 Bit by the plugin?

If you have a 14bit MIDI controller, and use our MIDI learn system, current versions of our plugins will detect this and automatically assign MSB and LSB.
You can see this on the MIDI table page, for instance when using Modwheel, the controller will then display 01+33, and the type will display Continuous14bit.
If this is displayed, then it's reacting to the 14bit resolution of your controller.
Otherwise it would display Continuous7bit in the type field.

[uselessmind]

Since now midi learn seems to recognize the 14bit Combos, how does this currently work with regards to Modulation sources like Modwheel or Breath as there is no option to tell the plugin to use MSB + LSB ?
Is there a good way to test if Modwheel is indeed recognized as 14 Bit by the plugin?

If you have a 14bit MIDI controller, and use our MIDI learn system, current versions of our plugins will detect this and automatically assign MSB and LSB.
You can see this on the MIDI table page, for instance when using Modwheel, the controller will then display 01+33, and the type will display Continuous14bit.
If this is displayed, then it's reacting to the 14bit resolution of your controller.
Otherwise it would display Continuous7bit in the type field.

Thanks for your answer, yes i known this part and it works just fine.
My question was about the predefined modulation sources like in the lower bar in Hive such ModWheel , Breath or what i can set ControlA and ControlB to be.
Since they are not part of the midi learn system how can i tell the difference there?

[tasmaniandevil]

Ah, sorry, misunderstood the question.
Mod Wheel, Breath, or the Ctrl A/B modulation sources will work with 7bit resolution if used as mod source.