Unwanted delay in sending MIDI message

Hi Florian,

1. I’m running 10.12
2. I have and it didn’t solve the problem
3. The delay *is* reflected in the timestamps on MT Pro
4. No network MIDI (although I will be incorporating that into my setup eventually and I turn off my WI-FI during performances/testing.
5. I didn’t try turning off automatic time and date
6. The computers are set to never sleep (etc.)

Thanks,
Mobley

Thanks Steve,

Unfortunately, I have a run of performances coming up, so I’ll be leaving things in their current stable state for a while, but next time I have some time off, I plan to try digging into it again.

I use the Windows version.

In Windows, you can change the “Task Priority”. I found running at a higher priority MTP became more reliable and had less random delays.

Can you do something similar in IOS?

Hi,
I’ve never seen performance issues with MT-Pro either on Windows or Mac. From Mac you might want to open a terminal window and the type

man renice

renice is a utility to alter the priority of a process.

To find the process ID for MT Pro you can type

ps -ax | grep -i bome

I hope this helps.

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

I have this same issue on my B computer on macOS. Main computer works fine. On B computer. One specific message randomly gets a 10 sec delay. If I bring MT in focus or I think just changing the focus away from the actual focus gets rid of the delay. If I run MIDI monitor, I see the message delayed message being sent. I will try changing the priority and see how that works. Thanks.

I’m curious to hear how this goes…I can’t remember now whether I ever actually fixed this issue in my project

@Mobley

There have been several releases of MT Pro since this was originally reported. Please install the latest version and see if the problem persists. If it does, please let us know what model of Mac you are using and version of MacOS. Also post your project file here or send it privately and we can take a look to see whether we can duplicate the problem. Please indicate which MIDI message is getting the random 10 second delay in your project file.

Steve Caldwell
Bome Customer Care


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

… so, I was on Bome 1.8.4. I had some extended delay on note triggered by a 100ms timer. At this time, I still have the issue. I have done the following which hasn’t worked yet.

  • re-installed Bome
  • upgraded to MT 1.9.0
  • I’m using an iConnectivity MIDI interface and switch the A and B computer ports

I want to try to renice, but I’m not sure of the command line to use.

I’m on a MacBook Pro 15” 2018 2.9GHz 6-core i9 with 32 GB of ram on Catalina. ( I hate this version of the MacBook Pro.)

Fortunately this happens only on the backup computer.

Anyone knows the renice command to use?

I’ll let you know when this is solved.

Hi,
Thanks for the additional information!

If you move the B Device Connector to computer A and the A device connector to computer B does the problem move to the other computer? If the problem moves, it is likely not a performance issue with the specific computer, rather a routing/configuration issue.

How is the MIDI routing on your iConnectivity set? Is the problem with a specific attached controller? In what direction and what controller (port) is the delay? To me it sound like maybe you might have a MIDI loop somewhere that causes things to hang and then eventually reset itself.

Maybe if I can get a sense of

1 - What is connected to where and how
2 - What the iConnectivity MIDI routing is set (including filters and re-maps if any)
3 - What the project file looks like
4 - What device(s) are involved in the occasional 1 second delay.

Steve Caldwell
Bome Customer Care


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

I was having the delay issue I’m on the timer for a while only on one of 2 computers in a redundancy system. I ended up having the problem occurring on the main computer as well as the backup. After trying many things, it seems like if you give the computer enough time to start before and between opening applications the problem is solved. I started doing that a few shows ago and haven’t seen the problem occur since.

Basically, my solution is to give your computer enough time to boot in between opening applications.