Bc2000 (for the BCF2000 & BCR2000)

Mark, 
Yeah, what I meant was in the byte position.. or as you said the
nth...xx position yeah.

Great editor, Mark, you have opened up a vast expanse to edit this
beast with.
Thank you!

I tried to email you but it bounced back.
I was offering to add some graphics to the manual.
If you send me the doc,  I will do so then send back to you for approval.
I was a bit daunted by the program at first... a few images in the
manual might have helped, what say you?

Kip

--- In bc2000@yahoogroups.com, "Mark van den Berg" <markwinvdb@...> wrote:
>
> --- In bc2000@yahoogroups.com, "k5kip_1999" <k5kip_1999@> wrote:
> > Here is the .tx for filter 1 cut off, voice #1.
> > 
> >   .tx $F0 $0F $05 $00 $00 $00 $00 $01 $00 *$00* $00 $0D $00 $01
$00 $00 
> > val4.7 val0.3 $F7
> > 
> > You will notice I am not using the val statements at the blue
location, 
> > when I observe the sysex coming out of my synth i see that those
values 
> > are /always /0, so I leave them.
> 
> > I would need it to edit that "voice" value and to edit the last two 
> > before the $f7.
> > I have been using Mark's editor for major construction.  I have found 
> > that setup goes pretty quick once you get used to it.  The ability of 
> > recording the sysex output from the synth is awesome.
> > I click the record, press the button or move slider on synth and i
have 
> > a capture of the sysex string.  However, I need then to edit the
orange 
> > bits above in the string.  When they are captured they have values
like 
> > $02 in them and need to be changed to the val4.7 val0.3. 
> > That, while was ok using Mark's editor, took a while and was very
> tedious.
> > So really, there needs to be a way to search and replace for those 
> > values on all strings.
> > I can envision a streamlined process coming out here.
> > Perhaps Mark can add in some kind of hex search and replace
function to 
> > his editor?
> 
> I'm not sure about the usefulness of an actual search & replace
> function to achieve your intended substitution: wouldn't the search &
> replace function then wrongly apply to ANY value of "$02" (to use your
> example)?
> So what I'm thinking of is a feature by which you can replace the n-th 
> item in every ".tx" line in a particular scope. I'll think about it.
> 
> Mark.
>