Synth-DIY Yahoo! Groups Archives

Thread

Sysex Programming

2009-05-18 by narcissus05@gmail.com

First of all hello to everyone in the list : this is my very first post.

I am a fairly seasoned synth programmer, always trying to get more and more juice from my machines, so i generally go deep into my synths guts when it comes to programing. Ì'm not the preset-user-type of musician.

I own an Access Virus, an Ensoniq ASR10 sampler, a Yamaha A4000 sampler, a Yamaha SY77, Korg Electribe ESX, etc, but my latest acquisition was a Waldorf Blofeld.

I never really cared too much if my BCR2000 could send continuous Sysex data, as i don't regularly need that feature. Control change messages have been enough for most of my projects.

But everything has its moments, and now i could really take advantage of this with my Blofeld.

Problem is that i'm not sure if BCR2000 has the ability to send continuous Sysex data using one of the knobs. Some say it's possible, some say it's not.

I really love my BCR and wouldn't like to have to sell it to buy something a lot less sexier like Novation Zero SL, which i'm sure can work with continuous Sysex but which i really do not like at all.

So i checked with the LEARN function, and although BCR can capture and assign a Sysex data string to a knob, it does not send continuous values.

I moved to software editors, particularly to Birdie´s Bcfredit. Great, i can assign a Sysex to a knob using it as a LEARNT knob (i simply wrote down the hex preceded by "$") but again, the knob only sends 2 discrete values.

I checked with MIDIOX and if i assign it to MIDI channel 1, the knob actually sends the Sysex correctly, but only in values 0 and 2. If i assign it to MIDI channel 2, the sent values are 1 and 3, and so on.

No matter if i choose Absolute, Relative, Abs14, Rel14 or whatever,the result is always the same : only 2 discrete values are sent.

I know this might be a very specific question, but i hope someone over here is able to explain to me :

a) if BCR2000 can send continuous Sysex Data

b) the way to achieve that

Thanks a lot for reading !

Re: Sysex Programming

2009-05-18 by k5kip_1999

--- In bc2000@yahoogroups.com, "narcissus05@..." <narcissus05@...> wrote:
>
sniped
> 
> I never really cared too much if my BCR2000 could send continuous Sysex data, as i don't regularly need that feature. Control change messages have been enough for most of my projects.
> 

Read the secretBc.pdf in the files section under documentation.
While I am not certain I am using the correct nomenclature...
continues sysex is possible, although it is may be more aptly called discrete sysex, because you are sending individual messages.
I built my sysex control of the VFX, with help from other users (rcpfender in particular) over a year ago and I have not revisited the process since. I meant to make some tut vids on that topic but I never got back to it.
So the answer is yes you "should" be able to do what you are after.

> Problem is that i'm not sure if BCR2000 has the ability to send continuous Sysex data using one of the knobs. Some say it's possible, some say it's not.

> I really love my BCR and wouldn't like to have to sell it to buy something a lot less sexier like Novation Zero SL, which i'm sure can work with continuous Sysex but which i really do not like at all.

I honestly don't know if the Zero can do what you are after or not.

> 
> So i checked with the LEARN function, and although BCR can capture and assign a Sysex data string to a knob, it does not send continuous values.

You will use .tx commands to send your sysex.
As I recall, I watched the sysex commands on midiox as they came out of the vfx, when I moved a control on the vfx. I watched which bits? (bytes? someone correct my terms please) changed.
More than likely one or two locations of the byte values will change.
That value you will insert "val x-x" THIS is key and this is where I forget what I did and why. You can use BcEdit or you can use Bcmanager.  I found it easy to capture "record" the custom command and paste it into the box. Then edit the byte that varies correctly.
This was several versions of bcmanager 1.3 i think, ago.

You may have to mess with clockwise and counter clockwise movement of each knob.  

> 
> I moved to software editors, particularly to Birdie´s Bcfredit. Great, i can assign a Sysex to a knob using it as a LEARNT knob (i simply wrote down the hex preceded by "$") but again, the knob only sends 2 discrete values.

I like bcmanager for this... but to each his own.

> I checked with MIDIOX and if i assign it to MIDI channel 1, the knob actually sends the Sysex correctly, but only in values 0 and 2. If i assign it to MIDI channel 2, the sent values are 1 and 3, and so on.

Bcmanager will help with this, however, you will have to read up and you will have to use hex values, I think, although new bcmanager may have made that easier.

> No matter if i choose Absolute, Relative, Abs14, Rel14 or whatever,the result is always the same : only 2 discrete values are sent.
> 
> I know this might be a very specific question, but i hope someone over here is able to explain to me :
> a) if BCR2000 can send continuous Sysex Data
> b) the way to achieve that

Take a look at some of the other presets here for controlling synths.
My vfx presets are here as well.
Those presets for controlling synths are sending sysex (like a cc (but only for an analogy comparison)) and intended for patch creation (well at least mine is).

You might look at the Ensoniqs asr first - look at my preset and then try to get one knob actually doing what you want it to.
Once you get the hang of it, you would probably be able to go to the blofield.

k

Show quoted textHide quoted text

> 
> Thanks a lot for reading !
>

Re: Sysex Programming

2009-05-20 by rpcfender

Hi and welcome
> I am a fairly seasoned synth programmer, always trying to get more and more juice from my machines, 

> Problem is that i'm not sure if BCR2000 has the ability to send continuous Sysex data using one of the knobs. Some say it's possible, some say it's not.

It can sen continious sysex, but you can't program this and a whole lot of other things from the unit itself.
As a programmer you have a choice of two editors to write the sysex (and there is also a text compiler) 
I still use my editor (available in the files area) but it is a script editor for the BC language, BCL, but it convert the BCL to sysex and send it to the BC and receive sysex and convert it to BCL.
Easy to learn and there are plenty of examples of other synth controllers.

Mark has produced a great graphic editor that you might prefer. It is much more sophisticated than my mine and sort of hides the the BCL from you. 
I don't think there is anything you can program by script that you can't do with Mark's editor

He also wrote a great pdf where he explains of all the functions of the BCs that we discovered.
Behringer wouldn't give us any info so it is what we have found out from various sources and experimentation. 

Mark has moved all his files to his new website and you find a link in the files section.

> I really love my BCR and wouldn't like to have to sell it to buy something a lot less sexier like Novation Zero SL, which i'm sure can work with continuous Sysex but which i really do not like at all.

Don't sell it.. there are only a couple of things the BC can't do. It has 14bit Midi numbers but some synths (particularly Emu) use negative 14 bit numbers and BC won't do this. There are some work arounds so get Mark's PDF and an editor and give it a go. 
When you get stuck post here and we will see if we can sort it out fore you.

All the best 

Royce

Sysex Programming

2009-12-30 by stublito

I just got a BCR2000 and would like to program it to send sysex to my MKS70, Lexicon lxp5 and Oberheim) Matrix 1000. I have done all this already with a Lexicon MRC and I put sysex in  most of my sequences, I just need a simple 1, 2, 3.

I looked at the script and BCR manager software posted here, it seems way too complicated. I just want to define the control, put the sysex header in and go.

Please help.

Stublito

Re: Sysex Programming

2009-12-30 by rpcfender

Hi Stublito
> I just got a BCR2000 and would like to program it to send sysex to my MKS70, Lexicon lxp5 and Oberheim) Matrix 1000. I have done all this already with a Lexicon MRC and I put sysex in most of my sequences, I just need a simple 1, 2, 3.
>
> I looked at the script and BCR manager software posted here, it seems way too complicated. I just want to define the control, put the sysex header in and go.

Don't we all , the rule is ' the more flexible, the more complicated' and the BC is very flexible

You might like to try writing script instead of the BC Manager.

Grab my editor
Grab Mark's pdf on the Behringer Control Language (BCL)
Take a look at BC Screts pdf to get an idea.

; is a comment
$ the number is in hex otherwise decimal
The script looks like this

$rev R1 ; for the BCR
$preset
.name 'Your preset'
.snapshot off
.request off
.egroups 4 ; make the top row of encoders into 4 rows
.fkeys on
.lock off
.init ; clear the preset in the edit buffer

$encoder 49 ; bottom left
.showvalue on ; the LED display
.mode 1dot ; the circle of LEDs around the encoder
.resolution 96 96 96 96
.default 0 ; starting point
.minmax 0 127
.tx $F0 $43 $10 $12 $24 val $F7 ; Output level for the Yamaha TQ5 synth

$button 9 ; group 2 - the switch on top of encoder 1 but with group 2 selected (group buttons - top far right)
.showvalue on
.mode incval 1 ; each time you press, increment the value
.default 1 ; starting point
.minmax 0 3
.tx $F0 $43 $10 $12 $20 val $F7 ; Rate scaling for operator 2 on the Yamaha TQ5 synth
$end

All the best

Royce

Re: [bc2000] Sysex Programming

2009-12-30 by jamo jamo

Hello Stublito,

I think you have to go manual learn mode for each of device. Probably time consuming but works.

You can find the some tips on download page with Alpha Juno - maybe this will help to set up your MKS 70.

After that you will probably will have enought experience to move to Lexicon and Oberheim.

Brgds

Show quoted textHide quoted text

On Wed, Dec 30, 2009 at 6:38 AM, stublito <ogusa@...> wrote:

I just got a BCR2000 and would like to program it to send sysex to my MKS70, Lexicon lxp5 and Oberheim) Matrix 1000. I have done all this already with a Lexicon MRC and I put sysex in most of my sequences, I just need a simple 1, 2, 3.

I looked at the script and BCR manager software posted here, it seems way too complicated. I just want to define the control, put the sysex header in and go.

Please help.

Stublito

Re: [bc2000] Re: Sysex Programming

2009-12-30 by ogusa@lava.net

THAN YOU!. That's it exactly. I'm  a database guy, all I needed was  
the headers and syntax (and to borrow a PC from work). My MIDI setup  
is (!) Mac OS 9.

When I'm done I'll post the templates.

Stublio


Quoting rpcfender <rpcfender@...>:

Show quoted textHide quoted text

