Penguin
Diff: SoundProcessingNotes
EditPageHistoryDiffInfoLikePages

Differences between version 11 and predecessor to the previous major change of SoundProcessingNotes.

Other diffs: Previous Revision, Previous Author, or view the Annotated Edit History

Newer page: version 11 Last edited on Sunday, December 21, 2003 4:11:43 pm by DanielLawson Revert
Older page: version 10 Last edited on Sunday, December 21, 2003 11:21:52 am by CraigBox Revert
@@ -44,9 +44,9 @@
 * Run the denoise tool. Its suggested to use any lead-in you can, but I only lead-out noise available. It seemed to do just as well. I ran it first with the defaults, then used the suggested settings on the url above. It seemed about the same really, although with the speakers I have on this computer it is hard to tell. 
  
 At this point, the tracks were a LOT cleaner and sounded great. 
  
-Unfortunately, Gramofile doesn't split the tracks out correctly any more. I figured I could run Gramofile over the unprocessed track and use its timing, or I could split the waves up manually. Gramofile did a fairly good job of picking the tracks out of the original waev file, although it needed some tweaking, and sometimes removed too much between songs. It writes out a filename.tracks file which you can edit, and in this case copy to a different name so that Gramofile will use on the processed wave file. 
+Unfortunately, Gramofile doesn't split the tracks out correctly any more. I figured I could run Gramofile over the unprocessed track and use its timing, or I could split the waves up manually. Gramofile did a fairly good job of picking the tracks out of the original wave file, although it needed some tweaking, and sometimes removed too much between songs. It writes out a filename.tracks file which you can edit, and in this case copy to a different name so that Gramofile will use on the processed wave file. 
  
 By this time I have a directory with 12 .wavs, named side1-1.wav to side1-6.wav and side2-1.wav to side2-6.wav. Nearly there! 
  
 A bit more reading and I found that cdrdao should let me write Audio cds where cdrecord failed earlier. It was worth a shot, so I decided to try it. I previously found another page describing the use of gramofile and audacity to clean up vinyl recordings, which suggested using cdrdao and a .toc file to write the audio tracks. Based on the notes at this page: http://www.togaware.com/linux/survivor/Recommended_Recording.html , the following shell script built a nice .toc file for me: 
@@ -65,4 +65,27 @@
  
  cdrdao write --speed 16 --device generic-mmc cd.toc 
  
 This time the write succeeded, although upon a visual inspection of the CD afterwards it seemed as though the disk was not written to, and it wouldn't play in either the computer or the stereo. Back to the drawing board. 
+  
+I burnt a CD in Nero, but had the same problem as with the very first copy I made - or a similar problem anyway. The music started off alright, but very quickly got very noisy, despite sounding OK on the computer.  
+  
+!! Third Attempt  
+  
+After a bit of thought, I realised one thing I might have been doing wrong. The GWC amplify tool didn't seem to work particularly well, and when it did work I think I was using it wrong. It puts up a prompt with 5 entry boxes - Left Channel Stard, End, Right Channel Start, End, and Feather Width (set to 2000, I left it). It stated the the maximum gain without clipping for this track was 25.something, which was a figure I'd seen elsewhere. So I set the 'End' values to 25. Which, in hindsight, probably meant an increasing amplification as the wave progressed, and which would have accounted for the increased noise further on in the CD and the poor noise correction performance - I doubt it can handle fixing an increasing noise source.  
+  
+So this time, I used DartPro (couldn't be assed finding another tool to do this, in case it wasn't the problem after all) to increase the gain, and then ran my declick/decrackle/denoise routine over this file. The waveform looked a lot better, and it sounded fine.  
+  
+I also discovered that GWC will mark track boundaries just as well as gramofile will, and will export a .toc file for me too. Better and better. I processed both sides, merged the two .toc files (the .toc format allows you to specify a filename and a start/end offset into the file, so you dont actually need to split the original file up :)  
+  
+  
+Console output from GWC giving some timing information:  
+ 6638 clicks repaired, 0 clicks marked, but remain unrepaired  
+ DECLICK in 65.811 real seconds  
+ 224 clicks repaired, 0 clicks marked, but remain unrepaired  
+ DECLICK in 18.114 real seconds  
+ 24 clicks repaired, 0 clicks marked, but remain unrepaired  
+ DECLICK in 17.278 real seconds  
+ DENOISE in 141.310 real seconds  
+  
+This is on an Athlon 1800 XP+ with 512 MB of ram, running 2.6.0-test11 / gentoo, and with an 80 GB 7200 RPM 8 MB Cache Maxtor HDD.  
+DECRACKLE information wasn't given, but it didn't take overly long - less than DENOISE. Each step requires some undo information (if you let it), and in the case of DECLICK and DENOISE requires a full undo file - as long as your original .wav