New subject: [Bug 54557] winmm:midi gets unexpected messages on w10pro64 (21H1)

22 Feb 2023


      https://bugs.winehq.org/show_bug.cgi?id=54557
Bug ID: 54557
           Summary: winmm:midi gets unexpected messages on w10pro64 (21H1)
           Product: Wine
           Version: unspecified
          Hardware: x86-64
                OS: Windows
            Status: NEW
          Severity: normal
          Priority: P2
         Component: winmm&mci
          Assignee: wine-bugs@winehq.org
          Reporter: fgouget@codeweavers.com
winmm:midi gets unexpected messages on w10pro64 (21H1):
* 2023-02-13 on w10pro64-fr (64-bit)
midi.c:988: Message 3c7, wParam=2f1e410, lParam=0 from midiStreamOpen
midi.c:1039: Message 320, wParam=e3006fc7, lParam=1 from midiStreamOut
midi.c:1039: Test failed: bad message 320/1 from midiStreamOut, expect
3c9/65f820
midi.c:1048: Message 320, wParam=e3006fc7, lParam=1 from midiStreamClose
midi.c:1048: Test failed: bad message 320/1 from midiStreamClose, expect 3c8/0
* 2023-02-20 on w10pro64-he (64-bit)
midi.c:662: Message 320, wParam=e3006fc7, lParam=1 from midiStream still paused
midi.c:662: Test failed: bad message 320/1 from midiStream still paused, expect
0/feedf00d
midi.c:685: Message 320, wParam=e3006fc7, lParam=1 from midiStream callback
midi.c:685: Test failed: bad message 320/1 from midiStream callback, expect
3ca/65f820
midi.c:686: Message 3ca, wParam=2eeb120, lParam=65f820 from midiStreamOut
midi.c:686: Test failed: bad message 3ca/65f820 from midiStreamOut, expect
3c9/65f820
...
midi.c:746: Message 3c9, wParam=2eeb120, lParam=65f820 from 0 bytes recorded
midi.c:746: Test failed: bad message 3c9/65f820 from 0 bytes recorded, expect
0/feedf00d
* 2023-02-21 on w10pro64-hi (64-bit)
midi.c:366: Message 320, wParam=e3006fc7, lParam=1 from midiOutLong unprepared
midi.c:366: Test failed: bad message 320/1 from midiOutLong unprepared, expect
0/feedf00d
midi.c:378: MIDIHDR flags=2 when unsent
midi.c:415: Message 320, wParam=e3006fc7, lParam=1 from midiOutClose
midi.c:415: Test failed: bad message 320/1 from midiOutClose, expect 3c8/0
midi.c:423: Message 3c8, wParam=2ea4810, lParam=0 from midiOutOpen WINDOW
midi.c:423: Test failed: bad message 3c8/0 from midiOutOpen WINDOW, expect
0/feedf00d
See https://test.winehq.org/data/patterns.html#winmm:midi
These are the only known instances so far so it looks like this is caused by a
change that happened in February.
Where 0x320 == WM_DWMCOLORIZATIONCOLORCHANGED ???
      0x3c8 == MM_MOM_CLOSE
      0x3c9 == MM_MOM_DONE
      0x3ca == MM_MOM_POSITIONCB
It's possible that 0x320 is the cause for all failures. If it really is
WM_DWMCOLORIZATIONCOLORCHANGED then it is probably caused by some other test
and thus really not related to midi. So it may make sense to add it to the
spurious_message() filter.
-- 
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.

[Bug 54557] New: winmm:midi gets unexpected messages on w10pro64 (21H1)