Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Mark Knecht <markknecht@attbi.com>
Cc: Alsa-Devel <alsa-devel@lists.sourceforge.net>
Subject: Re: HDSP 9652 MIDI Timing - Much improved, but no Port 1...
Date: Fri, 24 Jan 2003 12:06:09 +0100	[thread overview]
Message-ID: <s5hr8b2yfha.wl@alsa2.suse.de> (raw)
In-Reply-To: <1043351090.2341.13.camel@Godzilla>

[-- Attachment #1: Type: text/plain, Size: 1230 bytes --]

At 23 Jan 2003 19:44:49 +0000,
Mark Knecht wrote:
> 
> Paul, Takashi-san and Clemens,
>    Hi. A couple of days ago Fernando got a new RPM built for Alsa which
> includes the recent HDSP 9652 MIDI timing fix that you worked together
> on and supplied about 10 days ago. I wanted to report back that the
> timing is now much improved. I haven't used it a lot yet, but I am
> playing moderately complicated songs now and the timing seems fine.
> Thanks.
> 
>    There is one problem that has come up new in this release. The HDSP
> 9652 has two MIDI ports. With this release I can only get MIDI out on
> Port 2. I cannot get MIDI out at all on Port 1. Both ports used to work
> on the previous version, albeit with bad timing, so this fix this has
> changed this aspect of the driver.

could you (or anyone HDSP owner) check the attached patch?


>    I also tried using kaconnect to look at the connections between
> Rosegarden and the alsa_sequencer. It shows that Rosegarden is hooked to
> 64:32 External MIDI 0 only. A second group, 64:0 External MIDI 0 shows
> up, but kaconnect will not connect to it. I do not know what that means,
> but it seems to be part of it.
 
rosegarden developers know better about this...


Takashi

[-- Attachment #2: hdsp-midi.dif --]
[-- Type: application/octet-stream, Size: 1139 bytes --]

Index: alsa-kernel/pci/rme9652/hdsp.c
===================================================================
RCS file: /suse/tiwai/cvs/alsa/alsa-kernel/pci/rme9652/hdsp.c,v
retrieving revision 1.16
diff -u -r1.16 hdsp.c
--- alsa-kernel/pci/rme9652/hdsp.c	20 Jan 2003 15:36:08 -0000	1.16
+++ alsa-kernel/pci/rme9652/hdsp.c	24 Jan 2003 10:54:24 -0000
@@ -844,7 +844,6 @@
 {
 	unsigned long flags;
 	int n_pending;
-	int clear_timer = 0;
 	int to_write;
 	int i;
 	unsigned char buf[128];
@@ -862,17 +861,9 @@
 				if ((to_write = snd_rawmidi_transmit (hmidi->output, buf, n_pending)) > 0) {
 					for (i = 0; i < to_write; ++i) 
 						snd_hdsp_midi_write_byte (hmidi->hdsp, hmidi->id, buf[i]);
-				} else {
-					clear_timer = 1;
 				}
 			}
-		} else {
-			clear_timer = 1;
 		}
-
-		if (clear_timer && hmidi->istimer && --hmidi->istimer <= 0) {
-			del_timer(&hmidi->timer);
-		} 
 	}
 
 	spin_unlock_irqrestore (&hmidi->lock, flags);
@@ -980,6 +971,8 @@
 		}
 	}
 	spin_unlock_irqrestore (&hmidi->lock, flags);
+	if (up)
+		snd_hdsp_midi_output_write(hmidi);
 }
 
 static int snd_hdsp_midi_input_open(snd_rawmidi_substream_t * substream)

      reply	other threads:[~2003-01-24 11:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-23 19:44 HDSP 9652 MIDI Timing - Much improved, but no Port 1 Mark Knecht
2003-01-24 11:06 ` Takashi Iwai [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=s5hr8b2yfha.wl@alsa2.suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=markknecht@attbi.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox