Linux Sound subsystem development
 help / color / mirror / Atom feed
From: jhall@UU.NET (Jeremy Hall)
To: linux-sound@vger.kernel.org
Subject: Re: best sound format and app. for recording voice.
Date: Sun, 13 Feb 2000 01:38:51 +0000	[thread overview]
Message-ID: <marc-linux-sound-95040832814836@msgid-missing> (raw)
In-Reply-To: <marc-linux-sound-95028036700135@msgid-missing>

oh good grief.

well that might work over a 2400 modem.

I remember a Linux encoder from long ago, I still have the files if
there's interest.  Microsoft has not seemed interested in providing a
product for Linux, their mediaplayer doesn't work for Linux, forcing us to
use mp3 to encode our audio.

_J

In the new year, Benno Senoner wrote:
> On Fri, 11 Feb 2000, Kai Vehmanen wrote:
> > On Fri, 11 Feb 2000, Benno Senoner wrote:
> > 
> > > I think Realaudio isn't that bad for this purpose (windows and linux encoder
> > > exists).
> > 
> > Where!?! Linux RA-player has been around for quite some time now, but I've
> > never heard about a RA-encoder for Linux! :o
> > 
> 
> Arg, I think I am wrong,
> I heard about Realserver for Linux, but I am not sure if it includes an
> 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
> .. hopefully there will be a Mozilla-of-the-streaming-protocols :-) )
> 
> 
> But as Artur pointed out, GSM isn't that bad at 12kbit/sec,
> plu when searching around the net I found a voice coder which runs
> at about 4.8kbit/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/
> 
> Benno.
> 

  parent reply	other threads:[~2000-02-13  1:38 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 [this message]
2000-02-13 14:21 ` Kai Vehmanen
2000-02-13 14:22 ` Kai Vehmanen
2000-02-13 21:57 ` Benno Senoner
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-95040832814836@msgid-missing \
    --to=jhall@uu.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