Usually this seemed to occur when trying to import an audio file, but there may have been other ways it could happen. There was an error which only occurred occasionally for a few users but had us mystified. We added extra diagnostic information to help us do that: These two important bugs that 3.0.0 users saw were hard for us to track down as we could not replicate them. 3.0.2 may only be a 'point' release, but we think it's one most people using 3.0.0 will want.Īfter 3.0.0 was launched a few users discovered a couple of mysterious bugs which we had not encountered in our extensive QA testing of alpha and Release Candidate builds.

Some of our bug-fixes are small changes in areas where the previous Audacity behaviour was not as we wanted. A mistake we made with Unicode prevented Audacity working in Korean and Japanese. Disappearing checkmarks in macOS Big Sur release turned out to be a Unicode issue, believed to be in Apple code, which we now work around in 3.0.2. One problem we tracked during 3.0.0 turned out to be a Windows update issue with Unicode input, which was resolved by a later Windows update. We, Microsoft and Apple all have made mistakes with Unicode that affected Audacity 3.0.0. Unicode is a system for representing many non-English letters and symbols. One cluster of bugs we fixed relate to Unicode. So we added more informative diagnostics for when there is an error.

We wanted to fix these and also to get more diagnostic information about what goes wrong when SQLite (the database we use) can't read or write a file. Some bugs which didn't show up in our testing of 3.0.0 became apparent once 3.0.0 was being used by more users. Audacity 3.0.2 is about bugfixes for Audacity 3.0.0.

Audacity help manual