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

[WineHQ Bugzilla]

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

kakurasan at gmail.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |aeikum at codeweavers.com

--- Comment #10 from kakurasan at gmail.com ---
The revised patch works as expected,
except for "Qsynth/FluidSynth + autoconnect" case:
* Non-FluidSynth devices: OK
* Qsynth/FluidSynth without autoconnect: OK
* Qsynth/FluidSynth with autoconnect:
    * Always able to open ports: OK
    * Broken playback: I'm still not sure whether it's really expected

> 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.

Is there a way to avoid this by modifying Wine...?

> There would be the same confusing behavior with a Linux MIDI player.

"aplaymidi" command (in alsa-utils) works as expected even when
libfluidsynth's autoconnect feature is in use.
(e.g. "aplaymidi -p [Qsynth port 1]:0,[Qsynth port 2]:0 /path/to/file.mid")

snd_seq_ev_set_subs() isn't used in the program.
("aseqnet" and "arecordmidi" use it)


Regarding the SND_SEQ_PORT_TYPE_MIDI_GENERIC hack for Qsynth/FluidSynth:
* It works as a workaround
* The hack should not be applied by default (See comment #8)
  but may be useful for some Qsynth users

-- 
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.