Re: [Jack-Devel] JackEngine::XRun: client = pure_data_0 was not run: state = 2 JackAudioDriver::ProcessGraphAsyncMaster: Process error

PrevNext  Index
DateThu, 09 Jan 2014 13:44:53 +1030
From Jonathan Woithe <[hidden] at just42 dot net>
ToPaul Davis <[hidden] at linuxaudiosystems dot com>
CcJACK <[hidden] at lists dot jackaudio dot org>
In-Reply-ToPaul Davis Re: [Jack-Devel] JackEngine::XRun: client = pure_data_0 was not run: state = 2 JackAudioDriver::ProcessGraphAsyncMaster: Process error
Follow-UpAdrian Knoth Re: [Jack-Devel] JackEngine::XRun: client = pure_data_0 was not run: state = 2 JackAudioDriver::ProcessGraphAsyncMaster: Process error
On Wed, Jan 08, 2014 at 12:26:27PM -0500, Paul Davis wrote:
> On Wed, Jan 8, 2014 at 11:51 AM, Fryderyk Dziarmagowski <
> [hidden]> wrote:
> > On 8 January 2014 15:25, Paul Davis <[hidden]> wrote:
> >> On Wed, Jan 8, 2014 at 5:02 AM, Alexandros Drymonitis <[hidden]>wrote:
> >> Can I use my firewire sound card with ALSA?
> >>
> >> not yet.
> >
> > sure you can: https://github.com/takaswie/snd-firewire-improve.git
> 
> i'm fairly sure that original poster was not asking about whether or not
> they can rebuild their kernel with work-in-progress drivers. ALSA support
> for firewire audio interfaces is awesome and exciting but AFAIK, the work
> is not done yet.

To provide further clarification about this, the snd-firewire driver work is
the first visible sign of moving the FFADO audio streaming code into the
kernel (device control will most likely be userspace due to certain
reasons).  I expect that once the initial code by Takashi is done we will
start to see more movement of the FFADO streaming component into the kernel
by using the initial drivers as a template.  I am very keen to do this for
the devices I maintain but there is a currently a lack of documentation
about how to go about writing such a driver within the ALSA framework. 
Hense the reliance on an initial driver as a template.

Having said that, snd-firewire is, as Paul said, a work in progress
experimental driver.  YMMV and it currently supports only certain devices
(each device family requires its own driver code; the current code is for
some DICE and BeBoB devices).  I believe the initial code may be pulled for
3.13 or 3.14 but further tweaks will almost certainly be needed.  This is
still very much under development and testing is certainly welcomed. 
However, it is certainly not ready for end-users who just need things to
work.

I hope this helps.

jonathan
PrevNext  Index

1389237324.23474_0.ltw:2, <20140109031453.GG18195 at marvin dot atrad dot com dot au>