Cpu core 1 spiking because of a virtual midi port

Bome Products
1

Hello, so I have a device from Intech studio, the midi port for this device is ‘Intech Grid Midi Device’

I have a preset on BMT set as follow :

  • input port : Intech Grid MIDI Device
  • output port : Intech from BMT (it’s a virtual port I created with loopmidi)

I created that virtual port so that I can pass to cubase the translated midi data, the issue is that as soon as I start moving the fader, the core 1 of my cpu get maxed out at 100% and my cpu fan get spinning like crazy, as soon as I release my finger from the fader and stop transmitting data, the cpu load decrease.

I tried closing bome midi translator, there is no more cpu spikes
I also tried disabling the virtual midi port ‘Intech from BMT’ and it stops the cpu spikes

Are you familiar with such issues ? It’s like there is too much data going to that virtual port

image
image1030×313 13.9 KB

image
image603×377 43.3 KB

2

It is possible that Cubase is reading MIDI from both the Intech Grid device and your loopMIDI device. It is also possible that you are sending other MIDI messages to Cubase. I would need to look at:

  1. Your input port configuration in Cubase. Make sure that Intech Grid is not selected
  2. Your output port configuration in Cubase. Make sure that your Intech from BMT is not selected.

You can find the MIDI port setup in the Studio setup menu of Cubase.

And if you post your project file, I can have a look there as well. I assume you are using LoopMIDI ports so that you can see the port names in Cubase. Although with LoopMIDI two system calls are made for each message where with Bome MIDI Translator Virtual ports (ie.BMT1) only 1 system call is made. I doubt if this would make enough difference to make your CPU spike however. I suspect it is a MIDI loop which is easy to do by mistake using LoopMIDI ports.

Steve Caldwell
Bome Customer Care

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

I made sure those ports are disabled on cubase, it seems to fix the issue for now. I am not sure if they were disabled before or no when I was having the issue this afternoon tho

thanks

4

OK, if it comes up again you can re-check. I suspect that Cubase was opening both the loopMIDI input and output port which was causing a MIDI loop and driving your CPU usage up.

Steve Caldwell
Bome Customer Care

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