[Bug 39048] MIDI Clock Messages are Corrupted Between Wine and ALSA

[wine-bugs at winehq.org]

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

Bruno Jesus <00cpxxx at gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
     Ever confirmed|0                           |1

--- Comment #6 from Bruno Jesus <00cpxxx at gmail.com> ---
I was able to reproduce what you said with gmidimonitor and MIDI Clock. MIDI is
a very obscure area to me but judging by wine source code comment I guess this
is a valid bug, and looking at the alsa documentation maybe wine is really
using the wrong method to send the data.

At file winealsa.drv/midi.c:

 906                 case 0x06:      /* Tune Request */
 907                 case 0x08:      /* Timing Clock. */
 908                 case 0x0A:      /* Start. */
 909                 case 0x0B:      /* Continue */
 910                 case 0x0C:      /* Stop */
 911                 case 0x0E:      /* Active Sensing. */
 912                     /* FIXME: Is this function suitable for these purposes
 913                        (and also Song Select and Song Position Pointer) */
 914                     snd_seq_ev_set_sysex(&event, 1, &evt);

Maybe it should actually use snd_rawmidi_write because this is not really a
sysex message.

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