Linux Sound subsystem development
 help / color / mirror / Atom feed
From: Benno Senoner <sbenno@gardena.net>
To: linux-sound@vger.kernel.org
Subject: Re: best sound format and app. for recording voice.
Date: Sun, 13 Feb 2000 21:57:05 +0000	[thread overview]
Message-ID: <marc-linux-sound-95047908809485@msgid-missing> (raw)
In-Reply-To: <marc-linux-sound-95028036700135@msgid-missing>

On Sun, 13 Feb 2000, Kai Vehmanen wrote:
> On Sat, 12 Feb 2000, Benno Senoner wrote:
> 
> > encoder. Anyway I try to avoid proprietary codecs.
> > ( Realnetworks still not able to deliver a decent realplayer for linux,
> > my guess is that if they do not open their protocols , Microsoft will kill
> > them just like they did with Nescape
> 
> It's interesting to see, what RealNetworks is going to do in the 
> near future. IMHO RN should open-source all their players and
> encoders, and for all platforms. And they should do it now. This would 
> have quite an impact. As mp3 suffers from licensing problems, many
> people would prefer a GPL'ed RA-de/encoder. Let's hope this happens.

I wouldn't be a Realnetworks shareholder right now ... :-)
they still think that they can fight M$ but with proprietary models this
will just not work.
Did you notice that they pulled Realaduio support from the latest mediaplayer ?
Why ? , simple: to force users to use MS-Audio.
Because Joe Average is too lazy (or too dumb :-) ) to download the RA Player.
:-)

If Realnetworks doesn't react right now, (opensourcing codecs would give them
a big boost in terms of acceptance).

It could easy happen that Linux will save their a** because the level playing
field of Linux.
But if we wait too much, all streaming sites will only run MS-Audio , and
M$ will be able to control the entire streming arena.
( with the advent of broadband , streaming will be a big $$$ business,
and M$ wants all of the pie) 

> 
> > But as Artur pointed out, GSM isn't that bad at 12kbit/sec,
> [...]
> > or if you want extreme low bit rates use the LPC-10 code , down to 2.4kbit/sec,
> > = 1.1MB/hour  :-)
> [...]
> > But I don't know if the quality high enough for you
> > http://www.arl.wustl.edu/~jaf/lpc/
> 
> Yep, there are plenty of encoders out there, but when distributing
> your music (or some other "popular" activity), ease of use and
> availability are crucial. And RealAudio is easy to use and it is 
> widely spread.

Agreed, but in this case the user wanted only to store his voice recordings 
on his own disk, therefore a special codec would be appropriate.

Benno.

  parent reply	other threads:[~2000-02-13 21:57 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-02-11  8:15 best sound format and app. for recording voice Benno Senoner
2000-02-11  9:03 ` John Starkey
2000-02-11 17:28 ` Kai Vehmanen
2000-02-12 17:59 ` Benno Senoner
2000-02-12 22:54 ` John Littler
2000-02-13  0:58 ` Tony Nugent
2000-02-13  1:38 ` Jeremy Hall
2000-02-13 14:21 ` Kai Vehmanen
2000-02-13 14:22 ` Kai Vehmanen
2000-02-13 21:57 ` Benno Senoner [this message]
2000-02-23 17:12 ` Kai Vehmanen
  -- strict thread matches above, loose matches on Subject: below --
2000-02-11  1:46 Bryan Bolden
2000-02-11  3:43 ` John Starkey
2000-02-11  6:11 ` Jeremy Hall
2000-02-11  7:28 ` Josh Steiner
2000-02-11  8:24 ` John Starkey
2000-02-11 14:31 ` Michael Black
2000-02-12  4:13 ` Artur Skawina

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=marc-linux-sound-95047908809485@msgid-missing \
    --to=sbenno@gardena.net \
    --cc=linux-sound@vger.kernel.org \
    /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