9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Don <north_@www.7f.no-ip.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Line-In
Date: Wed, 27 Feb 2002 10:06:44 +0000	[thread overview]
Message-ID: <8f6cf824.0202261232.6dd646e0@posting.google.com> (raw)
In-Reply-To: <20020226152718.CFE7C19980@mail.cse.psu.edu>

> i'm not familiar with the term "cdr" as an audio format, but i'm
> guessing you're refering to the audio format on a CD. that's PCM,
> and yes, it's the same format you read/write on /dev/audio.
> 
Right on. I got the term "cdr" from the 'sox' manpage.

> // I've tried using lame to convert P9 /dev/audio data to mp3...
> 
> one step at a time. can you get data from /dev/audio to start
> with? just try 'cat /dev/audio > /tmp/foo', yell into the mic some,
> and then kill the cat. the contents of /tmp/foo should be PCM
> audio, suitable for 'cat /tmp/foo > /dev/audio'.
> 
Of course. 

> assuming you're getting audio data, are you sure lame is working?
> i had issues with it producing valid but garbage mp3 files. for my
> experiences, take a look at http://9srv.net/mpeg/ - the summary
> is that i use BladeEnc quite succesfully. the single line to compile
> it, and a binary in case you have problems, are available there.
> ?
Apparently the problem was that LAME and sox were not working. Though, I
find it odd, since, every file made on Linux/BSD will translate fine with
LAME/sox on my FreeBSD machine. :| That is why I thought the problem was
my understanding of the audio file format. Every mp3 file produced on 
Plan 9 ended up as pure garbage, though, a valid mp3 file was generated. 
Once I tried bladeenc on plan9 everything turned out sweet as cake ;)
Thanks,
Don (north_)
http://www.7f.no-ip.com/


  reply	other threads:[~2002-02-27 10:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-26 15:27 anothy
2002-02-27 10:06 ` Don [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-02-28 17:09 anothy
2002-02-26 16:35 Russ Cox
2002-02-26 10:15 Don

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=8f6cf824.0202261232.6dd646e0@posting.google.com \
    --to=north_@www.7f.no-ip.com \
    --cc=9fans@cse.psu.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;
as well as URLs for NNTP newsgroup(s).