Debugging MIDI issues

[ralmond]

I'm running wine-8.0 (Ubuntu repack 4) under Ubuntu 23.04
I'm trying to get an application called `FCB1010UnO.exe` running under wine.
I had some success before getting this app to talk to my external midi device.
Now, however, I'm not getting a connection, and the lights on the midi cable, which should indicate traffic is coming are not lighting.

The MIDI interface is being recognized in the drop-down list in the app. Also, in my pipewire viewer, I see the MIDI interface connected to the wine midi device.
I'm not, however, seeing midi devices listed in `winecfg`. I tried setting `winetricks sound=alsa`, but that seemed to make things worse (there is no `sound=pipewire` option).

Running with `WINEDEBUG=+msacm` doesn't show any activity when I'm trying to make my connection.
I do get the following messages when the app is first starting:
```
03ec:trace:msacm:MSACM_ReorderDriversByPriority
03ec:trace:msacm:MSACM_ReorderDriversByPriority RegOpenKeyW failed, possibly key does not exist yet
03ec:trace:msacm:MSACM_RegisterDriver (L"msacm32.dll", L"msacm32.dll", 0000000000000000)
```

What other steps can I try to find out where the problem is happening?

[angelmealey]

Hello,
I think you should debug with Wine logging. Enable debug logging in Wine to get more detailed information about the issue. In the terminal, set the WINEDEBUG variable to include MIDI-related logging:

Code: Select all

shell
export WINEDEBUG=+midi,+msacm
```

After setting the environment variable, launch the application from the same terminal window and observe the debug output in the terminal. This may provide insights into any errors or issues related to MIDI communication.