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

[WineHQ Bugzilla]

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

--- Comment #12 from kakurasan at gmail.com ---
> Setting event destination directly has its advantage, that the event will only
> reach the very specific port, but when someone uses wine to interact with a
> Windows program or analyze the MIDI traffic it generates this may become a
> disadvantage.

> Reverting all the changes make it impossible to tap on Windows applications
> MIDI traffic (useful for reverse engineering Windows software for various MIDI
> hardware) or change the MIDI connections (useful to make better use of
> application that do not provide the MIDI connectivity configuration wanted).

When I want to capture MIDI traffic from such apps (including older Wine),
I usually use "snd-seq-dummy" module (Midi Through) or aseqview.

Wine --> snd-seq-dummy or aseqview
snd-seq-dummy or aseqview --> MIDI device
 +--------------------------> arecordmidi or other native MIDI app

(Some Windows MIDI apps need to change MIDI mapper registry setting)

This is not easier to use than current Wine, but not impossible.


However, IMO, we don't have to revert to the old behavior:
* When the "Auto Connect MIDI Inputs" checkbox is unchecked,
  it works as expected
* Similar confusing behavior occurs in some native apps too
  (at least Rosegarden)
* It's enough to make it known to Wine+Qsynth users:
  WineHQ Wiki, World Wine News, upcoming release note, etc.

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