> Hi Stublito
>> I just got a BCR2000 and would like to program it to send sysex to my
> MKS70, Lexicon lxp5 and Oberheim) Matrix 1000. I have done all this
> already with a Lexicon MRC and I put sysex in  most of my sequences, I
> just need a simple 1, 2, 3.
>>
>> I looked at the script and BCR manager software posted here, it seems
> way too complicated. I just want to define the control, put the sysex
> header in and go.
>
> Don't we all , the rule is  ' the more flexible, the more complicated'
> and the BC is very flexible
>
> You might like to try writing script instead of the BC Manager.
>
> Grab my editor
> Grab Mark's pdf on the Behringer Control Language (BCL)
> Take a look at BC Screts pdf to get an idea.
>
> ; is a comment
> $ the number is in hex otherwise decimal
> The script looks like this
>
> $rev R1  ; for the BCR
> $preset
>    .name 'Your preset'
>    .snapshot off
>    .request off
>    .egroups 4    ; make the top row of encoders into 4 rows
>    .fkeys on
>    .lock off
>    .init             ; clear the preset in the edit buffer
>
> $encoder 49  ; bottom left
>    .showvalue on   ; the LED display
>    .mode 1dot        ; the circle of LEDs around the encoder
>    .resolution 96 96 96 96
>    .default 0      ; starting point
>    .minmax   0 127
>    .tx  $F0 $43 $10 $12 $24 val $F7  ; Output level for the Yamaha TQ5
> synth
>
> $button 9     ; group 2 - the switch on top of encoder 1 but with group
> 2 selected (group buttons - top far right)
>    .showvalue on
>    .mode incval 1        ; each time you press, increment the value
>    .default 1      ; starting point
>    .minmax   0 3
>    .tx  $F0 $43 $10 $12 $20 val $F7  ; Rate scaling for operator 2 on the
> Yamaha TQ5 synth
> $end
>
> All the best
>
> Royce
>
>

MKS-70 Sysex Script

2009-12-31 by ogusa@lava.net

I think this is it, need to get a PC and upload it and try it out.  
Programmed it with Filemaker, already had the sysex stuff databased.  
Toughest part was mapping out the controls to the available knobs.  
Used the buttons to increment the 4 step values. Would appreciate a  
quick check to see if I'm missing any bits.

THANK YOU!

Stublito


$rev R1  ; for the BCR
$preset
   .name 'MKS 70 Tone A'
   .snapshot off
   .request off
   .egroups 4   ; make the top row of encoders into 4 rows - only used  
two though
   .fkeys on
   .lock
   .init    ; clear the preset in the edit buffer

$encoder 1   .showvalue on    1dot        .resolution 96 96 96 96  
.default 0   .minmax   0 127 .tx  $F0 $41 $36 $07 $24 $20 $01 $2F val  
$F7  ; MKS 70 Tone A ENV-1 Attack

$encoder 2   .showvalue on    1dot        .resolution 96 96 96 96  
.default 0   .minmax   0 127 .tx  $F0 $41 $36 $07 $24 $20 $01 $30 val  
$F7  ; MKS 70 Tone A ENV-1 Decay

$encoder 3   .showvalue on    1dot        .resolution 96 96 96 96  
.default 0   .minmax   0 127 .tx  $F0 $41 $36 $07 $24 $20 $01 $31 val  
$F7  ; MKS 70 Tone A ENV-1 Sus

$encoder 4   .showvalue on    1dot        .resolution 96 96 96 96  
.default 0   .minmax   0 127 .tx  $F0 $41 $36 $07 $24 $20 $01 $32 val  
$F7  ; MKS 70 Tone A ENV-1 Rel

$encoder 5  .showvalue on    1dot        .resolution 96 96 96 96  
.default 0   .minmax   0 127 .tx  $F0 $41 $36 $07 $24 $20 $01 $33 val  
$F7  ; MKS 70 Tone A Env1 Key Follow

$encoder 6  .showvalue on    1dot        .resolution 96 96 96 96  
.default 0   .minmax   0 127 .tx  $F0 $41 $36 $07 $24 $20 $01 $2C val  
$F7  ; MKS 70 Tone A LFO Waveform

$encoder 7 .showvalue on    1dot        .resolution 96 96 96 96  
.default 0   .minmax   0 127 .tx  $F0 $41 $36 $07 $24 $20 $01 $2E val  
$F7  ; MKS 70 Tone A LFO Speed

$encoder 8 .showvalue on    1dot        .resolution 96 96 96 96  
.default 0   .minmax   0 127 .tx  $F0 $41 $36 $07 $24 $20 $01 $2D val  
$F7  ; MKS 70 Tone A LFO Delay

$encoder 9  .showvalue on    1dot        .resolution 96 96 96 96  
.default 0   .minmax   0 127 .tx  $F0 $41 $36 $07 $24 $20 $01 $34 val  
$F7  ; MKS 70 Tone A ENV-2 Attack

$encoder 10  .showvalue on    1dot        .resolution 96 96 96 96  
.default 0   .minmax   0 127 .tx  $F0 $41 $36 $07 $24 $20 $01 $35 val  
$F7  ; MKS 70 Tone A ENV-2 Decay

$encoder 11  .showvalue on    1dot        .resolution 96 96 96 96  
.default 0   .minmax   0 127 .tx  $F0 $41 $36 $07 $24 $20 $01 $36 val  
$F7  ; MKS 70 Tone A ENV-2 Sustain

$encoder 12  .showvalue on    1dot        .resolution 96 96 96 96  
.default 0   .minmax   0 127 .tx  $F0 $41 $36 $07 $24 $20 $01 $37 val  
$F7  ; MKS 70 Tone A ENV-2 Rel

$encoder 13  .showvalue on    1dot        .resolution 96 96 96 96  
.default 0   .minmax   0 127 .tx  $F0 $41 $36 $07 $24 $20 $01 $38val  
$F7  ; MKS 70 Tone A ENV-2 Key Follow

$encoder 14  .showvalue on    1dot        .resolution 96 96 96 96  
.default 0   .minmax   0 127 .tx  $F0 $41 $36 $07 $24 $20 $01 $2C val  
$F7  ; MKS 70 Tone A LFO Waveform Duplicate

$encoder 15 .showvalue on    1dot        .resolution 96 96 96 96  
.default 0   .minmax   0 127 .tx  $F0 $41 $36 $07 $24 $20 $01 $2E val  
$F7  ; MKS 70 Tone A LFO Speed Duplicate

$encoder 16 .showvalue on    1dot        .resolution 96 96 96 96  
.default 0   .minmax   0 127 .tx  $F0 $41 $36 $07 $24 $20 $01 $2D val  
$F7  ; MKS 70 Tone A LFO Delay Duplicate

$encoder 33   .showvalue on    1dot        .resolution 96 96 96 96  
.default 0   .minmax   0 127 .tx  $F0 $41 $36 $07 $24 $20 $01 $0D val  
$F7  ; MKS 70 Tone A DCO-1 Octave

$encoder 34   .showvalue on    1dot        .resolution 96 96 96 96  
.default 0   .minmax   0 127 .tx  $F0 $41 $36 $07 $24 $20 $01 $0E val  
$F7  ; MKS 70 Tone A DCO-1 LFO Level

$encoder 35   .showvalue on    1dot        .resolution 96 96 96 96  
.default 0   .minmax   0 127 .tx  $F0 $41 $36 $07 $24 $20 $01 $0F val  
$F7  ; MKS 70 Tone A DCO-1 Pitch Env

$encoder 36   .showvalue on    1dot        .resolution 96 96 96 96  
.default 0   .minmax   0 127 .tx  $F0 $41 $36 $07 $24 $20 $01 $13 val  
$F7  ; MKS 70 Tone A DCO-2 Tune

$encoder 37   .showvalue on    1dot        .resolution 96 96 96 96  
.default 0   .minmax   0 127 .tx  $F0 $41 $36 $07 $24 $20 $01 $15 val  
$F7  ; MKS 70 Tone A DCO-2 LFO Level

$encoder 38   .showvalue on    1dot        .resolution 96 96 96 96  
.default 0   .minmax   0 127 .tx  $F0 $41 $36 $07 $24 $20 $01 $16 val  
$F7  ; MKS 70 Tone A DCO-2 Pitch Env

$encoder 39   .showvalue on    1dot        .resolution 96 96 96 96  
.default 0   .minmax   0 127 .tx  $F0 $41 $36 $07 $24 $20 $01 $14 val  
$F7  ; MKS 70 Tone A DCO-2 Fine Tune

$encoder 40   .showvalue on    1dot        .resolution 96 96 96 96  
.default 0   .minmax   0 127 .tx  $F0 $41 $36 $07 $24 $20 $01 $2B val  
$F7  ; MKS 70 Chorus Mode

$button 41   .showvalue on   .mode incval 30     .default 30   .minmax  
   0 3   .tx  $F0 $41 $36 $07 $24 $20 $01 $0B val $F7  ; MKS 70 Tone A  
DCO-1 Range <33,<65, <93, <127

$encoder 41   .showvalue on    1dot        .resolution 96 96 96 96  
.default 0   .minmax   0 127   .tx  $F0 $41 $36 $07 $24 $20 $01 $21  
val $F7  ; MKS 70 Tone A VCF Hi Pass <33,<65, <93, <127

$button 42   .showvalue on   .mode incval 32     .default 1   .minmax   
  0 3   .tx  $F0 $41 $36 $07 $24 $20 $01 $0C val $F7  ; MKS 70 Tone A  
DCO-1 Waveform

$encoder 42  .showvalue on    1dot        .resolution 96 96 96 96  
.default 0   .minmax   0 127   .tx  $F0 $41 $36 $07 $24 $20 $01 $22  
val $F7  ; MKS 70 Tone A VCF Freq

$encoder 43  .showvalue on    1dot        .resolution 96 96 96 96  
.default 0   .minmax   0 127   .tx  $F0 $41 $36 $07 $24 $20 $01 $23  
val $F7  ; MKS 70 Tone A VCF Q

$encoder 44  .showvalue on    1dot        .resolution 96 96 96 96  
.default 0   .minmax   0 127   .tx  $F0 $41 $36 $07 $24 $20 $01 $24  
val $F7  ; MKS 70 Tone A VCF LFO

$button 44   .showvalue on   .mode incval 30     .default 30   .minmax  
   0 3   .tx  $F0 $41 $36 $07 $24 $20 $01 $10 val $F7  ; MKS 70 Tone A  
DCO-2 Range <33,<65, <93, <127

$encoder 45  .showvalue on    1dot        .resolution 96 96 96 96  
.default 0   .minmax   0 127   .tx  $F0 $41 $36 $07 $24 $20 $01 $25  
val $F7  ; MKS 70 Tone A VCF Env

$button 45   .showvalue on   .mode incval 32     .default 1    .minmax  
   0 3   .tx  $F0 $41 $36 $07 $24 $20 $01 $11 val $F7  ; MKS 70 Tone A  
DCO-2 Waveform

$encoder 46   .showvalue on    1dot        .resolution 96 96 96 96  
.default 0   .minmax   0 127   .tx  $F0 $41 $36 $07 $24 $20 $01 $26  
val $F7  ; MKS 70 Tone A VCF Key Follow

$button 46   .showvalue on   .mode incval 32     .default 1   .minmax   
  0 3   .tx  $F0 $41 $36 $07 $24 $20 $01 $12 val $F7  ; MKS 70 Tone A  
