When I start Ardour, for example, which employs the ALSA driver (optionally through JACK), it is able to employ the audio interface for a while but this will invariably and eventually result in a string of buffer under-runs, at which point the DAW automatically disengages from using the audio interface. Any attempt to reconnect to the interface results in a segfault. I realise this may appear to be a fault in Ardour itself but there are no such issues with the regular onboard interface. If you want I can run some tests, but you'll have to guide me through it.
Adriano
On lun, 28 mag, 2018 at 3:38 PM, Takashi Sakamoto o-takashi@sakamocchi.jp wrote:
Hi, (C.C.ed alsa-devel)
On May 28 2018 07:05, Adriano Michael Petrosillo wrote:
Hi,
I'm contacting you regarding a few issues with my Echo Audiofire 12. It has the latest firmware (5.8). With a recent kernel (4.15.0-22-generic) it is recognised by the OS but it works unreliably, leading to system instability.
Please explain about your experiences which made you be unreliable and feel instability to your system so that the others such as me can get them.
Here is the dmesg output:
[ 6019.402918] firewire_core 0000:04:07.0: PHY ID mismatch in self ID: 0 != 1 [ 6019.402931] firewire_core 0000:04:07.0: topology build failed [ 6019.934272] firewire_core 0000:04:07.0: rediscovered device fw0 [ 6065.194414] firewire_core 0000:04:07.0: phy config: new root=ffc1, gap_count=5 [ 6065.700801] firewire_core 0000:04:07.0: created device fw1: GUID 0014865e75918c0e, S400 [ 6067.619626] snd-fireworks fw1.0: Invalid CIP header for AMDTP: 00000000:00000000 [ 6067.619663] snd-fireworks fw1.0: Invalid CIP header for AMDTP: 00000000:00000000 [ 6067.619670] snd-fireworks fw 1.0: Invalid CIP header for AMDTP: 00000000:00000000 [ 6067.619676] snd-fireworks fw1.0: Invalid CIP header for AMDTP: 00000000:00000000 [ 6067.619683] snd-fireworks fw1.0: Invalid CIP header for AMDTP: 00000000:00000000 [ 6067.619689] snd-fireworks fw1.0: Invalid CIP header for AMDTP: 00000000:00000000 [ 6067.619695] snd-fireworks fw1.0: Invalid CIP header for AMDTP: 00000000:00000000 [ 6067.619701] snd-fireworks fw1.0: Invalid CIP header for AMDTP: 00000000:00000000 [ 6067.619706] snd-fireworks fw1.0: Invalid CIP header for AMDTP: 00000000:00000000 [ 6067.619712] snd-fireworks fw1.0: Invalid CIP header for AMDTP: 00000000:00000000
In the beginning of packet streaming, your unit transfers packets with invalid CIP header, as shown. But enough later it starts to transfer the packet correctly. The above message is irrelevant to your issue.
It is also impossible to use as a system card, and alsamixer is unable to set the volumes for the 12 channels, but here I'm probably doing something wrong. If you want to improve support for the card, I can cooperate, I have no coding skills unfor tunately.
ALSA fireworks driver adds no control element set in Linux system. This is a design not to bring complexity into kernel stuffs. For control feature to DSP on your unit, please use 'hinawa-fireworks-cui' in 'hinawa-utils'[1] with 'libhinawa'[2], or ffado-dbus-server/ffado-mixer[3].
[1] https://github.com/takaswie/hinawa-utils [2] https://github.com/takaswie/libhinawa [3] http://subversion.ffado.org/
Regards
Takashi Sakamoto