FFADO is a userspace solution for using Firewire audio interfaces under Linux. It is provided as a source-only release. FFADO comprises two main components:
Website issues which surfaced in May 2020 are currently being investigated.
29 May 2020: The FFADO project is pleased to make FFADO version 2.4.3 available. This is a bug-fix release to address some minor problems which have been noted in version 2.4.2.
FFADO version 2.4.3 is available as a tarball: libffado-2.4.3.tgz.
To contact us, please use our mailing lists.
All our historical releases can be accessed from our files area.
Our development wiki can still be accessed.
21 May 2020: we have become aware of a problem which developed with our website in the last couple of days. While this is investigated we have activated this placeholder to make the task easier.
26 May 2020: Investigations have progressed slowly due to time constraints. Independent protection mechanisms are being triggered due to incoming traffic which targets various CMS vulnerabilities. However, it is possible that the site may also have been damaged. Rest assured that we have backups of the content if it becomes necessary to use them. Since the project has little need for the dynamic site components these days, we may move the content which remains relevant to static pages if a restoration turns out to be needed.
24 June 2020: It has been determined that no site content has been lost. Even so, we are seriously considering adopting a mostly static project site, since we do not currently have an urgent need for a dynamic CMS. While all the important content is currently accessible, there are additional historic comment posts associated with various FFADO devices which might prove useful as a reference in future. We are currently determining how best to approach this.
14 July 2020: Further testing has shown that the original site infrastructure is still intact. It has been spun up on a separate server and shown to be fully functional. The inability to access the site in May therefore appears to be solely due to the protection mechanisms mentioned on 26 May. This is good news as it means the site has not been damaged. Even so, the static site option appears to be the best way to bring the site back, and that is what is being pursued. There is no estimate as to how far off this might be.