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

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@...:

> 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
>
>
>
>

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.