From: Bruce <abruceperson@gmail.com>
To: Florian Faber <faber@faberman.de>, alsa-devel@alsa-project.org
Subject: Re: Can't get capturing from RME Hammerfall MADI card to work: sound loops & silcence
Date: Tue, 08 Oct 2013 14:59:46 +1100 [thread overview]
Message-ID: <52538332.3070501@gmail.com> (raw)
In-Reply-To: <52453824.9070308@faberman.de>
On 27/09/2013 5:47 PM, Florian Faber wrote:
> Clemens,
>
>>> Similar issues here, but can add it all seems to work absolutely fine with
>>> alsa 1.0.15, but fails with 1.0.18+.
>> This sound like some change in the driver introduced a bug.
> the driver works fine with versions up to 1.0.27. I have the card
> running on a daily base with current kernel versions.
Hi Flo (or driver developers),
I cannot get our card to work with alsa 1.0.27 (or 1.0.18), but it does
work fine with 1.0.15. I'm trying to work out what could be different
from my setup to yours. I have tried different PCs, different Linux
distributions and two different HDSP cards.
I'm using a HDSPe MADI Rev1.1 loaded with the latest firmware. Is yours
the same ?
May I send you a particular application to attempt running on your
system with 1.0.27 and see if it works ?
*Note* I can use all parts of 1.0.27 (eg, lib, alsamixer, aplay)
/except/ for the Hammerfall driver (remains at 1.0.15) and it still
works for me. I cannot install the new driver under an older kernel due
to incompatibilities, but trying 1.0.18 or 1.0.27 (including later
driver) with a newer kernel fails.
I thought if I could somehow get the 1.0.15 hammerfall driver working
with a new kernel (help ??) I could then somehow step through the
subsequent changes made to the driver one by one till it breaks. This
approach could take some considerable time, so any pointers as to how to
do this would be much appreciated ! I do not profess to know much about
alsa driver development, or how to even access the (svn ?) revision
steps, but this might be the only way to work out what is happening here.
Cheers,
Bruce
PS: I will also ask the Hammerfall Linux forum, but that seems a bit
inactive now.
>
>
> Flo
--
Cheers,
Bruce
prev parent reply other threads:[~2013-10-08 3:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-27 6:08 Can't get capturing from RME Hammerfall MADI card to work: sound loops & silcence Niels Laukens
2013-09-27 7:07 ` bruce
2013-09-27 7:43 ` Clemens Ladisch
2013-09-27 7:47 ` Florian Faber
2013-10-02 15:16 ` Jörn Nettingsmeier
2013-10-08 3:59 ` Bruce [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=52538332.3070501@gmail.com \
--to=abruceperson@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=faber@faberman.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).