DCO- Crossmod <33,<65, <93, <127

$button 47   .showvalue on   .mode incval 32     .default 1   .minmax   
  0 3   .tx  $F0 $41 $36 $07 $24 $20 $01 $1A val $F7  ; MKS 70 Tone A  
DCO Dynamics <33,<65, <93, <127

$encoder 47  .showvalue on    1dot        .resolution 96 96 96 96  
.default 0   .minmax   0 127   .tx  $F0 $41 $36 $07 $24 $20 $01 $27  
val $F7  ; MKS 70 Tone A VCF Dynamics

$button 48   .showvalue on   .mode incval 32     .default 1   .minmax   
  0 3   .tx  $F0 $41 $36 $07 $24 $20 $01 $1B val $F7  ; MKS 70 Tone A  
DCO Env Mode  <33,<65, <93, <127

$encoder 48  .showvalue on    1dot        .resolution 96 96 96 96  
.default 0   .minmax   0 127   .tx  $F0 $41 $36 $07 $24 $20 $01 $28  
val $F7  ; MKS 70 Tone A VCF Env Mode

$encoder 49   .showvalue on    1dot        .resolution 96 96 96 96  
.default 0   .minmax   0 127   .tx  $F0 $41 $36 $07 $24 $20 $01 $1C  
val $F7  ; MKS 70 Tone A DCO-1 Mix Level

$encoder 50   .showvalue on    1dot        .resolution 96 96 96 96  
.default 0   .minmax   0 127   .tx  $F0 $41 $36 $07 $24 $20 $01 $1D  
val $F7  ; MKS 70 Tone A DCO-2 Mix Level

$encoder 51   .showvalue on    1dot        .resolution 96 96 96 96  
.default 0   .minmax   0 127   .tx  $F0 $41 $36 $07 $24 $20 $01 $1E  
val $F7  ; MKS 70 Tone A DCO-2 Mix Env

$encoder 52   .showvalue on    1dot        .resolution 96 96 96 96  
.default 0   .minmax   0 127   .tx  $F0 $41 $36 $07 $24 $20 $01 $1F  
val $F7  ; MKS 70 Tone A DCO-2 Mix Dynamics

$encoder 53   .showvalue on    1dot        .resolution 96 96 96 96  
.default 0   .minmax   0 127   .tx  $F0 $41 $36 $07 $24 $20 $01 $20  
val $F7  ; MKS 70 Tone A DCO-2 Mix Env Mode

$encoder 54   .showvalue on    1dot        .resolution 96 96 96 96  
.default 0   .minmax   0 127   .tx  $F0 $41 $36 $07 $24 $20 $01 $29  
val $F7  ; MKS 70 Tone A VCA Base Level

$encoder 55   .showvalue on    1dot        .resolution 96 96 96 96  
.default 0   .minmax   0 127   .tx  $F0 $41 $36 $07 $24 $20 $01 $2A  
val $F7  ; MKS 70 Tone A VCA Dynamics

$encoder 56  .showvalue on    1dot        .resolution 96 96 96 96  
.default 0   .minmax   0 127   .tx  $F0 $41 $36 $07 $24 $20 $01 $38  
val $F7  ; MKS 70 Tone A VCA Env Mode

$end

Re: MKS-70 Sysex Script

2009-12-31 by rpcfender

You'll have some trouble loading this

> I think this is it, need to get a PC and upload it and try it out.
> Programmed it with Filemaker, already had the sysex stuff databased.
> Toughest part was mapping out the controls to the available knobs.
> Used the buttons to increment the 4 step values. Would appreciate a
> quick check to see if I'm missing any bits.

$rev R1 ; for the BCR
$preset
.name 'MKS 70 Tone A'
.snapshot off
.request off
.egroups 4 ; make the top row of encoders into 4 rows - only used two though- then you should use
.egroups 2 ; and this will use just the top two buttons -

; so the top row will always be usefull otherwise you could press group3 button and ther top row would stop working

.fkeys on
.lock
.init ; clear the preset in the edit buffer

; The BC separates each line into a nice formatted code
$encoder 1
.showvalue on
.mode 1dot ; the mode word is missing
.resolution 96 96 96 96
.default 0
.minmax 0 127
.tx $F0 $41 $36 $07 $24 $20 $01 $2F val $F7 ; MKS 70 Tone A ENV-1 Attack

$button 47
.showvalue on
.mode incval 32 ;I don't think this is right - this says to jump by 32 each time the button is pressed
.default 1
.minmax 0 3
.tx $F0 $41 $36 $07 $24 $20 $01 $1A val $F7 ; MKS 70 Tone A DCO Dynamics

$end

Nearly there

Royce

Re: [bc2000] Re: MKS-70 Sysex Script

2009-12-31 by ogusa@lava.net

Thank you. We don't usually do new lines in database land, so I'll  
have to fix that.

I suspected the egroups command, thanks for confirming that too.

Got the missing word "mode".

The increment commands are correct. The data breakpoints for the 4  
position switches are 0, 32, 64, 96.

Again, THANK YOU.

Stublito

Quoting rpcfender <rpcfender@...>:

Show quoted textHide quoted text

> You'll have some trouble loading this
>
>> I think this is it, need to get a PC and upload it and try it out.
>> Programmed it with Filemaker, already had the sysex stuff databased.
>> Toughest part was mapping out the controls to the available knobs.
>> Used the buttons to increment the 4 step values. Would appreciate a
>> quick check to see if I'm missing any bits.
>
>
> $rev R1  ; for the BCR
> $preset
>   .name 'MKS 70 Tone A'
>   .snapshot off
>   .request off
>   .egroups 4       ; make the top row of encoders into 4 rows - only used
> two though- then you should use
>    .egroups 2 ; and this will use just the top two buttons -
>
> ; so the top row will always be usefull otherwise you could press group3
> button and ther top row would stop working
>
>   .fkeys on
>   .lock
>   .init    ; clear the preset in the edit buffer
>
> ; The BC separates each line into a nice formatted code
> $encoder 1
>     .showvalue on
>     .mode 1dot     ; the mode word is missing
>     .resolution 96 96 96 96
>     .default 0
>     .minmax   0 127
>     .tx  $F0 $41 $36 $07 $24 $20 $01 $2F val   $F7    ; MKS 70 Tone A
> ENV-1 Attack
>
> $button 47
>    .showvalue on
>    .mode incval 32     ;I don't think this is right - this says to jump
> by 32 each time the button is pressed
>    .default 1
>    .minmax    0 3
>    .tx  $F0 $41 $36 $07 $24 $20 $01 $1A val $F7  ; MKS 70 Tone A   DCO
> Dynamics
>
> $end
>
>
> Nearly there
>
> Royce
>
>

Re: [bc2000] Re: MKS-70 Sysex Script

2009-12-31 by ogusa@lava.net

$rev R1  ; for the BCR
$preset
   .name 'MKS 70 Tone A'
   .snapshot off
   .request off
   .egroups 2   ; make the top row of encoders into 2 rows
   .fkeys on
   .lock
   .init    ; clear the preset in the edit buffer

$encoder 1
     .showvalue on  
     .mode 1dot       
     .resolution 96 96 96 96
     .default 0
     .minmax   0 127
     .tx  $F0 $41 $36 $07 $24 $20 $01 $2F val $F7  ; MKS 70 Tone A ENV-1 Attack

$encoder 2
     .showvalue on  
     .mode 1dot       
     .resolution 96 96 96 96
     .default 0
     .minmax   0 127
     .tx  $F0 $41 $36 $07 $24 $20 $01 $30 val $F7  ; MKS 70 Tone A ENV-1 Decay

$encoder 3
     .showvalue on  
     .mode 1dot       
     .resolution 96 96 96 96
     .default 0
     .minmax   0 127
     .tx  $F0 $41 $36 $07 $24 $20 $01 $31 val $F7  ; MKS 70 Tone A ENV-1 Sus

$encoder 4
     .showvalue on  
     .mode 1dot       
     .resolution 96 96 96 96
     .default 0
     .minmax   0 127
     .tx  $F0 $41 $36 $07 $24 $20 $01 $32 val $F7  ; MKS 70 Tone A ENV-1 Rel

$encoder 5
     .showvalue on  
     .mode 1dot       
     .resolution 96 96 96 96
     .default 0
     .minmax   0 127
     .tx  $F0 $41 $36 $07 $24 $20 $01 $33 val $F7  ; MKS 70 Tone A  
Env1 Key Follow

$encoder 6
     .showvalue on  
     .mode 1dot       
     .resolution 96 96 96 96
     .default 0
     .minmax   0 127
     .tx  $F0 $41 $36 $07 $24 $20 $01 $2C val $F7  ; MKS 70 Tone A LFO Waveform

$encoder 7
     .showvalue on  
     .mode 1dot       
     .resolution 96 96 96 96
     .default 0
     .minmax   0 127
     .tx  $F0 $41 $36 $07 $24 $20 $01 $2E val $F7  ; MKS 70 Tone A LFO Speed

$encoder 8
     .showvalue on  
     .mode 1dot       
     .resolution 96 96 96 96
     .default 0
     .minmax   0 127
     .tx  $F0 $41 $36 $07 $24 $20 $01 $2D val $F7  ; MKS 70 Tone A LFO Delay

$encoder 9
     .showvalue on  
     .mode 1dot       
     .resolution 96 96 96 96
     .default 0
     .minmax   0 127
     .tx  $F0 $41 $36 $07 $24 $20 $01 $34 val $F7  ; MKS 70 Tone A ENV-2 Attack

$encoder 10
     .showvalue on  
     .mode 1dot       
     .resolution 96 96 96 96
     .default 0
     .minmax   0 127
     .tx  $F0 $41 $36 $07 $24 $20 $01 $35 val $F7  ; MKS 70 Tone A ENV-2 Decay

$encoder 11
     .showvalue on  
     .mode 1dot       
     .resolution 96 96 96 96
     .default 0
     .minmax   0 127
     .tx  $F0 $41 $36 $07 $24 $20 $01 $36 val $F7  ; MKS 70 Tone A  
ENV-2 Sustain

$encoder 12
     .showvalue on  
     .mode 1dot       
     .resolution 96 96 96 96
     .default 0
     .minmax   0 127
     .tx  $F0 $41 $36 $07 $24 $20 $01 $37 val $F7  ; MKS 70 Tone A ENV-2 Rel

$encoder 13
     .showvalue on  
     .mode 1dot       
     .resolution 96 96 96 96
     .default 0
     .minmax   0 127
     .tx  $F0 $41 $36 $07 $24 $20 $01 $38val $F7  ; MKS 70 Tone A  
ENV-2 Key Follow

$encoder 14
     .showvalue on  
     .mode 1dot       
     .resolution 96 96 96 96
     .default 0
     .minmax   0 127
     .tx  $F0 $41 $36 $07 $24 $20 $01 $2C val $F7  ; MKS 70 Tone A LFO Waveform

$encoder 15
     .showvalue on  
     .mode 1dot       
     .resolution 96 96 96 96
     .default 0
     .minmax   0 127
     .tx  $F0 $41 $36 $07 $24 $20 $01 $2E val $F7  ; MKS 70 Tone A LFO  
Speed Duplicate

$encoder 16
     .showvalue on  
     .mode 1dot       
     .resolution 96 96 96 96
     .default 0
     .minmax   0 127
     .tx  $F0 $41 $36 $07 $24 $20 $01 $2D val $F7  ; MKS 70 Tone A LFO  
Delay Duplicate

$encoder 33
     .showvalue on  
     .mode 1dot       
     .resolution 96 96 96 96
     .default 0
     .minmax   0 127
     .tx  $F0 $41 $36 $07 $24 $20 $01 $0D val $F7  ; MKS 70 Tone A DCO-1 Octave

$encoder 34
     .showvalue on  
     .mode 1dot       
     .resolution 96 96 96 96
     .default 0
     .minmax   0 127
     .tx  $F0 $41 $36 $07 $24 $20 $01 $0E val $F7  ; MKS 70 Tone A  
DCO-1 LFO Level

$encoder 35
     .showvalue on  
     .mode 1dot       
     .resolution 96 96 96 96
     .default 0
     .minmax   0 127
     .tx  $F0 $41 $36 $07 $24 $20 $01 $0F val $F7  ; MKS 70 Tone A  
DCO-1 Pitch Env

$encoder 36
     .showvalue on  
     .mode 1dot       
     .resolution 96 96 96 96
     .default 0
     .minmax   0 127
     .tx  $F0 $41 $36 $07 $24 $20 $01 $13 val $F7  ; MKS 70 Tone A DCO-2 Tune

$encoder 37
     .showvalue on  
     .mode 1dot       
     .resolution 96 96 96 96
     .default 0
     .minmax   0 127
     .tx  $F0 $41 $36 $07 $24 $20 $01 $15 val $F7  ; MKS 70 Tone A  
DCO-2 LFO Level

$encoder 38
     .showvalue on  
     .mode 1dot       
     .resolution 96 96 96 96
     .default 0
     .minmax   0 127
     .tx  $F0 $41 $36 $07 $24 $20 $01 $16 val $F7  ; MKS 70 Tone A  
DCO-2 Pitch Env

$encoder 39
     .showvalue on  
     .mode 1dot       
     .resolution 96 96 96 96
     .default 0
     .minmax   0 127
     .tx  $F0 $41 $36 $07 $24 $20 $01 $14 val $F7  ; MKS 70 Tone A  
DCO-2 Fine Tune

$encoder 40
     .showvalue on  
     .mode 1dot       
     .resolution 96 96 96 96
     .default 0
     .minmax   0 127
     .tx  $F0 $41 $36 $07 $24 $20 $01 $2B val $F7  ; MKS 70 Chorus Mode

$button 41
     .showvalue on  
     .mode incval 30    
     .default 30
     .minmax   0 3
     .tx  $F0 $41 $36 $07 $24 $20 $01 $0B val $F7  ; MKS 70 Tone A  
DCO-1 Range <33,<65, <93, <127

$encoder 41
     .showvalue on  
     .mode 1dot       
     .resolution 96 96 96 96
     .default 0
     .minmax   0 127
     .tx  $F0 $41 $36 $07 $24 $20 $01 $21 val $F7  ; MKS 70 Tone A VCF  
Hi Pass <33,<65, <93, <127

$button 42
     .showvalue on  
     .mode incval 32   
     .default 1
     .minmax   0 3
     .tx  $F0 $41 $36 $07 $24 $20 $01 $0C val $F7  ; MKS 70 Tone A  
DCO-1 Waveform

$encoder 42
     .showvalue on  
     .mode 1dot       
     .resolution 96 96 96 96
     .default 0
     .minmax   0 127
     .tx  $F0 $41 $36 $07 $24 $20 $01 $22 val $F7  ; MKS 70 Tone A VCF Freq

$encoder 43
     .showvalue on  
     .mode 1dot       
     .resolution 96 96 96 96
     .default 0
     .minmax   0 127
     .tx  $F0 $41 $36 $07 $24 $20 $01 $23 val $F7  ; MKS 70 Tone A VCF Q

$encoder 44
     .showvalue on  
     .mode 1dot       
     .resolution 96 96 96 96
     .default 0
     .minmax   0 127
     .tx  $F0 $41 $36 $07 $24 $20 $01 $24 val $F7  ; MKS 70 Tone A VCF LFO

$button 44
     .showvalue on  
     .mode incval 30   
     .default 30
     .minmax   0 3
     .tx  $F0 $41 $36 $07 $24 $20 $01 $10 val $F7  ; MKS 70 Tone A  
DCO-2 Range <33,<65, <93, <127

$encoder 45
     .showvalue on  
     .mode 1dot       
     .resolution 96 96 96 96
     .default 0
     .minmax   0 127
     .tx  $F0 $41 $36 $07 $24 $20 $01 $25 val $F7  ; MKS 70 Tone A VCF Env

$button 45
     .showvalue on  
     .mode incval 32   
     .default 1
     .minmax   0 3
     .tx  $F0 $41 $36 $07 $24 $20 $01 $11 val $F7  ; MKS 70 Tone A  
DCO-2 Waveform

$encoder 46
     .showvalue on  
     .mode 1dot       
     .resolution 96 96 96 96
     .default 0
     .minmax   0 127
     .tx  $F0 $41 $36 $07 $24 $20 $01 $26 val $F7  ; MKS 70 Tone A VCF  
Key Follow

$button 46
     .showvalue on  
     .mode incval 32   
     .default 1
     .minmax   0 3
     .tx  $F0 $41 $36 $07 $24 $20 $01 $12 val $F7  ; MKS 70 Tone A  
DCO- Crossmod <33,<65, <93, <127

$button 47
     .showvalue on  
     .mode incval 32   
     .default 1
     .minmax   0 3
     .tx  $F0 $41 $36 $07 $24 $20 $01 $1A val $F7  ; MKS 70 Tone A DCO  
Dynamics <33,<65, <93, <127

$encoder 47
     .showvalue on  
     .mode 1dot       
     .resolution 96 96 96 96
     .default 0
     .minmax   0 127
     .tx  $F0 $41 $36 $07 $24 $20 $01 $27 val $F7  ; MKS 70 Tone A VCF Dynamics

$button 48
     .showvalue on  
     .mode incval 32   
     .default 1
     .minmax   0 3
     .tx  $F0 $41 $36 $07 $24 $20 $01 $1B val $F7  ; MKS 70 Tone A DCO  
Env Mode  <33,<65, <93, <127

$encoder 48
     .showvalue on  
     .mode 1dot       
     .resolution 96 96 96 96
     .default 0
     .minmax   0 127
     .tx  $F0 $41 $36 $07 $24 $20 $01 $28 val $F7  ; MKS 70 Tone A VCF Env Mode

$encoder 49
     .showvalue on  
     .mode 1dot       
     .resolution 96 96 96 96
     .default 0
     .minmax   0 127
     .tx  $F0 $41 $36 $07 $24 $20 $01 $1C val $F7  ; MKS 70 Tone A  
DCO-1 Mix Level

$encoder 50
     .showvalue on  
     .mode 1dot       
     .resolution 96 96 96 96
     .default 0
     .minmax   0 127
     .tx  $F0 $41 $36 $07 $24 $20 $01 $1D val $F7  ; MKS 70 Tone A  
DCO-2 Mix Level

$encoder 51
     .showvalue on  
     .mode 1dot       
     .resolution 96 96 96 96
     .default 0
     .minmax   0 127
     .tx  $F0 $41 $36 $07 $24 $20 $01 $1E val $F7  ; MKS 70 Tone A  
DCO-2 Mix Env

$encoder 52
     .showvalue on  
     .mode 1dot       
     .resolution 96 96 96 96
     .default 0
     .minmax   0 127
     .tx  $F0 $41 $36 $07 $24 $20 $01 $1F val $F7  ; MKS 70 Tone A  
DCO-2 Mix Dynamics

$encoder 53
     .showvalue on  
     .mode 1dot       
     .resolution 96 96 96 96
     .default 0
     .minmax   0 127
     .tx  $F0 $41 $36 $07 $24 $20 $01 $20 val $F7  ; MKS 70 Tone A  
DCO-2 Mix Env Mode

$encoder 54
     .showvalue on  
     .mode 1dot       
     .resolution 96 96 96 96
     .default 0
     .minmax   0 127
     .tx  $F0 $41 $36 $07 $24 $20 $01 $29 val $F7  ; MKS 70 Tone A VCA  
Base Level

$encoder 55
     .showvalue on  
     .mode 1dot       
     .resolution 96 96 96 96
     .default 0
     .minmax   0 127
     .tx  $F0 $41 $36 $07 $24 $20 $01 $2A val $F7  ; MKS 70 Tone A VCA Dynamics

$encoder 56
     .showvalue on  
     .mode 1dot       
     .resolution 96 96 96 96
     .default 0
     .minmax   0 127
     .tx  $F0 $41 $36 $07 $24 $20 $01 $38 val $F7  ; MKS 70 Tone A VCA Env Mode

$end


Quoting rpcfender <rpcfender@...>:

Show quoted textHide quoted text

> You'll have some trouble loading this
>
>> I think this is it, need to get a PC and upload it and try it out.
>> Programmed it with Filemaker, already had the sysex stuff databased.
>> Toughest part was mapping out the controls to the available knobs.
>> Used the buttons to increment the 4 step values. Would appreciate a
>> quick check to see if I'm missing any bits.
>
>
> $rev R1  ; for the BCR
> $preset
>   .name 'MKS 70 Tone A'
>   .snapshot off
>   .request off
>   .egroups 4       ; make the top row of encoders into 4 rows - only used
> two though- then you should use
>    .egroups 2 ; and this will use just the top two buttons -
>
> ; so the top row will always be usefull otherwise you could press group3
> button and ther top row would stop working
>
>   .fkeys on
>   .lock
>   .init    ; clear the preset in the edit buffer
>
> ; The BC separates each line into a nice formatted code
> $encoder 1
>     .showvalue on
>     .mode 1dot     ; the mode word is missing
>     .resolution 96 96 96 96
>     .default 0
>     .minmax   0 127
>     .tx  $F0 $41 $36 $07 $24 $20 $01 $2F val   $F7    ; MKS 70 Tone A
> ENV-1 Attack
>
> $button 47
>    .showvalue on
>    .mode incval 32     ;I don't think this is right - this says to jump
> by 32 each time the button is pressed
>    .default 1
>    .minmax    0 3
>    .tx  $F0 $41 $36 $07 $24 $20 $01 $1A val $F7  ; MKS 70 Tone A   DCO
> Dynamics
>
> $end
>
>
> Nearly there
>
> Royce
>
>

Re: MKS-70 Sysex Script

2010-01-01 by rpcfender

Hi

> The increment commands are correct. The data breakpoints for the 4
> position switches are 0, 32, 64, 96.

$button 42
.showvalue on
.mode incval 32 ;
.default 1
.minmax 0 3
.tx $F0 $41 $36 $07 $24 $20 $01 $0C val $F7 ; MKS 70 Tone A DCO-1 Waveform

This won't give you what you want. You need to increase the minmax value

$button 42
.showvalue on
.mode incval 32
.default 1
.minmax 0 96
.tx $F0 $41 $36 $07 $24 $20 $01 $0C val $F7 ; MKS 70 Tone A DCO-1 Waveform

Note that when you reach 96 the next press returns val to 0
With incval watch out for reversing the minmax values
eg
.minmax 0 3 ;works
.minmax 3 0 ; won't count backwards as you might think

.mode incval -1
.minmax 0 3 ; now this counts backwards

>
> Again, THANK YOU.

Pleasure

Royce

Re: MKS-70 Sysex Script

2010-01-01 by psionic11

If I'm understanding Royce correctly, you still need to correct many of your buttons.  For example --

$button 48
.showvalue on  
.mode incval 32   
.default 1
.minmax 0 3
.tx $F0 $41 $36 $07 $24 $20 $01 $1B val $F7  ; MKS 70 Tone A DCO
Env Mode <33,<65, <93, <127

Firstly, the command ".mode incval 32" will make values jump by 32 at a time: 0, 32, 64, 96, 128=0 (wraps around), 32, 64, etc.  But as you've set ".default 1", then the values would jump 1, 33, 65, 97, 129=1, 33...

Secondly, as Royce has already pointed out, your ".minmax 0 3" will only allow values 0, 1, 2, 3, then wrap back around.  Thus, you need to make it ".minmax 0 127" so that you can get the values needed by your MKS-70, that is ALL values up to 127.  Setting incval to jump by 32 while only having minmax's max at 3 will not result in 0, 32, 64, 96, 0, 32..., but instead in 0, 0, 0, 0..., because 3 is your max.  Correct, Royce?

Lastly, in your comments, you indicate that the MKS Env Modes are <33, <65, <93, and <127.  Shouldn't that <93 instead be <97.  I'm assuming the MKS is looking for 4 ranges to be switched thru, 32 per jump: 0-32, 33-64, 64-96, 97-127.

Hope that's correct.

Re: [bc2000] Re: MKS-70 Sysex Script

2010-01-02 by ogusa@lava.net

This is a great board. Thanks so much to you guys.

I'm going to do all my synths, this one is the hardest. I'll upload my  
templates when they are done.

Happy New Year.

Stublito

Quoting psionic11 <psionic11@...>:

Show quoted textHide quoted text

> If I'm understanding Royce correctly, you still need to correct many  
>  of your buttons.  For example --
>
> $button 48
> .showvalue on
> .mode incval 32
> .default 1
> .minmax 0 3
> .tx $F0 $41 $36 $07 $24 $20 $01 $1B val $F7  ; MKS 70 Tone A DCO
> Env Mode <33,<65, <93, <127
>
> Firstly, the command ".mode incval 32" will make values jump by 32   
> at a time: 0, 32, 64, 96, 128=0 (wraps around), 32, 64, etc.  But as  
>  you've set ".default 1", then the values would jump 1, 33, 65, 97,   
> 129=1, 33...
>
> Secondly, as Royce has already pointed out, your ".minmax 0 3" will   
> only allow values 0, 1, 2, 3, then wrap back around.  Thus, you need  
>  to make it ".minmax 0 127" so that you can get the values needed by  
>  your MKS-70, that is ALL values up to 127.  Setting incval to jump   
> by 32 while only having minmax's max at 3 will not result in 0, 32,   
> 64, 96, 0, 32..., but instead in 0, 0, 0, 0..., because 3 is your   
> max.  Correct, Royce?
>
> Lastly, in your comments, you indicate that the MKS Env Modes are   
> <33, <65, <93, and <127.  Shouldn't that <93 instead be <97.  I'm   
> assuming the MKS is looking for 4 ranges to be switched thru, 32 per  
>  jump: 0-32, 33-64, 64-96, 97-127.
>
> Hope that's correct.
>
>
>
>
> ------------------------------------
>
> Yahoo! Groups Links
>
>
>
>

Re: MKS-70 Sysex Script

2010-01-02 by rpcfender

> If I'm understanding Royce correctly, you still need to correct many of your buttons. For example --
>
> $button 48
> .showvalue on
> .mode incval 32
> .default 1
> .minmax 0 3
> .tx $F0 $41 $36 $07 $24 $20 $01 $1B val $F7 ; MKS 70 Tone A DCO
> Env Mode <33,<65, <93, <127

adding 32 gives
Env Mode <33,<65, <97, <129
but we can't have a data byte of 129
Are these the correct values??

>
> Firstly, the command ".mode incval 32" will make values jump by 32 at a time: 0, 32, 64, 96, 128=0 (wraps around), 32, 64, etc. But as you've set ".default 1", then the values would jump 1, 33, 65, 97, 129=1, 33...

Not quite
You are correct when you say ".mode incval 32" will make values jump by 32 at a time

.default 1 just means 'the first time this preset is selected after power on the control will have the value 1'
After you have pressed or twisted the control the BC remembers the value even if you change presets and come back again.

When the BC loops back it always goes to the Min value
.minmax 0 127
33
65
97
00
32
64
96
00

Although it started on 1 (default) it returns to the Min value. For 1 33 65 97 you need...
.minmax 1 97 (I choose 97 because it tells me what the last value is but 127 is OK)
33
65
97
01
33
65
97
01
33
65
97

Is you head hurting yet??

>Setting incval to jump by 32 while only having minmax's max at 3 will not result in 0, 32, 64, 96, 0, 32..., but instead in 0, 0, 0, 0..., because 3 is your max. Correct, Royce?

Absolutely

All the best

Royce

Re: [bc2000] Re: MKS-70 Sysex Script

2010-01-03 by ogusa@lava.net

Hopefully, not a dumb question. I couldn't find this in the available lit.

Can the BC transmit the default values of the newly selected patch?  
This would be very useful for using the thing as a lighting controller  
or for synth programming when you want a basic synth patch to start  
programming ffrom.

Thanks

Stublito

Quoting rpcfender <rpcfender@...>:

Show quoted textHide quoted text

>> If I'm understanding Royce correctly, you still need to correct many
> of your buttons.  For example --
>>
>> $button 48
>> .showvalue on
>> .mode incval 32
>> .default 1
>> .minmax 0 3
>> .tx $F0 $41 $36 $07 $24 $20 $01 $1B val $F7  ; MKS 70 Tone A DCO
>> Env Mode <33,<65, <93, <127
>
> adding 32 gives
> Env Mode <33,<65, <97, <129
> but we can't have a data byte of  129
> Are these the correct values??
>
>>
>> Firstly, the command ".mode incval 32" will make values jump by 32 at
> a time: 0, 32, 64, 96, 128=0 (wraps around), 32, 64, etc.  But as you've
> set ".default 1", then the values would jump 1, 33, 65, 97, 129=1, 33...
>
> Not quite
> You are correct when you say  ".mode incval 32" will make values jump by
> 32 at a time
>
> .default 1 just means 'the first time this preset is selected after
> power on the control will have the value 1'
> After you have pressed or twisted the control the BC remembers the value
> even if you change presets and come back again.
>
> When the BC loops back it always goes to the Min value
> .minmax 0 127
> 33
> 65
> 97
> 00
> 32
> 64
> 96
> 00
>
> Although it started on 1 (default) it returns to the Min value. For 1 33
> 65 97 you need...
> .minmax 1 97        (I choose 97 because it tells me what the last value
> is but 127 is OK)
> 33
> 65
> 97
> 01
> 33
> 65
> 97
> 01
> 33
> 65
> 97
>
> Is you head hurting yet??
>
>
>> Setting incval to jump by 32 while only having minmax's max at 3 will
> not result in 0, 32, 64, 96, 0, 32..., but instead in 0, 0, 0, 0...,
> because 3 is your max.  Correct, Royce?
>
> Absolutely
>
> All the best
>
> Royce
>
>

MKS-70 Sysex Script Load Error

2010-01-04 by ogusa@lava.net

So I installed the Win driver on an XP laptop and tried uploading the  
script using the BC Editor, got an Er 22 - I'm assuming the generic  
newbie error ;)

I even tried the default Fantom Script same error.

Wassup?

Thanks again all,

Stublito


Quoting ogusa@...:

Show quoted textHide quoted text

> Hopefully, not a dumb question. I couldn't find this in the available lit.
>
> Can the BC transmit the default values of the newly selected patch?
> This would be very useful for using the thing as a lighting controller
> or for synth programming when you want a basic synth patch to start
> programming ffrom.
>
> Thanks
>
> Stublito
>
> Quoting rpcfender <rpcfender@...>:
>
>>> If I'm understanding Royce correctly, you still need to correct many
>> of your buttons.  For example --
>>>
>>> $button 48
>>> .showvalue on
>>> .mode incval 32
>>> .default 1
>>> .minmax 0 3
>>> .tx $F0 $41 $36 $07 $24 $20 $01 $1B val $F7  ; MKS 70 Tone A DCO
>>> Env Mode <33,<65, <93, <127
>>
>> adding 32 gives
>> Env Mode <33,<65, <97, <129
>> but we can't have a data byte of  129
>> Are these the correct values??
>>
>>>
>>> Firstly, the command ".mode incval 32" will make values jump by 32 at
>> a time: 0, 32, 64, 96, 128=0 (wraps around), 32, 64, etc.  But as you've
>> set ".default 1", then the values would jump 1, 33, 65, 97, 129=1, 33...
>>
>> Not quite
>> You are correct when you say  ".mode incval 32" will make values jump by
>> 32 at a time
>>
>> .default 1 just means 'the first time this preset is selected after
>> power on the control will have the value 1'
>> After you have pressed or twisted the control the BC remembers the value
>> even if you change presets and come back again.
>>
>> When the BC loops back it always goes to the Min value
>> .minmax 0 127
>> 33
>> 65
>> 97
>> 00
>> 32
>> 64
>> 96
>> 00
>>
>> Although it started on 1 (default) it returns to the Min value. For 1 33
>> 65 97 you need...
>> .minmax 1 97        (I choose 97 because it tells me what the last value
>> is but 127 is OK)
>> 33
>> 65
>> 97
>> 01
>> 33
>> 65
>> 97
>> 01
>> 33
>> 65
>> 97
>>
>> Is you head hurting yet??
>>
>>
>>> Setting incval to jump by 32 while only having minmax's max at 3 will
>> not result in 0, 32, 64, 96, 0, 32..., but instead in 0, 0, 0, 0...,
>> because 3 is your max.  Correct, Royce?
>>
>> Absolutely
>>
>> All the best
>>
>> Royce
>>
>>
>
>
>
>
>
> ------------------------------------
>
> Yahoo! Groups Links
>
>
>
>

