Search found 59476 matches
- Thu Jan 15, 2009 4:57 pm
- Forum: Windows
- Topic: Delay in recording
- Replies: 8
- Views: 1301
Re: Delay in recording
My 500MHz Pentium III manages at least 6 or 7 tracks. My 3GHz Pentium IV can handle well over 20 tracks - I've never had enough tracks going for it to start struggling at all. If you have a modern computer and it is choking on just 5 tracks, then you should look in the "Tips" (see link at ...
- Wed Jan 14, 2009 11:00 pm
- Forum: Windows
- Topic: distorted recording
- Replies: 1
- Views: 203
Re: distorted recording
Possibly, possibly not.
Could you describe your setup so that we have a clear mental picture of exactly what you are doing.
Uploading a short sample of the recording somewhere on the internet and posting a link might also help.
Could you describe your setup so that we have a clear mental picture of exactly what you are doing.
Uploading a short sample of the recording somewhere on the internet and posting a link might also help.
- Wed Jan 14, 2009 10:57 pm
- Forum: General Feedback and Discussion
- Topic: Selection Tool Trouble
- Replies: 2
- Views: 1744
- Wed Jan 14, 2009 10:49 pm
- Forum: Recording Techniques
- Topic: Recording over loop
- Replies: 1
- Views: 3257
Re: Recording over loop
select the audio that you want to repeat, then select "Repeat" from the effects menu and enter the number of times that you want it to repeat. To hear other tracks while recording a new one, go to preferences (from Edit menu) and in the Audio I/O tab select "play other tracks while re...
- Wed Jan 14, 2009 8:52 pm
- Forum: Recording Techniques
- Topic: How to fix small sections in recording (record over)
- Replies: 3
- Views: 717
Re: How to fix small sections in recording (record over)
Use Audacity 1.3.6
Select the desired area before you press record.
Select the desired area before you press record.
- Wed Jan 14, 2009 8:51 pm
- Forum: Windows
- Topic: LAME ENCODER ON A NETWORK
- Replies: 1
- Views: 241
Re: LAME ENCODER ON A NETWORK
Try putting Lame in the Audacity program directory on each computer.
- Wed Jan 14, 2009 8:29 pm
- Forum: Recording Techniques
- Topic: Recording set up advice
- Replies: 6
- Views: 1093
Re: Recording set up advice
If you are happy with mono recording you will not need anything special - most sound cards will do the job (but probably not on-board sound cards as they are usually rubbish quality. I use a Behringer UCA 202 with a mixing desk to record the main output and it works great (and only around $30). Most...
- Wed Jan 14, 2009 8:10 pm
- Forum: Mac OS X
- Topic: part of Audacity menu bar not highlighted & accessible
- Replies: 2
- Views: 490
Re: part of Audacity menu bar not highlighted & accessible
To access the effects and analyse menus you must have some audio selected (click and drag your mouse across a track). The help file is not included in Audacity 1.2, but is available on line here: http://audacityteam.org/help/documentation There is also a lot of additional information in the Audacity...
- Wed Jan 14, 2009 8:06 pm
- Forum: Recording Techniques
- Topic: How to fix small sections in recording (record over)
- Replies: 3
- Views: 717
Re: How to fix small sections in recording (record over)
Start recording a good time before the section that you want to correct - it will record onto a new track.
Stop the recording after you have gone past the part that needs correcting.
Cut or cross-fade from the original track to the newly recorded track and back to the original track.
Stop the recording after you have gone past the part that needs correcting.
Cut or cross-fade from the original track to the newly recorded track and back to the original track.
- Wed Jan 14, 2009 7:16 pm
- Forum: Compiling Audacity
- Topic: Problem compiling 1.3.6 and CVS
- Replies: 4
- Views: 2889
Re: Problem compiling 1.3.6 and CVS
I'm getting similar (but different) fatal compile errors on Ubuntu 8.10 when compiling from the 1.3.6 source Tarball. During the compile there was an error: *** Could not run GTK+ test program, checking why... *** The test program failed to compile or link. See the file config.log for the *** exact...