Bome Midi Translator project does not work the same way as on the old PC

adriangarciaselva · August 18, 2025, 11:42am

Hello, everyone! I have a problem with Bome Midi Translator that I don’t know how to solve, and it’s driving me crazy.
I bought a new PC (Intel i7-13620h processor, 32 GB of RAM), but after installing the software I use (Traktor 3 and Bome Midi Translator) and the drivers for my Midi controllers (Xone K1), I find that the Bome Midi Translator project doesn’t work like it did on my old PC. Specifically, some Midi Out messages are not being sent correctly between the controller, Traktor, and Bome Midi Translator, which mainly affects the operation of the LED lights on the Xone K1 controllers (basically, they don’t respond as expected). I know the problem must be in the Bome Midi Translator settings, because when I use Traktor and Bome Midi is closed, these problems disappear. However, not using Bome Midi is not an option for me, as I would like to use the Bome Midi project I used on my old PC to improve my workflow.
Is it possible that, despite importing the project from one PC to another (and also the settings options), some parameter has been changed that is causing this problem?
I have tried absolutely everything, from using various versions of Traktor to using the software with Windows 11 and also Windows 10. I have also used an earlier version of Bome Midi Translator, but that has not solved the problem.
It should be noted that the original project was configured with version 1.9.1 (build 1060) of Bome Midi Translator, and the current version is 1.9.1 (build 1064).

I know it’s a very difficult problem to solve, but maybe I’m missing some simple issue that is causing the problem. Any possible clues would be greatly appreciated!

Thanks for reading and best regards!

SteveC · August 18, 2025, 3:44pm

Hi,

The most common issue for this is that you may have other applications also trying to open the same port as Bome MIDI Translator Pro . On Windows, only one application or controller can access a given port. They cannot share access to the same port.

I would need to see your project file and have you describe specifically which translators seem to work fine and which ones do not. Maybe one or two examples. It would also help to know how you have assigned your aliases and what ports are being used on Traktor. Maybe an example of a specific translator that is not working correctly, would help.

Steve Caldwell
Bome Customer Care

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

adriangarciaselva · August 19, 2025, 1:54pm

Hi Steve,

Thanks for your reply and for your time. Unfortunately, the problem I’m experiencing is very difficult to figure out (I actually wrote this post as a last resort, knowing that it would be very difficult to find the solution).

Actually, all the translators are working correctly. The problem I’m experiencing seems to be in the communication of MIDI Out messages between Traktor, Bome, and the Xone K1.

Basically, my project has a few translators that perform extra filtering of some MIDI messages between Traktor and the Xone K1 controller, so most of the MIDI commands are in Traktor’s own mapping. The MIDI configuration of the project is as follows: in Traktor, in the controller manager, the MIDI input and output ports are Bome Midi Translator Virtual Port 1; in Bome Midi Translator, the MIDI Router is connected as follows:

Xone K1 In → Bome Midi Translator Virtual Port 1 In
Bome Midi Translator Virtual Port 1 Out → Xone K1 Out

This is the configuration I use on my old PC and it works perfectly on that same computer.

The problem I am experiencing (and which only occurs when Bome is open) is that, with the new PC, some of the LED lights on the Xone K1 do not light up or change color when they should. For example, let’s imagine that Traktor effect 1 is off, so the “A” button is red. When I press the “A” button to activate effect 1, the color of the button changes to green. However, sometimes this does not happen, and even though effect 1 has been activated in Traktor after pressing the button, the “A” button remains red (it should be green, since effect 1 is activated).

This happens randomly or without following a specific pattern, so I am unable to isolate the problem to analyze it properly. I have tried almost everything I can think of, but nothing has worked. The only logical reason I can think of is that Traktor’s “Send monitor state” message (which is essential for activating lights/color changes) is sometimes processed before the MIDI Out itself, which means that the light status update occurs before the change and, therefore, the color change does not occur. Even so, I don’t find this explanation very coherent either.