Re: MKS-70 Sysex Script Load Error

2010-01-04 by rpcfender

You fist problem. You can use snapshot in the preset section

$preset
  .snapshot on

This will cause the BC to output all the current values when you select this preset.
If you haven't selected this preset since turning on the unit it will send the defaults.
The BC remembers your changes even when you change presets until you turn off the unit or overwrite the preset.


You should get Mark's BCL pdf from his website. It has all the Error codes

Error 22 is invalid Message index

Each line of the  BCL script is wrapped in a header and $F7 to produce a sysex message.
Part of the header is a line counter - the Message index.
Something in you script is causing the program to miscount.
You are saying the Fantom script is also causing this error.
As no one else has reported this problem, perhaps it is your setup.

What mode is the BC in U1 U2 etc?
Have you got a Midi interface on the laptop?
Try using S1 and Midi cables.

Royce



--- In bc2000@yahoogroups.com, ogusa@... wrote:

Show quoted textHide quoted text

>
> So I installed the Win driver on an XP laptop and tried uploading the  
> script using the BC Editor, got an Er 22 - I'm assuming the generic  
> newbie error ;)
> 
> I even tried the default Fantom Script same error.
> 
> Wassup?
> 
> Thanks again all,
> 
> Stublito
> 
> 
> Quoting ogusa@...:
> 
> > Hopefully, not a dumb question. I couldn't find this in the available lit.
> >
> > Can the BC transmit the default values of the newly selected patch?
> > This would be very useful for using the thing as a lighting controller
> > or for synth programming when you want a basic synth patch to start
> > programming ffrom.
> >
> > Thanks
> >
> > Stublito
> >
> > Quoting rpcfender <rpcfender@...>:
> >
> >>> If I'm understanding Royce correctly, you still need to correct many
> >> of your buttons.  For example --
> >>>
> >>> $button 48
> >>> .showvalue on
> >>> .mode incval 32
> >>> .default 1
> >>> .minmax 0 3
> >>> .tx $F0 $41 $36 $07 $24 $20 $01 $1B val $F7  ; MKS 70 Tone A DCO
> >>> Env Mode <33,<65, <93, <127
> >>
> >> adding 32 gives
> >> Env Mode <33,<65, <97, <129
> >> but we can't have a data byte of  129
> >> Are these the correct values??
> >>
> >>>
> >>> Firstly, the command ".mode incval 32" will make values jump by 32 at
> >> a time: 0, 32, 64, 96, 128=0 (wraps around), 32, 64, etc.  But as you've
> >> set ".default 1", then the values would jump 1, 33, 65, 97, 129=1, 33...
> >>
> >> Not quite
> >> You are correct when you say  ".mode incval 32" will make values jump by
> >> 32 at a time
> >>
> >> .default 1 just means 'the first time this preset is selected after
> >> power on the control will have the value 1'
> >> After you have pressed or twisted the control the BC remembers the value
> >> even if you change presets and come back again.
> >>
> >> When the BC loops back it always goes to the Min value
> >> .minmax 0 127
> >> 33
> >> 65
> >> 97
> >> 00
> >> 32
> >> 64
> >> 96
> >> 00
> >>
> >> Although it started on 1 (default) it returns to the Min value. For 1 33
> >> 65 97 you need...
> >> .minmax 1 97        (I choose 97 because it tells me what the last value
> >> is but 127 is OK)
> >> 33
> >> 65
> >> 97
> >> 01
> >> 33
> >> 65
> >> 97
> >> 01
> >> 33
> >> 65
> >> 97
> >>
> >> Is you head hurting yet??
> >>
> >>
> >>> Setting incval to jump by 32 while only having minmax's max at 3 will
> >> not result in 0, 32, 64, 96, 0, 32..., but instead in 0, 0, 0, 0...,
> >> because 3 is your max.  Correct, Royce?
> >>
> >> Absolutely
> >>
> >> All the best
> >>
> >> Royce
> >>
> >>
> >
> >
> >
> >
> >
> > ------------------------------------
> >
> > Yahoo! Groups Links
> >
> >
> >
> >
>

Re: [bc2000] Re: MKS-70 Sysex Script Load Error

2010-01-08 by ogusa@lava.net

Thanks for the snapshot hint. Yes I'll read the parameter stuff, sorry..

So this other Er_22 thing is really weird.

I decided to try deleting bits of the Fantom code (from the bottom up)  
that defaults every time you power up. I kept getting the Er_22 until  
I deleted from $encoder 44 down (I left the $end on of course).

I used U-2 and U-3 and selected the BCR2000 Port 1 as the output.   
Perhaps the firmware is buggy?

THANK YOU! How can I buy you a beer or two?

Stublito



Quoting rpcfender <rpcfender@....au>:

Show quoted textHide quoted text

> You fist problem. You can use snapshot in the preset section
>
> $preset
>   .snapshot on
>
> This will cause the BC to output all the current values when you   
> select this preset.
> If you haven't selected this preset since turning on the unit it   
> will send the defaults.
> The BC remembers your changes even when you change presets until you  
>  turn off the unit or overwrite the preset.
>
>
> You should get Mark's BCL pdf from his website. It has all the Error codes
>
> Error 22 is invalid Message index
>
> Each line of the  BCL script is wrapped in a header and $F7 to   
> produce a sysex message.
> Part of the header is a line counter - the Message index.
> Something in you script is causing the program to miscount.
> You are saying the Fantom script is also causing this error.
> As no one else has reported this problem, perhaps it is your setup.
>
> What mode is the BC in U1 U2 etc?
> Have you got a Midi interface on the laptop?
> Try using S1 and Midi cables.
>
> Royce
>
>
>
> --- In bc2000@yahoogroups.com, ogusa@... wrote:
>>
>> So I installed the Win driver on an XP laptop and tried uploading the
>> script using the BC Editor, got an Er 22 - I'm assuming the generic
>> newbie error ;)
>>
>> I even tried the default Fantom Script same error.
>>
>> Wassup?
>>
>> Thanks again all,
>>
>> Stublito
>>
>>
>> Quoting ogusa@...:
>>
>> > Hopefully, not a dumb question. I couldn't find this in the available lit.
>> >
>> > Can the BC transmit the default values of the newly selected patch?
>> > This would be very useful for using the thing as a lighting controller
>> > or for synth programming when you want a basic synth patch to start
>> > programming ffrom.
>> >
>> > Thanks
>> >
>> > Stublito
>> >
>> > Quoting rpcfender <rpcfender@...>:
>> >
>> >>> If I'm understanding Royce correctly, you still need to correct many
>> >> of your buttons.  For example --
>> >>>
>> >>> $button 48
>> >>> .showvalue on
>> >>> .mode incval 32
>> >>> .default 1
>> >>> .minmax 0 3
>> >>> .tx $F0 $41 $36 $07 $24 $20 $01 $1B val $F7  ; MKS 70 Tone A DCO
>> >>> Env Mode <33,<65, <93, <127
>> >>
>> >> adding 32 gives
>> >> Env Mode <33,<65, <97, <129
>> >> but we can't have a data byte of  129
>> >> Are these the correct values??
>> >>
>> >>>
>> >>> Firstly, the command ".mode incval 32" will make values jump by 32 at
>> >> a time: 0, 32, 64, 96, 128=0 (wraps around), 32, 64, etc.  But as you've
>> >> set ".default 1", then the values would jump 1, 33, 65, 97, 129=1, 33...
>> >>
>> >> Not quite
>> >> You are correct when you say  ".mode incval 32" will make values jump by
>> >> 32 at a time
>> >>
>> >> .default 1 just means 'the first time this preset is selected after
>> >> power on the control will have the value 1'
>> >> After you have pressed or twisted the control the BC remembers the value
>> >> even if you change presets and come back again.
>> >>
>> >> When the BC loops back it always goes to the Min value
>> >> .minmax 0 127
>> >> 33
>> >> 65
>> >> 97
>> >> 00
>> >> 32
>> >> 64
>> >> 96
>> >> 00
>> >>
>> >> Although it started on 1 (default) it returns to the Min value. For 1 33
>> >> 65 97 you need...
>> >> .minmax 1 97        (I choose 97 because it tells me what the last value
>> >> is but 127 is OK)
>> >> 33
>> >> 65
>> >> 97
>> >> 01
>> >> 33
>> >> 65
>> >> 97
>> >> 01
>> >> 33
>> >> 65
>> >> 97
>> >>
>> >> Is you head hurting yet??
>> >>
>> >>
>> >>> Setting incval to jump by 32 while only having minmax's max at 3 will
>> >> not result in 0, 32, 64, 96, 0, 32..., but instead in 0, 0, 0, 0...,
>> >> because 3 is your max.  Correct, Royce?
>> >>
>> >> Absolutely
>> >>
>> >> All the best
>> >>
>> >> Royce
>> >>
>> >>
>> >
>> >
>> >
>> >
>> >
>> > ------------------------------------
>> >
>> > Yahoo! Groups Links
>> >
>> >
>> >
>> >
>>
>
>
>
>
> ------------------------------------
>
> Yahoo! Groups Links
>
>
>
>

Update: MKS-70 Sysex Script Load Error

2010-01-09 by ogusa@lava.net

So I tried (on OS X) dumping a sysex file I downloaded from the  
Behringer site using Sysex librarian. Mode U-1 Port 1, got an E 6  
error within the first second, the Sysex librarian was still grinding  
away after the error.

I tried dumping the current template FROM the BCR to Sysex Librarian  
and only got a file 17 bytes long.

