All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Juhana Sadeharju" <kouhia@nic.funet.fi>
To: linux-sound@vger.kernel.org
Subject: Re: [linux-audio-dev] Re: Multimedia compression
Date: Mon, 19 Jun 2000 18:50:01 +0000	[thread overview]
Message-ID: <marc-linux-sound-96200429928831@msgid-missing> (raw)
In-Reply-To: <marc-linux-sound-96126686903146@msgid-missing>


>From:	Benno Senoner <sbenno@gardena.net>
>
>I prefer to use MPEG Layer 2 ( MP2) at 384kbit (lossy) which outperforms all
>MP3 based codecs even 320kbit. 

How do you know it? Where I could read tests about it?
I have used layer 3 with 320 kbps for compressing radio and cassette
recordings (both music and sound samples snipped from them), so, most
probably I have used the right compressor. But is layer 3 with 320 kbps
somehow not enough for studio mikes (voice, guitar, etc.) or for digital
synth tracks?

Of course, for compressing the final mix (20-bit or greater) of studio work,
the 16-bit MP3 is not enough. But 16-bit could be enough for individual
sounds, vocals, etc. However, I would not use any MP3 compression for even
those because I would record only with 20-bit A/Ds in studio. I have used
MP3 only because I have nothing better than 16-bit A/Ds. So, what compressor
I could use for 20- or 24-bit material? Should we look at ourself for
20- or 24-bit compressor or can MP3 or AAC handle them (similarly than JPEG
can handle 16-bit/channel images)?

Note that 16-bit is most probably enough for mic recordings, but the
extra bits are needed for having extra room. I would not want to dither
20-bit recording down to 16-bit even it would fit very well.

Juhana

  reply	other threads:[~2000-06-19 18:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-06-17 18:33 [linux-audio-dev] Re: Multimedia compression John Lazzaro
2000-06-19 18:50 ` Juhana Sadeharju [this message]
2000-06-20 11:54 ` Benno Senoner
2000-06-20 22:28 ` Dustin Barlow
2000-06-20 22:40 ` paco
2000-06-20 23:02 ` paco
2000-06-20 23:04 ` paco

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-96200429928831@msgid-missing \
    --to=kouhia@nic.funet.fi \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.