Audacity Forum

Probably the most user friendly way to mark "end of tracks", assuming that tracks to be processed contain non-silent audio, is to use an empty track. As long the plug-in is reset after running then it is quite easy to count the tracks, for example: ;type analyze ;info "Use Debug butto...

It's quite peculiar how the bursts of noise are so regular.
At what point did the noise appear? Was it in the original recording?

Sorry I don't use iTunes.
Help for iTunes is here: http://www.apple.com/support/itunes/

Could you post a short sample of the raw, unprocessed recording that includes a few seconds of noise only and a couple of seconds of your voice.
Please send the sample as a WAV file (1 MB maximum).
See here for how to attach files: http://forum.audacityteam.org/viewtopic ... 49&t=64936

If the voice sounds badly distorted, or if it is buried under a lot of noise then it is probably too far gone to be repaired.
If it is something else, please post a sample (http://forum.audacityteam.org/viewtopic ... 49&t=64936)

The recording is badly distorted due to the sound level being so high. Unfortunately the damage cannot be repaired.

PhotosGuy wrote:I was thinking about maybe something arranged around the S key.

The keyboard shortcuts can be customised in "preferences": http://manual.audacityteam.org/o/man/ke ... ences.html

The processed sound quality is not really affected by hardware. With slow hardware processing tracks just takes longer than with a fast machine, but the end result is identical. Hardware, drivers and hardware configuration can have a big effect on playback quality. Trying to play a lot of tracks on ...

it does NOT meet today's acceptable recording/playback criteria of quality.' Hence your enquiry about microphones. Did we say that virtually any mic pre-amp over $30 is likely to be much better than the one that is built into the computer? Even a cheap computer microphone is likely to give better r...

I've noticed that you have used (s-rest 0) for the first track. This doesn't work, It does exactly what I intended it to do - nothing. It returns a null sound. It's a little trick to quickly do nothing to a track without generating an error. It's much faster than returning "s". The trick ...