mirror of
https://codeberg.org/armin/tcd.git
synced 2026-09-01 05:50:46 +02:00
fix README
This commit is contained in:
parent
2ec7d5ec1a
commit
f5f7d416c2
1 changed files with 2 additions and 2 deletions
|
|
@ -34,7 +34,7 @@ audio was produced by a lossy encoder. Combined, these clues give a verdict.
|
|||
What tcd displays and what each number means
|
||||
---------------------------------------------
|
||||
|
||||
Here is the example output you saw:
|
||||
Here is example output from an MP3 file:
|
||||
|
||||
```
|
||||
File: ./08 You Got Me.mp3
|
||||
|
|
@ -80,7 +80,7 @@ off high frequencies to save space. The cutoff gets lower as the bitrate drops:
|
|||
| 96 kbps | ~13000 Hz (~59%) | Significant high-end missing |
|
||||
| 64 kbps | ~11000 Hz (~50%) | Sounds dull, heavily filtered |
|
||||
|
||||
**What 94.3% means for your file:** 20790 / 22050 = 94.3%. The cutoff is very
|
||||
**What 94.3% means for the example file:** 20790 / 22050 = 94.3%. The cutoff is very
|
||||
close to the theoretical maximum. This is what we expect from a 320 kbps
|
||||
encode. If this same file showed 54% (~12000 Hz), it would mean the treble
|
||||
was chopped off by an aggressive low-bitrate encoder, and someone just
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue