14 Aug
2015
14 Aug
'15
3:55 a.m.
Saw something I didn't expect while debugging my production box; in
/proc/asound/cards, an entry named FCA202, which was my Behringer FCA202
firewire interface. Since when does ALSA do Firewire interfaces?
I'm tracking a very intermittent freezup bug of some sort, and thought
perhaps this ALSA driver was interfering with JACK and its Firewire side,
and have blacklisted the driver involved (snd_oxfw) just in case. It will
take a lot of testing to come to an opinion whether or not this eliminated
the problem.
But meanwhile, does this mean that I have the option of using
JACK-->ALSA-->FCA202 as well as JACK-->Firewire-->FCA202?
Anyone know which perhaps I should prefer for high performance at low
latency? I'm running 96KHz and liking it a lot...
In case it helps: kernel 4.1.3 Liquorix, Debian Testing, 64-bit, up to
date.
--
*Jonathan E. Brickman jeb(a)ponderworthy.com
<http://login.jsp/?at=02e47df3-a9af-4cd9-b951-1a06d255b48f&mailto=jeb@ponderworthy.com>
(785)233-9977
<%28785%29233-9977>Hear some of our music at http://ponderworthy.com
<http://ponderworthy.com/> !Music of compassion; fire, and life!!!*
14 Aug
14 Aug
4:35 a.m.
Various recent versions of ALSA now have native support for Firewire,
migrated/ported/reimplemented from FFADO. So yes,
JACK->ALSA->{firewire device} is now possible for at least some
devices.
On Thu, Aug 13, 2015 at 9:55 PM, Jonathan Brickman <jeb(a)ponderworthy.com> wrote:
Saw something I didn't expect while debugging my
production box; in
/proc/asound/cards, an entry named FCA202, which was my Behringer FCA202
firewire interface. Since when does ALSA do Firewire interfaces?
I'm tracking a very intermittent freezup bug of some sort, and thought
perhaps this ALSA driver was interfering with JACK and its Firewire side,
and have blacklisted the driver involved (snd_oxfw) just in case. It will
take a lot of testing to come to an opinion whether or not this eliminated
the problem.
But meanwhile, does this mean that I have the option of using
JACK-->ALSA-->FCA202 as well as JACK-->Firewire-->FCA202?
Anyone know which perhaps I should prefer for high performance at low
latency? I'm running 96KHz and liking it a lot...
In case it helps: kernel 4.1.3 Liquorix, Debian Testing, 64-bit, up to
date.
--
Jonathan E. Brickman jeb(a)ponderworthy.com (785)233-9977
Hear some of our music at http://ponderworthy.com !
Music of compassion; fire, and life!!!
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user(a)lists.linuxaudio.org
http://lists.linuxaudio.org/listinfo/linux-audio-user
3:14 p.m.
On Thu, 13 Aug 2015 20:55:01 -0500
Jonathan Brickman <jeb(a)ponderworthy.com> wrote:
Saw something I didn't expect while debugging my
production box; in
/proc/asound/cards, an entry named FCA202, which was my Behringer FCA202
firewire interface. Since when does ALSA do Firewire interfaces?
This seems to be a 4.x addition. I discovered it last week when I was setting
up my live recording laptop and upgraded to the 4.x kernel, and couldn't start Jack
with my FW mixer.
I haven't yet done a FFADO/ALSA comparison for stability, so I just removed the
ALSA modules before starting jack, and everything was OK.
rmmod snd_dice snd_firewire_lib
But meanwhile, does this mean that I have the option
of using
JACK-->ALSA-->FCA202 as well as JACK-->Firewire-->FCA202?
Yes, but beware of conflicting kernel modules. If jack doesn't start with
your device, this is likely why.
Anyone know which perhaps I should prefer for high
performance at low
latency? I'm running 96KHz and liking it a lot...
I have yet to try the ALSA drivers (but may run some tests today).
--
======================================================================
Joe Hartley - UNIX/network Consultant - jh(a)brainiac.com
Without deviation from the norm, "progress" is not possible. - FZappa
3:36 p.m.
On 08/14/2015 03:14 PM, Joe Hartley wrote:
This seems to be a 4.x addition.
snd-bebob by Takashi Sakamoto has been in the kernel since 3.16 so well
over a year: https://ieee1394.wiki.kernel.org/index.php/Release_Notes
Jeremy
8:08 p.m.
On Fri, 14 Aug 2015 15:36:34 +0200
Jeremy Jongepier <jeremy(a)autostatic.com> wrote:
On 08/14/2015 03:14 PM, Joe Hartley wrote:
Must be my setup, as I've been testing with Ardour4.2 & jack using the
ALSA driver and I don't see snd-bebob loaded, only snd_firewire_lib,
firewire_ohci and firewire_core. I didn't have this issue until I'd upgraded
to 4.1 so I guess I'd successfully delayed the problem until now.
On the plus side, I've been testing this morning with the above setup
under kernel 4.1.4 on an Arch system and I have over 3.5 hours recorded of
all 16 channels from my mixer without a single xrun. There are still some
glitches - I have to start JACK twice as the first attempt fails, and I see
dmesg errors about DMA contexts, but the second time seems to work.
--
======================================================================
Joe Hartley - UNIX/network Consultant - jh(a)brainiac.com
Without deviation from the norm, "progress" is not possible. - FZappa
This seems to be a 4.x addition.
snd-bebob by Takashi Sakamoto has been in the kernel since 3.16 so well
over a year: https://ieee1394.wiki.kernel.org/index.php/Release_Notes
3347
days inactive
3347
days old
linux-audio-user@lists.linuxaudio.org
4 comments
4 participants
participants (4)
-
Jeremy Jongepier -
Joe Hartley -
Jonathan Brickman -
Paul Davis