Random bug on a working script

Hello Steeve !

I'm using :

• Irig blueboard
• Connected by bluetooth with CME WidiBud as mentionned in the bomebox doc

When we toggle button A, B or C on the blueboard, it activate/deactivate 3 presets in the bomebox. An other preset toggle the light of A, B and C, depending of the state of the presets.

It works very well, but randomly the feedback with the light does not work. The toggle of the script works very well each time, but the toggle of the light sometimes get stuck (for even 1 or more seconds). So the light does not reflect anymore the state of the script.

I wonder if it could be a hardware problem, but what is strange is that the information going from the IrigBlueBoard TO the Bomebox is always working perfectly. It is the feedback information from the bomebox to the irig blueboard (that should light on the led) that sometimes does not work.

Thank you very much for your precious help !

NB : On the attached file the preset [7] and [8] are irrevelant for this case.

 

Hi,

Are you saying it always works perfectly when running on PC with MT Pro but you randomly get the issue when you run the same project on BomeBox? If so, are you also using the WidiBud when working on the computer.

To me it sound like it could either be a latency issue with WidiBud or perhaps something in the BomeBox.  When running on BomeBox, are you also using WiFi for anything? It could be perhaps WiFi traffic slowing things down.  

 

With that said, you might want to put a slight delay on preset switch just in case BomeBox is working busy on enabling/disabiling presets while also trying to updating the LED's.   I don't think this is the issue however.

Also, you have 3  All Notes-Off timers running concurrently so you are trying to send 128 * 3  or 384 note off messages at the same time you are updating the LED's. That is an additional 1,152 bytes of MIDI traffic at the same time you are trying to switch presets and update LED's. This is more likely the issue you are seeing especially if you are using MIDI DIN ports.

 

Also it looks like you are using n1 for notes counters for all channels and running all all-notes off timers concurrently.  I'm not sure why this is working correctly. I believe each all-notes off timer needs it's on global variable or you should have them executed sequentially.  Actually just one all-notes off timer that handles all channels would be more bulletproof.

The single all-notes off  timer would go sequencially through MIDI CH 1, then increment the channel count and then go sequencially through CH 2 etc. (or visa versa). You could put a delay of say 10ms on this to give your LED action to complete before running the all-notes off timer.

 

I'm really speculating right now as random problems are a little tougher to track down but this looks like the most likely suspect. 

I'm attaching an all-note-off project that I did in November that iterates through all channels. You can alter the rules to skip all midi channels higher than 3 if you want.

You may also need to update the global variables to the ones you use. You should be able to just copy and past the translator into your project. then edit the rules, etc. Disable your existing notes-off translators for testing and when you are done, delete them.

 

Steve Caldwell
Bome Q and A Moderator and
Independent Bome Consultant/Specialist
bome@sniz.biz

 

Steve Caldwell
Bome Q and A Moderator and
Independent Bome Consultant/Specialist
bome@sniz.biz

 

 

 

Hi Steve,

Thank you very much for your fast answer.

First of all, I'm sorry, it was in the afternoon before going on stage and I didn't take time to debug properly. By the way, it really got worse on stage, the light got quickly stuck in a state, and it always stayed like this.

So back home :

1. I tried on the computer with bome midi translator -> Same things, with all other scripts off (no note off sending, no deactivate preset, etc ...). Some led changes are missing, while I can see that the good informations is sent out of Bome Midi Translator. And it happened that the light got stuck

2. I modified my script to work with x-touch mini, and I've heavily tested it, on the computer, and on the bomeBox -> Zero bugs ! Even if I tapped hundred time on the three buttons as fast as I could.

So I think either widibud or IrigBlueBoard is defective. I'm going to look for a better foot controller midi or usb, but really not bluetooth, I don't feel at ease with that technology for the stability I need on stage.

For my allNotesOff script, they don't fire at the same time. This foot controller is for the accordion player. The accordion is also midi, and the scripts block the note on the 3 channels of the accordion. When the player hit A, B or C a channel is open or closed. When a channel is closed, AllNotesOff are sent specifically on that channel (because sometimes she close the channel with still a finger on a key).

Thank you for the allNotesOff script. I'm going to replace my clumsy midiPanic script on another project with this one !

 

Hi Steve,

Thank you very much for your fast answer.

First of all, I'm sorry, it was in the afternoon before going on stage and I didn't take time to debug properly. By the way, it really got worse on stage, the light got quickly stuck in a state, and it always stayed like this.

So back home :

1. I tried on the computer with bome midi translator -> Same things, with all other scripts off (no note off sending, no deactivate preset, etc ...). Some led changes are missing, while I can see that the good informations is sent out of Bome Midi Translator. And it happened that the light got stuck

2. I modified my script to work with x-touch mini, and I've heavily tested it, on the computer, and on the bomeBox -> Zero bugs ! Even if I tapped hundred time on the three buttons as fast as I could.

So I think either widibud or IrigBlueBoard is defective. I'm going to look for a better foot controller midi or usb, but really not bluetooth, I don't feel at ease with that technology for the stability I need on stage.

For my allNotesOff script, they don't fire at the same time. This foot controller is for the accordion player. The accordion is also midi, and the scripts block the note on the 3 channels of the accordion. When the player hit A, B or C a channel is open or closed. When a channel is closed, AllNotesOff are sent specifically on that channel (because sometimes she close the channel with still a finger on a key).

Thank you for the allNotesOff script. I'm going to replace my clumsy midiPanic script on another project with this one !

 

OK, for all notes off, I was less concerned about going out the right MIDI port and more concerned that the adjustment to the same global variable by multiple translators concurrently could cause problems. If you stick with the same MIDI controller, you might need to do some force delays if it cannot react fast enough to MIDI being sent for it's LED states. Although as you say, this might not be the controllers issue and maybe related to bluetooth latency although I'm pretty sure CME has put a lot of work into keeping bluetooth latency to a minimum. Personally I have not tested any bluetooth MIDI with either my BomeBoxe's or my PC.

I tried with latency, but it didn't work. This afternoon, I tested the blueboard in normal mode which toggle the led internally, and on the bluetooth of my computer, and I had the same problem of stucked led (in on or off state). So now I'm sure the trouble comes from the irig blueboard and neither the CME, neither the bomeBox, neither my script.

I looked it up and found other users complaining about this. Maybe contact IK Multimedia support? https://www.ikmultimedia.com/contact-support/mi/