You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After opening midi ports using OS.open_midi_inputs() then disconnecting a midi device, the following error will be spammed in the terminal and editor debugger tab
ERROR: snd_rawmidi_read error: No such device
at: read_in (drivers/alsamidi/midi_driver_alsamidi.cpp:147)
Also tested on Godot v4.2.2.stable - macOS 11.7.10 - GLES3 (Compatibility) - Intel Iris OpenGL Engine - Intel(R) Core(TM) i5-4278U CPU @ 2.60GHz (4 Threads)
With no issue, so this appears to only affect the ALSA midi driver
The text was updated successfully, but these errors were encountered:
not-my-username
changed the title
"ERROR: snd_rawmidi_read error: No such device" When disconnecting midi device,
"ERROR: snd_rawmidi_read error: No such device" When disconnecting midi device
Jun 15, 2024
Tested versions
Reproducible all the way back to Godot_v3.1-stable_x11, when the MIDIDriver was added in this commit
Bug only effects Linux system where Godot uses the ALSA midi driver
System information
Godot v4.2.2.stable unknown - EndeavourOS #1 SMP PREEMPT_DYNAMIC Wed, 12 Jun 2024 20:17:17 +0000 - X11 - GLES3 (Compatibility) - NVIDIA GeForce RTX 3060 (nvidia; 550.90.07) - Intel(R) Xeon(R) CPU E3-1271 v3 @ 3.60GHz (8 Threads)
Issue description
After opening midi ports using
OS.open_midi_inputs()
then disconnecting a midi device, the following error will be spammed in the terminal and editor debugger tabAlso tested on
Godot v4.2.2.stable - macOS 11.7.10 - GLES3 (Compatibility) - Intel Iris OpenGL Engine - Intel(R) Core(TM) i5-4278U CPU @ 2.60GHz (4 Threads)
With no issue, so this appears to only affect the ALSA midi driver
Steps to reproduce
Run the project below, or use the code:
Then disconnect a midi device from you system
Minimal reproduction project (MRP)
v4.2.2.stable: Midi Device Disconnect Error.zip
The text was updated successfully, but these errors were encountered: