From: Amaury Jacquot <sxpert@esitcom.org>
To: Steve Harris <S.W.Harris@ecs.soton.ac.uk>
Cc: linux-audio-user@music.columbia.edu,
linux-audio-dev@music.columbia.edu,
alsa-devel@lists.sourceforge.net
Subject: Re: Firewire Audio Card Support
Date: Thu, 18 Nov 2004 15:44:36 +0100 [thread overview]
Message-ID: <419CB554.3080709@esitcom.org> (raw)
In-Reply-To: <20041118143205.GA21282@login.ecs.soton.ac.uk>
Steve Harris wrote:
> On Thu, Nov 18, 2004 at 03:15:52 +0100, Olaf Christ wrote:
>
>>Hi,
>>
>>as the owner of a firewire audio card (Motu 828mkII) I was disappointed when
>>trying to use it under linux. Asking Motu to provide tech docs and/or linux
>>drivers is useless: "We will possibly release linux drivers in the future,
>>but we never release any kind of technical documentation."
>
>
> That is actually a big improvemnt. When we (linuaudio.org) were demoing at
> Sounds Live in London earlier this year, the were telling thier users that
> they had no intention of supporting linux, and wouldn't release docs.
>
> Though with the number of thier users we were sending to them to ask, I
> guess they were getting a bit concerned :)
>
> - Steve
what's the rationale behind the "we won't release any docs" nonsense ?
someone needs to come out with a professionnal libre-design sound
card... (can't be that hard)
Amaury
-------------------------------------------------------
This SF.Net email is sponsored by: InterSystems CACHE
FREE OODBMS DOWNLOAD - A multidimensional database that combines
robust object and relational technologies, making it a perfect match
for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8
next prev parent reply other threads:[~2004-11-18 14:44 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <31148074.1100630541337.JavaMail.root@scooter.psp.pas.earthlink.net>
[not found] ` <419C9D47.4090606@x-i.net>
[not found] ` <419C9D47.4090606-l4pODZ2nMLw@public.gmane.org>
2004-11-18 14:15 ` Firewire Audio Card Support Olaf Christ
[not found] ` <200411181515.52218.olaf-Cb7RZHV19h6Y/VGTjfr9Sg@public.gmane.org>
2004-11-18 14:32 ` [Alsa-devel] " Steve Harris
2004-11-18 14:44 ` Amaury Jacquot [this message]
2004-11-18 15:09 ` Giuliano Pochini
2004-11-18 15:15 ` Amaury Jacquot
2004-11-18 19:54 ` Pieter Palmers
[not found] ` <419CFE12.1070908-8ZVx2yYfyutX2QMWbMbClIble9XqW/aP@public.gmane.org>
2004-11-18 19:19 ` [Alsa-devel] " Takashi Iwai
2004-11-18 20:16 ` Lee Revell
2004-11-18 22:07 ` [linux-audio-dev] " Jens M Andreasen
2004-11-18 22:49 ` Jan Depner
2004-11-18 22:54 ` Re: [linux-audio-dev] Re: [Alsa-devel] " Mark Knecht
2004-11-18 23:52 ` [linux-audio-user] " Florian Schmidt
[not found] ` <1100809010.10150.5.camel-sMXKvD5kdRZ9Itub2Jo68g@public.gmane.org>
2004-11-19 17:12 ` Jussi Laako
[not found] ` <1100884361.13133.10.camel-7xOsYr0MI4rPaj0P+rXokA@public.gmane.org>
2004-11-19 18:37 ` Re: [linux-audio-dev] " Lee Revell
2004-11-19 20:26 ` Re: [linux-audio-user] " Martin Langer
2004-11-20 10:22 ` Giuliano Pochini
2004-11-18 19:36 ` Pieter Palmers
[not found] <20041118145603.CA5511D211A@sc8-sf-uberspam1.sourceforge.net>
2004-11-19 2:14 ` Yon Mercury
[not found] <20041118194002.842C81D4895@sc8-sf-uberspam1.sourceforge.net>
2004-11-19 2:33 ` Yon Mercury
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=419CB554.3080709@esitcom.org \
--to=sxpert@esitcom.org \
--cc=S.W.Harris@ecs.soton.ac.uk \
--cc=alsa-devel@lists.sourceforge.net \
--cc=linux-audio-dev@music.columbia.edu \
--cc=linux-audio-user@music.columbia.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox