--- In bc2000@yahoogroups.com, "hubert_langlois" <hubert_langlois@...>
wrote:
>
> --- In bc2000@yahoogroups.com, "rpcfender" <rpcfender@> wrote:
> >
> > Hi Hubert
> > > It might help if you post your .tx also.
> >
> > Are you using an editor?
> > Normally it is better if you can post some of the script that isn't
> > working
> >
> > > > I've made a template for my Alesis Micron with the original
> Behringer
> > > > (crap) editor. This worked. Next I've adapted this template in
> > > > BCRManager and experimented a bit with the resolution controls.
> Since
> > > > then I've encountered some problems with the resolution i.e.
the bcr
> > > > tends to skip values which translates in hearable stepping. This
> also
> > > > happens with parameters I only changed the name, nothing else.
Even
> > > > lower resolutions (e.g. 96), lower then previous settings are
giving
> > > > this problem. I did check the documentation and experimented with
> > > > ifferent values. Someone knows a way to solve this? The format
> for the
> > > > Micron is 14-bit NRPN.
> >
> > You might like to try resolutions that are related to the default 96
> > ie 96 / 2 = 48
> > The encoders appear to have a physical resolution of 96.
> > This is 3.75 degrees between values which can be a bit hard to
control.
> >
> > If you are editing using the script try
> > .resolution 48 ; which is the same as .resolution 48 48 48 48
> >
> > Setting it at 48 means you have to turn twice as far to get to the
> > next value (7.5 degrees). You could try 24 or 12 or 6 etc
> >
> > Let me know how you get on.
> > There are quite a few posts on this subject that you might like to
> > look through.
> >
> > All the best
> >
> > Royce
> >
>
>
> Thanks everyone for your answers. I haven't been able to work any
> further on this issue until recently; my apologies for the late
> feedback. Last few days I did some extensive testing with Midi-Ox to
> see where exactly the problem was and what the exact Midi output was.
> It seems that the problem is global for the BCR2000 and not only
> concerning NRPN parameters.
>
> > The encoders appear to have a physical resolution of 96.
> > This is 3.75 degrees between values which can be a bit hard to
control.
>
> If I interpret this well, this means that regardless how fast or how
> slow a knob is twisted (when .resolution 96 and range 0-96, mode:
> absolute) I should monitor 96 Midi messages in Midi-Ox. So I set up a
> CC message , put the .resolution 96 and noticed that Midi-Ox was only
> receiving +-6-10 Midi messages when turning the knob quite fast, when
> turning at a slower rate it still didn't give me the full 96
> resolution. Repeated tests in new templates showed the same result. I
> tried all kind of setups, downgraded the OS, upgraded again, different
> knobs etc...
> Strange is that I remember not to have these issues when using the BCR
> out of the box. They seem to have appeared after experimenting with
> the resolution.
>
> > It might help if you post your .tx also.
>
> By which you mean .txt? How can I attach such a file to my post (or
> should I upload it to the files section?)
>
> Kind regards,
> Hubert
>
Hi,
Basically, I'd like to know if the above mentioned problem is normal.
If so I can continue to work on the problem or look for a workaround.
If not, I fear it goes straight into the garbage bin (no more warranty).
Thanks,
Hubert
