Bc2000 (for the BCF2000 & BCR2000)

> First .tx string no result, will reinitialize after a little while of
> turning the knob.

dash it all !

> Second .tx string causes sysex err and keyboard reinitialize
immediately.
So we are both wrong

> Judging by the midiquest dump i posted in the sysex section, from
> midiquest, filter cutoff #1 has a 13 where yours has a twelve.

I noticed that too but
pp 12 -
Page 12 Filter #1
Page 13 Filter #2
Both the Page and Slot start at 0 so there isn't that sort of problem.
I have had to make quite a few "adjustments" to MidiQuest over the years
to get it to work.

Have you checked  that the VFX  is set to channel 1 (or 0 if they work
that way) for the global Midi channel or Sysex Global channel or
whatever it is called?

> I tired to do this with the second .tx string. Which btw matches the
> dump from midiquest, however, crash.

>
> Hmmmm... my sysex knowledge is not so good, yet.
We all seem to be learning.

Can you get the VFX to output parameter sysex?

I see that there is a VFX - SD and a VFX-SD II in MidiQuest. What model
is yours?

Can you get your Editor to work on any parameter on the VFX?
(what is it and what is the sysex string in MidiOx?)
If you can, try to modify the .tx line and see if you can control the
VFX from the BCR.

Royce