Re: [SLUG] Just thinking.
May I suggest to use of some audio editor to compare the wave? Don't know any good audio editor under linux though. Years ago I used catwalk (or something like that) under windows. Lester On Mon, Jun 30, 2003 at 05:43:28PM +1000, Bill Bennett wrote: I use cdparanoia to rip an audio track. I store it as AudioA.wav. I use cdrecord to burn the track. I rip the burned track and store it as AudioB.wav. I'd like to compare the files to see what sort of job I've made. a) Is there a Linux programme to do this? b) Would anyone care to speculate on what I'd find? Regards, Bill Bennett. -- SLUG - Sydney Linux User's Group - http://slug.org.au/ More Info: http://lists.slug.org.au/listinfo/slug -- SLUG - Sydney Linux User's Group - http://slug.org.au/ More Info: http://lists.slug.org.au/listinfo/slug
Re: [SLUG] Just thinking.
On Wed, 2 Jul 2003 20:06:24 +1000 Lester Cheung [EMAIL PROTECTED] wrote: May I suggest to use of some audio editor to compare the wave? Probably not a really good way to do it, expecially not for any piece of sound longer than about 10 seconds. Don't know any good audio editor under linux though. http://sweep.sf.net/ http://audacity.sf.net/ and others. Erik -- +---+ Erik de Castro Lopo [EMAIL PROTECTED] (Yes it's valid) +---+ Laws of Thermodynamics: 1) You cannot win. 2) You cannot break even. 3) You cannot get out of the game. -- SLUG - Sydney Linux User's Group - http://slug.org.au/ More Info: http://lists.slug.org.au/listinfo/slug
Re: [SLUG] Just thinking.
On Tue, Jul 01, 2003 at 03:23:29PM +1000, Bill Bennett wrote: Many thanks to the people who replied to my posting. It was prompted by my getting cdparanoia and cdrecord to produce a disc. (Never mind the sarcasm, it was a major miracle. My next project is to raise the dead.) cdparanoia's propaganda says that it will fix small problems on a disk. All well and good. But having ripped an audio track, fixed or not, it has to be burned, ie., what with translation to .wav, software to send this file to the burner and the burning process itself, there is room for error(s). We do not live in the best of all possible worlds. Hence my enquiry. In my case, ripper and burner are not the same instrument, although even if they were, the argument remains unchanged. There are also these thoughts: even if errors *are* shown to exist, they may not amount to much, human hearing being what it is and if they *do* amount, I may not be able to do much about them. Here's a strategy: I think the CD standard is meant to be fault tolerant - a story I've heard is you should be able to drill a 5mm hole in a CD and not notice the difference in quality. So if CDparanoia can't read a small part of your CD for some reason, it will make up something in the gap (e.g. blank space). Clean your CDs before you rip them. If you do find differences or the copied CD is noticably worse or are just curious: get CD paranoia to rip 5,10, or 100 copies (depending on how much you care and how much time you have) and see if they are all the same. something like this: for i in (*.wav); do for j in (*.wav); do cmp $i $j; done; done; will output any differences. My script does every comparison twice, but it is very simple. Do this to the original and the source. Try multiple CD-ROM drives if you can. If you get say 10 copies, 6 are the same as each other and the other 4 are all different to each other, the burn one of the 6 good copies. (and delete the other 9 copies) cheers, Woody I will, however, post what results I get. I will be interested in this too! cheers, -- Woody -- SLUG - Sydney Linux User's Group - http://slug.org.au/ More Info: http://lists.slug.org.au/listinfo/slug
Re: [SLUG] Just thinking.
Here's a strategy: I think the CD standard is meant to be fault tolerant - a story I've heard is you should be able to drill a 5mm hole in a CD and not notice the difference in quality. I remember hearing this in college, a number of years ago, so myself and a friend (a mechanical engineer) drilled a 3mm hole in a CD.. guess what it wouldn't play :-), I think though if you have a really high-end CD player this is true, but most bog end ones don't even bother with the ECC stuff on audio .. Dave. -- David Airlie, Software Engineer http://www.skynet.ie/~airlied / [EMAIL PROTECTED] pam_smb / Linux DECstation / Linux VAX / ILUG person -- SLUG - Sydney Linux User's Group - http://slug.org.au/ More Info: http://lists.slug.org.au/listinfo/slug
Re: [SLUG] Just thinking.
Dave Airlie wrote: I remember hearing this in college, a number of years ago, so myself and a friend (a mechanical engineer) drilled a 3mm hole in a CD.. guess what it wouldn't play :-), wouldn't you have to drill two holes opposite each other otherwise the CD would be unbalanced? Dave. -- SLUG - Sydney Linux User's Group - http://slug.org.au/ More Info: http://lists.slug.org.au/listinfo/slug
Re: [SLUG] Just thinking.
quote who=Bill Bennett I use cdparanoia to rip an audio track. I store it as AudioA.wav. I use cdrecord to burn the track. I rip the burned track and store it as AudioB.wav. I'd like to compare the files to see what sort of job I've made. a) Is there a Linux programme to do this? Sure, run md5sum on the two files, like this: $ md5sum jdub* 43418bbfc74efc6b94397e427cd3fa32 jdub-face.base64 5c926bcaeeb89add1c4edabffbaca22b jdub.png If the md5sums match, then they have exactly the same content. b) Would anyone care to speculate on what I'd find? I doubt they'd come out exactly the same, but that's just a guess. If you end up doing it, please share the results! :-) - Jeff -- Get Informed: SCO vs. IBMhttp://sco.iwethey.org/ If you want to start a debate on a subject, however, all that seems to be necessary is to involve perennial target Richard Gooch. - LWN -- SLUG - Sydney Linux User's Group - http://slug.org.au/ More Info: http://lists.slug.org.au/listinfo/slug
Re: [SLUG] Just thinking.
On Tue, Jul 01, 2003 at 02:26:41AM +1000, Jeff Waugh wrote: quote who=Bill Bennett I use cdparanoia to rip an audio track. I store it as AudioA.wav. I use cdrecord to burn the track. I rip the burned track and store it as AudioB.wav. I'd like to compare the files to see what sort of job I've made. a) Is there a Linux programme to do this? Sure, run md5sum on the two files, like this: $ md5sum jdub* 43418bbfc74efc6b94397e427cd3fa32 jdub-face.base64 5c926bcaeeb89add1c4edabffbaca22b jdub.png If the md5sums match, then they have exactly the same content. To a very high degree of probability, but there is a chance they could be different. Other simple checks: ls -l # check the length (size) diff # will tell you if they differ diff -a | less # will show you where they differ (in binary) b) Would anyone care to speculate on what I'd find? I doubt they'd come out exactly the same, but that's just a guess. If you end up doing it, please share the results! :-) I'd expect no difference, or small differences. cheers, Woody -- SLUG - Sydney Linux User's Group - http://slug.org.au/ More Info: http://lists.slug.org.au/listinfo/slug
Re: [SLUG] Just thinking.
How about 'cmp' That's what its for! -- SLUG - Sydney Linux User's Group - http://slug.org.au/ More Info: http://lists.slug.org.au/listinfo/slug
Re: [SLUG] Just thinking.
On Mon, 2003-06-30 at 17:43, Bill Bennett wrote: I use cdparanoia to rip an audio track. I store it as AudioA.wav. I use cdrecord to burn the track. I rip the burned track and store it as AudioB.wav. I'd like to compare the files to see what sort of job I've made. Well, if I were you I'd convert your ripped .wav files to something like raw audio data -- .wav is a generic format that has all sorts of bizaare variants, but mostly I'd suspect suble differences in the header which render your comparison useless (unless it comes out the same :)). They can for example record free form comments, which from a cd ripper might record the date and time of the rip. There is also some padding which happens on the end of cdaudio tracks. I'm not sure if you get that in the ripped file or not. I assume it would be the same for both the source and the target disks, but I'm really not sure. I'm not actually up to date on audio formats atm. .raw seems like a safe bet to me. Then using diff or something to compare the files. Maybe even vimdiff, so you can see if the errors are at the very start or end (since those errors are meaningless manifestations of protocol). HTH James. -- SLUG - Sydney Linux User's Group - http://slug.org.au/ More Info: http://lists.slug.org.au/listinfo/slug
Re: [SLUG] Just thinking.
Many thanks to the people who replied to my posting. It was prompted by my getting cdparanoia and cdrecord to produce a disc. (Never mind the sarcasm, it was a major miracle. My next project is to raise the dead.) cdparanoia's propaganda says that it will fix small problems on a disk. All well and good. But having ripped an audio track, fixed or not, it has to be burned, ie., what with translation to .wav, software to send this file to the burner and the burning process itself, there is room for error(s). We do not live in the best of all possible worlds. Hence my enquiry. In my case, ripper and burner are not the same instrument, although even if they were, the argument remains unchanged. There are also these thoughts: even if errors *are* shown to exist, they may not amount to much, human hearing being what it is and if they *do* amount, I may not be able to do much about them. I will, however, post what results I get. Thanks again, Bill Bennett. -- SLUG - Sydney Linux User's Group - http://slug.org.au/ More Info: http://lists.slug.org.au/listinfo/slug