If anyone can offer any other possible explanation, it could be a good clue to help me find the source of the problem. Of course, I understand that the problem goes beyond Bome Midi, but, as I said before, turning to the experts at Bome was my last resort

Once again, thanks to the community and staff for everything!

Best regards!

SteveC · August 19, 2025, 2:15pm

Hi, here is where the log window of Bome MIDI Translator Pro could be helpful. Turn on Logging and then check MIDI IN, MIDI OUT, Incoming, and Outgoing. Press the A button and if the LED does not light, then record (copy and paste) what is seen in the log file. Then we should understand what is going on.

Alternately, you can try posting your project file and maybe I can help you figure it out.

Steve Caldwell
Bome Customer Care

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

adriangarciaselva · August 20, 2025, 11:39am

Hello again, Steve,

Thank you for your help. I followed your instructions and created two documents with the Log Window information for two errors that I managed to capture. The problem with viewing the Log Window directly is that, in my case, since I have to use Traktor’s “Send Monitor State” command, this window logs a large number of messages that are sent at the same time (the “Send Monitor State” command in Traktor is a global function that “updates” all available MIDI Outs, so a large number of messages are sent). Even so, these messages are all passed directly through the MIDI router, activating very few translators, so there should be no problem at the processing level.

That’s why I’ve created two documents that are easier to analyze. I’ve provided them in the following links, along with a description of each error:

Error 1 link: LED does not turn off - Google Sheets. The button is off and has no color. The button is pressed and the effect is activated, the LED lights up red; the button is pressed again and the effect is turned off, but the LED does not turn off, it remains red (it should turn off). Therefore, in this problem, the error occurs after the second press of the button (it is indicated in the document). In this error, the MIDI IN and OUT for the red color are the same message: “9D 34 7F” for on and “8D 34 00” for off (note E3).
Error 2 link: LED does not change color - Google Sheets. The button is lit red, indicating that the effect is off. The button is pressed and the effect is activated, but the button turns off (no color) instead of turning green. In this case, the error occurs on the first press. The MIDI In is 9D 2A 7F for on and 8D 2A 00 for off (note F#2). For colors, in this case red would be MIDI Out 9D 2A 7F (note F#2), and green would be MIDI Out 9D 72 7F (note F#8).

There are three “tables” in both documents. The first one is colored blue, which corresponds to the Log Window record of the correct operation of the commands if the rest of the MIDI Out messages are deleted, so the controller does not light up, except for the button that has been configured for that specific operation (in this case, when I disable the rest of the commands that allow the buttons to light up, I have never been able to reproduce any of the errors).
The second table is colored green and shows the Log Window record of correct operation when the problem does not occur and all MIDI Out messages are operational.
The third column is colored red and shows the Log Window record when the problem has occurred and all MIDI Out messages are operational. In these tables, I have included a column titled “Location of the message in the Log Window register,” which shows the correspondence between the messages in the three tables (blue, green, and red) using letters, to make it easier to identify the sequence of messages between the three situations in each error.

I have reviewed these logs and cannot find an explanation for the problem. For example, in error 1 (the red LED button does not turn off), the message log is exactly the same in the green column (correct operation) as in the red column (incorrect operation) from the moment the button is pressed, which is when the error occurs (row 204). Therefore, although Bome Midi records the same messages in the same sequence, in one situation the button turns off correctly and in the other it stays on red incorrectly.

I am also providing the file corresponding to the Bome project in this message, in case that is where the problem lies.

And again, the most curious (and maddening) thing is that on my old PC (i7-7700HQ, 16 GB RAM), everything works perfectly (and I have used this project for many hours, so I can assure that it is stable and has never given a single error).

Could there be a difference in the way the processor of the new PC (i7-13620H) affects the way MIDI messages are processed?

As I said in previous messages, I think this problem is very complex to solve, but I greatly appreciate the help and interest you have shown.

Thanks again and best regards!
Bome Project with led issues.bmtp (78.0 KB)

SteveC · August 20, 2025, 2:20pm

Hi,

Could you show me how you have your aliases set up and which virtual ports are used for everything?

Do you have your aliases set up the same way on both the old project and the new project?

I see you have XONE K1 and XON K1 :(2) so it is clear these are your Xone controllers.

You are also using Bome MIDI Translator Virtual 1 In and Bome MIDI Translator Virtual 1 Out but without aliases. What are they attached to?

You are using Bome MIDI Translator 4 Virtual In and Out. What are these connected to? You are also using Bome MIDI Translator 2 Virtual In and out. What are they connected to.

Here are the aliases that you are using which I’m not sure how you have them assigned?

From your evaluation it appears that you are sending note-off messages in the form of 8x yy zz instead of 9x yy 00. So this is why the LED is not turning off.

I suspect the crux of the reason your project is not working is due to alias assignment and that you probably have the proper note-off format in your translators for certain aliases.

I suspect if you get your aliases set correctly things will work but you really should spend some time reviewing these two tutorials and adjusting your project file for better structure.

You can learn more about aliases from this tutorial.
For more information about device selection, see this tutorial.

In summary, the processor or platform should make no different but I suspect this is a problem with how you have set up your aliases on each computer which allows the working computer to use translators for note-on and note-off messages where the non-working one is using MIDI thru paths instead resulting in the wrong form of outgoing note-on or note-off messages.

If you trun on Outgoing and Incoming in the log window, these messages are handled by translators that way you can see which messages are handled by translators. If you see MIDI IN and MIDI out with not incoming or outgoing, these messages are handled by MIDI thru paths.

You can use a filter string in the bottom of the log window to restrict the messages you want to look at so that you don’t have to look at all messages. For instand, for the first message type you might filter on “34” to see only the problem note messages.

If you only want to see translator type message using preset 3, then you could filter on “3.”

Steve Caldwell
Bome Customer Care

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

adriangarciaselva · August 22, 2025, 6:58am

Hi Steve,

Thank you for your reply and for the material. I already watched these videos a year ago when I started using Bome Midi. I also reread the manual a few times before posting this entry (I even searched for similar posts in this forum). But I haven’t found anything similar to the problem I’m experiencing.

From your reply, I think we’re straying from the focus of the problem.

In the project I provided you with in my previous message, there are no aliases because I don’t usually use them in Bome Midi. Since I only use a small number of MIDI ports, I don’t think I need aliases to facilitate project management. If I understand the concept correctly, aliases allow flexibility and ease of use of the project on different computers and by different users, but they do not provide any different functionality with respect to the correct routing of the actual MIDI ports (which is what I do in my project). Even so, I have modified the project, adding the following aliases and setting up the following MIDI routing (I am also attaching the project file to this message):

If I’m not mistaken, I think everything should be correctly configured in terms of aliases and port routing (in Traktor, the MIDI input and output ports are Bome Midi Virtual Port 1 and 2, corresponding to each Xone K1).

As I feared, the use of aliases has not corrected the erroneous behavior of the Out messages and the LEDs. In fact, I can confirm that, surprisingly, the use of aliases has aggravated the problem, with the LEDs now performing even worse. This has left me with no logical explanation for the problem.

As for sending note-off messages in the form of 8x yy zz, this is how Traktor sends them by default, since, as I mentioned earlier, these MIDI Out problems I am experiencing are not related to any translator or project preset, as these messages are only passed through the port router to the different input and output devices. In other words, the message in the form 8x yy zz is not processed at any time. Furthermore, as I showed in the document “LED does not turn off”, the blue columns (columns A-D) contain the original command sequence that works correctly, in which the message with the format 8x yy zz always works and turns off the LED.

I’m starting to think that this is actually an internal problem with Bome Midi Translator. If I assign the Xone K1 device as the MIDI output port in Traktor, then all MIDI Out problems are solved and all LEDs work perfectly. This is why I suspect that the problem lies in the way Bome Midi manages the sending of messages through the port router. But that doesn’t explain why my project works perfectly on the old PC.

Best regards!
Project problem with port aliases.bmtp (76.9 KB)

SteveC · August 22, 2025, 1:57pm

Thanks for taking the time to do this and I’m sorry we haven’t figured it out quite yet.

Let’s go to your original project file then. I suspect that on your new PC, Traktor is configured differently than your old PC.

Please do the following.

Open your project file and make sure it is set up correctly with Traktor

In your log window, check MIDI IN, MIDI OUT, Incoming and Outgoing.

Press Encoder 1 twice (xD 34 xx) where x = 8 or 9 - Error 1 issue
Press Button 11 twice (xd 2a xx) where x = 8 or 9 - Error 2 issue

The objective is to see how Traktor reacts to these button presses.

Do it both on your old system and your new system and compare.

Send the entire log window results of both tests (Control A and the Control C to copy) then Control V to paste. I can filter the results you send so you don’t need to put it in a spreadsheet.

If you want, you can clear the log window so that the other spurrious messages do not show up but don’t worry about it. I will focus on the messages that you are having problems with.

Also if you want to only see note message for error 1, you can put “34” in the filter window of the log and see if there are extraneous MIDI messages coming or going out that maybe you have not captured before.

Perhaps there is some other message that is causing the LED to stay red.

I suspect Traktor is set up to toggle LED feedback on your old system (working) and for momentary on your new system (non-working) . But if you share the results I should be able to tell.

I ran this simple test project that uses global variable ga to toggle the state of LED 1 (red and off) and button 11 (red and green). I’m using a Xone K2 which is similar to the K1 but has a sound card built in as well.

So I suspect that the issue is probably with the way Traktor is set up for MIDI feedback on your new system and not an issue with Bome MIDI Translator Pro (but we shall see after your test).

Again, the below is just a test file to test the toggle function of both buttons and not related to your original project other than a way to test the XONE K1 or K2.

XONE-K2-Test-2025-08-22.bmtp (1.4 KB)

Steve Caldwell
Bome Customer Care

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

SteveC · August 22, 2025, 3:45pm

Perhaps if you put in translators for the 2 notes in questions instead of using MIDI thru, it will work. Put a delay on the outgoing action of the LED. So far, I’ve tested MIDI thru with my controller and haven’t found any issues. Also make sure that Traktor is not sending directly to your Xone K1 and that it always goes through Bome MIDI Translator Pro .

There is no reason I could think of within Bome MIDI Translator Pro why it should not work the same on both PCs given everything else is configured the same.

Generally, if things happen “randomly” things are very difficult to troubleshoot. I usually start disabling translators and removing MIDI thru paths to see if things happen less often. I notice you use timers a lot.
The might cause some “randomness” if they are asyncronous so maybe try disabling them while testing to see if that helps. I don’t see any tied to notes, however.

It is always difficult to diagnose a projects written by someone else, especially if it is not well documented. I really have no ideas on why you use the global variable for and what a lot of these translators are supposed to do. Sometimes when I read my own projects I have the same issue so I try to document everything within the translators using the comment “//” marks.

Finally, I usually try not to use MIDI thru paths as they have bitten me before.

For instance this rule

exit rules, skip outgoing action

will essentially disable the swallow option so if there is an outgoing action (other than None), the MIDI thru message will go through. Swallow only works if:

The outgoing action executes
or
the outgoing action is none

Otherwise, the incoming message will be passed using the MIDI thru path. Maybe a MIDI thru message is ‘sneaking by’.

Steve Caldwell
Bome Customer Care

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

adriangarciaselva · August 22, 2025, 5:03pm

Hello again, Steve.

I greatly appreciate your time and dedication in helping me find a possible solution.

Following your instructions, I have captured the messages displayed in the Log window on both the old and new PCs, interacting with the two buttons we discussed (notes 11 and 34). As there are a lot of messages, I am sending them in separate files:

New pc - Note 11 with Traktor MIDI Out to Bome Midi Virtual Ports (error).txt (21.0 KB)

New pc - Note 34 (encoder) with Traktor MIDI Out to Bome Midi Virtual Ports (error).txt (22.0 KB)

New pc - Note 11 with Traktor MIDI Out to Bome Midi Virtual Ports (no error).txt (33.2 KB)

New pc - Note 34 (encoder) with Traktor MIDI Out to Bome Midi Virtual Ports (no error).txt (22.8 KB)

Old pc - Note 11 with Traktor MIDI Out to Bome Midi Virtual Ports (no error).txt (37.3 KB)

Old pc - Note 34 (encoder) with Traktor MIDI Out to Bome Midi Virtual Ports (no error).txt (19.7 KB)

There is one issue that has raised some questions for me, and that is the number of messages that are recorded by the Log window when the Bome Midi Translator ports are enabled as MIDI output ports in Traktor:

When the Bome Midi Translator virtual ports are set as MIDI Out devices in Traktor, up to 350 messages are sent per button press (this occurs on both PCs).

Instead, when the Xone K1 is used as Traktor’s MIDI out ports (keeping the Bome Midi virtual ports as input ports), the number of messages recorded in the Log window is drastically reduced:

These two documents show the messages captured by the Log window when the Xone K1 is set as MIDI out ports in Traktor:
Old and New pc - Note 11 with Traktor MIDI Out to Xone K1.txt (432 Bytes)

Old and New pc - Note 34 (encoder) with Traktor MIDI Out to Xone K1.txt (430 Bytes)

Is it possible that Traktor generates a loop between the MIDI in and out ports selected in its configuration?

In any case, this does not seem to be the problem, as the same thing happens on the old PC and I do not experience this issue.

Regarding Traktor’s LED configuration, the software does not really allow for many options in this case.

As for Traktor not sending directly to the Xone K1 and always going through Bome MIDI Translator Pro, this is really where the problem occurs. If Traktor sends directly to Xone K1, all the LEDs work perfectly. When Traktor has the Bome Midi virtual port as its MIDI Out device, then random failures occur.

I had considered adding timers to delay the sending of the “Send Monitor State,” but I would like to know why the project works differently on both PCs.

Regarding the translators in my project, I have tried disabling all translators and presets, and this has not solved the problem. That’s why I think it must be something related to MIDI routing.

Finally, as for not using MIDI thru, that’s not possible, since my Traktor maps have more than 1,000 commands, so transferring everything to Bome MIDI would be practically impossible.

Once again, thank you for everything, Steve!

Best regards!

SteveC · August 22, 2025, 7:08pm

Interesting, so it seems that in some cases Traktor is sending duplicate messages.

Try the following. I have added translators to suppress note off messages for notes 0x34 and 0x2a from the Xone device on Channel 14. Maybe these note-off messages are getting Traktor confused.

I’m not sure why Traktor would send more messages when using Bome MIDI Translator Pro. There indeed could be a MIDI loop somewhere. The likely culprit here would be loopBE as the MIDI routing in Bome MIDI Translator Pro router looks fine. Of course there could be a translator or preset that has some incorrect routes causing a loop.

It would be interesting to see what the extra messages that you see are.

Of course if you want to manipulate messages from Tracktor using Bome MIDI Translator Pro you will need to use virtual ports out of Traktor.

Using your original (working) project.

Bome Project with led issues–sjc.bmtp (78.5 KB)

Steve Caldwell
Bome Customer Care

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

SteveC · August 22, 2025, 7:34pm

Here is my evaluation of your Working and Non-Working (Note 34) logs with the other messages removed. I’m not sure why one is working and one is not as they appear to be sending and receiving the same MIDI message for note 34. Hopefully I evaluated the right files or you gave me the right (non-working) file. You also had a working New note 34 file but I didn’t look at that.

I’m scratching my head on the orange cells which seems to be sending a duplicate message from Traktor.

Steve Caldwell
Bome Customer Care

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