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 16:03:00 +0200	[thread overview]
Message-ID: <4DEE2F94.5070001@stackingdwarves.net> (raw)
In-Reply-To: <4DEE251B.3040807@stackingdwarves.net>

takashi, one question:

On 06/07/2011 03:18 PM, Jörn Nettingsmeier wrote:

> GOTCHA. it looks like it's higher up in the code. i just ran jack
> with my RME DIGI9652 (different driver!), and presto: when i ran
> faberman's rawmiditest or the micstasy remote (on the MADI card, not
> on the DIGI), there's xruns again. slightly less, but very likely
> caused by midi traffic. i'm just cross-checking with a make -j8
> kernel build, and there are no xruns, only when i have midi traffic.

if midi traffic on one card causes jack xruns on another, that rules out
jackd, doesn't it? reason i'm asking is you suggested to try
alsa-lib/test/latency.c, and i have trouble understanding how to run it.
i get

kleineronkel:/local/build/alsa-git/alsa-lib/test # ./latency -r 48000 -P
hw:1,0 -C hw:1,0 -c64 --period 64 -f FLOAT_LE -s 10
Scheduler set to Round Robin with priority 99...
Playback device is hw:1,0
Capture device is hw:1,0
Parameters are 48000Hz, FLOAT_LE, 64 channels, non-blocking mode
Poll mode: no
Loop limit is 480000 frames, minimum latency = 64, maximum latency = 4096
Access type not available for playback: Invalid argument
Unable to set parameters for playback stream: Invalid argument

it seems to be hardcoded to SND_PCM_ACCESS_RW_INTERLEAVED, i guess that 
won't work...

i changed it to ..._NONINTERLEAVED, but now i'm stuck at:

kleineronkel:/local/build/alsa-git/alsa-lib/test # ./latency -r 48000 -P 
hw:1,0 -C hw:1,0 -f FLOAT_LE
Scheduler set to Round Robin with priority 99...
Playback device is hw:1,0
Capture device is hw:1,0
Parameters are 48000Hz, FLOAT_LE, 2 channels, non-blocking mode
Poll mode: no
Loop limit is 1440000 frames, minimum latency = 64, maximum latency = 4096
Sample format not available for playback: Invalid argument
Unable to set parameters for playback stream: Invalid argument

same issue with [US][16|24|32]-[BE|LE].



-- 
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 13:56 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
2011-06-07 13:18       ` Jörn Nettingsmeier
2011-06-07 14:03         ` Jörn Nettingsmeier [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=4DEE2F94.5070001@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).