OK, so I´ll leave the faders send 7bit Pitchbend data and smooth out level jumps within cubase, no problem...
Cheers,
Emre
Am 07.01.11 15:34 schrieb "Mark" unter :
--- In bc2000@yahoogroups.com , Emre Tanner <tanner-music@...> wrote:
> The faders send pitchbend data but in BC Manager I can set the range only
> from 1-127.
BC Manager merely follows the capabilities of the BCF in this respect.
> So I put out a text file of the preset and changed the faders
> parameters:
>
> I deleted the "easypar" part and put in
> .minmax 0 16383
> .tx $E0 val0.6 val7.13 (for first fader)
Another side-note: I'm not sure why you would resort to manually editing text files if you're already using BC Manager: in BC Manager you can make these settings via the fader dialog box's "Custom output" tab.
> Well, this way cubase indeed responds to fader movements with much better
> resolution, BUT the BCF2000´s faders doesn´t catch up with movements within
> cubase, so it´s a oneway communication.
> Any help to overcome this problem is much appreciated!
As far as I know, this problem cannot be overcome: a "custom output" definition (".tx") never responds to incoming MIDI data; only "standard output" definitions (".easypar") do.
It IS possible to use BOTH a standard and a custom definition for the same fader/encoder/button, but I can't see how this would help in this case, in particular since the respective ranges (0-127 and 0-16383) don't match.
Mark.