alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: "Jörn Nettingsmeier" <nettings@stackingdwarves.net>
To: Takashi Iwai <tiwai@suse.de>
Cc: Adrian Knoth <adi@drcomp.erfurt.thur.de>,
	alsa-devel@alsa-project.org, Florian Faber <faber@faberman.de>
Subject: Re: MIDI issue with RME HDSPM MADI
Date: Tue, 07 Jun 2011 15:06:05 +0200	[thread overview]
Message-ID: <4DEE223D.2000702@stackingdwarves.net> (raw)
In-Reply-To: <4DEB77C5.6010305@stackingdwarves.net>

On 06/05/2011 02:34 PM, Jörn Nettingsmeier wrote:
> On 06/03/2011 06:08 PM, Takashi Iwai wrote:
>> At Wed, 01 Jun 2011 19:27:32 +0200,
>> Jörn Nettingsmeier wrote:
>>>
>>> Hi *!
>>>
>>>
>>> The HDSPM MADI driver seems to have an issue with its MIDI
>>> implementation. It is rock-solid for audio under Jack at 64
>>> frames/period, but as soon as I start using the MIDI over MADI interface
>>> (to remote-control my Micstasy preamps), I'm getting xruns every ten
>>> seconds or so.
>>
>> Maybe we can just replace the midi stuff into workqueue.
>> Below is a very quick and untested patch.  Does it work?
>
> patch applies and works, no crashes here.
> but no change in xrun behaviour either.
>
> for the record, i'm running the kernel with threadirqs.
>
> i guess by using a workqueue, we have eliminated the possibility that
> anything in the midi bottom half of the driver is hogging the hardware
> resources to cause an xrun, right?

new datapoint: the xruns are the same when i use the physical midi 
interface of the HDSP MADI instead of the MIDI over MADI one.

i wonder: can anybody reproduce this issue with another card supported 
by the hsdpm.c driver?
if it's higher up in the code, it should affect other hardware as well. 
or maybe not, since the problem might not show on cards with less than 
64 channels...

i'm digging through some kernel-related books regarding scheduler 
instrumentation, but progress is kinda slow... if anyone could suggest 
some hot leads to follow, i'd be glad to :)

best,


jörn



-- 
Jörn Nettingsmeier
Lortzingstr. 11, 45128 Essen, Tel. +49 177 7937487

Meister für Veranstaltungstechnik (Bühne/Studio)
Tonmeister (VDT)

http://stackingdwarves.net
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel

  reply	other threads:[~2011-06-07 12:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-01 17:27 MIDI issue with RME HDSPM MADI Jörn Nettingsmeier
2011-06-03 16:08 ` Takashi Iwai
2011-06-05 12:34   ` Jörn Nettingsmeier
2011-06-07 13:06     ` Jörn Nettingsmeier [this message]
2011-06-07 13:18       ` Jörn Nettingsmeier
2011-06-07 14:03         ` Jörn Nettingsmeier

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=4DEE223D.2000702@stackingdwarves.net \
    --to=nettings@stackingdwarves.net \
    --cc=adi@drcomp.erfurt.thur.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=faber@faberman.de \
    --cc=tiwai@suse.de \
    /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;
as well as URLs for NNTP newsgroup(s).