All of lore.kernel.org
 help / color / mirror / Atom feed
From: thet <parenthetical@halfshavedyaks.xyz>
To: alsa-devel@alsa-project.org
Subject: RME Fireface alsa driver - improved but still not working
Date: Wed, 17 Apr 2019 21:59:23 +0100	[thread overview]
Message-ID: <663f96f0-8652-ce5e-7572-ade544ff3cd3@halfshavedyaks.xyz> (raw)
In-Reply-To: <20190105085024.GA29901@workstation>

I notice that the RME fireface alsa driver snd-fireface now works a
little since 4.19 I think

In earlier kernels 4.18 and below the midi worked on the FF400 but no
audio and the FF800 was not supported at all.

now the midi works on both FF400 and FF800 and the audio works a little.

the kernel I am using is 5.0.0-7.1-liquorix-amd64 #1 ZEN SMP PREEMPT
liquorix 5.0-6ubuntu1~bionic (2019-04-06) x86_64 x86_64 x86_64 GNU/Linux

(I am also happy to test with a different kernel but I am not able to
compile it myself so it would need to be available in a repo.)

The audio however does not work correctly. It is unstable, sometimes it
works for a while but other times it glitches or even becomes wildly
distorted.

I am not a kernel developer at all - but I am willing to test and post
logs if it helps - if anyone here can give me clear instructions about
how to test.

Also - is it possible for a user to disable the audio part of the driver
but still use the midi part?

This would allow me to use the audio with FFADO and the midi with alsa.
FFADO doesn't support midi on these devices so it is great that alsa
does -  but running both at once can be tricky as the alsa driver does
not let FFADO take over the device once it has it.

Can I suggest that maybe the audio and midi drivers for these devices
could be made as separate kernel modules? Then if one part has problems
it need not be loaded. I'm not sure if this is feasible but if it is it
would allow more flexibility in how they are used.

thanks

Thet



_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
https://mailman.alsa-project.org/mailman/listinfo/alsa-devel

  reply	other threads:[~2019-04-17 20:59 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-11 19:51 RME Fireface alsa driver thet
2018-12-11 20:43 ` Takashi Sakamoto
     [not found]   ` <a61bd3e8-0ace-3ef1-ffa4-f56c3c67fd31@halfshavedyaks.xyz>
2018-12-17 14:16     ` Takashi Sakamoto
2018-12-18 23:38       ` thet
2018-12-19  4:22         ` Takashi Sakamoto
2018-12-19 14:51           ` thet
2019-01-05  8:50             ` Takashi Sakamoto
2019-04-17 20:59               ` thet [this message]
2019-04-23  6:03                 ` RME Fireface alsa driver - improved but still not working Takashi Sakamoto

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=663f96f0-8652-ce5e-7572-ade544ff3cd3@halfshavedyaks.xyz \
    --to=parenthetical@halfshavedyaks.xyz \
    --cc=alsa-devel@alsa-project.org \
    /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.