I bought the BCR used off of eBay. It seems to function OK in every  
other respect (I haven't tried actually CONTROLLING anything yet though.

Any advice would be very welcome.

Thanks

Stublito

Quoting ogusa@...:

Show quoted textHide quoted text

> Thanks for the snapshot hint. Yes I'll read the parameter stuff, sorry..
>
> So this other Er_22 thing is really weird.
>
> I decided to try deleting bits of the Fantom code (from the bottom up)
> that defaults every time you power up. I kept getting the Er_22 until
> I deleted from $encoder 44 down (I left the $end on of course).
>
> I used U-2 and U-3 and selected the BCR2000 Port 1 as the output.
> Perhaps the firmware is buggy?
>
> THANK YOU! How can I buy you a beer or two?
>
> Stublito
>
>
>
> Quoting rpcfender <rpcfender@...>:
>
>> You fist problem. You can use snapshot in the preset section
>>
>> $preset
>>   .snapshot on
>>
>> This will cause the BC to output all the current values when you
>> select this preset.
>> If you haven't selected this preset since turning on the unit it
>> will send the defaults.
>> The BC remembers your changes even when you change presets until you
>>  turn off the unit or overwrite the preset.
>>
>>
>> You should get Mark's BCL pdf from his website. It has all the Error codes
>>
>> Error 22 is invalid Message index
>>
>> Each line of the  BCL script is wrapped in a header and $F7 to
>> produce a sysex message.
>> Part of the header is a line counter - the Message index.
>> Something in you script is causing the program to miscount.
>> You are saying the Fantom script is also causing this error.
>> As no one else has reported this problem, perhaps it is your setup.
>>
>> What mode is the BC in U1 U2 etc?
>> Have you got a Midi interface on the laptop?
>> Try using S1 and Midi cables.
>>
>> Royce
>>
>>
>>
>> --- In bc2000@yahoogroups.com, ogusa@... wrote:
>>>
>>> So I installed the Win driver on an XP laptop and tried uploading the
>>> script using the BC Editor, got an Er 22 - I'm assuming the generic
>>> newbie error ;)
>>>
>>> I even tried the default Fantom Script same error.
>>>
>>> Wassup?
>>>
>>> Thanks again all,
>>>
>>> Stublito
>>>
>>>
>>> Quoting ogusa@...:
>>>
>>> > Hopefully, not a dumb question. I couldn't find this in the   
>>> available lit.
>>> >
>>> > Can the BC transmit the default values of the newly selected patch?
>>> > This would be very useful for using the thing as a lighting controller
>>> > or for synth programming when you want a basic synth patch to start
>>> > programming ffrom.
>>> >
>>> > Thanks
>>> >
>>> > Stublito
>>> >
>>> > Quoting rpcfender <rpcfender@...>:
>>> >
>>> >>> If I'm understanding Royce correctly, you still need to correct many
>>> >> of your buttons.  For example --
>>> >>>
>>> >>> $button 48
>>> >>> .showvalue on
>>> >>> .mode incval 32
>>> >>> .default 1
>>> >>> .minmax 0 3
>>> >>> .tx $F0 $41 $36 $07 $24 $20 $01 $1B val $F7  ; MKS 70 Tone A DCO
>>> >>> Env Mode <33,<65, <93, <127
>>> >>
>>> >> adding 32 gives
>>> >> Env Mode <33,<65, <97, <129
>>> >> but we can't have a data byte of  129
>>> >> Are these the correct values??
>>> >>
>>> >>>
>>> >>> Firstly, the command ".mode incval 32" will make values jump by 32 at
>>> >> a time: 0, 32, 64, 96, 128=0 (wraps around), 32, 64, etc.  But as you've
>>> >> set ".default 1", then the values would jump 1, 33, 65, 97, 129=1, 33...
>>> >>
>>> >> Not quite
>>> >> You are correct when you say  ".mode incval 32" will make values jump by
>>> >> 32 at a time
>>> >>
>>> >> .default 1 just means 'the first time this preset is selected after
>>> >> power on the control will have the value 1'
>>> >> After you have pressed or twisted the control the BC remembers the value
>>> >> even if you change presets and come back again.
>>> >>
>>> >> When the BC loops back it always goes to the Min value
>>> >> .minmax 0 127
>>> >> 33
>>> >> 65
>>> >> 97
>>> >> 00
>>> >> 32
>>> >> 64
>>> >> 96
>>> >> 00
>>> >>
>>> >> Although it started on 1 (default) it returns to the Min value. For 1 33
>>> >> 65 97 you need...
>>> >> .minmax 1 97        (I choose 97 because it tells me what the last value
>>> >> is but 127 is OK)
>>> >> 33
>>> >> 65
>>> >> 97
>>> >> 01
>>> >> 33
>>> >> 65
>>> >> 97
>>> >> 01
>>> >> 33
>>> >> 65
>>> >> 97
>>> >>
>>> >> Is you head hurting yet??
>>> >>
>>> >>
>>> >>> Setting incval to jump by 32 while only having minmax's max at 3 will
>>> >> not result in 0, 32, 64, 96, 0, 32..., but instead in 0, 0, 0, 0...,
>>> >> because 3 is your max.  Correct, Royce?
>>> >>
>>> >> Absolutely
>>> >>
>>> >> All the best
>>> >>
>>> >> Royce
>>> >>
>>> >>
>>> >
>>> >
>>> >
>>> >
>>> >
>>> > ------------------------------------
>>> >
>>> > Yahoo! Groups Links
>>> >
>>> >
>>> >
>>> >
>>>
>>
>>
>>
>>
>> ------------------------------------
>>
>> Yahoo! Groups Links
>>
>>
>>
>>
>
>
>
>
>
> ------------------------------------
>
> Yahoo! Groups Links
>
>
>
>

Re: Update: MKS-70 Sysex Script Load Error

2010-01-10 by rpcfender

Have you tried using a Midi interface?

There was a batch of BCs with what I believe was a faulty USB buffer or micro. This is just my opinion of course.
I bought a BCF and replaced it twice with similar serial numbered units. I finally got the one that was on display and that has been fine.

They were all OK with the Midi connection S1 to S4

Royce

--- In bc2000@yahoogroups.com, ogusa@... wrote:

Show quoted textHide quoted text

>
> So I tried (on OS X) dumping a sysex file I downloaded from the  
> Behringer site using Sysex librarian. Mode U-1 Port 1, got an E 6  
> error within the first second, the Sysex librarian was still grinding  
> away after the error.
> 
> I tried dumping the current template FROM the BCR to Sysex Librarian  
> and only got a file 17 bytes long.
> 
> I bought the BCR used off of eBay. It seems to function OK in every  
> other respect (I haven't tried actually CONTROLLING anything yet though.
> 
> Any advice would be very welcome.
> 
> Thanks
> 
> Stublito
> 
> Quoting ogusa@...:
> 
> > Thanks for the snapshot hint. Yes I'll read the parameter stuff, sorry..
> >
> > So this other Er_22 thing is really weird.
> >
> > I decided to try deleting bits of the Fantom code (from the bottom up)
> > that defaults every time you power up. I kept getting the Er_22 until
> > I deleted from $encoder 44 down (I left the $end on of course).
> >
> > I used U-2 and U-3 and selected the BCR2000 Port 1 as the output.
> > Perhaps the firmware is buggy?
> >
> > THANK YOU! How can I buy you a beer or two?
> >
> > Stublito
> >
> >
> >
> > Quoting rpcfender <rpcfender@...>:
> >
> >> You fist problem. You can use snapshot in the preset section
> >>
> >> $preset
> >>   .snapshot on
> >>
> >> This will cause the BC to output all the current values when you
> >> select this preset.
> >> If you haven't selected this preset since turning on the unit it
> >> will send the defaults.
> >> The BC remembers your changes even when you change presets until you
> >>  turn off the unit or overwrite the preset.
> >>
> >>
> >> You should get Mark's BCL pdf from his website. It has all the Error codes
> >>
> >> Error 22 is invalid Message index
> >>
> >> Each line of the  BCL script is wrapped in a header and $F7 to
> >> produce a sysex message.
> >> Part of the header is a line counter - the Message index.
> >> Something in you script is causing the program to miscount.
> >> You are saying the Fantom script is also causing this error.
> >> As no one else has reported this problem, perhaps it is your setup.
> >>
> >> What mode is the BC in U1 U2 etc?
> >> Have you got a Midi interface on the laptop?
> >> Try using S1 and Midi cables.
> >>
> >> Royce
> >>
> >>
> >>
> >> --- In bc2000@yahoogroups.com, ogusa@ wrote:
> >>>
> >>> So I installed the Win driver on an XP laptop and tried uploading the
> >>> script using the BC Editor, got an Er 22 - I'm assuming the generic
> >>> newbie error ;)
> >>>
> >>> I even tried the default Fantom Script same error.
> >>>
> >>> Wassup?
> >>>
> >>> Thanks again all,
> >>>
> >>> Stublito
> >>>
> >>>
> >>> Quoting ogusa@:
> >>>
> >>> > Hopefully, not a dumb question. I couldn't find this in the   
> >>> available lit.
> >>> >
> >>> > Can the BC transmit the default values of the newly selected patch?
> >>> > This would be very useful for using the thing as a lighting controller
> >>> > or for synth programming when you want a basic synth patch to start
> >>> > programming ffrom.
> >>> >
> >>> > Thanks
> >>> >
> >>> > Stublito
> >>> >
> >>> > Quoting rpcfender <rpcfender@>:
> >>> >
> >>> >>> If I'm understanding Royce correctly, you still need to correct many
> >>> >> of your buttons.  For example --
> >>> >>>
> >>> >>> $button 48
> >>> >>> .showvalue on
> >>> >>> .mode incval 32
> >>> >>> .default 1
> >>> >>> .minmax 0 3
> >>> >>> .tx $F0 $41 $36 $07 $24 $20 $01 $1B val $F7  ; MKS 70 Tone A DCO
> >>> >>> Env Mode <33,<65, <93, <127
> >>> >>
> >>> >> adding 32 gives
> >>> >> Env Mode <33,<65, <97, <129
> >>> >> but we can't have a data byte of  129
> >>> >> Are these the correct values??
> >>> >>
> >>> >>>
> >>> >>> Firstly, the command ".mode incval 32" will make values jump by 32 at
> >>> >> a time: 0, 32, 64, 96, 128=0 (wraps around), 32, 64, etc.  But as you've
> >>> >> set ".default 1", then the values would jump 1, 33, 65, 97, 129=1, 33...
> >>> >>
> >>> >> Not quite
> >>> >> You are correct when you say  ".mode incval 32" will make values jump by
> >>> >> 32 at a time
> >>> >>
> >>> >> .default 1 just means 'the first time this preset is selected after
> >>> >> power on the control will have the value 1'
> >>> >> After you have pressed or twisted the control the BC remembers the value
> >>> >> even if you change presets and come back again.
> >>> >>
> >>> >> When the BC loops back it always goes to the Min value
> >>> >> .minmax 0 127
> >>> >> 33
> >>> >> 65
> >>> >> 97
> >>> >> 00
> >>> >> 32
> >>> >> 64
> >>> >> 96
> >>> >> 00
> >>> >>
> >>> >> Although it started on 1 (default) it returns to the Min value. For 1 33
> >>> >> 65 97 you need...
> >>> >> .minmax 1 97        (I choose 97 because it tells me what the last value
> >>> >> is but 127 is OK)
> >>> >> 33
> >>> >> 65
> >>> >> 97
> >>> >> 01
> >>> >> 33
> >>> >> 65
> >>> >> 97
> >>> >> 01
> >>> >> 33
> >>> >> 65
> >>> >> 97
> >>> >>
> >>> >> Is you head hurting yet??
> >>> >>
> >>> >>
> >>> >>> Setting incval to jump by 32 while only having minmax's max at 3 will
> >>> >> not result in 0, 32, 64, 96, 0, 32..., but instead in 0, 0, 0, 0...,
> >>> >> because 3 is your max.  Correct, Royce?
> >>> >>
> >>> >> Absolutely
> >>> >>
> >>> >> All the best
> >>> >>
> >>> >> Royce
> >>> >>
> >>> >>
> >>> >
> >>> >
> >>> >
> >>> >
> >>> >
> >>> > ------------------------------------
> >>> >
> >>> > Yahoo! Groups Links
> >>> >
> >>> >
> >>> >
> >>> >
> >>>
> >>
> >>
> >>
> >>
> >> ------------------------------------
> >>
> >> Yahoo! Groups Links
> >>
> >>
> >>
> >>
> >
> >
> >
> >
> >
> > ------------------------------------
> >
> > Yahoo! Groups Links
> >
> >
> >
> >
>

