I imported a 5.1 file into the new version and downconverted it to stereo, which it did fine.
Then i did the standard ‘effects - dynamic range compression’ and after about 20 seconds it froze and returned to the previous state of the file.
I then exported the uncompressed stereo file to wav, also no problem.
Closed audacity, opened it up again, imported the stereo wav file and when i tried to compress it again the same thing happened; froze after a short while and than it undid the compression and went back to the file.
I’ve reinstalled 2.4.2 and the compression works fine on the big file there, so it’s not an issue of a full SSD drive or lack of memory i think.
WIndows 10 home edition, 8 gig ram memory, i7-4700MQ CPU @ 2.40 GHz.
It’s a little rough to get a plug-in or series of tools that does the same jobs as Chris. His design metaphor is unique. Can you split the job in two and do it in halves?
I do know of one problem Chris has. He uses uncontrolled look-ahead and doesn’t like running off the end of a sound file (Wile E. Coyote and the cliff). Do you intentionally put Unimportant Stuff on the ends of your show so he has something to chew on while he’s sorting it all out?
I used Chris for years and never caught on because I always did trimming after compressing. You can run into serious sound problems if you apply Chris as a last pass process with no trimming.
Haven’t run into any problems with this compressor before really, i mainly use it for compressing audio (no trimming) where dialog is inaudible vs the huge explosions in films and series. It works fine with older verions of Audacity. Hmmm…
Same problem here. 90min track and Chris’ compressor bombs out. Weirdly though, it also does this using default compressor too. Normalise and limiter were working but now both stop with no visible change to wav file.
Check that the track does not start before time=0.
There’s a bug that occurs in the built-in compressor when it is applied to audio that is in “negative time”.
For Nyquist plug-in effects, there’s a bug in Audacity 3.0.0 that causes them to silently fail on long tracks. In most cases (but not all cases) that is tracks longer than about 45 minutes. This has been fixed for the next version of Audacity (3.0.1) which is scheduled for release next month. The workaround for now is to process long tracks in sections.