public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: ccrawford@acb.org
To: speakup@braille.uwo.ca
Subject: Re: Inability to make a audio cd of mp3s
Date: Sun, 24 Nov 2002 13:48:49 -0500 (EST)	[thread overview]
Message-ID: <Pine.LNX.4.44.0211241347580.5176-100000@localhost.localdomain> (raw)
In-Reply-To: <20021124144705.GF12690@rednote.net>

Janina,

	Actually, you were making the point that I was making i
n my message.

-- Charlie.

On Sun, 24 Nov 2002, Janina Sajka wrote:

> No, they can't possibly sound better converted from mp3 to wav. It's an
> old story, you can't make silk from a sow's ear.
> 
> The mp3 format is a compressed format. Aspects of the original recording
> have been thrown away in the compression process. That information is
> gone forever. You can't magically get the richer details available in an
> uncompressed format like wav by converting from mp3 to wav.
> 
> This is also an example of how dissengenuous the recording industry is
> over peer to peer file sharing. The copies being shared, for the most
> part, are no where near the quality of the recordings shrink wrapped in
> the music store. It's not as they say, that every digital copy is an
> exact duplicate of the original. That's just balderdash. And there are
> many many more ways to make an inexact digital copy, just as there have
> long been ways to make an extremely accurate analog copy of analog
> media.
> 
> But, I diagress yet again.
> 
> 
> Charles Crawford writes:
> > From: ccrawford@acb.org
> > 
> > 	I don't really know the answer to your question but it brings up a 
> > question of my own.  Given the dynamics of mp3 recording, how does 
> > converting them to a wave file do any good?  Do they sound any better?
> > 
> > -- charlie.
> > 
> > 
> > On Sat, 23 Nov 2002, Patricia Logan wrote:
> > 
> > >      Hi!  I have gotten a lot of mp3s from a friend.  I 
> > > transformed them to wav files using mpg123 as described on this 
> > > list.  When I tried to copy these onto a disc using cdrecord in 
> > > -dao mode I got the message that the tracks had to be passed, 
> > > having to be lumtiples of some number which I can't remember. How 
> > > difficult will it be to dealwith this?
> > > 
> > >      Pat Logan
> > > 
> > > 
> > > 
> > > _______________________________________________
> > > Speakup mailing list
> > > Speakup@braille.uwo.ca
> > > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> > > 
> > 
> > 
> > _______________________________________________
> > Speakup mailing list
> > Speakup@braille.uwo.ca
> > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> 
> 



  parent reply	other threads:[~ UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Distro Question Glenn Ervin
 ` Chuck Hallenbeck
 ` Inability to make a audio cd of mp3s Patricia Logan
   ` Igor Gueths
   ` Kerry Hoath
   ` Ann Parsons
     ` ccrawford
       ` Janina Sajka
         ` ccrawford
       ` Igor Gueths
   ` ccrawford
     ` Janina Sajka
       ` Igor Gueths
       ` ccrawford [this message]
         ` Maurice A. Mines
           ` Janina Sajka
             ` Maurice A. Mines
 ` Distro Question Ralph W. Reid
   ` dashielljt
     ` Toby Fisher
 Inability to make a audio cd of mp3s Janina Sajka
 ` Patricia Logan
   ` Igor Gueths
   ` Janina Sajka

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=Pine.LNX.4.44.0211241347580.5176-100000@localhost.localdomain \
    --to=ccrawford@acb.org \
    --cc=speakup@braille.uwo.ca \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).