Missing MIDI devices and uncooking bug

Bugs
1

Tested on both latest 2023 and 2025, windows 11.

This bugreport is two-fold:

a) with many MIDI In DATs causing heavy lost frames when they refer to a missing device
b) uncooking their parent doesn’t stop these lost frames, only bypassing

Steps:
0. Edit /local/midi table so there is an invalid indevice

  1. Create a Base COMP
  2. Add a bunch of MIDI In DATs, like 20 (not an issue with CHOPs)
  3. ! FPS starts dropping
  4. Uncook the base COMP → FPS is still tanked
  5. Bypassing alleviates the issue
2

The example/test doesn’t have to be so extreme actually.

Here I added a Hog CHOP to put the system at the brink of losing frames (empty project), still stable 60 frames when indevice column is empty.

Then writing something random into the cell, there’s -15 fps immediately.

image
image1734×765 48.5 KB

@snaut bringing your attention on this

3

bumping this again

5

Hey @function.store ,

Sorry this issue got missed. We are able to reproduce and are investigating the behavior.

Varad

1 Like
7

This was happening due to the DAT attempting to open the MIDI port each frame but failing to do so. It will be fixed in builds 2025.3904+.

For now, in addition to bypassing, toggling the ‘Active’ parameter off also restores the project FPS.

Varad

1 Like
8

Great news, is there a quick and easy way to automatically bypass the offending operators?

9

I’m not sure of another workaround other than just bypassing or turning off Active on the DATs. Depending on your case, maybe you could use a script to do this if a MIDI In DAT goes into a warning state due to unable to open the MIDI interface.