https://bugs.winehq.org/show_bug.cgi?id=49099
Bug ID: 49099 Summary: MIDI events sent to all devices at once Product: Wine Version: 5.5 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winealsa.drv Assignee: wine-bugs@winehq.org Reporter: jpm@it-he.org Distribution: ---
I am using an old version of Cakewalk SONAR to control a large number of synthesizers. These are connected via an ESI M8Uex MIDI interface, which appears to ALSA as 16 MIDI outputs and outputs over a single USB connection ("ESI M8U eX - ESI M8U eX MIDI 1", "ESI M8U eX - ESI M8U eX MIDI 2").
In WINE 4.x this has been working fine, but a recent Ubuntu upgrade has bumped WINE to 5.5, and now SONAR is sending the same MIDI commands to all 16 ports on the ESI device instead of just e.g. port 2. For example, if you play the organ part in isolation, it should be sending these notes to the Hammond XM-1 module on port 4 of the ESI device. But it is also sending these to the drum machine on port 6, the Triton on port 1 and so on.
It does not appear to be sending the MIDI data to the Roland UM-ONE interface also attached the system, however.
As a workaround I have reverted to an old version of winealsa.drv.so from 2017 which I happened to have lying around from some earlier experiment. This has made the problem go away.
I can try building WINE myself to find the point at which the bug was introduced, but looking at the recent changes in git I'd be inclined to suspect this commit: https://github.com/wine-mirror/wine/commit/3d57cc2863f2f9a5ace40d29317b3ff43...
...since it appears to be using a much less fine-grained approach to sending MIDI data to the devices.
It is quite likely that it works fine for the case of a USB synthesizer where one instrument is on one port, but for something like a 4x4 MIDI interface there appears to be a regression.
Thanks, Joseph P Morris
https://bugs.winehq.org/show_bug.cgi?id=49099
Sagawa sagawa.aki+winebugs@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |sagawa.aki+winebugs@gmail.c | |om
https://bugs.winehq.org/show_bug.cgi?id=49099
Chris Xiong chirs241097@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |chirs241097@gmail.com
https://bugs.winehq.org/show_bug.cgi?id=49099
--- Comment #1 from Sagawa sagawa.aki+winebugs@gmail.com ---
From my point of view, this is a duplicate of Bug 52220.
https://bugs.winehq.org/show_bug.cgi?id=49099
Joseph Morris jpm@it-he.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED
--- Comment #2 from Joseph Morris jpm@it-he.org --- (In reply to Sagawa from comment #1)
From my point of view, this is a duplicate of Bug 52220.
Looks like it. I've just installed 7.0 rc4 (with the 52220 fix) and the problem seems to be resolved without needing to revert winealsa to some old version as I've been doing up to now.
https://bugs.winehq.org/show_bug.cgi?id=49099
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #3 from Alexandre Julliard julliard@winehq.org --- Closing bugs fixed in 7.0-rc5.