[Bug 52220] TMIDI Player, Cherry: Playback with multiple MIDI ports is broken

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=52220

--- Comment #7 from Jacek Konieczny <jajcus at jajcus.net> ---
> It works as expected but there are two issues when using Qsynth.

Yes, i noticed those too. I think that the Qsynth default is a bit
unreasonable, but there is something wrong in wine too.

> As a workaround, Qsynth users need to uncheck the
> "Auto Connect MIDI Inputs" checkbox in the "Setup" dialog.

Yes, that improves things a bit.

> Issue one: When it's checked, Wine often fails to open Qsynth's MIDI ports.

That is the weird one, that I have not really connected to the qsynth
autoconnect feature. This is definitely a bug. Maybe wine is trying to get
'exclusive' access to the MIDI port, which does not really make sense on Linux
ALSA (sequencer ports are supposed to be shared unless they use special flags
to prevent that). I'll investigate that.

> Issue two: When checked, even if Wine successfully opens
all MIDI ports, the playback is still broken.

That I would say is 'working as intended' – when you have multiple qsynths
started each with 'auto-connect ports' then all wine MIDI outputs would be
connected to all the synths running. There would be the same confusing behavior
with a Linux MIDI player. This won't happen e.g. with multiple hardware
synthesizers, as they would not connect automatically anywhere.

-- 
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.