Was the feature request accepted ?
Was the feature request submitted and accepted ?
I can only figure out how to do 7 bit in “CV > MIDI-CC” in Rack 2 [free|pro]
The MIDI CC to CV module now has an option in the right click menu for 14 bit MIDI messages.
Hey there,
today I again setup a controller for sending 14bit values to the right endpoint, but do not had success again.
The controller is the BeatStep Pro, MIDI-CAT the receiver controlling a VCO frequency. Values from 0-127 in 7-bit are more coarse than turning that freq knob by mouse.
What I did… I mapped BSP knob 1 in MIDI-CAT and assign it to the VCO, this works fine in 7-bit CC.
If I turn on 14-bit for this in MIDI-CAT, VCO freq do not change anymore. So I close VCV and open Arturia MIDI Control Center and setup knob 1 to NRPN Mode with NRPN Option and LSB 6 and MSB 38 for CC06 MIDI-CAT receiving this knob.
A MIDI monitor receiving the 14-bit values from BSP, but VCO freq do not.
It’s awkward, I don’t know how to finally configure this,
so I need to ask 
Thanks ahead!
NRPN is not the same as 14-bit MIDI, these are two different „protocols“ within the specification.
1 Like
Hey Ben,
thank you for your respond.
Isn’t NRPN the only way (modern) midi controller expand the (regular) 0-127 range?
If I setup BSP in NRPN for the endless knob, MIDI-MON receives
cc6=[0-127] cc98=6 cc99=38 in a LSB=6 MSB=38 configuration.
MIDI-CAT forward this to the VCO, but only in 7-bit mode.
MIDI assignment after mapping mode is always cc06 for this knob, regardless BSP is in CC or NRPN mode.
But if this isn’t 7/14-bit mode in BSP(and others), what I not 100 percent know,
OR/AND LSB and MSB values not calculated, I’m going a wrong way here. 
… and it’s possible.
Would be really nice one can explain the setup he/she is using on whatever controller for transmitting 14-bit subdivisions to the corresponding modules.
Thank you so much for your very nice work on so many modules, Ben!
any of the first 32 controls can be optionally paired with a control offset 32 higher to give 14-bit control.
NRPN is an extension of that, where controller 99 - NRPN Most Significant Byte (MSB) - followed by 98 - NRPN Least Significant Byte (LSB) sent as a pair specify the parameter to be changed.
Instead of using NRPN, I use the “relative” mode of the BeatStep Pro - It has 3 different modes - I don’t remember which one I used in the VCV module by Stoermelder.
I don’t have a patch handy, but here’s one I posted earlier for the Ableton Push2, that shows the use of MIDI-STEP with PILE to control CV’s
EDIT:
Some DIY 14-bit midi controller links
Hey Jens Peter,
thanks for your respond and work too.
I do setup BSP in the past and right now again to compare the “relative” mode, but this is not interpreted as 14-bit in MIDI-CAT, which I like to use.
In “Relative #1” mode BSP transmit only 3 changes, 63-65, this is displayed in BSP and in MIDI-MON, and the assigned VCO freq knob in 7-bit mapping do only “rotate” +/-1 around 64 and do not respond in MIDI-CAT 14-bit setup, the BSP mode #2 and #3 do similar.
So my understanding is we need the usual 128 CCs *128 times to become
that precise resolution… and we are done. 
But for this it is
good to know how to setup that mystic MSB/LSB (LSB/MSB?) thing.
… what the relative modes in BSP really do is something I not use so far, only testing it, but it’s the same behave in software like VSTs.
… and sorry to all involved peoples, right now I see again it’s a long way subject.
I began too with the BCR2000 configuring this without susceptible third party software translating MSB/LSB in a 0-16.384 range, with no luck or good results today.
Would be nice taking care to other “things”, do not like stumble
all the time with this.
cu
… and I would really like to have that 14-bit controller “thing”… currently it is essential to move the VCO freq knop with mouse to hear all the gradations… the mouse/usb/vcv “bus” is more sensitive than all endless controller in 7-bit.
… and I can’t use most of them extensive.
In “Relative mode”, the increment (+1) and decrement (-1) are “counted” by the PILE modules - they send out the CV - the resolution is more than midi 14 bit, step size can be set to 1E-6 for example and range -10 to 10. (you can even map the stepsize knop to another input, to be able to change it). But I’m not C++ skilled enough to tell you the exact resolution - (iec559?)
If you send the CV’s from multiple PILE modules to one CV-MAP, you have something like MIDI-CAT, but with much more configuration options for ranges, step-size, slew etc.
I’m searching a way controlling modules in VCV that do not have CV input for a particular knob, and I would like to see this way the position of the knob, here at easy for a VCO freq knob.
But your tip is very nice for CV, I do have to realize whats possible with that.
Thanks.
Oooh, will experiment now with this… sounds very interesting.
NRPN thing is still a mystery…
That works awesome, can’t belive!
Thank you for that hint and work!
… NRPN is now far away for VCV.
Hey,
fully fixed in the past to this NRPNthing, somedays bring in “relative mode”, but finally stay there.
This module(s), and way beyond that, so useful…
It’s not only much more expensive do that all in hardware, but even software modules somehow like this are so good at least to combine.
Really like, stoerte’…(thank you, Ben:) … this will occupy some time 
(currently its hard to realize a long time static module setup with differently precisions so a VCO freq could comfortably be route to endless controller)
But now this will possible, only the way isn’t present right now…
EDIT: Would like some, 2 or 4(?) presets for STEP in PILE one can decide easily to change precision… but this does not belong in this topic.
@Jens.Peter.Nielsen, are you still wanting to do get CV output as CCs in 14-bit mode? I had the same need and couldn’t find another solution, so I just coded it up. Rack is now working (excellently) with the high-res mode on my Intellijel Midi 1U/CVx pair.
Yes, I would like to have that - I have pcb’s to build a few MI Yarns, (I don’t know if they have 14-bit control - if not, the FW is opensource.) they use different 16 bit DAC’s(DAC8564) compared to the Intellijel Midi 1U/CVx (LTC2609 in the Midi1U) - but should be good enough to output 14-bit resolution CV.
As to the jitter, the LSB is sent always, the MSB is only sent on change. The preferred order is MSB/LSB. The MSB message can buffer the control value such that the terminal LSB triggers a MSBCache*128+LSB assignment. The MSB changing without the LSB changing is statistically less likely than any other combination. I’m not sure if I would go as far as implementation of dither for delta-sigma dynamic range extension based on a controller timed byte emission.
EDIT: if the emission nyquist is not high enough, the “noise” would perhaps muddy the sound. It maybe advantageous to say emit a percent of the unchanging MSB bytes, as the initialization state of what is in the MSBCache needs to be sent within a reasonable performance start interval, and in some sense be immune to frame errors on reception. All Notes Off/Program Change would be ideal MSB sync points if perfect transmission was assumed.
It really was just a data rate thing. Come to think of it, having the individual bits of program change would be “good” boolean CV signals.
EDIT2: perhaps 7 inputs and 7 outputs for x->a, y->b, z->c, etc. splitting the program change message VCA style.
Thanks for this clear explanation! Alain