Re: [bc2000] Re: Update: MKS-70 Sysex Script Load Error

2010-01-11 by ogusa@lava.net

Thanks, I'll try it, though it is humbug rewiring my rig.

Stublito

Quoting rpcfender <rpcfender@...>:

Show quoted textHide quoted text

> Have you tried using a Midi interface?
>
> There was a batch of BCs with what I believe was a faulty USB buffer  
>  or micro. This is just my opinion of course.
> I bought a BCF and replaced it twice with similar serial numbered   
> units. I finally got the one that was on display and that has been   
> fine.
>
> They were all OK with the Midi connection S1 to S4
>
> Royce
>
> --- In bc2000@yahoogroups.com, ogusa@... wrote:
>>
>> So I tried (on OS X) dumping a sysex file I downloaded from the
>> Behringer site using Sysex librarian. Mode U-1 Port 1, got an E 6
>> error within the first second, the Sysex librarian was still grinding
>> away after the error.
>>
>> I tried dumping the current template FROM the BCR to Sysex Librarian
>> and only got a file 17 bytes long.
>>
>> I bought the BCR used off of eBay. It seems to function OK in every
>> other respect (I haven't tried actually CONTROLLING anything yet though.
>>
>> Any advice would be very welcome.
>>
>> Thanks
>>
>> Stublito
>>
>> Quoting ogusa@...:
>>
>> > Thanks for the snapshot hint. Yes I'll read the parameter stuff, sorry..
>> >
>> > So this other Er_22 thing is really weird.
>> >
>> > I decided to try deleting bits of the Fantom code (from the bottom up)
>> > that defaults every time you power up. I kept getting the Er_22 until
>> > I deleted from $encoder 44 down (I left the $end on of course).
>> >
>> > I used U-2 and U-3 and selected the BCR2000 Port 1 as the output.
>> > Perhaps the firmware is buggy?
>> >
>> > THANK YOU! How can I buy you a beer or two?
>> >
>> > Stublito
>> >
>> >
>> >
>> > Quoting rpcfender <rpcfender@...>:
>> >
>> >> You fist problem. You can use snapshot in the preset section
>> >>
>> >> $preset
>> >>   .snapshot on
>> >>
>> >> This will cause the BC to output all the current values when you
>> >> select this preset.
>> >> If you haven't selected this preset since turning on the unit it
>> >> will send the defaults.
>> >> The BC remembers your changes even when you change presets until you
>> >>  turn off the unit or overwrite the preset.
>> >>
>> >>
>> >> You should get Mark's BCL pdf from his website. It has all the   
>> Error codes
>> >>
>> >> Error 22 is invalid Message index
>> >>
>> >> Each line of the  BCL script is wrapped in a header and $F7 to
>> >> produce a sysex message.
>> >> Part of the header is a line counter - the Message index.
>> >> Something in you script is causing the program to miscount.
>> >> You are saying the Fantom script is also causing this error.
>> >> As no one else has reported this problem, perhaps it is your setup.
>> >>
>> >> What mode is the BC in U1 U2 etc?
>> >> Have you got a Midi interface on the laptop?
>> >> Try using S1 and Midi cables.
>> >>
>> >> Royce
>> >>
>> >>
>> >>
>> >> --- In bc2000@yahoogroups.com, ogusa@ wrote:
>> >>>
>> >>> So I installed the Win driver on an XP laptop and tried uploading the
>> >>> script using the BC Editor, got an Er 22 - I'm assuming the generic
>> >>> newbie error ;)
>> >>>
>> >>> I even tried the default Fantom Script same error.
>> >>>
>> >>> Wassup?
>> >>>
>> >>> Thanks again all,
>> >>>
>> >>> Stublito
>> >>>
>> >>>
>> >>> Quoting ogusa@:
>> >>>
>> >>> > Hopefully, not a dumb question. I couldn't find this in the
>> >>> available lit.
>> >>> >
>> >>> > Can the BC transmit the default values of the newly selected patch?
>> >>> > This would be very useful for using the thing as a lighting controller
>> >>> > or for synth programming when you want a basic synth patch to start
>> >>> > programming ffrom.
>> >>> >
>> >>> > Thanks
>> >>> >
>> >>> > Stublito
>> >>> >
>> >>> > Quoting rpcfender <rpcfender@>:
>> >>> >
>> >>> >>> If I'm understanding Royce correctly, you still need to correct many
>> >>> >> of your buttons.  For example --
>> >>> >>>
>> >>> >>> $button 48
>> >>> >>> .showvalue on
>> >>> >>> .mode incval 32
>> >>> >>> .default 1
>> >>> >>> .minmax 0 3
>> >>> >>> .tx $F0 $41 $36 $07 $24 $20 $01 $1B val $F7  ; MKS 70 Tone A DCO
>> >>> >>> Env Mode <33,<65, <93, <127
>> >>> >>
>> >>> >> adding 32 gives
>> >>> >> Env Mode <33,<65, <97, <129
>> >>> >> but we can't have a data byte of  129
>> >>> >> Are these the correct values??
>> >>> >>
>> >>> >>>
>> >>> >>> Firstly, the command ".mode incval 32" will make values   
>> jump by 32 at
>> >>> >> a time: 0, 32, 64, 96, 128=0 (wraps around), 32, 64, etc.    
>> But as you've
>> >>> >> set ".default 1", then the values would jump 1, 33, 65, 97,   
>> 129=1, 33...
>> >>> >>
>> >>> >> Not quite
>> >>> >> You are correct when you say  ".mode incval 32" will make   
>> values jump by
>> >>> >> 32 at a time
>> >>> >>
>> >>> >> .default 1 just means 'the first time this preset is selected after
>> >>> >> power on the control will have the value 1'
>> >>> >> After you have pressed or twisted the control the BC   
>> remembers the value
>> >>> >> even if you change presets and come back again.
>> >>> >>
>> >>> >> When the BC loops back it always goes to the Min value
>> >>> >> .minmax 0 127
>> >>> >> 33
>> >>> >> 65
>> >>> >> 97
>> >>> >> 00
>> >>> >> 32
>> >>> >> 64
>> >>> >> 96
>> >>> >> 00
>> >>> >>
>> >>> >> Although it started on 1 (default) it returns to the Min   
>> value. For 1 33
>> >>> >> 65 97 you need...
>> >>> >> .minmax 1 97        (I choose 97 because it tells me what   
>> the last value
>> >>> >> is but 127 is OK)
>> >>> >> 33
>> >>> >> 65
>> >>> >> 97
>> >>> >> 01
>> >>> >> 33
>> >>> >> 65
>> >>> >> 97
>> >>> >> 01
>> >>> >> 33
>> >>> >> 65
>> >>> >> 97
>> >>> >>
>> >>> >> Is you head hurting yet??
>> >>> >>
>> >>> >>
>> >>> >>> Setting incval to jump by 32 while only having minmax's max  
>>  at 3 will
>> >>> >> not result in 0, 32, 64, 96, 0, 32..., but instead in 0, 0, 0, 0...,
>> >>> >> because 3 is your max.  Correct, Royce?
>> >>> >>
>> >>> >> Absolutely
>> >>> >>
>> >>> >> All the best
>> >>> >>
>> >>> >> Royce
>> >>> >>
>> >>> >>
>> >>> >
>> >>> >
>> >>> >
>> >>> >
>> >>> >
>> >>> > ------------------------------------
>> >>> >
>> >>> > Yahoo! Groups Links
>> >>> >
>> >>> >
>> >>> >
>> >>> >
>> >>>
>> >>
>> >>
>> >>
>> >>
>> >> ------------------------------------
>> >>
>> >> Yahoo! Groups Links
>> >>
>> >>
>> >>
>> >>
>> >
>> >
>> >
>> >
>> >
>> > ------------------------------------
>> >
>> > Yahoo! Groups Links
>> >
>> >
>> >
>> >
>>
>
>
>
>
> ------------------------------------
>
> Yahoo! Groups Links
>
>
>
>

Bc2000 (for the BCF2000 & BCR2000)

Sysex Programming

Sysex Programming

Re: Sysex Programming

Re: Sysex Programming

Sysex Programming

Re: Sysex Programming

Re: [bc2000] Sysex Programming

Re: [bc2000] Re: Sysex Programming

MKS-70 Sysex Script

Re: MKS-70 Sysex Script

Re: [bc2000] Re: MKS-70 Sysex Script

Re: [bc2000] Re: MKS-70 Sysex Script

Re: MKS-70 Sysex Script

Re: MKS-70 Sysex Script

Re: [bc2000] Re: MKS-70 Sysex Script

Re: MKS-70 Sysex Script

Re: [bc2000] Re: MKS-70 Sysex Script

MKS-70 Sysex Script Load Error

Re: MKS-70 Sysex Script Load Error

Re: [bc2000] Re: MKS-70 Sysex Script Load Error

Update: MKS-70 Sysex Script Load Error

Re: Update: MKS-70 Sysex Script Load Error

Re: [bc2000] Re: Update: MKS-70 Sysex Script Load Error

Move to quarantaine