Upgrading from version 1.8.1 to 1.9.1 doesn't work

I need help. The configuration file you see for my XTouch Mini tablet was working with previous versions, and when I upgrade to this one, it doesn’t show anything. What could this be?
I’m using Mac OS X Ventura.
Thanks.

BehringerXTouchMini_CaptureOne20_v1.bmtp (26.4 KB)

Hi and welcome to the Bome community!

When you say it doesn’t show anything, do you mean that Bome MIDI Translator Pro does not open? Did you look in the menu bar at the top. I believe by default Bome MIDI Translator Pro starts minimized but you can change that in settings.

If this isn’t it then make sure you have given Bome MIDI Translator Pro access in Accessibility and Security and Privacy setting on your Mac.

Steve Caldwell
Bome Customer Care


Also available for paid consulting services: bome@sniz.biz
1 Like

Hello, what I mean is that it doesn’t output anything, there is no output, there is MIDI in, but the output part of the program that I have uploaded to you doesn’t produce anything.

It is then likely that you don’t have your aliases set up to point to the proper MIDI ports.

You can get to the alias definitions by using the MENU item ‘MIDI’ the ‘Edit Project Port Aliases’. The settings file that defines these aliases was likely overwritten in the upgrade. Once you re-establish them, it should work fine going forward.

You can learn more about aliases from this tutorial.

Steve Caldwell
Bome Customer Care


Also available for paid consulting services: bome@sniz.biz

I’m sorry, but I feel incapable of doing it without help. I don’t know how to implement it, and I’m about to abandon the project and try to implement another type of translator. Can you try the BMTp and see if it has output (keystrokes)?

Hi, I apologize. I didn’t look at your project file and now I realize you are sending keystroke outputs. I noticed the incoming MIDI messages on many of the translators are not correct. I fixed translator 1-3 in preset 0. I’m not sure why it even worked with version 1.8.1

The others still need to be adjusted.

Here is the detail on translator 0.1 as it is fixed.

You could also add a new action to ensure that your application if focused prior to sending keystrokes.

I created a new preset and translator for this (2.0).

You will have to change the outgoing action to focus on CaptureOne instead of Editplus though (I don’t have CaptureOne on my computer0.

BehringerXTouchMini_CaptureOne20_v1-sjc.bmtp (27.1 KB)

Steve Caldwell
Bome Customer Care


Also available for paid consulting services: bome@sniz.biz

Thanks Steve,
If I load version 1.8.2 build 853, everything works perfectly without having to modify my .bmtp file.
The problem is that often version 1.8.1 doesn’t load in Ventura, or if it does, it doesn’t appear at the top of my Mac’s taskbar, and I can’t activate the MIDI capture checkbox, which means no keystrokes are output when I press the buttons on the mixer.
Actually, there’s no need for the capture one.app program, since the output is keystrokes, and you can check for output in any browser or text editor.

This is strange because the translators are definitely not correct in your original file. Did you try the file I sent you for Exposure?

You are looking for the value of pp which is a local variable and by definition the value is not defined so it can be any random value unless it is initially set.

In section 10.3 of the manual you will see this.

Note that Local Variables are not pre-initialized: if you don't define them in the
Incoming Action, and you don't set them to a value in a Rule, a Local Variable can have
any (random) value

So it is perhaps by chance working on 1.8.1.

Can you tell me the build number your are using on 1.8.1? If it is not build number 1064, please retry with build number 1064 which should be in your account page for download.

The please look at Systems Setting then Privacy & Security and make sure Bome MIDI Translator Pro has permissions there.

Finally make sure Bome MIDI Translator Pro is not focused when you trigger the translators or go to MT Pro Settings, then Options and make sure “Suppress outgoing keystroke when focused” is unchecked.

If you want to check whether the keystroke is being sent, you can open the log window and check the “Outgoing” box. If it is being suppressed, it will tell you there.

If none of this works, please get back to me with your findings. It would be helpful if you provide a screen shot of your log window.

Steve Caldwell
Bome Customer Care


Also available for paid consulting services: bome@sniz.biz