Bc2000 (for the BCF2000 & BCR2000) group photo

Yahoo Groups archive

Bc2000 (for the BCF2000 & BCR2000)

Index last updated: 2026-04-28 23:16 UTC

Thread

Resolution, How to use it.

Resolution, How to use it.

2008-04-02 by themaker4

I've been using My self-made editors for the BCR2000 for a while now and it kicks ass 
(will post them as soon as I fixed te following problem) though 1 thing seems to be wrong 
with every one of them. The encoders don't seem to snap to a certain value. So some 
encoders will output : 31 32 31 32 31etc value when set to value 31.

I posted this problem here before and learned that this is most likely something wrong 
with the resolution settings. I tried different resolution settings but no luck.(I use BC-
convert on OSX) The problem is that I don't really know how to use the resolution 
parameters besides that the 4 values apply to 4 different turning speeds...

I wonder:

Do they have to "fit" the number of steps an encoder has?

So for instance if an encoder can only have 5 values (eg "val 0 4") do I have to adjust the 
resolution a certain way so that it can no longer jump between 3 and 4?

I now use the same resolution settings (eg. .resolution 24 48 56 96) for all encoders 
though some encoders have different ranges than others. so This might be the problem..?

Please Advise....

Cheers

The Maker

Re: Resolution, How to use it.

2008-04-03 by rpcfender

The Maker

> I've been using My self-made editors for the BCR2000 for a while now
and it kicks ass
> (will post them as soon as I fixed te following problem) though 1
thing seems to be wrong
> with every one of them. The encoders don't seem to snap to a certain
value. So some
> encoders will output : 31 32 31 32 31etc value when set to value 31.
>
> I posted this problem here before and learned that this is most likely
something wrong
> with the resolution settings. I tried different resolution settings
but no luck.(I use BC-
> convert on OSX) The problem is that I don't really know how to use the
resolution
> parameters besides that the 4 values apply to 4 different turning
speeds...
>
> I wonder:
>
> Do they have to "fit" the number of steps an encoder has?
>

To get the single steps you need to turn the encoder slowly.

The encoders seem to have a resolution of 96. That is the default value
for .resoution
This is the greatest number of values per turn you can have without
loosing a midi value

$B0 12 23
$B0 12 24
$B0 12 25
$B0 12 26
$B0 12 27
etc

Any smaller you have to turn the encoder farther to get a new value, but
if you turn it slowly you will get each value.
The smaller the number the harder it is to skip a value even if you turn
it faster.

Larger numbers  (eg .resolution 120) and you start to skip values even
if you are turning slowly.
$B0 12 23
$B0 12 24
$B0 12 26
$B0 12 27
$B0 12 29
etc

.resolution 192   (2 x 96) will skip every second value if you turn it
slowly
$B0 12 23
$B0 12 25
$B0 12 27
$B0 12 29
$B0 12 31
etc

> So for instance if an encoder can only have 5 values (eg "val 0 4") do
I have to adjust the
> resolution a certain way so that it can no longer jump between 3 and
4?

if you have .minmax 0 4 perhaps you would be better of with an
incrementing button

.button 1
.showvalue on
.easypar CC 01  12 4 0 increment 1   ;note that the min and max are
reversed for the increment

$B0 12 1
$B0 12 2
$B0 12 3
$B0 12 4
$B0 12 0
$B0 12 1
$B0 12 2
$B0 12 3
etc

>
> I now use the same resolution settings (eg. .resolution 24 48 56 96)
for all encoders
> though some encoders have different ranges than others. so This might
be the problem..?

if your range is greater than 96 then you will drop value or two .

If the range is 0 127 I like to set the values to something like

.resolution  32 64 96 300

The 300 means a quick flick to the 127 or the 0 value then slowly for
fine adjustments

Too low a value means you turn the thing and nothing happens for ages,
but perhaps this is what you want.

Just try a whole lot of values to see what you like.

By the way
.resolution 56
is the same as
.resolution 56 56 56 56

All the best

Royce

Re: Resolution, How to use it.-----Still Skipping values

2008-04-15 by themaker4

Thanks again Royce, I've messed around with the settings a bit, but still I get the skipping 
values. I think my BCR is just malfunctioning. Even when I load the "only Controllers" 
preset from the behringer site I get the skipping values...... Anyone else encountered this 
problem? thinking of getting a new one!

The Maker


--- In bc2000@yahoogroups.com, "rpcfender" <rpcfender@...> wrote:
Show quoted textHide quoted text
>
> The Maker
> 
> > I've been using My self-made editors for the BCR2000 for a while now
> and it kicks ass
> > (will post them as soon as I fixed te following problem) though 1
> thing seems to be wrong
> > with every one of them. The encoders don't seem to snap to a certain
> value. So some
> > encoders will output : 31 32 31 32 31etc value when set to value 31.
> >
> > I posted this problem here before and learned that this is most likely
> something wrong
> > with the resolution settings. I tried different resolution settings
> but no luck.(I use BC-
> > convert on OSX) The problem is that I don't really know how to use the
> resolution
> > parameters besides that the 4 values apply to 4 different turning
> speeds...
> >
> > I wonder:
> >
> > Do they have to "fit" the number of steps an encoder has?
> >
> 
> To get the single steps you need to turn the encoder slowly.
> 
> The encoders seem to have a resolution of 96. That is the default value
> for .resoution
> This is the greatest number of values per turn you can have without
> loosing a midi value
> 
> $B0 12 23
> $B0 12 24
> $B0 12 25
> $B0 12 26
> $B0 12 27
> etc
> 
> Any smaller you have to turn the encoder farther to get a new value, but
> if you turn it slowly you will get each value.
> The smaller the number the harder it is to skip a value even if you turn
> it faster.
> 
> Larger numbers  (eg .resolution 120) and you start to skip values even
> if you are turning slowly.
> $B0 12 23
> $B0 12 24
> $B0 12 26
> $B0 12 27
> $B0 12 29
> etc
> 
> .resolution 192   (2 x 96) will skip every second value if you turn it
> slowly
> $B0 12 23
> $B0 12 25
> $B0 12 27
> $B0 12 29
> $B0 12 31
> etc
> 
> > So for instance if an encoder can only have 5 values (eg "val 0 4") do
> I have to adjust the
> > resolution a certain way so that it can no longer jump between 3 and
> 4?
> 
> if you have .minmax 0 4 perhaps you would be better of with an
> incrementing button
> 
> .button 1
> .showvalue on
> .easypar CC 01  12 4 0 increment 1   ;note that the min and max are
> reversed for the increment
> 
> $B0 12 1
> $B0 12 2
> $B0 12 3
> $B0 12 4
> $B0 12 0
> $B0 12 1
> $B0 12 2
> $B0 12 3
> etc
> 
> >
> > I now use the same resolution settings (eg. .resolution 24 48 56 96)
> for all encoders
> > though some encoders have different ranges than others. so This might
> be the problem..?
> 
> if your range is greater than 96 then you will drop value or two .
> 
> If the range is 0 127 I like to set the values to something like
> 
> .resolution  32 64 96 300
> 
> The 300 means a quick flick to the 127 or the 0 value then slowly for
> fine adjustments
> 
> Too low a value means you turn the thing and nothing happens for ages,
> but perhaps this is what you want.
> 
> Just try a whole lot of values to see what you like.
> 
> By the way
> .resolution 56
> is the same as
> .resolution 56 56 56 56
> 
> All the best
> 
> Royce
>

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.