Your message dated Thu, 28 Oct 2010 10:58:22 +0200
with message-id <20101028085821.gq14...@ltw.loris.tv>
and subject line Re: Bug#601652: need to delete cache or libffado2 fails
has caused the Debian Bug report #601652,
regarding need to delete cache or libffado2 fails
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
601652: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=601652
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libffado2
Version: 2.0.1+svn1856-5
Severity: important

The attached program fails when the libffado2 cache exists
(~/.ffado/cache).  It spills the following error message in
ffado_streaming_start():

libiec61883 warning: iec61883_cmp_create_p2p_output: Failed to set the oPCR[0] 
plug for node 0.
ERROR: messagebuffer not initialized: 1248856282860: Error 
(ieee1394service.cpp)[1413] allocateIsoChannelCMP: Could not do CMP from 
FFC0:00 to FFC1:-1
ERROR: messagebuffer not initialized: 1248856282871: Error (avc_avdevice.cpp)[ 
816] startStreamByIndex: Could not allocate ISO channel for SP 0
ERROR: messagebuffer not initialized: 1248856282877: Warning 
(devicemanager.cpp)[ 863] startStreamingOnDevice: Could not start stream 0 of 
device 0x464300
ERROR: messagebuffer not initialized: 1248856282884: Warning 
(devicemanager.cpp)[ 900] startStreaming: Could not start streaming on device 
0x464300!
ERROR: messagebuffer not initialized: 1248856282890: Fatal (ffado.cpp)[ 211] 
ffado_streaming_start: Could not start the streaming system

Deleting the cache (rm -r ~/.ffado/cache) will resolve the issue.

As far as I can see, there is no option to disable the cache.  A
shared library writing to the user's home directory is not exactly
good programming style anyway.

Severity important because it renders the library useless, unless you
delete the cache each time before you run a libffado2 application.



--- End Message ---
--- Begin Message ---
On Thu, Oct 28, 2010 at 09:07:06AM +0200, Max Kellermann wrote:

> The attached program fails when the libffado2 cache exists
> (~/.ffado/cache).  It spills the following error message in

You'd be the first who experiences such a problem.

> ERROR: messagebuffer not initialized: 1248856282871: Error
> (avc_avdevice.cpp)[ 816] startStreamByIndex: Could not allocate ISO
> channel for SP 0

Looks like your device got locked by a previous run. You need to
power-cycle it or run ffado-test BusReset.


Note that FFADO can be pretty picky about the components involved.
Firstly, it's advisable to run it on Linux 2.6.36 when using the new
Juju firewire stack (or stick to the old ieee1394 stack).

Second, the Firewire controller in use is important:

   http://subversion.ffado.org/wiki/HostControllers

Also the version in Debian is outdated, you clearly want to use FFADO
svn trunk. We're in freeze and I've already discussed it with the
release team, there's no chance to update anymore.


With regard to all your other bugreports: we more or less know the game.
There's probably no use in filing more bug reports against Debian, you
better instantly go upstream, there's a developer mailinglist:

   https://lists.sourceforge.net/lists/listinfo/ffado-devel


Last but not least: I'm not entirely convinced about writing a
player-specific output plugin for hardware-specific devices. This should
all be abstracted via some common layer, and the preferred way of
running FFADO at the moment is via jackd and then to bridge with
pulseaudio-module-jack to consumer-level applications like mpd.

Given that mpd already has a jack output plugin, there's even no need
for pulseaudio.


Note that there is some work to move FFADO into the kernel, at least the
streaming processors. It will then be exposed as an ALSA device.


HTH

-- 
mail: a...@thur.de      http://adi.thur.de      PGP/GPG: key via keyserver


--- End Message ---
_______________________________________________
pkg-multimedia-maintainers mailing list
pkg-multimedia-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/pkg-multimedia-maintainers

Reply via email to