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: Is there any way to (one more question)...?

2008-11-06 by islandgroove2002

Hi Mark,

first of all when a BC first starts up it has initial values that all 
snap to the position they were saved as part of the preset. I am 
wondering if it is possible to set each preset so that it has no 
initial value when the preset is first initialized so that for 
example the faders on the BCF would not jump to a position when the 
device was turned on.

Second, and this is the one that is causing me the most grief, when a 
knob, button or fader is adjusted and then you switch to another 
preset, the values that were last changed in the previous preset are 
saved so that when the preset is selected again the values jump to 
how they were last set.

The problem with that for me is that I may select a conflicting 
snapshot of values to be transmit while using a different preset and 
then when I go back to the preset, it snaps to the last adjusted 
values milliseconds before I send it a burst of entirely different 
values from my computer so sometimes there is a conflict between the 
values stored at preset change and the values sent from the computer.
This is really hard to explain clearly, but the point is that I do 
not want the BC's to remember anything beyond the CC assignments 
stored in each preset so that when I move a bunch of faders and knobs 
in one preset switch to another preset, move a bunch of faders and 
knobs again and then move back to the previous preset the BC doesn't 
recall my previous adjustments so that there will be no conflict with 
the CC values that are instantly sent from the computer to the BC 
each time I change a preset.

To sum it up, software I am running on my computer is already doing 
the job of remembering what was changed in the last preset so I don't 
need the BC's doing that also.
The reason I am doing this is because I have assembled a "feedback 
battery" within Plogue Bidule with a plugin called midiCCreset that 
continuously updates the visual feedback on the BC's across multiple 
presets/midi channels, even when I trigger entire banks of value 
changes across multiple midi channels worth of mappings within my 
host. 

--- In bc2000@yahoogroups.com, "Mark van den Berg" <markwinvdb@...> 
wrote:
>
> --- In bc2000@yahoogroups.com, "islandgroove2002"
> <islandgroove2002@> wrote:
> > I guess ideally my BCR/F presets would contain no initial or 
default 
> > values, nor would they store or recall any changed values for the 
> > previously accessed presets since powering on.
> > In other words, to have completely dumb presets that only 
contained 
> > controller assignments and whatever current values were sent from 
my 
> > computer.
> 
> I'm still not quite sure whether I FULLY understand what you want, 
and
> it would be pointless if I started producing lengthy ruminations 
about
> irrelevant things, so could you give a step-by-step example showing
> EXACTLY what the undesired behavior is?
> 
> Mark.
>

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.