File: FOR_TESTING

package info (click to toggle)
checkmp3 1.98-6
  • links: PTS
  • area: main
  • in suites: etch, etch-m68k
  • size: 180 kB
  • ctags: 136
  • sloc: ansic: 1,212; makefile: 60
file content (59 lines) | stat: -rw-r--r-- 1,033 bytes parent folder | download | duplicates (4)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
Here's a little something that will help in spotting problems
with the addition of new features...




1) Take a known good mp3, and run:

md5sum <mp3_file.mp3>

Then run mp3_check -a -sf <mp3_file.mp3> > <new_mp3.mp3>

They should be the same (by comparing the md5sums of both mp3s).

This will try to fix an already good mp3, and thus should 
not make any changes.

** Especially with VBR files.





2) Take a known good mp3, cut it in half, and add some junk
in the center (dd if=/dev/zero of=junk bc=2000) and glue it all
back (with the junk in the middle).

Then run mp3_check -a -sf <mp3_file.mp3> > <new_mp3.mp3>

I would like it to be able to strip out the junk, and return
the original mp3, but I don't think it works quite yet.

Anyone willing to take a look at this? :)


** Especially with VBR files.





3) Take a known good mp3, and run:

md5sum <mp3_file.mp3>

Then run mp3_check -a -s <mp3_file.mp3> > <new_mp3.mp3>

They should be the same (without fixing anything).








Any other tests are welcome. :)

-Eric