Bc2000 (for the BCF2000 & BCR2000)

Hi Steve.

Maybe it is time to start lobbying them so that they develop this
device further. I guess there are enough people here to pressure
Behringer.

There are also lots of people who could "counter-advertise" the
product. And I am fairly sure Behringer would not like it.

I got one of the first prototypes of the BCF2000 in April 2004 and
got "in love" with the concept as soon as I got it. After that, I
have been in touch with the PR managers (Torsten Notzke and David
Lim) and dev department. At the time, they were listening to us and
were very "commercial" . But, about 18 months ago, a new PR manager
arrived and since then, they stopped talking to me, probably tired
of my questions pertaining the further dev of the device. I wrote
two huge reviews of the product for big French websites (in
September 2004 and in August 2005) and became some sort of BCF2000
guru among the community in France (wrote lots of tutorials, tips
and tricks, modified the BCFViewer... ), and...before I knew it, I
had become a "prescriptor" (sorry, I don't know if the term exists
in english. It means that through what I did, the sales increased
dramatically) . So much so that I was offered a free BCF 2000 by
Behringer when the final release was available.

But, now that the product is a hit (and it is) and the BCFs have
been flying off the shelves, they don't give a toss anymore about
what users would like. When I see how Frontier Designs developed
their Alphatrack and TranZport software, I keep thinking that the
BCF 2000 could be even better than what it currently is.

I guess if all this mailing list pressures Behringer, we may get
some responses. They don't know this mailing list. The first thing
would be to let them know it and ask them to participate. It would
be positive for them as well as for users. If they don't want to,
then it means that they don't give a s**t about their customers once
they have given their money.

Cheers.
Jérôme.
http://www.espace- cubase.org

--- In bc2000@yahoogroups. com, Steve Meiers wrote:
>
> I suspect that the development department is only a few people and
that they contract out a lot of the work. Behringer almost never
revisits their code, with the exception of the FCB1010, but even
then, very reluctantly. I own a Behringer FCB1010, BCF2000, DDX3216
and some others. All have minimal response to user suggestions for
improvement.
>
> With the FCB, there is a great Yahoo group with a few programmers
who actually made some great improvements, as in this group, too.
It's only because of these folks that I haven't given up on
Behringer products entirely and the fact that the bang-for-the- buck
is usually unbeatable, despite product support shortcomings - and
an optimism that I can somehow make it work for my needs. But the
learning curve for some of these products is very intense. I'm not a
programmer either, but I am an electronics technician and a
technical writer. I document network appliances for specialized
internet servers and think that I can read and understand technical
information, but I would like to see LOT more application examples
for these products.
>
> But it is extremely obvious that these products could be SO MUCH
MORE than Behringer allows if only a little more software support
were forthcoming from the manufacturer and the interfaced device and
software - which should be in everyone's interest.
>
> The DDX for example is such a killer mixer, and if Behringer would
only devote a programmer to interfacing it (and the BCx2000 line as
well) to recording software, they would be the obvious choice for
anyone getting started in DAW or MIDI control. What a waste of good
products on a lack of simple software interfacing. They don't even
need to write tons of code, simple make better interfaces from
existing products. The software companies should be cooperating with
Behringer too, but apparently Behringer isn't lobbying them to do
so.
>
> I could rag on this one for hours.
>
> Steve M
>
> Some of these companies have amazingly short sighted business
plans and activities.