From: "Mark Knecht" <mknecht@controlnet.com>
To: Paul Davis <paul@linuxaudiosystems.com>,
Clemens Ladisch <clemens@ladisch.de>
Cc: Alsa-Devel <Alsa-Devel@lists.sourceforge.net>
Subject: RE: MIDI getting killed by Jack?
Date: Thu, 11 Sep 2003 06:56:10 -0700 [thread overview]
Message-ID: <NDBBLGIKBJENLAMOLFHGEEPPDCAB.mknecht@controlnet.com> (raw)
In-Reply-To: <200309111306.h8BD6Tfv007234@oud>
Paul,
I'm pretty sure that I was not the intended audience for this level of
technical data, but it does raise the question (for me) as to whether this
problem might be created by using the 'wrong' (I.e. - undocumented
requirements) kernel?
The machine exhibiting the problem is running a pretty much vanilla
Gentoo 2.4.20 kernel with preemptive multitasking and low latency scheduling
turned on. This kernel does not have the capabilities patch. The problem
occurs when I run Jack as a user.
I have not investigated what happens as root.
However, as I stated in my second message yesterday, none of the above
seems to impact the system if I get my MIDI input through the MidiSport vs.
the HDSP 9652, so my presumption is that the first-order problem lies with
that driver and not the kernel.
Please let me know specifically if there is anything you would like me to
try.
Thanks,
Mark
> -----Original Message-----
> From: Paul Davis [mailto:paul@linuxaudiosystems.com]
> Sent: Thursday, September 11, 2003 6:06 AM
> To: Clemens Ladisch
> Cc: Mark Knecht; Alsa-Devel
> Subject: Re: [Alsa-devel] MIDI getting killed by Jack?
>
>
> >When an interrupt for MIDI input occurs, the hdsp driver disables all
> >further MIDI interrupts until the current input data has been read. I
> >don't know why it does this, but you may try to remove/disable lines
> >3181, 3182, 3188, and 3189 in hdsp.c.
>
> the hdsp driver is one of the first alsa drivers to use tasklets to
> handle MIDI without impacting audio latency (that is, we can continue
> processing audio i/o even while MIDI i/o is pending). once we have
> launched a tasklet to handle MIDI input, there is no point handling
> more interrupts that tell us the same thing.
>
> the tasklet stuff relies on the kernel scheduler, but AFAIK, the
> tasklet effectively runs like the kernel equivalent of a SCHED_FIFO
> thread. i don't know at what priority, however.
>
> --p
>
>
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
next prev parent reply other threads:[~2003-09-11 13:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-10 16:15 MIDI getting killed by Jack? Mark Knecht
2003-09-10 20:13 ` Mark Knecht
2003-09-11 8:18 ` Clemens Ladisch
2003-09-11 13:06 ` Paul Davis
2003-09-11 13:56 ` Mark Knecht [this message]
2003-09-11 15:02 ` Clemens Ladisch
2003-09-11 16:13 ` Mark Knecht
2003-09-11 15:42 ` Clemens Ladisch
2003-09-11 14:06 ` Mark Knecht
[not found] <NDBBLGIKBJENLAMOLFHGOENADDAB.mknecht@controlnet.com>
2003-09-24 1:00 ` alsa-devel
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=NDBBLGIKBJENLAMOLFHGEEPPDCAB.mknecht@controlnet.com \
--to=mknecht@controlnet.com \
--cc=Alsa-Devel@lists.sourceforge.net \
--cc=clemens@ladisch.de \
--cc=paul@linuxaudiosystems.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.