![]() After you OK the ACX-Check Analysis, the RAM has to be unloaded, which could also stress the machine. ![]() Suffice to say on my Mac it pushes Audacity’s RAM use to 1.2 GB for a half hour 32-bit mono track and 1.5 GB for a half hour 32-bit stereo track. The problem is that ACX-Check writes the entire audio data in the selection to RAM (memory) because this is necessary to analzye it for the type of plugin it is (Nyquist).Īlso at least on Mac, ACX-Check seems to use more RAM than is warranted by the audio data, which we’ll have to look into. Given your question is nothing to with what that user is doing, the decision to start a new topic is easily made. Even if you actually were ripping vinyl with the exact same mixer as the user in that topic, it would be very difficult to deal with two people at once in the same topic. Is this the right place to post this issue, or should I start a new topic? I am on 2.1.2, but still on 10.11.2 because I haven’t got round to making space for the latest iteration of El Capitan. It was fine when I was doing 15 minute samples, but on clips of 30 minutes or more this problem consistently arises. Gale, I have an issue where the ACX Check Plugin causes Audacity (and sometimes the whole computer) to hang and become unresponsive, necessitating Force Quit or a forced shutdown. Most recent versions of Audacity on Mac have a few bugs for various reasons, but for purposes of recording you are probably best off using the latest 2.1.2 from. Also, you did not tell us your Audacity version (see the pink panel at the top of the page).
0 Comments
Leave a Reply. |