I am not able to reproduce the problem and I don’t know what causes it. No one would use Audacity if this was normal so I’m sure this is not everyone’s experience. The current version is available via the Audacity website: Audacity ® | Download for Windows The first thing I would suggest is updating to the current 2.3.3 version to see if the problem still exists. In a few cases, such as this one, if none of the regular forum contributors can reproduce the problem, and there is no record of a bug that can explain the problem, the post may remain without a reply for a couple of days (in case someone comes along that can provide an answer).Īudacity 2.0.3 is a very old version. The vast majority of posts receive replies within 24 hours, and most receive replies much quicker than that (which is better than many commercial products where you can be waiting weeks for a reply). Audacity should NOT be running this poorly.Īudacity is developed, documented and supported by volunteers. I also have a Core i7 and 16 GB of RAM with dedicated graphics. Glad I’m not the only one facing this issue. I’ve tried closing everything and only have Audacity running and it’s still unacceptably slow. I’m using 2.3.3 on a Windows 10 machine with a Core i7 processor and 8gb of RAM. Quite frequently, Audacity will show as “not responding” for up to a minute or two. Select 1 second of audio and hit delete? 2 or 3 seconds before a response. Moving the cursor involves a 3 to 5 second delay. Just mixing down a two-track 30-second commercial can take 2 minutes or more. There must be something wrong – this can’t be normal. Even if I only have two tracks – a voice track and a music track – even a 30-second commercial can be so incredibly slow that Audacity is not really an option for use. I mostly use Audacity to produce radio commercials. We also often run only Cakewalk and will disable Wi-fi during sessions since you don't want other programs and processes interrupting.I’m having the same problem. Of course if you have only one or two tracks, most processors (and memory) can keep up and you can get away with loading up the FX and a couple of instruments without turning things off during record. It's VST FX and instruments that introduce latency that the program has to adjust for. That's often a huge challenge for the program and processor and you will get delays during recording.īut with a decent buffer size for the project and track freezing, there shouldn't be any delays especially on audio tracks since they take so little effort from the processor. So turn off FX, lower the buffer size to something that doesn't start chopping up the sound, record, then turn it all back on and increase the buffer size if necessary.Īlso, if you have Input Echo on Auto Thru on an audio track, your asking the processor to go fast enough to process the signal in realtime. If your buffer is large, that too will introduce delays during recording on instruments/keyboards. In that case, we will freeze problem tracks to take the load off the CPU. If the processor is being asked to do too much (and the performance meters aren't a good measure of that) you will get stuttering, drop outs, distortion and other artifacts. Are you talking delays during record or playback? VST instruments or audio?ĭuring recording, delays can occur if the processor is being ask to do too much at the same time (which is why many of us turn off effects during record.) But playback should be fine.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |