Audacity Forum

Tip for the future: Once you have completed the recording, export that audio as a WAV file as a safety copy.

Tip2: do it in chunks of less than 15 hours (that's a lot for Audacity to chew on)

WC

DVDdoug is correct that you can't alter the level of the recorded signal when using WASAPI loopback - you need to use the sound-supplying app to control the signal level.

WC

Exactamundo

kozikowski wrote:High on everybody's wish list is the ability to make a WAV and cancel out all previous MP3 damage.

Maybe you could have one of those ready for the start of next month Koz ...

Let me ponder this ... But if we did this then the existing proposal for creating a zoom toolbar and adding commands would be redundant. I can see the benefit of your proposal here if we were to add more than the one or two extra zoom command buttons to the toolbar. Would you propose leaving the sin...

-1 on the basis of the extra clicks

See also: http://wiki.audacityteam.org/wiki/Propo ... om_Toolbar

Peter

What were the exact settings you used, if you don't mind my asking? *DeClick = 30 (default is 50) *Pitch Protection = "on" (default is "off") though leave this "off" for brass recordings *Reverse = "on" (there is no processing penalty for this and it helps on...

At this point I think we would need to make some design decisions. Does the user want to make unattended recording OR does the user want hands-on audio editing. Well this particular piece of functionality is Vaughan's baby (IIRC he was commissioned to write it) - and he always intended into be a ha...

So I just tried ClickRepair on the sample posted in this thread - worked well there too: See this sticky thread on ClickRepair: http://forum.audacityteam.org/viewtopic.php?f=28&t=1994

WC

steve wrote:Interestingly, the damage is rather similar to the damage that this user was getting: http://forum.audacityteam.org/viewtopic ... 69#p268269

I just ran the audio sample in that other thread through Brian Davies' ClickRepair and it fixed it up pretty well ...

WC