Bc2000 (for the BCF2000 & BCR2000)

How can I get a 14 bit midi fader/knob resolution for the BCF2000 midi-controller? Especialy for Image-Lines "FL Studio" or the Arturia Synths.

I try to explain my problem, I hope you can understand my english:

Theoretically, like some said, it's possible to have smooth 14 bit resolution for the endless encoders and faders.
At least with Arturia Moog Modular 14-bit midi controlling with BCF2000 is possible, like some people in Arturia forum wrote. (I asked the question there too, but didn't get a helping answer until now.)

With BC-Manager, I changed the knob values to 16383 and tried to have 14-bit absolute or relative value changing, but it doesn't work with "Fruityloops" or Arturias "MoogModularV".

For exsample: after changing the settings of BCF's encoders to 14 bit and set "Value 2" to 16383, in  Moog Modulars standalone-mode, knob-tweaking of filtersweeps are still 7-bit rough.
I know there is a NRPN-Checkbox in MoogModularV and when I press learn on the software, BCF's knob is registered.
Then, I see in the BC display continous value changes like "...5083, 5084, 5085,..." and so on, till 16383, but I always hear just every 127 steps a frequency change and this change sounds still 7-bit-like.
I have to turnaround the BCF-encoder now many times more, but the precision and sonic result is the same like 7-Bit. 

When I put the mouse-cursor above a knob of Moog Modular, like "cutoff", on MMV a small window appears, where the acutall frequenzy-value is listet and refreshed during tweaking. So, when I turn the encoder, the values change in fine resoluted 16383 steps on BC display, but on the small Moog window, the frequency-value changes in a rough way, only every 127 steps - and you hear a value-jump. While BC dsiplay counts exactly every 16383 step, the Moog-window just shows 363.78Hz and after 127 steps it jumps noticable to a value of 426.77Hz, for example.

Someone in Arturia Forum suggested, I should use not high vlaues like 16383, instead test it with 512 or 1024. So, I changed the settings for my test-encoder to:

----------------------------------------

$rev F1 ; Firmware 1.10; BC Manager 2.1.2
$preset
  .name 'test_jf (all controlls) '
  .snapshot off
  .request off
  .egroups 4
  .fkeys on
  .lock off
  .init
$encoder 1
  .easypar NRPN 1 1 0 512 absolute/14
  .showvalue on
  .mode 12dot
  .resolution 96 96 96 96
  .default 0

...

-----------------------------------------

The result is: after many turnarounds of the BC-encoder, MMV's filter knob turns still very slowly till it reaches a value of 32.60 Hz and when BCF's display reached a count of "512".
Changing the "Value"-setting on BCManagers "General"-page has no effect. For example a value of 64 or 16383 causes the same knob behaviour as described above.

Side question:
I use BCF in U1 USB-mode. Is it better to connect it via MIDI to the port of my emu1212m Soundcard? Does this perhaps has influence on 14 bit resolution? 

Frustrating is: when I use an encoder which is configured with normal 7-bit CC127 default-settings, MMV- or Fruityloop-knobs behave like they should: they slide from 0 to highest value, but with this damn, noticable 7-bit leveljumps. *sigh*.
Please, does anyone know a solution for a higher midi resolution to work smooth, especially in Fruityloops? 
At least an answer that I should forget it, would help me, not to waste more time in trying this...