Bc2000 (for the BCF2000 & BCR2000) group photo

Yahoo Groups archive

Bc2000 (for the BCF2000 & BCR2000)

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

Message

RE: [bc2000] Programming BCR for the Dave Smith Evolver Desktop

2011-07-21 by Greg Long

Not only do I have a preset for the Tetra on the BCR2000 but I am working on
software that loads the data from the current patch into the BCR2000 so you
can see the patch.

Right now only layer A is populated with data but is makes a big difference
to see the patch before editing it from the BCR. 

 

All of the buttons and encoders are setup to use NRPN's to control the
Tetras parameters.

 

 

 

From: bc2000@yahoogroups.com [mailto:bc2000@yahoogroups.com] On Behalf Of
longstrongturtle
Sent: Wednesday, July 20, 2011 9:22 PM
To: bc2000@yahoogroups.com
Subject: [bc2000] Programming BCR for the Dave Smith Evolver Desktop

 

  

Hey Folks, I downloaded the templates for the Evolver Desktop off this site
and it seems like the templates use System Exclusive messages to change
settings on the Evolver Desktop. All of the knobs in these templates go from
0-127 which doesn't make sense considering a lot of the parameters on the
Evolver have different ranges, for example one parameter has a range of
0-200 on the Evolver and some have a range of 1-4.

I have an Evolver with the version 3.0 operating system which allows you to
use MIDI Continuous Controller mapping, the previous versions only used
System Exclusive messages which is what the presets on here were written
for. Now what I am wondering is if I programmed a preset for the BCR-2000
using CC mapping instead of SysEx, would the LEDS move to their relative
positions when I change presets on the Evolver Desktop? Currently, when
changing patches on the Evolver Desktop, the knobs remain where they are on
the BCR even if I have the midi out from the Evolver Desktop going into the
midi-in on the BCR-200. That is what i'm most confused about and couldn't
find a clear answer about. Thanks!

Attachments

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.