BCL Blocks

5 posts / 0 new
Last post
cairnsfella
cairnsfella's picture
BCL Blocks

I am really sorry to trouble people with this stupid question, but I honestly cant find a clear refernce to this (clear to me that is).

Quite simply, is it normal that a preset contains a second - seemingly unstored - set of data that I can see in the BCL editor, following the first instance after the $store statement.

If I send a preset without the second instance, it always cones back with it added again.

An example may be clearer.

If I send:

$rev R1 ; Firmware 1.10; BC Manager 3.1.0
$preset
  .name '                        '
  .snapshot off
  .request off
  .egroups 4
  .fkeys on
  .lock off
  .init
$encoder 1
  .showvalue on
  .mode 12dot
  .resolution 12 128 1280 2300
  .minmax 0 128
  .tx $F0 $43 $10 $58 $03 $7B $00 $00 $00 $00 $00 reloffs $0040 val $00 $00 $00 $00 $00 $00 $00 $00 $00 $00 $00 $00 $00 $00 $00 $7F $05 $F7
$store 19
$end

I get the following back.

$rev R1 ; Firmware 1.10; BC Manager 3.1.0
$preset
  .name '                        '
  .snapshot off
  .request off
  .egroups 4
  .fkeys on
  .lock off
  .init
$encoder 1
  .showvalue on
  .mode 12dot
  .resolution 12 128 1280 2300
  .minmax 0 128
  .tx $F0 $43 $10 $58 $03 $7B $00 $00 $00 $00 $00 reloffs $0040 val $00 $00 $00 $00 $00 $00 $00 $00 $00 $00 $00 $00 $00 $00 $00 $7F $05 $F7
$store 19
$preset
  .name '                        '
  .snapshot off
  .request off
  .egroups 4
  .fkeys on
  .lock off
  .init
$encoder 1
  .showvalue on
  .mode 12dot
  .resolution 12 128 1280 2300
  .minmax 0 128
  .tx $F0 $43 $10 $58 $03 $7B $00 $00 $00 $00 $00 reloffs $0040 val $00 $00 $00 $00 $00 $00 $00 $00 $00 $00 $00 $00 $00 $00 $00 $7F $05 $F7
$end

What is more frustrating, is that yesterday when I first noticed this, I swear there were different values between the two. I mean fundementally different e.g. encoder resolutions differed. But today I dont seem to be able to find an example of that.

I guess I shouldnt care too much if all seems to work, it's just when I was having some teething problems yesterday, I felt it may have been down to this issue.

Not a biggie, but I guess someone that know can simply say "yes" - normal, or "No" - not normal (i.e. a problem at my end).

Thanks

 

Mark van den Berg
Mark van den Berg's picture

is it normal that a preset contains a second - seemingly unstored - set of data that I can see in the BCL editor, following the first instance after the $store statement. [...] I swear there were different values between the two.

I think this is the same question as question 23 in the FAQ section of the BC Manager manual:

 I loaded selected presets into the BCL editor. When I select e.g. presets 11-16, they all load, but so does preset 0, which is tacked on the end. Was that your intention?

The main part of my reply to that question was:

Yes:

When sending presets to the B-Control, BC Manager first sends (to use your example) memory presets 11-16, then preset 0 (the temporary preset). The latter is necessary for restoring preset 0 to the current values maintained by BC Manager, because preset 0 on the B-Control is used as a gateway for presets 11-16. So it seems logical to copy this behavior in the BCL editor window — which is why preset 0 is appended. The idea is that the user can edit the BCL text, then send it directly to the B-Control with the same 'automatic' restoration facility of preset 0.

However, I admit that in other situations (such as yours) it might be easier to leave out preset 0 at the end. I could include an on/off-switch in the BCL editor window's menu, or simply add another menu item that leaves out preset 0.

For explanation of preset 0 in general, see question 8 in the FAQ section.

Now that you're complaining about the appended preset 0 in the BCL editor, I'll see if I can indeed implement the on/off switch I was suggesting in the upcoming BC Manager 4.0.0.

By the way: if you're a BCL addict and on Windows, you may want to start using the BC Manager 3.2.0 Alpha 2 version (cf. this topic) if you're not already doing so: this version introduces syntax highlighting for the BCL editor. (If you're on macOS, you'll have to wait for version 4.0.0 for this.)

Hope this helps,
Mark.

cairnsfella
cairnsfella's picture

Thanks for the response.. but first of all

Now that you're complaining about the appended preset 0 in the BCL editor, I'll see if I can indeed implement the on/off switch I was suggesting in the upcoming BC Manager 4.0.0.

No no no no no no no no no no.

I am certainly NOT complaining. Not at all. As I am neither in a position to complain as I am very new to this level of Midi understanding. Nor would I complain about a facility you have so kindly provided (and that I hope one day to be capable of using properly). So no.. no complaints. I was just curious.

With regard to your FAQ, I must apologise, as I have read through both the Manual and the Midi implementation, but must confess, not all of it has stuck (perhaps not too much at all at this point). And though I obviously scanned back through with some pertinent search terms, I obviously still misssed this.

Even now I will need time to degest your response. My first thought is that I am using preset 32, so it looks at though that situation should not apply. But as I say, give me time to digest.

Once I get my head around the current issue I will have a look at 3.2.0 as you have suggested.

Many thanks. I will report back on my success (hopefully) or failure (hopefully not) in due course.

Again. Many thanks.

 

 

Mark van den Berg
Mark van den Berg's picture

Sorry!
I should have been more precise:
Instead of "now that you're complaining about the appended preset 0" I should have written "now that you're bringing this up again".
Humans have a subconscious tendency to exaggerate. I try not to, but in this case I did... sad

Anyway, I've already implemented an extra menu item in the BCL editor that does not append preset 0.
It will be part of BC Manager 4.0.0.

Mark.

cairnsfella
cairnsfella's picture

PS. Just to clarify.

The example I gave shows preset 19, but I just randomly generated this example. The behaviour was noted whilst I was actively programming preset 32. I didnt use this example as 1. It is much longer, and 2. My dodgy standard of sysex configuration may have detracted from the actual issue I was raising.