Hi Bome forum,
My first go with the Bomebox:
Not usable so far….
Marked as spam
Hi and welcome to the Bome forum! Most of the instability issues we have seen with Bomebox stem from how it is getting it’s power. Do you have it connected to a hub? If so, I suggest you connect it directly to a tested stable power source instead. Some hubs have special charging ports that although are great for fast charging devices, are terrible power sources for Bomebox. My recommendation is you power it through USB power adapter instead and then retest.
I anticipate you have already validated that your project file works on MT Pro before transferring to your Bomebox. I will raise your concern to Bome as well if they have any troubleshooting tips.
Bome Q&A Moderator at Independent Bome Programmer.
Marked as spam
Thanks for the feedback, great idea. I will connect it to a dedicated charger. To be fair, I have it connected to a powered USB hub, but I also have an Analog RYTM, Fastlane USB, Launchpad Pro, Faderfox PC44, and a USB lamp. 😄 I will try it later today.
Connecting it direct to a USB charger seemed to help a bit. I received slightly more light feedback to my Launchpad Pro, but only CC messages – none of the SysEx. No messages from my Launchpad are being received by the Bomebox. Clock and transport gets passed, but not much more. Most of my project is not working. It works perfectly when using Bome on my mac. I’m an experienced IT/network guy, and I know my way around my synths and MIDI. As such, all the basic and advanced settings in the Bomebox make perfect sense to me – I don’t see anything wrong there. It seems to be set as it should be. As for troubleshooting it, since there is no activity log, no MIDI monitor, and no way to edit the translators on the Bomebox, I have no clue where to start. =/
Go the “routing page” and see if you can see the various devices. If you see them assign them to the same aliases as your project in MT pro.
Marked as spam
Hmmm yeah, naturally that was the first thing I did when I turned it on and uploaded my project. I’m a bit further ahead than that.
Didn’t mean to offend you. Just making sure all the basics were covered. I think Florian will need to provide assistance from here. I’m good with Q&A but certainly no Bombox expert. I have one though and fortunately it works perfectly for me.
No offense at all! Sorry if I came across that way. I appreciate your help for sure.
Have you received your box just this week? Then you’re among the first to have received an updated firmware. Despite all our testing, it is still possible that you’re experiencing a bug in the new firmware.
For nailing down the problem a bit, could you please do this: when you get that situation again where no MIDI is relayed by the BomeBox, try pressing the PAIR button and report here if that helped at all.
We will create a web page asap where you can download the original and the latest firmware, so that you can switch and try (and then, switch back, if wanted).
Marked as spam
Thanks Florian. I will try the pair button tomorrow, will also be very happy to try the original firmware. I received it just today, so I guess it’s the new firmware.
I’m not using the DIN ports yet, only USB. I wanted to try things out first without changing the config that I have on my computer. I’ll spend more time with it tomorrow and report back.
Just in case, you can try the old firmware here:
But be careful to not disconnect power when upgrading (or downgrading)! It takes approx. 1 minute.
I downgraded and it’s the same. My configuration is complicated and this doesn’t look like it’s going to be easy to get working. MTP works perfectly. Not sure what I can do here. I still don’t know where to start.
Have you tested this with a Launchpad Pro? There are three virtual MIDI ports on a LP Pro, which all get detected by the OS as separate MIDI devices: Live port (ableton), MIDI Port (for DIN connections), and Standalone port (for normal USB MIDI usage). They get enumerated in that order and listed in MTP in that order. MTP also lists them with their port names so it is easy to determine which one is which. The Bomebox does not. I’m trying to connect to the Standalone port. After trying each one and finally determining which one it is (#2, which is in a different logical order than it should be), I restart the project, which is supposed to light up the pads according to how I’ve configured it. Most of the light instructions are SysEx. Nothing gets lit. Also, the Bomebox does not pass any incoming MIDI from the Launchpad to any of the instruments. I’m not sure how much time I can spend on this….
Please understand that the BomeBox is a device and a computer is a computer. The BomeBox is not running Windows or macOS. So it\’s inevitable that you\’ll see some differences. MTP displays all MIDI ports in alphabetical order. The BomeBox puts them in order, too, but depending on the hardware, subdevices might be displayed with an index number instead of a name. The order of index numbers is as reported by the device.
Using the alias system, it is fast to change from index #1 to #2 and try all 3 different available ports.
And, as said via PM, please send me your project file so that I can have a look and try it.
Now for finding out what is going on, the best approach is to start with a very simple project. Or just a pass-through to a computer using Bome Network. Adding routes to a computer can give you a powerful tool for debugging your project.
Also, you can try the \”Launchpad Pong\” project file delivered with the BomeBox. Not sure if it works on a Launchpad Pro, though. It works on the other Launchpads.
Thanks for working with us on this.
Many thanks, here’s what I’ve determined from my testing:
I was setting a global variable upon initialization of the project to establish the MIDI channel for my Launchpad Pro, since I have a ton of translators for it in my project. It became clear that the Bomebox doesn’t like that for some reason. When I hard coded it, all of my outgoing translators started working, so yay for that. I would, however, like to be able to use that global variable because of the number of translators I use for the LP Pro, so I would like to be able to change its channel with a variable. I hope that can be resolved.
More importantly, though — none of my incoming translators that send SysEx to the Launchpad are working, and that means that none of the lights on the Launchpad are operating. I have directly connected the Launchpad to the Bomebox, with nothing else connected, and still the SysEx messages do not work – so that suggests either that it’s a problem specific to the LP Pro, or that SysEx doesn’t work on the Bomebox, which I rather doubt. Have you used SysEx to light the pads on a regular Launchpad? I tried the Pong project (which only uses CC to light the Launchpad) and it is working for me.
So my biggest issue is that SysEx is not working.
I have a launchpad mini and I’m sure it is getting sysex just fine with Ableton connected through Bomebox. Ableton uses sysex for changing modes. However my Bomebox is packed for the next few weeks while I move so will not be able to test it for another few weeks. I’m pretty sure I’m on the old firmware as I bought my unit maybe a month or two after it was released.
I’ve tried both firmware versions, and my LP Pro does not receive any sysex from the bomebox.
No, Ableton does not natively support sysex at all. Much to the chagrin of many….
Ableton sends Sysex when changing modes. I know that because 1) I have monitored it 2) I have looked at the support scripts. It really depends on the controller you use. My Launch control both sends and receives sysex from Ableton Live.
Well, maybe the python MIDI Remote Script for the LP sends sysex to the LP to change the mode, but you cannot send or receive sysex in Ableton unless you use Max.
In any case, I do not wish to relay sysex messages from Ableton through my Bomebox. I want my Bomebox to send sysex. I don’t want to use a computer in my setup, which is why I bought a Bomebox, and the Bomebox is not sending sysex to my Launchpad Pro.
OK wish my Bomebox wasn’t packed or I would try to duplicate the problem.
=D I appreciate your commiseration. I await feedback from Flo-b-wan…
The solution is to use on activation of current preset (or on project file is opened).
Regarding Sys Ex, I’ve made some tests. It works fine for me with a Launchpad Mini. The attached project file will do 2 things:
1) upon start (on activation of current preset), it sends a ID request as a Sys Ex message to the Launchpad. It will return a Sys Ex message with its ID. If you have connected the BomeBox to a computer using Bome Network, you can receive the Launchpad’s reply.
2) upon pressing any button on the Launchpad, it’ll show a scrolling message on the Launchpad, invoked by a longer Sys Ex message.
Note that the attached project does not work with an original Launchpad. Must be Mini, S, or Pro (I assume).
Hope that helps some!
Marked as spam
Could you elaborate on this more. I’m not sure what you are saying here and why it is a problem.
”I’ve made some tests. Found out that you were using the Enable Processing incoming action for initialization. That’s not a good idea, it’s only called when starting MT Pro (or the BomeBox), but might be happening before loading the project. It’s also called when returning from panic mode or when processing is enabled again by way of an outgoing action.”
There are 3 similar incoming actions:
Disable/Enable Processing –> Processing is enabled
Does this clarify what I meant, Steve?
That’s clear, thanks for pointing that out Florian. I will adjust my project accordingly, test with your project, and report back. many thanks for the easter sunday help
oh, one more clarification: Ian had sent his project file to me in private. That’s how I knew how he had implemented things.
After making the switch from Enable/Disable Processing to Preset Activation/Deactivation, all my problems seem to be solved and the Bomebox is singing as I’d hoped it would. I haven’t been able to test with my instruments at my studio, but I’m pretty sure it will be working. All sysex light instructions are functioning and my project looks like it’s working exactly as it did in MTP. Thanks a ton, Florian – my deep gratitude for your help over the holiday, and your excellent contribution to MIDI wizardry.
One thing — the Launchpad Sysex Test project crashes the Launchpad Pro when you switch to the Device Mode page. The thing just restarts. I didn’t look into it too deeply, but I since I never saw a scrolling message, I’d expect the sysex that is supposed to run the message may have a different effect on the LP Pro. I don’t see anything like that happening on my project, so I’m not worried, but thought you should know…. =D
Clear, Florian. I guess I have been doing things correctly but didn’t realize about the possible side affects of the functionality that I never used.
Glad to see Ian is up and running!
Happy Easter everyone!
you too steve, many thanks for your help
Great! crossing my fingers that it’ll work in the studio, too.
Well as I understand LP midi was modeled after LP-S but I’m pretty sure there are some differences in Sysex with LP pro.
I would have to check the manual.
Yeah, the Pro is a different beast with the new modes and such. I’d not be surprised if there are differences in the sysex instructions.