I get a crash while editing rules in a Translator with a large block of rules. I’ve tried to reduced the scenario to a simple case, but repeated failed, so I am sending the full .bmts file. Here’s how I reproduce the issue:
Scroll to the block of code near the bottom of the rules.
Note that there are two labels ‘ChannelGT18’. It is possible that this tees up the crash. The duplicate label was part of a copy-paste from the block of code above, as I was in the middle of editing.
Locate the rule 14 from the end that reads if oo!=24 then Goto ‘ChannelGT18’
Edit that line. In particular it happens sometimes if I modify the label in the Goto, sometimes when I modify the value 24. It often happens if I modify the value 24 to something beginning with ‘0x’ while trying to type a hex value …
Sorry I couldn’t reduce it to a smaller test case, but this is a transient bug that goes away with changes in the rules.
Oh no, that does not sound good. Editing rules usually work without problems, and I have just tried to reproduce it, but without a crash.
Maybe it would be a good idea to disable the translator while you are editing the rules. It is possible that some keystrokes caused some processing of the translator and put it in a loop.
Steve Caldwell
Bome Customer Care
Also available for paid consulting services: bome@sniz.biz
Yes, I believe the BMT timer I set is still running while I’m editing, and the MIDI is still flowing. Didn’t think of that …
So I’m using a LaunchPad to do things on my CQ20B - mute/unmute channels and such. I am changing the pad color on the LaunchPad when I mute/unmute. Issue is that the pad colors get out of step with the mixer, if changes are made directly on the mixer (i.e. via their MixPad app). So …
I am polling the Mixer on a 1-sec timer from BMT. Using NRPM and getting the results back by more NRPM. A lotta traffic.
Is there a better way to do this, other than polling the hardware??
Hi Clint,
whenever there is a crash report, it has highest priority for us. Fortunately, it seems your crash is only related to editing, so it’s unlikely it’ll happen during a performance.
As Steve guessed, it could be that incoming MIDI traffic while editing the rules could be the cause of the crash. A safe way to temporarily stop all MIDI traffic is to press the STOP button in the toolbar (or Shift-ESC).
Of course, a crash should never happen, even if there’s a lot of MIDI data going on, so the crash report will be very welcome.
Thanks a lot, we’ll have a look at the crash dump.
PS: I’ve removed the link from your post, crash reports should not be made public, they can contain sensitive information about your computer. I’ve downloaded it, so you can remove it from your drop box.