[Appologies for the cross-posting]
[Please DON'T use reply-to-all to reply on this email]
With this I'm hoping to gather some data that can help us in convincing
the firewire device manufacturers that we are of some significance to
their sales (I'm actually wondering if we are...). So I would like to
ask everyone on these lists that has/considers/considered purchasing a
firewire audio device if they would be so kind as to answer the
** Those that have bought one or more firewire devices...
* can you provide which device(s), preferably with their GUID (can be
found out using gscanbus or sometimes on the device itself)
* Do they work with linux?
** Those that considered buying a firewire device:
* What device(s) did you consider buying?
* What device did you go for in the end (if applicable)?
* To what extent was the lack of Linux support a determining factor in
** Those that consider buying a firewire device:
* What device(s) are you consider buying?
* How important is Linux support for you?
** any comments?
It would be nice if you would reply to this email with the answers
inlined with the questions. Please don't reply-to-all but reply to
pieterp(a)joow.be in order not to spam the mailing list with these
answers. It would also be nice if you left the subject line intact such
that I can auto-filter these messages.
Again, sorry to bother you guys with this, but it's a bit difficult to
convince manufacturers without some decent data.
PS: If you know other freebob/ffado users that are not subscribed to
these list please pass this mail on.
Here's a quick update regarding latest developments:
Last couple months have been incredibly busy. One of the things I've been
working on is getting us a dedicated high-bandwidth access. Since the
release of UbuntuStudio our server has been running steadily at 110% of
network bandwidth utilization. Thanks to the hard work of our volunteers the
server has not melted (yet, :-). This week, I've had already half-dozen
meetings (whenever I am subjected to such a torture, I feel as if my IQ has
irreparably dropped ;-), some of which pertained directly to the aforesaid
predicament. At this point I am unable to promise anything but as long as
everything goes as planned, as early as this fall we may be able to move our
server to a dedicated Internet2 node (meaning practically guaranteed
100MB+/second connection). Our more immediate plan is to replace the
existing server with a dedicated Linux box which would run off of a
dedicated 100mBit connection. So, let's keep our fingers crossed!
I have been getting steady stream of questions about Linuxaudio.org's
participation in various conferences. Given that we are still unable to
generate revenue, I am wondering if we could organize a group of
Linuxaudio.org ambassadors who, whenever they would participate in various
events/conferences/expos, would also do some PR for us. If interested,
please contact me asap. Please also mention event you are interested in
covering so that we can minimize overalp. Since I believe in leading by
example, I have already made plans to cover this year's ICMC which is going
to take place in Copenhagen next month ;-). If any of you plan on being
there, please make sure to look me up, so that we can go for a pint or two.
So much for now. Stay tuned for more updates!
Ivica Ico Bukvic, D.M.A.
Department of Music - 0240
Blacksburg, VA 24061
(540) 231-5034 (fax)
Some updates and new things on my webpages.
First official release of jconv.
Jconv is a command line jack client performing FFT-based
convolution using a mix of up to five partition sizes,
small ones at the start of the IR, and building up to
the optimum size further on. It allows zero-delay
convolution with moderate CPU load. Jconv uses the
multi-threaded convolution engine developed for use
in Aella, a convolution engine optimised for reverb
processing that is nearing completion.
Main features of jconv:
- Any convolution matrix up 64 by 64, as long as your
CPU(s) can take it.
- Allows to trade off processing delay to CPU load, and
remains efficient even when configured for zero delay.
- Reads the same config files as Jace which it will
The beta version released two months ago to some
volunteers contained a bug discovered and patched
by Martin Rumori. It did not affect configurations
using independent 1-to-1 convolutions, only matrix
Update of Ambdec
Some small changes and bugfixes. The configuration
format now also permits the use of mixed-order de-
coders (2nd order horizontal, 1st order vertical).
TetraProc / TetraCal.
Both are ready and have been used for real Ambisonic
recordings, but release of TetraCal awaits a required
update of Aliki, and completion of the manual that
describes the calibration procedure.
If you want to use Core Sound's TetraMic with
TetraProc this is possible today. I signed an NDA
with Core Sound giving me access to the impulse
response measurements performed by Core Sound on
each mic. Given the serial number, I can process
these using TetraCal and provide a matching config
file for TetraProc.
You can see some examples of this on the updated
screenshots page for TetraProc.
As usual: <www.kokkinizita.net/linuxaudio>
Follie! Follie! Delirio vano è questo !