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

Display programs for normal mode?

Display programs for normal mode?

2008-07-29 by schivins

Now that I got the BCF working I would like to use it in normal mode.
I tried it in MCU mode and it worked fine but seemed limited and I can
not program anything when in that mode.

So I started programming it via the Tracktion software as a custom
controller. I got all the volumes and pans working. I am having some
mute and solo issues but that is not the BCF of course. They seem to
work but I seem to have to double hit them to toggle them correctly. I
will play with it more.

Anyone use theirs like this? For any software? Any issues with doing
it this way? Any positives or negatives?


My main question I guess is; are there any display programs like the
one for MCU mode but for normal mode?

An on screen display that would change naming the tracks, when you
switch presets would be invaluable to know what you are controlling.

I also cannot get Tracktion to allow me to assign the BCF as an output
device so I cannot move a physical slider when I move it in software.
Again not the BCF's fault. I am unsure if I even need this but it
would be nice. MCU mode works fine this way.

Re: [bc2000] Display programs for normal mode?

2008-07-30 by Karl Lurman

The problem is, MCU mode passes more messages down the wire that can
be interpreted by the controller and the DAW itself. Part of these
messages include the display information, which in turn can be
interpreted by some kind of visual display (on an MCU, this
information is shown on the LCD instead of course).

When you go down the route of making your own midi bindings for the
BCF, your display program would need to understand what you are trying
to reproduce without that extra MCU information, in particular, the
display info. Infact, it would need to completely understand what very
basic midi messages mean and how they correspond with the
software/hardware you are trying to control (and of course it's
individual parts and components). I hope you see, thats not an easy
task.

MCU is great because it sets up a 'standard' that ensures consistent
controller assignments and messaging between controllers and
DAW/software/other hardware. This means display software can be
written (Husker du for example) knowing that things should be in a
fairly set format and with some idea of how to go about displaying
stuff.

Hope that helps?

You might want to look at setting up non-standard MCU presets provided
by users in the group. I am unsure of how much support there is for
BCF though. Some of these presets may allow for you to have MCU
emulation AND be able to assign custom control presets too.

Karl
Show quoted textHide quoted text
On Wed, Jul 30, 2008 at 6:44 AM, schivins <babylon05@...> wrote:
> Now that I got the BCF working I would like to use it in normal mode.
> I tried it in MCU mode and it worked fine but seemed limited and I can
> not program anything when in that mode.
>
> So I started programming it via the Tracktion software as a custom
> controller. I got all the volumes and pans working. I am having some
> mute and solo issues but that is not the BCF of course. They seem to
> work but I seem to have to double hit them to toggle them correctly. I
> will play with it more.
>
> Anyone use theirs like this? For any software? Any issues with doing
> it this way? Any positives or negatives?
>
> My main question I guess is; are there any display programs like the
> one for MCU mode but for normal mode?
>
> An on screen display that would change naming the tracks, when you
> switch presets would be invaluable to know what you are controlling.
>
> I also cannot get Tracktion to allow me to assign the BCF as an output
> device so I cannot move a physical slider when I move it in software.
> Again not the BCF's fault. I am unsure if I even need this but it
> would be nice. MCU mode works fine this way.
>
>

Re: Display programs for normal mode?

2008-07-30 by schivins

Thanks! If I can figure out how to add some extra programming while in
MCU mode, that would solve the problem!

I still have a lot to learn with this thing but I will say it is a
very nice piece of equipment, especially for the price. I want to get
another one and chain them. I hope MCU mode supports that as well :)

--- In bc2000@yahoogroups.com, "Karl Lurman" <karl.lurman@...> wrote:
Show quoted textHide quoted text
>
> The problem is, MCU mode passes more messages down the wire that can
> be interpreted by the controller and the DAW itself. Part of these
> messages include the display information, which in turn can be
> interpreted by some kind of visual display (on an MCU, this
> information is shown on the LCD instead of course).
> 
> When you go down the route of making your own midi bindings for the
> BCF, your display program would need to understand what you are trying
> to reproduce without that extra MCU information, in particular, the
> display info. Infact, it would need to completely understand what very
> basic midi messages mean and how they correspond with the
> software/hardware you are trying to control (and of course it's
> individual parts and components). I hope you see, thats not an easy
> task.
> 
> MCU is great because it sets up a 'standard' that ensures consistent
> controller assignments and messaging between controllers and
> DAW/software/other hardware. This means display software can be
> written (Husker du for example) knowing that things should be in a
> fairly set format and with some idea of how to go about displaying
> stuff.
> 
> Hope that helps?
> 
> You might want to look at setting up non-standard MCU presets provided
> by users in the group. I am unsure of how much support there is for
> BCF though. Some of these presets may allow for you to have MCU
> emulation AND be able to assign custom control presets too.
> 
> Karl
> 
> On Wed, Jul 30, 2008 at 6:44 AM, schivins <babylon05@...> wrote:
> > Now that I got the BCF working I would like to use it in normal mode.
> > I tried it in MCU mode and it worked fine but seemed limited and I can
> > not program anything when in that mode.
> >
> > So I started programming it via the Tracktion software as a custom
> > controller. I got all the volumes and pans working. I am having some
> > mute and solo issues but that is not the BCF of course. They seem to
> > work but I seem to have to double hit them to toggle them correctly. I
> > will play with it more.
> >
> > Anyone use theirs like this? For any software? Any issues with doing
> > it this way? Any positives or negatives?
> >
> > My main question I guess is; are there any display programs like the
> > one for MCU mode but for normal mode?
> >
> > An on screen display that would change naming the tracks, when you
> > switch presets would be invaluable to know what you are controlling.
> >
> > I also cannot get Tracktion to allow me to assign the BCF as an output
> > device so I cannot move a physical slider when I move it in software.
> > Again not the BCF's fault. I am unsure if I even need this but it
> > would be nice. MCU mode works fine this way.
> >
> >
>

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.